Mamoru TASAKA kirjoitti 29.4.2021 klo 8.55:
Greg Hellings wrote on 2021/04/29 14:46:
So I built my package a few times for F34 in the Rawhide cycle (e.g.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-90a4c6ba11)
It was rebuilt successfully by releng for F34 (e.g.
https://koji.fedoraproject.org/koji/buildinfo?buildID=1695213)
However, it does not appear in F34 in this version (1.9.0-3) but
instead in
a version from 2 months before my last build and 4 months before the
releng
build (1.9.0RC3-1 from last August). Neither do any of the newer builds
live in Rawhide.
What am I doing wrong that my package has happily built, but apparently
never made it into Rawhide or F34? Those later builds, up through
1.9.0-2,
are in F33. Is there some additional step that's new in the F34 cycle
that
I missed, that I need to do? I'm executing a rebuild of the package so I
can push it through Bodhi, but the previous versions also went through
there but never appeared on mirrors.
--Greg
I guess this is because "1.9.0RC3-1.fc34" is higher than "1.9.0-3.fc34"
with
rpm versioning.
$ rpmdev-vercmp "1.9.0RC3-1.fc34" "1.9.0-3.fc34"
1.9.0RC3-1.fc34 > 1.9.0-3.fc34
You should have used "1.9.0-0.1.RC3" or "1.9.0~RC3-1.fc34".
If you want to upgrade to "1.9.0", you have to use epoch, or
you can wait for 1.9.1 to be released?
Just a note, these schemes are documented in the packaging guidelines:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/
_______________________________________________
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
