Re: Questions about package pinning

Hi Panu,

On Fri, 30 Jul 2004 16:32:56 +0300
Panu Matilainen <[email protected]> wrote:

> > Mmmh... ok, makes sense, and it did fix the "(not found)" issue. I
> > didn't go that way because it felt to me like there could be many
> > "core" components on different repos -- as well as "stable" (for
> > kde-redhat above). I guess I got it all wrong.
> 
> Not all wrong, just slightly :) The problem is that unless the
> release.* files are correctly set up, there's nothing you can do to
> differentiate two "core" components from different repositories.
> Complaining to repository maintainer is the best thing you can do in
> that case, see below...

Got it.

> Last I talked to Gustavo he had some reservations about it so haven't
> committed it yet until I talk to him again (he seems to be on vacation
> currently)

Cool.

> >  Still, in the case
> > above, why did priority = 0 not work? Or it would work _if_ I also
> > had the (fixed) entry for freshrpms above (which seems redundant to
> > me)?
> 
> Because there's no "kde-redhat" component? (it's called "stable" and
> here we go again with these overlapping component names...)

Right, of course. Sorry for the stupid question... ={

> You'll want to use 'apt-cache policy' without any packages after it,
> then it becomes quite obvious what to put in there:
> [pmatilai@chip pmatilai]$ apt-cache policy
> Package Files:
>  100 RPM Database
>  500 http://fedora.quicknet.nl fedora/2/i386/stable pkglist
>      release v=2,o=Fedora Extras,a=stable,l=Fedora Extras,c=stable
>      origin fedora.quicknet.nl
>  500 http://fedora.quicknet.nl fedora/2/i386/updates pkglist
>      release v=2,o=Fedora Core,a=stable,l=Fedora Extras,c=updates
>      origin fedora.quicknet.nl
>  500 http://fedora.quicknet.nl fedora/2/i386/os pkglist
>      release v=2,o=Fedora Core,a=stable,l=Fedora Extras,c=os
>      origin fedora.quicknet.nl
>  500 file: 2/Fedora/os pkglist
>      release v=Unknown,o=Unknown,a=Unknown,l=Unknown,c=os
> 
> The last one there is a typical example of incomplete repository setup
> where you can only hope that the component is different enough from
> everything else. Or complain to repository maintainer...

Excellent, that seems to have all the info I need. Panu, you're TheMan!
=)

> > Ok. IMHO it's a pitty, specially considering that, with more and
> > more repositories popping up, package pinning usefulness increases
> > proportionally.
> 
> Indeed....

Well, if I learn enough of it, I will try to gather all info
and publish it somewhere. However, I feel there's still quite some
ground to cover... ={

Thks again,

Andre

-- 
Andre Oliveira da Costa
([email protected])