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
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
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
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
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 ->
5 matches
Mail list logo
