On Tue, Jun 08, 2021 at 03:31:07PM -0500, Greg Hellings wrote: > Quick question about the Epoch tag in a spec file: I goofed during F34's > rawhide series and packaged an RC of my package with the wrong version name > (1.9.0RC3-1 instead of 1.9.0-0.1) which causes it to sort higher in > ordering than the final 1.9.0-5. From what I can gather, the proper > resolution for this is to add an Epoch tag to the SRPM file and build > 1:1.9.0-5. However, adding the epoch tag seems to have no effect. When I > try to build, I'm told version 1.9.0-5 is already built for Rawhide/Fedora > 34. > > Is there a way to claw back the improperly versioned 1.9.0RC3 package from > ages ago? Is there some magic to enable the Epoch tag that I'm missing? How > do I get 1.9.0 final package out into Fedora? This problem is because koji ignores the epoch when checking if a build version already exists and stores output in directories whose name does not contain the epoch. The solution is simply to *also* bump the release tag to '6'. This makes koji see it is as a new build and the epoch change makes the RPM upgrade path happy. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
