Yum problem

Michael Semcheski mhsemcheski at gmail.com
Thu Oct 25 22:20:37 UTC 2007


Its like "someone should invent a program that automatically scans an
RPM for dependencies and goes and fetches them from a repository
automatically!"

And they should call it, delicious.  No, tastey.  They should call it
the Bluehound Unpacker, RePositator, or burp for short.

Just having some fun after a long day.

On 10/25/07, Dave Burns <tburns at hawaii.edu> wrote:
> rpm -qR -p yum*.rpm
>
> I think this will look into the rpm file and list the packages on
> which it depends. Hmm, output look like it might be a package, a
> 'capability' or a file, so you might need more detective work to find
> the list of packages. Seems like there should be a simpler way, but if
> so I couldn't find it by RTFM.
>
> On 10/25/07, Dave Burns <tburns at hawaii.edu> wrote:
> > Why not resolve them on your good box?
> >
> > Won't this do the trick? Even if they were not identical, this should
> > give you a big hint.
> >
> >  rpm -qR yum
> >
> > Or you could unpack (or query?) the rpm file itself, the spec will say
> > what it depends on, won't it? I don't know how to do that, but there
> > must be a way.
> >
> > Dave
> >
> > >If I could use yum to resolve those
> > > dependencies, it would be easy!  But since yum is not working, and I
> > > think it could be a dubious effort to try to resolve all those
> > > dependencies by hand...
> >
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>




More information about the fedora-list mailing list