====================================================================== The results in this summary consider Test Updates! ======================================================================
Summary of broken packages (by src.rpm name):
balsa blahtexml cobbler doodle easystroke edje fedora-release frepple fusecompress gnome-python2-desktop kst libguestfs libvirt-qpid linphone mail-notification matahari openscada ovaldi ovirt-server perl-Archive-RPM perl-Fedora-Bugzilla qpidc telepathy-feed zikula-module-menutree
====================================================================== Broken packages in fedora-13-development-i386:
1:libguestfs-1.0.84-1.fc13.i686 requires /lib/libdevmapper-event-lvm2snapshot.so.2.02 1:libguestfs-1.0.84-1.fc13.i686 requires /lib/libntfs-3g.so.73 1:libguestfs-1.0.84-1.fc13.i686 requires /lib/libdevmapper-event-lvm2mirror.so.2.02 1:libguestfs-1.0.84-1.fc13.i686 requires /lib/libntfs-3g.so.73.0.0 balsa-2.4.6-3.fc13.i686 requires libgmime-2.4.so.2 blahtexml-0.6-5.fc12.i686 requires libxerces-c.so.28 doodle-0.6.7-5.fc12.i686 requires libextractor.so.1 easystroke-0.5.2-1.fc13.i686 requires libboost_serialization-mt.so.5 edje-0.9.9.050-6.fc12.i686 requires libembryo.so.0 frepple-0.7.1-1.fc13.i686 requires libxerces-c.so.28 fusecompress-2.6-3.fc12.i686 requires libboost_iostreams-mt.so.5 fusecompress-2.6-3.fc12.i686 requires libboost_serialization-mt.so.5 fusecompress-2.6-3.fc12.i686 requires libboost_system-mt.so.5 fusecompress-2.6-3.fc12.i686 requires libboost_program_options-mt.so.5 fusecompress-2.6-3.fc12.i686 requires libboost_filesystem-mt.so.5 gnome-python2-totem-2.29.1-4.fc13.i686 requires libtotem-plparser.so.12 koan-2.0.3.1-1.fc13.noarch requires mkinitrd kst-fits-1.8.0-5.fc12.i686 requires cfitsio = 0:3.140 kst-netcdf-1.8.0-5.fc12.i686 requires libnetcdf_c++.so.4 kst-netcdf-1.8.0-5.fc12.i686 requires libnetcdf.so.4 libvirt-qpid-0.2.17-3.fc12.i686 requires qpidc >= 0:0.5.790661 linphone-2.1.1-4.fc12.i686 requires libortp.so.7 mail-notification-5.4-17.fc13.i686 requires libgmime-2.4.so.2 matahari-0.0.4-7.fc13.i686 requires qpidc >= 0:0.5.819819 openscada-demo-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibSYS = 0:0.6.4.1-8.fc13 openscada-demo-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibComplex1 = 0:0.6.4.1-8.fc13 openscada-demo-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibMath = 0:0.6.4.1-8.fc13 openscada-plc-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibSYS openscada-plc-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibComplex1 openscada-plc-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibMath openscada-server-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibSYS openscada-server-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibComplex1 openscada-server-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibMath openscada-visStation-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibSYS openscada-visStation-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibComplex1 openscada-visStation-0.6.4.1-8.fc13.i686 requires openscada-Special-FLibMath ovaldi-5.5.25-2.fc13.i686 requires libxerces-c.so.28 ovirt-server-0.100-4.fc12.noarch requires qpidd ovirt-server-0.100-4.fc12.noarch requires qpidc perl-Archive-RPM-0.05-1.fc13.noarch requires perl(MooseX::Types::DateTimeX) perl-Fedora-Bugzilla-0.13-2.fc13.noarch requires perl(MooseX::Types::DateTimeX) qmf-devel-0.5.819819-4.fc13.i686 requires qpidc-client-devel = 0:0.5.819819-4.fc13 qpidc-server-devel-0.5.819819-4.fc13.i686 requires qpidc-client-devel = 0:0.5.819819-4.fc13 qpidc-server-rdma-0.5.819819-4.fc13.i686 requires qpidc-client-rdma = 0:0.5.819819-4.fc13 qpidc-server-ssl-0.5.819819-4.fc13.i686 requires qpidc-client-ssl = 0:0.5.819819-4.fc13 telepathy-feed-0.13-7.fc12.i686 requires libtelepathy.so.2 zikula-module-menutree-2.2-1.fc13.noarch requires zikula >= 0:1.2
====================================================================== Broken packages in fedora-13-development-x86_64:
1:libguestfs-1.0.84-1.fc13.i686 requires /lib/libdevmapper-event-lvm2snapshot.so.2.02 1:libguestfs-1.0.84-1.fc13.i686 requires /lib/libntfs-3g.so.73 1:libguestfs-1.0.84-1.fc13.i686 requires /lib/libdevmapper-event-lvm2mirror.so.2.02 1:libguestfs-1.0.84-1.fc13.i686 requires /lib/libntfs-3g.so.73.0.0 1:libguestfs-1.0.84-1.fc13.x86_64 requires /lib64/libdevmapper-event-lvm2snapshot.so.2.02 1:libguestfs-1.0.84-1.fc13.x86_64 requires /lib64/libdevmapper-event-lvm2mirror.so.2.02 1:libguestfs-1.0.84-1.fc13.x86_64 requires /lib64/libntfs-3g.so.73 1:libguestfs-1.0.84-1.fc13.x86_64 requires /lib64/libntfs-3g.so.73.0.0 balsa-2.4.6-3.fc13.x86_64 requires libgmime-2.4.so.2()(64bit) blahtexml-0.6-5.fc12.x86_64 requires libxerces-c.so.28()(64bit) doodle-0.6.7-5.fc12.i686 requires libextractor.so.1 doodle-0.6.7-5.fc12.x86_64 requires libextractor.so.1()(64bit) easystroke-0.5.2-1.fc13.x86_64 requires libboost_serialization-mt.so.5()(64bit) edje-0.9.9.050-6.fc12.i686 requires libembryo.so.0 edje-0.9.9.050-6.fc12.x86_64 requires libembryo.so.0()(64bit) frepple-0.7.1-1.fc13.i686 requires libxerces-c.so.28 frepple-0.7.1-1.fc13.x86_64 requires libxerces-c.so.28()(64bit) fusecompress-2.6-3.fc12.x86_64 requires libboost_system-mt.so.5()(64bit) fusecompress-2.6-3.fc12.x86_64 requires libboost_program_options-mt.so.5()(64bit) fusecompress-2.6-3.fc12.x86_64 requires libboost_iostreams-mt.so.5()(64bit) fusecompress-2.6-3.fc12.x86_64 requires libboost_filesystem-mt.so.5()(64bit) fusecompress-2.6-3.fc12.x86_64 requires libboost_serialization-mt.so.5()(64bit) gnome-python2-totem-2.29.1-4.fc13.x86_64 requires libtotem-plparser.so.12()(64bit) koan-2.0.3.1-1.fc13.noarch requires mkinitrd kst-fits-1.8.0-5.fc12.x86_64 requires cfitsio = 0:3.140 kst-netcdf-1.8.0-5.fc12.x86_64 requires libnetcdf.so.4()(64bit) kst-netcdf-1.8.0-5.fc12.x86_64 requires libnetcdf_c++.so.4()(64bit) libvirt-qpid-0.2.17-3.fc12.x86_64 requires qpidc >= 0:0.5.790661 linphone-2.1.1-4.fc12.i686 requires libortp.so.7 linphone-2.1.1-4.fc12.x86_64 requires libortp.so.7()(64bit) mail-notification-5.4-17.fc13.x86_64 requires libgmime-2.4.so.2()(64bit) matahari-0.0.4-7.fc13.x86_64 requires qpidc >= 0:0.5.819819 openscada-demo-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibSYS = 0:0.6.4.1-8.fc13 openscada-demo-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibComplex1 = 0:0.6.4.1-8.fc13 openscada-demo-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibMath = 0:0.6.4.1-8.fc13 openscada-plc-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibSYS openscada-plc-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibComplex1 openscada-plc-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibMath openscada-server-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibSYS openscada-server-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibComplex1 openscada-server-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibMath openscada-visStation-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibSYS openscada-visStation-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibComplex1 openscada-visStation-0.6.4.1-8.fc13.x86_64 requires openscada-Special-FLibMath ovaldi-5.5.25-2.fc13.x86_64 requires libxerces-c.so.28()(64bit) ovirt-server-0.100-4.fc12.noarch requires qpidd ovirt-server-0.100-4.fc12.noarch requires qpidc perl-Archive-RPM-0.05-1.fc13.noarch requires perl(MooseX::Types::DateTimeX) perl-Fedora-Bugzilla-0.13-2.fc13.noarch requires perl(MooseX::Types::DateTimeX) qmf-devel-0.5.819819-4.fc13.i686 requires qpidc-client-devel = 0:0.5.819819-4.fc13 qmf-devel-0.5.819819-4.fc13.x86_64 requires qpidc-client-devel = 0:0.5.819819-4.fc13 qpidc-server-devel-0.5.819819-4.fc13.i686 requires qpidc-client-devel = 0:0.5.819819-4.fc13 qpidc-server-devel-0.5.819819-4.fc13.x86_64 requires qpidc-client-devel = 0:0.5.819819-4.fc13 qpidc-server-rdma-0.5.819819-4.fc13.x86_64 requires qpidc-client-rdma = 0:0.5.819819-4.fc13 qpidc-server-ssl-0.5.819819-4.fc13.x86_64 requires qpidc-client-ssl = 0:0.5.819819-4.fc13 telepathy-feed-0.13-7.fc12.x86_64 requires libtelepathy.so.2()(64bit) zikula-module-menutree-2.2-1.fc13.noarch requires zikula >= 0:1.2
====================================================================== Broken packages in fedora-updates-testing-13-i386:
fedora-release-rawhide-13-0.4.noarch requires fedora-release-13-0.4
====================================================================== Broken packages in fedora-updates-testing-13-x86_64:
fedora-release-rawhide-13-0.4.noarch requires fedora-release-13-0.4
On Fri, 2010-02-19 at 11:09 +0000, Michael Schwendt wrote:
fedora-release
This one is fixed by a later update request. Hopefully we'll get it published today.
Michael, would you be at all interested in modifying your script to automatically dump negative karma with the broken dep info into the update request?
On Fri, 19 Feb 2010 09:43:42 -0800, Jesse wrote:
On Fri, 2010-02-19 at 11:09 +0000, Michael Schwendt wrote:
fedora-releaseThis one is fixed by a later update request. Hopefully we'll get it published today.
Michael, would you be at all interested in modifying your script to automatically dump negative karma with the broken dep info into the update request?
No interest due to several reasons, at least:
* With repoclosure output, there is no mapping from "broken dep to bodhi ticket". Implementing such a mapping would not be trivial. And a different strategy of finding dep breakage would duplicate some of what Will Woods is working on.
* Negative karma on updates, which are marked stable already, is useless.
* Only the bodhi update submitter is notified about comments, afaik. That is less useful than mailing to the package-owner@... alias.
On Sat, Feb 20, 2010 at 13:25:00 +0100, Michael Schwendt mschwendt@gmail.com wrote:
- Only the bodhi update submitter is notified about comments, afaik.
That is less useful than mailing to the package-owner@... alias.
My experience is that once you submit a comment about an update, you get copied on further comments for that same update. I don't think that helps in the context of this thread, but I didn't want people getting what appears to be incorrect information on how bodhi comments work.
On Sat, 20 Feb 2010 09:20:34 -0600, Bruno wrote:
- Only the bodhi update submitter is notified about comments, afaik.
That is less useful than mailing to the package-owner@... alias.
My experience is that once you submit a comment about an update, you get copied on further comments for that same update. I don't think that helps in the context of this thread, but I didn't want people getting what appears to be incorrect information on how bodhi comments work.
True. I could have phrased it better. Everyone who leaves a comment in a bodhi ticket is subscribed to it and receives notifications for subsequent comments/activities in that ticket. [That generates quite a lot of "spam" when many people leave comments.] Initially, though, only the submitter of the update receives a first comment, and not the full team of pkg co-maintainers.
On Sat, 2010-02-20 at 13:25 +0100, Michael Schwendt wrote:
No interest due to several reasons, at least:
- With repoclosure output, there is no mapping from "broken dep to bodhi
ticket". Implementing such a mapping would not be trivial. And a different strategy of finding dep breakage would duplicate some of what Will Woods is working on.
Hrm, I hadn't thought about multipackage updates, but single package updates can just be referenced by srpm n-v-r, eg:
$ bodhi -k +1 --comment "Installed and X still works" xorg-x11-server-1.7.99.901-5.20100215.fc13
- Negative karma on updates, which are marked stable already, is useless.
True, I'm mostly concerned about things in testing, and double concerned about things in 13-testing.
- Only the bodhi update submitter is notified about comments, afaik.
That is less useful than mailing to the package-owner@... alias.
In one aspect yes it is less useful. In another aspect it is very useful, as we are using karma on critical packages as a barrier to entry into stable. Automatically adding negative karma due to broken deps helps prevent such breakage from hitting the branched 13 repo.
If there is no interest, that's fine, I can try to work something up myself, maybe even a script to take your email and do something with it.
Thanks again for providing this information!
On Sat, 20 Feb 2010 08:24:52 -0800, Jesse wrote:
- With repoclosure output, there is no mapping from "broken dep to bodhi
ticket". Implementing such a mapping would not be trivial. And a different strategy of finding dep breakage would duplicate some of what Will Woods is working on.
Hrm, I hadn't thought about multipackage updates, but single package updates can just be referenced by srpm n-v-r, eg:
$ bodhi -k +1 --comment "Installed and X still works" xorg-x11-server-1.7.99.901-5.20100215.fc13
Guess what Extras repoclosure (= the forked repoclosure from Fedora Extras era) does. It prints the src.rpm (and the "related" library packages like mash does it) already, but this is insufficient for submitting automated bodhi comments.
The package that suffers from unresolvable dependencies is not always the update that breaks something. For the most common form of dep breakage it is necessary to find the culprit. [That can be anything from a SONAME change to a missing/bad Obsoletes or a forgotton rebuild.]
-
Bruno Wolff III -
Jesse Keating -
Michael Schwendt