Niels Thykier <ni...@thykier.net> (2016-05-22): > Cyril Brulebois: > > Just stumbled upon this: > > | (stretch-amd64-devel)kibi@wodi:~$ apt-file update > > | W: chmod 0700 of directory /var/lib/apt/lists/partial failed - > > SetupAPTPartialDirectory (1: Operation not permitted) > > | E: Could not open lock file /var/lib/apt/lists/lock - open (13: > > Permission denied) > > | E: Unable to lock directory /var/lib/apt/lists/ > > | W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches > > (13: Permission denied) > > | W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - > > RemoveCaches (13: Permission denied) > > | E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission > > denied) > > | E: Unable to lock the administration directory (/var/lib/dpkg/), are you > > root? > > The user-cache feature has been removed in apt-file 3[1]. It is > possible to emulate it with some additional setup.
Any chance you could perform a uid check or something similar before running apt update? Failing with a little more self-explaining error message might be interesting… > Please have a look at the section > "Special configurations similar to apt-file 2" > in apt-file(1). Mind you, the resulting config file will almost > certainly need some tweaking. > > Thanks, > ~Niels > > [1] It is related to migrating to the apt-acquire feature. APT does not > have a method of directly supporting user-caches and only fetching some > items. It requires keeping track of all possible items being fetched > and disabling those you do not need. Yeah, I remember the dd@ thread now… KiBi.
signature.asc
Description: Digital signature
