Re: btdownload errors (FC4 isos)

Phil Schaffner <[email protected]>
Newsgroups gmane.linux.freshrpms.user
Organization NASA Langley Research Center
Message-ID <[email protected]>
On Sun, 2005-06-19 at 12:35 +0200, Dag Wieers wrote: 
> On Sat, 18 Jun 2005, Phil Schaffner wrote:
> 
... 

Hope this thread is not too stale.  Had substantial interruptions with
ISP outages, and building FC3 evolution on CentOS4 after getting fed up
with apparent memory-leak problems that seem to have been fixed in later
versions - but that's OT here.

> > > Moral of the story - upgrade is in order.
> > 
> > Just ran updates on home machine after installing BitTorrent-4.1.2-1
> > earlier today.  Dag bittorrent-4.1.1-2.1.fc3.rf wants to obsolete it
> > even though the other version is higher:
> > 
> > # yum update
> > ...
> > Dependencies Resolved
> > Transaction Listing:
> >   Install: bittorrent.noarch 0:4.1.1-1.1.fc3.rf - dag
> >   Update: bzip2.i386 0:1.0.2-13.FC3.1 - updates-released
> >   Update: bzip2-devel.i386 0:1.0.2-13.FC3.1 - updates-released
> >   Update: bzip2-libs.i386 0:1.0.2-13.FC3.1 - updates-released
> >   Update: checkpolicy.i386 0:1.17.5-1.2 - updates-released
> >   Update: gzip.i386 0:1.3.3-14.fc3 - updates-released
> >   Update: selinux-policy-targeted.noarch 0:1.17.30-3.9 - updates-released
> >   Update: spamassassin.i386 0:3.0.4-1.fc3 - updates-released
> >   Update: util-linux.i386 0:2.12a-24.3 - updates-released
> > 
> > Performing the following to resolve dependencies:
> >   Install: python-khashmir.noarch 0:4.1.1-2.1.fc3.rf - dag
> > 
> > Other Transactions:
> >   Obsoleting: BitTorrent.noarch 0:4.1.2-1 with bittorrent.noarch 0:4.1.1-1.1.fc3.rf
> > 
> > Total download size: 2.8 M
> > Is this ok [y/N]: n
> > Exiting on user Command
> > Complete!
> > #
> > 
> > Disabled Dag repo for now. :-(
> 
> Or uninstall python-khashmir. 

But I had already un-installed python-khashmir to avoid conflicts with
(Beta) BitTorrent-4.1.2-1.  bittorrent-4.1.1-2.1.fc3.rf causes yum to
pull it in as a dependency, as well as obsoleting BitTorrent-4.1.2-1.

> The bittorrent people made it themselves easier by providing python-
> khashmir inside the bittorrent package. Which is nice for the users
> that download it from the website, as they only have to download 1
> file.
> 
> But that's not very good packaging, as no other package can depend on 
> python-khashmir.

Agree that it would be better to package separately if other packages
need python-khashmir.  On my home system, with loads of add-on stuff
from rpmforge and friends installed, nothing else needs it.

Still think obsoleting a newer version of a package is a questionable
practice, especially when the older version is broken (yeah, hindsight
is 20:20 :-).  Hope you can update your repo to a well-packaged
bittorrent-4.1.x, presumably after it gets out of Beta.  Meanwhile, sure
would be nice if the working version were not obsoleted.

Don't mean to be unduly complaining, and am probably guilty of looking
the proverbial gift horse in the mouth, but just want to give clear
feedback on problems encountered.  All your hard work and service to the
community is certainly appreciated.  Hope the new-world journey is going
(has gone) well.

Phil
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.