Summary of broken packages (by owner):
berrange AT redhat.com perl-Test-AutoBuild-darcs-1.2.2-3.fc9.noarch
ebmunson AT us.ibm.com libhugetlbfs-test-1.1-6.fc9.ppc libhugetlbfs-test-1.1-6.fc9.ppc64 libhugetlbfs-test-1.1-6.fc9.x86_64 lsvpd-1.6.4-1.fc9.i386 lsvpd-1.6.4-1.fc9.ppc lsvpd-1.6.4-1.fc9.ppc64 lsvpd-1.6.4-1.fc9.x86_64
karlthered AT gmail.com gtkmozembedmm-1.4.2.cvs20060817-20.fc9.i386 gtkmozembedmm-1.4.2.cvs20060817-20.fc9.ppc gtkmozembedmm-1.4.2.cvs20060817-20.fc9.ppc64 gtkmozembedmm-1.4.2.cvs20060817-20.fc9.x86_64
katzj AT redhat.com livecd-tools-017.1-1.fc9.ppc64
lxtnow AT gmail.com gspiceui-0.9.65-2.fc9.ppc64
oliver AT linux-kernel.at syck-php-0.61-4.3.fc9.i386 syck-php-0.61-4.3.fc9.ppc syck-php-0.61-4.3.fc9.ppc64 syck-php-0.61-4.3.fc9.x86_64
orion AT cora.nwra.com paraview-3.2.1-6.fc9.i386 paraview-mpi-3.2.1-6.fc9.i386
than AT redhat.com 1:qt-sqlite-4.3.5-2.fc9.i386 1:qt-sqlite-4.3.5-2.fc9.ppc 1:qt-sqlite-4.3.5-2.fc9.ppc64 1:qt-sqlite-4.3.5-2.fc9.x86_64
wart AT kobold.org cyphesis-selinux-0.5.15-6.fc9.i386 cyphesis-selinux-0.5.15-6.fc9.ppc cyphesis-selinux-0.5.15-6.fc9.ppc64 cyphesis-selinux-0.5.15-6.fc9.x86_64
====================================================================== Broken packages in fedora-9-i686:
cyphesis-selinux-0.5.15-6.fc9.i386 requires cyphesis = 0:0.5.15-6.fc9 syck-php-0.61-4.3.fc9.i386 requires php = 0:5.2.5
====================================================================== Broken packages in fedora-9-ppc64:
cyphesis-selinux-0.5.15-6.fc9.ppc64 requires cyphesis = 0:0.5.15-6.fc9 libhugetlbfs-test-1.1-6.fc9.ppc64 requires libhugetlbfs = 0:1.1-6.fc9 perl-Test-AutoBuild-darcs-1.2.2-3.fc9.noarch requires darcs >= 0:1.0.0 syck-php-0.61-4.3.fc9.ppc64 requires php = 0:5.2.5
====================================================================== Broken packages in fedora-9-ppc:
cyphesis-selinux-0.5.15-6.fc9.ppc requires cyphesis = 0:0.5.15-6.fc9 libhugetlbfs-test-1.1-6.fc9.ppc requires libhugetlbfs = 0:1.1-6.fc9 syck-php-0.61-4.3.fc9.ppc requires php = 0:5.2.5
====================================================================== Broken packages in fedora-9-x86_64:
cyphesis-selinux-0.5.15-6.fc9.x86_64 requires cyphesis = 0:0.5.15-6.fc9 libhugetlbfs-test-1.1-6.fc9.x86_64 requires libhugetlbfs = 0:1.1-6.fc9 paraview-3.2.1-6.fc9.i386 requires paraview-data = 0:3.2.1-6.fc9 paraview-mpi-3.2.1-6.fc9.i386 requires paraview-data = 0:3.2.1-6.fc9 syck-php-0.61-4.3.fc9.x86_64 requires php = 0:5.2.5
====================================================================== Broken packages in fedora-updates-9-i686:
1:qt-sqlite-4.3.5-2.fc9.i386 requires qt = 1:4.3.5-2.fc9 gtkmozembedmm-1.4.2.cvs20060817-20.fc9.i386 requires gecko-libs = 0:1.9 lsvpd-1.6.4-1.fc9.i386 requires libvpd_cxx-2.0.so.1
====================================================================== Broken packages in fedora-updates-9-ppc:
1:qt-sqlite-4.3.5-2.fc9.ppc requires qt = 1:4.3.5-2.fc9
====================================================================== Broken packages in fedora-updates-9-ppc64:
1:qt-sqlite-4.3.5-2.fc9.ppc64 requires qt = 1:4.3.5-2.fc9 gspiceui-0.9.65-2.fc9.ppc64 requires gwave gtkmozembedmm-1.4.2.cvs20060817-20.fc9.ppc64 requires gecko-libs = 0:1.9 livecd-tools-017.1-1.fc9.ppc64 requires yaboot lsvpd-1.6.4-1.fc9.ppc64 requires libvpd_cxx-2.0.so.1()(64bit)
====================================================================== Broken packages in fedora-updates-9-ppc:
gtkmozembedmm-1.4.2.cvs20060817-20.fc9.ppc requires gecko-libs = 0:1.9 lsvpd-1.6.4-1.fc9.ppc requires libvpd_cxx-2.0.so.1
====================================================================== Broken packages in fedora-updates-9-x86_64:
1:qt-sqlite-4.3.5-2.fc9.x86_64 requires qt = 1:4.3.5-2.fc9 gtkmozembedmm-1.4.2.cvs20060817-20.fc9.i386 requires gecko-libs = 0:1.9 gtkmozembedmm-1.4.2.cvs20060817-20.fc9.x86_64 requires gecko-libs = 0:1.9 lsvpd-1.6.4-1.fc9.x86_64 requires libvpd_cxx-2.0.so.1()(64bit)
On Fri, Aug 8, 2008 at 9:00 AM, Michael Schwendt mschwendt@gmail.comwrote:
Summary of broken packages (by owner):
berrange AT redhat.com perl-Test-AutoBuild-darcs-1.2.2-3.fc9.noarch
ebmunson AT us.ibm.com libhugetlbfs-test-1.1-6.fc9.ppc libhugetlbfs-test-1.1-6.fc9.ppc64 libhugetlbfs-test-1.1-6.fc9.x86_64 lsvpd-1.6.4-1.fc9.i386 lsvpd-1.6.4-1.fc9.ppc lsvpd-1.6.4-1.fc9.ppc64 lsvpd-1.6.4-1.fc9.x86_64
karlthered AT gmail.com gtkmozembedmm-1.4.2.cvs20060817-20.fc9.i386 gtkmozembedmm-1.4.2.cvs20060817-20.fc9.ppc gtkmozembedmm-1.4.2.cvs20060817-20.fc9.ppc64 gtkmozembedmm-1.4.2.cvs20060817-20.fc9.x86_64
katzj AT redhat.com livecd-tools-017.1-1.fc9.ppc64
lxtnow AT gmail.com gspiceui-0.9.65-2.fc9.ppc64
This one has already been fixed in release *-3.fc9
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael Schwendt wrote: | Summary of broken packages (by owner): | | ebmunson AT us.ibm.com | lsvpd-1.6.4-1.fc9.i386 | lsvpd-1.6.4-1.fc9.ppc | lsvpd-1.6.4-1.fc9.ppc64 | lsvpd-1.6.4-1.fc9.x86_64 |
These are caused by a bug I reported about a month and a half ago, libvpd's library numbers got bumped down in the 2.0.2 release. https://bugzilla.redhat.com/show_bug.cgi?id=452851
There's been no action on it since then; I'm not sure whether it should be against lsvpd, which would just need a rebuild with the new library number, or to get libvpd's library number back where it was (assuming it's binary compatible).
- -- J. Randall Owens | http://www.ghiapet.net/ ProofReading Markup Language | http://prml.sourceforge.net/
On Fri, 08 Aug 2008 04:16:28 -0700, J. Randall Owens wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Michael Schwendt wrote: | Summary of broken packages (by owner): | | ebmunson AT us.ibm.com | lsvpd-1.6.4-1.fc9.i386 | lsvpd-1.6.4-1.fc9.ppc | lsvpd-1.6.4-1.fc9.ppc64 | lsvpd-1.6.4-1.fc9.x86_64 |
These are caused by a bug I reported about a month and a half ago, libvpd's library numbers got bumped down in the 2.0.2 release. https://bugzilla.redhat.com/show_bug.cgi?id=452851
There's been no action on it since then;
The corresponding update in bodhi was this: https://admin.fedoraproject.org/updates/F9/FEDORA-2008-4187
Effectively, this soname problem has been reported in two places.
I'm not sure whether it should be against lsvpd, which would just need a rebuild with the new library number, or to get libvpd's library number back where it was (assuming it's binary compatible).
libvpd 2.0.0 had major version 0, libvpd 2.0.1 bumped to major version 1, then they reverted that in 2.0.2. Meanwhile 2.0.3 is available and stays at major version 0.