[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Qbittorrent depsolving problem



On Fri, 12 Jun 2009 12:56:22 -0430, Patrick wrote:

> On Fri, 2009-06-12 at 17:35 +0100, Frank Murphy wrote:
> > On 12/06/09 16:59, Patrick O'Callaghan wrote:
> > <snip>
> > 
> > >
> > > So it looks like there's a package missing in the repos. Does anyone
> > > have QBT working on a 64-bit F11 system?
> > >
> > > poc
> > >
> > 
> > Try
> > yum --enablerepo=updates-testing whatprovides */libtorrent-rasterbar.so.3
> 
> That did it, thanks.
> 
> Is there no automated check that any package in the standard repo has
> all its dependancies also in the standard repo? Seems like an obvious
> thing to have, unless I'm missing something.
> 
> poc
> 

No, there isn't. There is still only my own initiative where I run Fedora Extras
repoclosure for F-11 and F-10 everytime new updates are published. Then
packagers receive reports by email. Or I even submit additional comments
in the Fedora Updates System. However, it doesn't help with packagers
who either don't follow processes painstakingly or who miss email
notifications (such as in this case). The Updates System doesn't
protect the repos from packages that break dependencies. Finding them
isn't much of a deal. Avoiding them in an automated way (e.g. excluding
bad package sets automatically) would increase the time the updates compose
process runs.

In the case of qbittorrent, an ABI incompatible rb_libtorrent library
had been announced and tagged into the F-11 buildroot without
the packagers of dependencies missing it. The qbittorrent packager
has run into the trap by additionally marking an update stable
without testing it:
https://admin.fedoraproject.org/updates/F11/FEDORA-2009-4432
It has been quite troublesome to get that fixed.
https://admin.fedoraproject.org/updates/F11/FEDORA-2009-5703

I can only recommend interested users to frequent the Fedora Updates
System, evaluate Test Updates before they get marked "stable", and
keep an extra eye on any updates which skip updates-testing and target
the stable repo directly.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]