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

Bug#800501: SystemError on missing files in /var/lib/apt/lists



Control: tag -1 unreproducible moreinfo

On Wed, Sep 30, 2015 at 10:12:52AM +0200, Sebastien Bacher wrote:
> Package: python-apt
> Version: 1.1.0~alpha3
> 
> Unsure when/how that is triggered but oneconf seems to hit that often in
> Ubuntu
> 
> example
> 
> "Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/oneconf/packagesethandler.py",
> line 63, in update
>     newpkg_list = self.distro.compute_local_packagelist()
>   File "/usr/lib/python3/dist-packages/oneconf/distributor/Ubuntu.py",
> line 42, in compute_local_packagelist
>     with apt.Cache() as apt_cache:
>   File "/usr/lib/python3/dist-packages/apt/cache.py", line 113, in __init__
>     self.open(progress)
>   File "/usr/lib/python3/dist-packages/apt/cache.py", line 166, in open
>     self._records = apt_pkg.PackageRecords(self._cache)
> SystemError: E:Could not open file
> /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_wily_restricted_binary-i386_Packages
> - open (2: No such file or directory), E:Could not open file
> /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_wily_multiverse_binary-i386_Packages
> - open (2: No such file or directory), E:Could not open file
> /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_wily_universe_binary-i386_Packages
> - open (2: No such file or directory), E:Could not open file
> /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_wily_main_binary-i386_Packages
> - open (2: No such file or directory), E:Could not open file
> /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_wily_restricted_binary-amd64_Packages
> - open (2: No such file or directory), E:Could not open file
> /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_wily_multiverse_binary-amd64_Packages
> - open (2: No such file or directory), E:Could not open file
> /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_wily_universe_binary-amd64_Packages
> - open (2: No such file or directory)"

You're probably opened the cache without holding a lock, and
an update ran in parallel. That's really the only possible
explanation I could think of.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
    - If you don't I might ignore you.


Reply to: