Description of problem:
perl-Carp-1.26-242.fc18.noarch remains following fedup f18 --> f19 upgrade
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start with default F18 Gnome Desktop Install
2. Upgrade F18 to latest upgrades
3. install fedup-0.7.3-3.fc.noarch
4. run the fedup-cli --network 19 command to it is complete
5. boot f19 system and run yum update taking all approved updates
perl-Carp-1.26-242.fc18.noarch remains when rpm -qa | grep fc18 is run
perl-Carp-1.26-242.fc19.noarch should exist and be usable by fedup
I wrote this bug against perl-Carp as they are packaging 1.26-241.fc19 and need to provide a perl-Carp-1.26-242.fc19 package for the F19 release process. "passing the buck" to fedup when the package doesn't exist and entering no comment or reasoning SHOULD BE UNACCEPTABLE.
I don't understand who and why needs perl-Carp-1.26-242.fc19. Latest package is perl-Carp-1.26-241.fc19. Can you explain why we should increase the release number from 241 to 242?
perl-Carp-1.26-242.fc18 is latest for Fedora18 and if perl-Carp-1.26-241.fc19 is latest for Fedora19 then a compare of the two will find the 18 package newer the 19 package and not install the older package. if 1.26-241.fc18 is not the same as 1.26-241.fc19 asevidenced by the existence of 1.26-242.fc18 then we have a numbering issue.
I see. It's because F18 got perl updates after removing the perl-Carp sub-package from F19 and fedup does not do `yum distro-sync'.
I'll try to identify all such cases and remove them from F18 and increase releases of standalone packages to supersede them.
There is or can emerge NEVRA regression with these perl sub-packages between F18 and F19:
perl-Carp-1.26-243.fc19 has been submitted as an update for Fedora 19.
perl-Carp-1.26-243.fc18 has been submitted as an update for Fedora 18.
Petr: note that there is an autoqa test that checks this for you. It's called 'upgradepath'. When the upgradepath test fails on a build you do, it is warning you that you're getting into this situation (higher NEVR on an older release).
Discussed at 2013-05-01 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-01/f19beta-blocker-review-2.2013-05-01-16.01.log.txt . Upgrade path issues are not in and of themselves freeze exceptions; they're only a big problem if they cause problems with the upgrade. This kind of thing can always be fixed with a later update. Rejected as a freeze exception.
Looks like at least one more package needs bumping, perl-Digest:
Error: Package: perl-Digest-1.17-242.fc18.noarch (@updates/18)
Requires: perl = 4:5.16.3-242.fc18
Removing: 4:perl-5.16.3-242.fc18.x86_64 (@updates/18)
perl = 4:5.16.3-242.fc18
Updated By: 4:perl-5.16.3-262.fc19.x86_64 (fedora)
perl = 4:5.16.3-262.fc19
Thanks. AutoQA did not catch it <http://autoqa.fedoraproject.org/results/567725-autotest/virt06.qa/depcheck/results/perl-5.16.3-243.fc18.html>.
perl-Digest-1.17-244.fc19, perl-Carp-1.26-243.fc19, perl-ExtUtils-Manifest-1.61-243.fc19, perl-Version-Requirements-0.101022-243.fc19, perl-threads-1.86-243.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
perl-5.16.3-244.fc18, perl-Digest-1.17-244.fc18, perl-Carp-1.26-243.fc18, perl-ExtUtils-Manifest-1.61-243.fc18, perl-parent-0.225-243.fc18, perl-Test-Simple-0.98-243.fc18, perl-Version-Requirements-0.101022-243.fc18, perl-threads-1.86-243.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.