Re: Fedora rawhide compose report: 20200802.n.0 changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2020-08-02 at 11:27 -0700, Kevin Fenzi wrote:
> On Sun, Aug 02, 2020 at 12:55:28PM +0000, Fedora Rawhide Report wrote:
> > OLD: Fedora-Rawhide-20200731.n.0
> > NEW: Fedora-Rawhide-20200802.n.0
> > 
> > ===== SUMMARY =====
> > Added images:        4
> > Dropped images:      5
> > Added packages:      11
> > Dropped packages:    6
> > Upgraded packages:   18240
> > Downgraded packages: 41
> 
> I ran the releng check-latest-build script to fix these 41 downgrades: 

Just went through these. Most were correct - the apparently-newer build
really was newer - but some were not, due to errors in package
versioning (the 'newer' build is actually an older build with a
problematic version). CCing the recent builders of all affected
packages to take appropriate action. Packagers, please refresh your
memory on
https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning
and https://fedoraproject.org/wiki/Package_Versioning_Examples ,
particularly regarding correct versioning of pre-release builds. When
correcting a package's versioning to meet the guidelines, please
remember to check if the corrected version parses as older, and if so
either bump the Epoch or do something else (e.g. cut an upstream
release, if you can) to fix that. I've put "FAO <FAS name>" at the
start of each item so you can just search for your FAS name to find the
package that I'm CCing you for.

>         ansible-lint-4.2.0-5.fc33 < ansible-lint-4.2.0a1-2.fc32
> retagged ansible-lint-4.2.0a1-2.fc32 to f33     

FAO pnemade: This is clearly a package versioning error, the Alpha
build should've been versioned 4.2.0-0.2.alpha1 or so. Will need a
4.2.1 or an epoch bump to fix unfortunately.

>         fpdns-0.10.0-4.20190131.fc33 < fpdns-0.10.0-20190131.fc31.2
> retagged fpdns-0.10.0-20190131.fc31.2 to f33                                                                        

FAO mmckinst, jplesnik: Also looks like a versioning error. The fc31.2
build is basically entirely missing the 'normal' release component.
Mark fixed the versioning in fpdns-0.10.0-1.20190131.fc32 , but did not
bump the epoch, so the new builds are lower versioned than the older
ones. Again needs an epoch bump or a new version (or a *really* big
release tag...) to fix properly.

>         git-lab-porcelain-0-2020325git75a12220.fc33.2 < git-lab-porcelain-0-20200123git4eeaa725.fc32.1
> retagged git-lab-porcelain-0-20200123git4eeaa725.fc32.1 to f33    

FAO nhorman: More date fun! This looks like a 0 typo: the newer build
has '2020325' instead of '20200325' (I do this one myself all the damn
time, sigh). Fixing that typo would make things work, though the
versioning is still violating the guidelines by not having a 0.x
release number between the (notional) version and the snapshot date.
Fixing that would require bumping either the notional version or the
epoch, though, and it likely won't ever cause a real problem unless
there's ever an actual stable release versioned '0'.
>  
>         golang-github-acobaugh-osrelease-0-3.20200607gita93a0a5.fc33 < golang-github-acobaugh-osrelease-0.0.0-1.2020
> 0607gita93a0a5.fc33                                                                                                 

FAO eclipseo, harrymichal: This looks like rpm considers 0.0.0 to be
higher than 0. Interesting. Needs a version higher than 0.0.0 or an
epoch bump.

>         icedtea-web-2.0.0-pre.0.3.alpha13.patched1.fc33.5 < icedtea-web-2.0.0-pre.2.alpha13.patched1.fc33
> retagged icedtea-web-2.0.0-pre.2.alpha13.patched1.fc33 to f33

FAO jvanek: you made the versioning more correct between icedtea-web-
2.0.0-pre.2.alpha13.patched1.fc33 and icedtea-web-2.0.0-
pre.0.2.alpha13.patched1.fc33 , but 'pre.0.2' (and 'pre.0.3' and
'pre.0.anything') parses as lower than 'pre.2', so this needed an epoch
bump to work right. (I think the 'pre' could also be left out as it
isn't doing anything useful, but IMBW there).

>         pveclib-1.0.4-4.fc33 < pveclib-1.0.4alpha2-3.fc33
> retagged pveclib-1.0.4alpha2-3.fc33 to f33

FAO munroesj52: this is a pre-release naming fail - '1.0.4alpha2'
parses as higher than '1.0.4' to rpm. Needs an epoch bump or a 1.0.5
release. Older build should have been versioned 'pveclib-1.0.4-
0.1.alpha2' or so, please bear that in mind for future pre-releases.

>         salt-3001-2.fc33 < salt-3001rc1-2.fc33
> retagged salt-3001rc1-2.fc33 to f33

FAO dmurphy18 (SaltStack Packaging Team): same as pveclib - '3001rc1'
parses as higher than '3001'. Needs epoch bump or release above 3001.
Older build should have been salt-3001-0.2.rc1. Also your email address
is wrong in the package changelog, it has .com.com not just .com. :)
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux