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

Bug#571660: /usr/bin/apt-get: could not lock /var.../lib/apt/lists/volatile... ("Impossible de verrouiller /var...")



Hi Damien Couroussé!

2010/2/26 Damien Couroussé <damien.courousse@free.fr>:
> apt-get source reports an error while trying to acquire locks under
> /var/lib/apt/lists
Thanks for your report! For your next one i have a little tip:
Preface a command with LANG=C to enforce english output to
help unlucky people like me who had by now never the chance
to learn French… (Latin for the win) ;)

For reference, your error in plain english should be:
E: Could not get lock %s - open (2: No such file or directory)
E: Could not open file %s - open (2: No such file or directory)
Both english strings are translated in the same way in fr.po…
(CC'ing Christian Perrier as this looks like a bug in the translation)

Looking at the sourcecode i guess
E: Could not open file <xyz> - open (2: No such file or directory)
is really meant as these files aren't lockfiles…

>  - apt-get is run without root superuser power,
>  - non other apt/aptitude processes are running at the same time,
>  - except for downloading source packages from time to time, I do not
>   use apt (I assume this is the reason why the lock files where not
>   available); I use aptitude for system maintenance and installation of
>   new packages.
>  - the problem was solved by manually creating the required files as a root user.
Do you have by chance added recently
deb-src http://volatile.debian.org/debian-volatile squeeze/volatile
main contrib non-free
to your sources.list ? Or to be specific: After your last
"apt-get update" (or "aptitude update") ?

At least it is reproducible for me in this case.
So apt-get should display a friendlier message indicating the possible
solution i guess… (apt-get update, not creating various empty files).
I will have a deeper look into it - thanks for pointing it out so far!


benignis cum salutibus,

David Kalnischkies



Reply to: