On Wed, Apr 29, 2020 at 02:06:06PM -0700, Michel Alexandre Salim wrote: > > > On 4/29/20 10:14 AM, Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > > > This is something that was asked a while ago and that we finally tackled. If a > > package is retired in Fedora, it will now be "disabled" in bugzilla, meaning no > > one can open new bugs against it. > > > > The script doing this ensures that the package is retired on all active branches > > before proceeding, so that if the package is retired on master and F32, the > > component remains enable in bugzilla for F31 (and F30). > > Thank you so much! I have a package in this state (0install): > - retired in master before F31 is branched > - no F31 and F32 branch > - still marked as active for F30 > > It seems that if I try and file a bug against 0install, I still get to pick > all of 30, 31, 32, and rawhide under Version. Is this expected? Unfortunately yes. Bugzilla can only disable a component for bugs, not specific versions of a component. > If this is a bug I can file a ticket. This is a bugbear -- the package has > "install" in the word and most of the bugs filed against it (and still being > filed) are misclassified from Anaconda. Well, when f30 goes eol it should be able to be closed right? kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
