Bug#854141: [Piuparts-devel] tzdata: purging tzdata leaves dangling /etc/localtime symlink

Am 22.03.2017 um 16:56 schrieb Andreas Beckmann: > tzdata (which is now in testing, too). But that should have happened > inbetween, so rescheduling the tzdata test in sid (from March 13) should > be sufficient. Btw, can you please reschedule the affected piuparts tests, so that

Bug#854141: [Piuparts-devel] tzdata: purging tzdata leaves dangling /etc/localtime symlink

Am 22.03.2017 um 16:56 schrieb Andreas Beckmann: > Control: notfound -1 2017a-1 > > On 2017-03-22 16:46, Michael Biebl wrote: > >> That bug seems to be still unfixed in the latest version >> >> https://piuparts.debian.org/sid/fail/tzdata_2017a-1.log >> >> 0m17.0s ERROR: FAIL: After purging files

Bug#854141: [Piuparts-devel] tzdata: purging tzdata leaves dangling /etc/localtime symlink

Am 22.03.2017 um 17:09 schrieb Andreas Beckmann: > And piuparts expects the chroot after the test to be in the same state > as before the test. But that chroot was created with the previous > version of tzdata installed, which was purged in a further minimizing > step, but left that dangling

Processed: Re: tzdata: purging tzdata leaves dangling /etc/localtime symlink

Processing control commands: > found -1 2017a-1 Bug #854141 {Done: Aurelien Jarno } [tzdata] tzdata: purging tzdata leaves dangling /etc/localtime symlink Marked as found in versions tzdata/2017a-1; no longer marked as fixed in versions tzdata/2017a-1 and reopened. --

Bug#854141: tzdata: purging tzdata leaves dangling /etc/localtime symlink

Control: found -1 2017a-1 On Sat, 04 Feb 2017 14:07:33 +0100 Andreas Beckmann wrote: > Package: tzdata > Version: 2016j-2 > Severity: important > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package left unowned

Bug#854141: [Piuparts-devel] tzdata: purging tzdata leaves dangling /etc/localtime symlink

Control: notfound -1 2017a-1 On 2017-03-22 16:46, Michael Biebl wrote: > That bug seems to be still unfixed in the latest version > > https://piuparts.debian.org/sid/fail/tzdata_2017a-1.log > > 0m17.0s ERROR: FAIL: After purging files have disappeared: > /etc/localtime ->

Processed: Re: [Piuparts-devel] tzdata: purging tzdata leaves dangling /etc/localtime symlink

Processing control commands: > notfound -1 2017a-1 Bug #854141 [tzdata] tzdata: purging tzdata leaves dangling /etc/localtime symlink No longer marked as found in versions tzdata/2017a-1. -- 854141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854141 Debian Bug Tracking System Contact

Bug#854141: [Piuparts-devel] tzdata: purging tzdata leaves dangling /etc/localtime symlink

On 2017-03-22 17:02, Michael Biebl wrote: > Well, the log says that tzdata_2017a-1 was installed and tested. > Now I'm confused. Can you explain what piuparts is doing there? And piuparts expects the chroot after the test to be in the same state as before the test. But that chroot was created

Processed: fixed 854141 in 2017a-1, closing 854141

Processing commands for cont...@bugs.debian.org: > fixed 854141 2017a-1 Bug #854141 [tzdata] tzdata: purging tzdata leaves dangling /etc/localtime symlink Marked as fixed in versions tzdata/2017a-1. > close 854141 Bug #854141 [tzdata] tzdata: purging tzdata leaves dangling /etc/localtime

Bug#858529: libc6: fgets repeats content after fork on stretch only

Package: libc6 Version: 2.24-9 Severity: normal Dear Maintainers, I'm testing a programming exercise for students, and found failed tests that I believe are due to libc6. I retried the minimal test case on every machine I have access to, and found that only my two Debian Stretch machines