Re: apt-rpm and vesion precedence

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I would like to thanks everybody for their useful answers.
Unfortunately, as often the bug is between the chair and the keyboard:
there was some pinning in the preference, installed by default, so I
didn't thought to it :-(


Panu Matilainen a =E9crit :
> On Thu, 11 May 2006, Yannick Patois wrote:
>> I think that the order of the pkgs above is by decrescent upgrade, and
>> it seems fine, for now: 1:30X-10.ires is bigger than 1:30X-10.cern
>> because 'i'>'c', right?
>=20
> Version comparisons involving strings are depend to some extent on the
> used rpm versions, but yes 1:30X-10.ires should be considered as
> newer than 1:30X-10.cern by rpm 4.2.x
>>
>> But when I try to upgrade:
>> # apt-get upgrade
>> Reading Package Lists... Done
>> Building Dependency Tree... Done
>> The following packages will be upgraded
>>   apt-sourceslist (303-8.ires1 =3D> 30X-10.cern)
>>
>> Why is the 30X-10.cern selected first?
> In apt other things can affect the package selections, namely pinning i=
n
> various forms. What does 'apt-cache policy apt-sourceslist' output?

There is some pinning, have a look:

# apt-cache policy apt-sourceslist
apt-sourceslist:
  Installed: 303-8.ires1
  Candidate: 1:30X-10.cern
  Version Table:
     1:30X-10.ires 0
        500 http://sbglinux.in2p3.fr ires/slc30X/i386/ires pkglist
     1:30X-10.cern 0
        980 http://sbglinux.in2p3.fr mirror/cern/slc30X/i386/apt/updates
pkglist
 *** 303-8.ires1 0
        500 http://sbglinux.in2p3.fr ires/slc30X/i386/ires pkglist
        100 RPM Database
     303-8.ires 0
        500 http://sbglinux.in2p3.fr ires/slc30X/i386/ires pkglist
     303-8.cern 0
        980 http://sbglinux.in2p3.fr mirror/cern/slc30X/i386/apt/os pkgli=
st
        980 http://sbglinux.in2p3.fr mirror/cern/slc30X/i386/apt/updates
pkglist
     303-7.cern 0
        980 http://sbglinux.in2p3.fr mirror/cern/slc30X/i386/apt/updates
pkglist
     30X-9.cern 0
        980 http://sbglinux.in2p3.fr mirror/cern/slc30X/i386/apt/updates
pkglist

That's pretty annoying :-(

I guess that default pinning is 500, and that even a more recent version
wont beat a 980 pin :-(
Is there a way to alter the package so that it would take precedence?

My problem is that I have a few tens of machines, using automatic update
from a default source, and I added my own to override a few pkgs. I
didn't saw that the original source sneakily added this pinning, thus
never selecting my packages. Can I do something without having to log
into each machine to tune this pining?

Thanks.

	Yannick

- --
 _/ Yannick Patois _________________ Address (home) __________________
| Garp on IRC (undernet/freenode)   | 1, rue de Bale                   |
| http://garp.feelingsurfer.net/    | 67100 Strasbourg                 |
| Tel-home: +(33)(0)3 88 84 88 16   | FRANCE                           |
| Portail d'informations de qualite: http://rezo.net                   |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEY5rKZY3s/IVpRFIRAo8SAJ4ir0wfxx2UPBIhaVwFCfoqMi226wCgueY7
Y9BQqv49uPAYbfJl7AVljHA=3D
=3DPcN9
-----END PGP SIGNATURE-----