Description of problem:
Using preupgrade on a fully updated version of F-12 to F-13 and then running
package-cleanup --orphans lists java-1.6.0-openjdk and java-1.6.0-openjdk-plugin as being orphaned. The reason is that the F12 version has a greater nvr than the F13 version - see below. Please push updated packages for F13.
# yum downgrade java-1.6.0-openjdk java-1.6.0-openjdk-plugin
Loaded plugins: presto, refresh-packagekit
Setting up Downgrade Process
--> Running transaction check
---> Package java-1.6.0-openjdk.x86_64 1:184.108.40.206-37.b17.fc13 set to be updated
---> Package java-1.6.0-openjdk.x86_64 1:220.127.116.11-38.b18.fc12 set to be erased
---> Package java-1.6.0-openjdk-plugin.x86_64 1:18.104.22.168-37.b17.fc13 set to be updated
---> Package java-1.6.0-openjdk-plugin.x86_64 1:22.214.171.124-38.b18.fc12 set to be erased
--> Finished Dependency Resolution
Package Arch Version Repository
java-1.6.0-openjdk x86_64 1:126.96.36.199-37.b17.fc13 fedora 25 M
java-1.6.0-openjdk-plugin x86_64 1:188.8.131.52-37.b17.fc13 fedora 101 k
Remove 0 Package(s)
Reinstall 0 Package(s)
Downgrade 2 Package(s)
Total download size: 25 M
Is this ok [y/N]:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
No, DON'T push this for F13. The higher-numbered versions in F11 and F12 are broken (100% CPU for any java applets).
I should have said, don't push the currently broken F11/F12 version - of course they should be fixed, then pushed.
That's not what I was asking.
The point is the nvr in F13 needs ALWAYS to be equal or greater than that in F12 (and F11). No exceptions.
> The point is the nvr in F13 needs ALWAYS to be equal or greater than that in
> F12 (and F11). No exceptions.
True, and the nvr in Rawhide should always be >= F13. Unfortunately, the maintainer for some reason pushed to F11 and F12 before pushing to either pre-release F13 or Rawhide.
Would doing this:
Push new builds of the b17 version to F11, F12, F13, bumping the epoch and ensuring that nvr(F11) <= nvr(F12) <= nvr(F13).
break anything? If not, that's probably the way to go until the b18 version is fixed properly.
I guess it depends on how long it takes to fix - if it's quick, the fixed version could be pushed to F13 and Rawhide first without bumping the epoch. There hasn't been any word from the maintainer yet so it's hard to say.
FYI, there's work on a new AutoQA test to prevent this sort of thing from happening again:
java-1.6.0-openjdk-184.108.40.206-39.b18.fc13 has been submitted as an update for Fedora 13.
java-1.6.0-openjdk-220.127.116.11-39.b18.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
This can be closed as CURRENTRELEASE now. (Too bad nothing got fixed.) Since the maintainer doesn't seem to be aware of these bug's existence (or negative karma), you'll have to do it.