#1805 tag java-1.5.0-gcj-1.5.0.0-28.fc11 to Fedora 11
Closed: Fixed None Opened 14 years ago by kasal.

please tag java-1.5.0-gcj-1.5.0.0-28.fc11 into dist-f11

This package escaped the Fedora 11 Mass Rebuild for various silly reasons.

The diff between the old *-25.fc11 and this 28.fc11 is exactly this:
1) javadoc-workaround patch: one line changed so that the patch applies
2) changed one BuildRequire so that mock initialisation does not fail because of bug #500314
In short, the source is effectively the same.

So the sources for the package are effectively the same. The package consists almost exclusively of symlinks, so the "recompilation" cannot contain bad "machine code".

Why is this important to include:

The previous build contained .i386.rpm instead of .i586.rpm, which can cause unpleasant surprises in certain situations. For example, "yum install java-devel" decides to install java-1.6.0-openjdk-devel on x86, in contrast to the fact that java-1.5.0-gcj-devel is selected on x86_64 and all other architectures. (And in contrast to the fact that java-1.5.0-gcj is selected by alternatives --auto as soon as both are installed on a system.)

In short, the problems caused by having the obsolete i386.rpm are rare, but hard to debug.
(I first noticed the issue in koji when the i586 build failed because openjdk was installed into the build tree instead of gcj.)

To sum up:
- if it won't get to F11, unpleasant suprises can waste people's time
- OTOH, the risk of the updated package is relatively small as the package should be the same as the previous one, see above and see the discussion on fedora-devel-java-list: http://thread.gmane.org/gmane.linux.redhat.fedora.java/3019/focus=3020


sane to me, but... any testing done against on this new build?

+1, tagging, moving, sending out a rescue party.

Metadata Update from @kasal:
- Issue set to the milestone: Fedora 11 Final

7 years ago

Login to comment on this ticket.

Metadata