#8847 Untag modules/tomcat stream stream-tomcat-201908 from fedora-modular-31 repo
Closed: Can't Fix 3 years ago by mohanboddu. Opened 4 years ago by csutherl.

  • Describe the issue

My in-development (not completed) module was released in F31, but it shouldn't have been.

$ dnf --repofrompath fedora-modular-31,https://dl.fedoraproject.org/pub/fedora/linux/development/31/Modular/x86_64/os --repo fedora-modular-31 module list 2>/dev/null | grep tomcat
tomcat               stream-tomcat-201908 default                                           Apache Servlet/JSP Engine, RI for Servlet 4.0/JSP 2.3 API

Can you please untag this module from the released repository and remove it from the distribution? By the time F32 is ready I should have the module development completed.

  • When do you need this? (YYYY/MM/DD)

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?

Users will continue to see a broken/unusable tomcat module in a stable Fedora release :(


Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

It looks like the module is back in fc31 somehow :( I've retired the branch, so not sure why it reappeared.

Metadata Update from @csutherl:
- Issue status updated to: Open (was: Closed)

4 years ago

Metadata Update from @mohanboddu:
- Issue assigned to mohanboddu

3 years ago

It looks like the module is back in fc31 somehow :( I've retired the branch, so not sure why it reappeared.

I guess I know why, the one that is in right now is part tagged into f32-modular which is not used for generating the repos anymore, we use f32-modular-updates tag for modular updates. So, the module build is shipped as part of F32 release and we cannot change it anymore.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Can't Fix
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata