Re: Problem pinning openoffice from lenny-backports
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Matteo Semplice wrote:
> Hi,
> I had started a similar thread in September, so I'll try to contribute
> here... The results of the discussion back there were:
> 1- you cannot pin openoffice in any distribution by simply giving it priority
> higher than 500, since you would need to pin all openoffice.org* packages and
> apt/preferences does not allow that: you'd have to list **explicitely** one
> by one all packages openoffice.org-base, openoffice.org-calc, etc.
Thank you for this explanation. Yours is better than the one on the
backports instruction page. It was not clear -- to me at any rate --
from the instruction page that each and every package would require
pinning. As there were about 30 packages to upgrade openoffice,
including all dependencies, pinning them would be onerous indeed -- and
unnecessary.
> 2- the second best option is what's explained in the backports.org
> instructions page, that is install it manually once as you did and
> pin openoffice.org/backports with priority 200. After the manual install,
> priority 200 is enough to let apt automagically upgrade openoffice when a new
> version is added to backports. At least it was working for me during the last
> months of etch...
>
> Regarding your error message, I cannot help on that. The only suggestion is
> that, when I had troubles with apt, I found very useful to run "apt-cache
> policy packagename".
In response to another message to me off list about the error message,
which I will forward to the list, I revised file /etc/apt/preferences to
include *only* those three lines:
Package: *
Pin: release a=lenny-backports
Pin-Priority: 200
and then ran "apt-get update".
This time I did not get any error message; so I think I am all right.
Ciao, Ken Heard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknZKT4ACgkQlNlJzOkJmTcKkACffQB9FtbNlF24RiCQsLz77HDi
BOEAn212O0C4yHXxYNN5BtE15KuWpn59
=4bb4
-----END PGP SIGNATURE-----
Reply to: