[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2021-03-12 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1829860 Title: APT unlocks in same order as it locks Status

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-09-12 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.8.3 --- apt (1.8.3) unstable; urgency=medium [ Simon Körner ] * http: Fix Host header in proxied https connections (LP: #1838771) [ Brian Murray ] * Do not include squashfs file systems in df output. (LP: #1756595) apt (1.8.2)

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-09-12 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.6.12 --- apt (1.6.12) bionic; urgency=medium [ TilmanK ] * Fix typo in German manpage translation [ Michael Zhivich ] * methods: https: handle requests for TLS re-handshake (LP: #1829861) [ Julian Andres Klode ] * Unlock dpkg

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-09-11 Thread Julian Andres Klode
Oh, as I wrote on the other bugs, autopkgtest regressions all went away, except for apport, which had the usual random failure also present in earlier failures. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu.

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-09-11 Thread Julian Andres Klode
Same for bionic 1.6.12: openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4 fcntl(4, F_SETFD, FD_CLOEXEC) = 0 fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 openat(AT_FDCWD, "/var/lib/dpkg/lock",

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-09-11 Thread Julian Andres Klode
So disco, 1.8.3: at the start: openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4 fcntl(4, F_SETFD, FD_CLOEXEC) = 0 fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 openat(AT_FDCWD, "/var/lib/dpkg/lock",

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-09-05 Thread Łukasz Zemczak
Hello Julian, or anyone else affected, Accepted apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.6.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-09-03 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1829860 Title: APT unlocks in same order as it locks

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-09-02 Thread Łukasz Zemczak
Hello Julian, or anyone else affected, Accepted apt into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.8.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-08-09 Thread Julian Andres Klode
** Description changed: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend.

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-08-09 Thread Julian Andres Klode
** Description changed: [Impact] APT releases the locks in the same order it acquires them, rather than reverse order. Given that we have no waiting for locks, this is not _super_ problematic, but it might be wrong: You'd get a lock failure on dpkg's lock, rather than lock-frontend.

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-08-05 Thread Julian Andres Klode
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you

[Touch-packages] [Bug 1829860] Re: APT unlocks in same order as it locks

2019-05-29 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.8.2+19.10 --- apt (1.8.2+19.10) eoan; urgency=medium * Upload to eoan apt (1.8.2) unstable; urgency=medium [ Alwin Henseler ] * Flip /: in documented default value of DPkg::Path (Closes: #917986) [ TilmanK ] * Fix typo in German