On Wed, Sep 30, 2015 at 10:59:26AM +0200, Sebastien Bacher wrote:
> > 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.
>
> Is there a way to hold a lock as a normal user process? (oneconf i
> 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.
Is there a way to hold a lock as a normal user process? (oneconf is an
user session service)
If not is there a standard way to detect that som
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):
> F
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_loc
4 matches
Mail list logo
