Processed: Re: Processed: Re: Bug#918379 closed by Emilio Pozuelo Monfort (Re: Bug#918379: please decide: severity of "fails to purge" issues)

2019-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 918379 src:piuparts Bug #918379 [release.debian.org] drop sid-strict? Bug reassigned from package 'release.debian.org' to 'src:piuparts'. Ignoring request to alter found versions of bug #918379 to the same values previously set Ignoring

Re: Processed: Re: Bug#918379 closed by Emilio Pozuelo Monfort (Re: Bug#918379: please decide: severity of "fails to purge" issues)

2019-01-08 Thread Holger Levsen
reassign 918379 src:piuparts #sorry for this noise thanks -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856

Processed: Re: Bug#918379 closed by Emilio Pozuelo Monfort (Re: Bug#918379: please decide: severity of "fails to purge" issues)

2019-01-08 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #918379 {Done: Emilio Pozuelo Monfort } [release.debian.org] please decide: severity of "fails to purge" issues Bug reopened Ignoring request to alter fixed versions of bug #918379 to the same values previously set > retitle -1 drop

Re: Bug#918379 closed by Emilio Pozuelo Monfort (Re: Bug#918379: please decide: severity of "fails to purge" issues)

2019-01-08 Thread Holger Levsen
s if there are leftover files after purge. " now that #918379 has been decided, i guess we can drop sid-strict -zwiebelbot- | (#debian-qa) Debian#918379: please decide: severity of "fails to purge" issues - https://bugs.debian.org/918379 so we can also close #856324 ok so I don'

Bug#918379: marked as done (please decide: severity of "fails to purge" issues)

2019-01-07 Thread Debian Bug Tracking System
Your message dated Mon, 7 Jan 2019 10:14:33 +0100 with message-id <4f315c66-a9e1-a4e4-4e6a-fa042d22c...@debian.org> and subject line Re: Bug#918379: please decide: severity of "fails to purge" issues has caused the Debian Bug report #918379, regarding please decide: severity of

Bug#918379: please decide: severity of "fails to purge" issues

2019-01-06 Thread Andreas Beckmann
> h01ger: what does 'fails to purge' mean? the purge fails (gives > errors) or the purge 'succeeds', but files are left? The failures intended to be raised to serious are all the cases where maintainer scripts will fail - ususally in some corner cases depending on (worst-case but

piuparts regressions for new packages? (Re: severity of "fails to purge" issues)

2019-01-05 Thread Holger Levsen
On Sat, Jan 05, 2019 at 05:52:17PM +0200, Adrian Bunk wrote: > On Sat, Jan 05, 2019 at 03:34:23PM +, Holger Levsen wrote: > >... > > There's also at least #918312 filed by Adrian Bunk. > > > > The reasoning that these bugs will block migrations anyway sounds sound > > - except for new

Bug#918379: please decide: severity of "fails to purge" issues

2019-01-05 Thread Holger Levsen
package: release.debian.org x-debbugs-cc: debian-pol...@lists.debian.org, piuparts-de...@lists.alioth.debian.org, Adrian Bunk Hi, filing this as a bug now. Please reassign to src:piuparts once you have decided... On Sat, Jan 05, 2019 at 03:34:23PM +, Holger Levsen wrote: > in >

Re: severity of "fails to purge" issues

2019-01-05 Thread Adrian Bunk
On Sat, Jan 05, 2019 at 03:34:23PM +, Holger Levsen wrote: >... > There's also at least #918312 filed by Adrian Bunk. > > The reasoning that these bugs will block migrations anyway sounds sound > - except for new packages though! >... Are you sure about the latter? For testing migration

severity of "fails to purge" issues

2019-01-05 Thread Holger Levsen
Hi, in https://github.com/anbe42/piuparts/commit/283dac3ae7e31fee51efb836468cd8ca5b61584f (not yet merged into the main piuparts repo) Andreas proposes to file bugs regarding failing to purge with severity 'serious" because "old bugs are filed/fixed and any failure due to a regression in sid