[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem pinning openoffice from lenny-backports



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

Eric Evans wrote:
> [ Ken Heard ]
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Tim Cutts wrote:
>>
>> <snip>
>>
>>> Would it not have been simpler just to have done:
>>>
>>> aptitude install openoffice.org/lenny-backports
>> That is what in effect I did, but with a slightly different command:
>> "aptitude -t lenny-backports install openoffice.org", which was successful.
>>
>>> I don't think pinning is necessary here.
>> No, it is not; but I thought I would take the opportunity to learn how
>> to pin.  Obviously I failed.
>>
>> I did however want to be able to have backport packages upgraded
>> automatically in accordance with the following from the backports
>> instruction page:
>>
>>  If you want to get your packages from backports upgraded automatically
>>  the following entry in /etc/apt/preferences should be sufficient:
>>
>> 	Package: *
>> 	Pin: release a=lenny-backports
>> 	Pin-Priority: 200
>>
>> After I got OpenOffice.org version 3 running I put those three lines --
>> and *only* those three lines -- in file /etc/apt/preferences.  Then when
>> I ran aptitude update I got back the same error message:
>>
>>  E: Invalid record in the preferences file, no Package header
> 
> That should work provided that you have those three lines exactly like you
> have them here, anchored to the beginning of the line (no white space in 
> front them).

I checked file /etc/apt/preferences and found that I did have a space at
the beginning of those three lines.  After fixing that file I ran once
again "apt-get update", and did not receive any error messages this
time.  So I think I am all right.  Thanks for the tip.

Regards, Ken Heard

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknZKpwACgkQlNlJzOkJmTcFlwCfY/S+qXMT3L+vNTN8z7H/CVP5
M6YAn2dyIdGXTIV4uNpHcqaDN2aQiVsN
=nAO5
-----END PGP SIGNATURE-----

Reply to: