On Tue, Dec 3, 2013 at 12:20 PM, R P Herrold <[email protected]> wrote: > when moving from 6.4 to 6.5 (the recent update) > > I am seeing a 'hands-off' upgrade break due to neo4j being > (probably improperly) tied to a specific Java version > > Error: Package: neo4j-1.9-0.1.M05.orc6.noarch (installed) > Requires: java7 >= 1:1.7.0 > Removing: 1:java-1.7.0-openjdk-1.7.0.45-2.4.3.2.el6_4.x86_64 > (@updates) > java7 = 1:1.7.0 > Updated By: 1:java-1.7.0-openjdk-1.7.0.45-2.4.3.3.el6.x86_64 (base) > Not found > > [herrold@centos-6 6]$ find -name "neo4j*" > ./assimilation/neo4j-1.9-0.1.M05.orc6.src.rpm > ./assimilation/attic/neo4j-1.9-0.1.M05.fc18.src.rpm > ./assimilation/attic/neo4j-1.9-0.1.M05.orc6.src.rpm > [herrold@centos-6 6]$ pwd > /home/herrold/build/6 > [herrold@centos-6 6]$ > > so I pulled a neo4j froma recent Fedora and built it, and the > .spec file therein is probably Java NEVR locked as a hardcoded > dependency (a common Fedora packaging mistake to see -- > over-use of such) > > [herrold@centos-6 6]$ rpmno.sh > ./assimilation/neo4j-1.9-0.1.M05.orc6.src.rpm > info: extracted ~/rpmbuild/SPECS/neo4j.spec > next: edit neo4j.spec and then: > rpmbuild -ba neo4j.spec > -or-: > rph-rpmbuild -ba neo4j.spec > [herrold@centos-6 6]$ ls *spec > neo4j.spec > [herrold@centos-6 6]$ grep quires neo4j.spec > Requires: java7 >= 1:1.7.0 > Requires: jpackage-utils >= 0:1.7.3 > Requires: java >= 1:1.7.0 > Requires: jpackage-utils >= 0:1.7.3 > [herrold@centos-6 6]$ > > yuck ... and it is a huge update > > Total download size: 547 M > > ... investigating a fix > > -- Russ herrold
This exact thing bit us at Eucalyptus, too. It's a pretty big mistake to make in a point release, to break the world's java deps. The only real answer, aside from telling users to downgrade their Java version, is to reset all the build requirements. Frustrating. --g -- Greg DeKoenigsberg, Eucalyptus Build your own AWS-compatible cloud in 30 minutes: http://eucalyptus.com/faststart _______________________________________________ Assimilation mailing list - Discovery-Driven Monitoring [email protected] http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation http://assimmon.org/
