Re: why does yumdownloader grab i586 package on an x86_64 system?

"Robert P. J. Day" <[email protected]>
Newsgroups gmane.linux.rpm.yum
Message-ID <[email protected]>
On Wed, 13 May 2009, James Antill wrote:

> "Robert P. J. Day" <[email protected]> writes:
>
> >   i wanted to download all binary rpms related to asterisk, so i ran:
> >
> > $ yumdownloader --resolve "asterisk*"
> >
> > and got a whack of x86_64 asterisk packages, plus a few dependencies
> > (which is what i expected), but in the midst of all that, i also got:
> >
> > ...
> > asterisk-devel-1.6.1-0.23.rc1.fc11.i586.rpm
> > asterisk-devel-1.6.1-0.23.rc1.fc11.x86_64.rpm
> > ...
>
>  yumdownloader isn't the same as yum-plugin-downloadonly.

  ah ... so how would i use the latter?

> > why would i have picked up that i586 package, given that i already
> > have the x86_64 package.  i deleted that package, and re-ran as:
> >
> > $ yumdownloader --resolve --archlist=x86_64 "asterisk*"
>
>  --archlist doesn't do that. You could use "asterisk*.x86_64" as the
> argument, or you can pass --exclude="asterisk*.i?86".

ok, the first suggestion worked, but i'm still puzzled about why that
i586 rpm was downloaded in the first place.  there are 64 asterisk*
rpms for f11 beta, and that was the only one whose i586 equivalent was
downloaded as well.  so why was that?  i checked and it doesn't look
like any of the others require it as a dependency.  what caused it to
be picked up?

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Linked In:                             http://www.linkedin.com/in/rpjday
Twitter:                                       http://twitter.com/rpjday
========================================================================
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.