Your message dated Sun, 13 Jan 2019 16:05:56 +0000
with message-id <[email protected]>
and subject line Bug#918379: fixed in piuparts 0.96
has caused the Debian Bug report #918379,
regarding better document what sid-strict tests
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
918379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918379
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: release.debian.org
x-debbugs-cc: [email protected],
[email protected], Adrian Bunk <[email protected]>
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 +0000, Holger Levsen wrote:
> 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 will block migration
> anyway", while we used to treat 'failing to purge' bugs as severity
> 'important' as in practice those bugs are merely annoying (while being a
> clear policy violation).
>
> 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!
>
> So I would like to have the opinion of the release team if you also
> think that those bugs should be filed with severity 'serious' nowadays.
> (As it was their opinion that this shouldn't be done previously.)
>
> What do you think?
this led to this discussion on #-release:
<ivodd> h01ger: what does 'fails to purge' mean? the purge fails (gives
errors) or the purge 'succeeds', but files are left?
<h01ger> both
<ivodd> and with 'both' you mean: 'either of these will produce that error'?
<h01ger> yes. https://piuparts.debian.org/templates/mail/ lists 5 cases with
purge failures
<ivodd> personally, if the purge command fails, I wouldn't even hesitate to\
call the serious (I'm surprised it wasn't filed as serious before)
<ivodd> if the command succeeds and files are left over, I might hesitate a
bit, but on the other hand, if you can't remove all the files, you
have no right to call that a 'successful' purge
<ivodd> so I wouldn't mind if that was filed as serious as well
<h01ger> usually purges are done manually so failing to purge with exit 1 doesnt
really have an effect. thats why it was important only
<ivodd> well, it means something is wrong, and the user gets to clean it up
manually
<ivodd> but I don't think we disagree here :)
<h01ger> :)
<ivodd> I don't really like adding new cases for RC bugs just before the
freeze,
but if this type of error has been tested for quite some time, then it
isn't really a 'new' case
<h01ger> ivodd: i think i will reply to the bug via [email protected] (assigned
to release.d.o) and include our replies there
<h01ger> yeah
<ivodd> ok
<h01ger> it has been tested since lenny :)
<ivodd> piuparts++
<h01ger> :) thanks!
--
cheers,
Holger
-------------------------------------------------------------------------------
holger@(debian|reproducible-builds|layer-acht).org
PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: piuparts
Source-Version: 0.96
We believe that the bug you reported is fixed in the latest version of
piuparts, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Holger Levsen <[email protected]> (supplier of updated piuparts package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 13 Jan 2019 16:56:06 +0100
Source: piuparts
Binary: piuparts piuparts-master piuparts-slave piuparts-common
Architecture: source
Version: 0.96
Distribution: unstable
Urgency: medium
Maintainer: piuparts developers team <[email protected]>
Changed-By: Holger Levsen <[email protected]>
Description:
piuparts - .deb package installation, upgrading, and removal testing tool
piuparts-common - common piuparts components
piuparts-master - piuparts master components
piuparts-slave - piuparts slave components
Closes: 889852 918379
Changes:
piuparts (0.96) unstable; urgency=medium
.
[ Andreas Beckmann ]
* bug-templates: Raise severity of "fails to purge" errors to serious.
(see #918379)
* distros.conf: Add jessie-lts as a full distro.
* piuparts.conf:
- Use jessie-lts as upgrade target and rename section
[jessie2proposed] => [jessie2lts]
- Add sections [wheezy2jessie-lts] and [jessie-lts2stretch].
- [wheezy2bpo2jessie]: Use jessie-lts as final upgrade target.
- Disable sections [wheezy-pu], [jessie-pu]: not used for lts releases.
* scripts/post_distupgrade_exceptions:
- Handle /etc/ca-certificates.conf stretch -> buster upgrade by
normalizing the file to match fresh installations. (Closes: #889852)
* scripts-broken-symlinks: Unbreak more symlinks.
.
[ Holger Levsen ]
* htdocs/index.tpl: stop referring people to the #debian-qa IRC channel, we
really prefer mail nowadays.
* instances/piuparts.conf-template.pejacevic:
- include sid-strict into json outputs.
- improve sid-strict description. Closes: #918379
* master-bin/detect_piuparts_issues: ignore files which vanish during run.
* Bump standards version to 4.3.0, no changes needed.
* d/copyright: update years.
Checksums-Sha1:
b25a2e26c5f044b728a5a3c0ca74a86ec4533045 2050 piuparts_0.96.dsc
3eb32a800dc56a686acb87ce1aabc29936fd916f 270182 piuparts_0.96.tar.gz
ee66c0d1311ddc5475124b3c60797d58360c215b 8309 piuparts_0.96_source.buildinfo
Checksums-Sha256:
9357fba9268909c4e4831f07e538e7004f709276576303b786609444ba079e15 2050
piuparts_0.96.dsc
37133ac07ee59037ed9628e3825034f4985e3ebef27cce2dbe3f99d834ae538d 270182
piuparts_0.96.tar.gz
05bdc99260cb56a427b97f1f4a8d1363a107ff5f196f8d24280f6c93ff37da38 8309
piuparts_0.96_source.buildinfo
Files:
582437d2525803871bcfbc7ae1c8a324 2050 devel optional piuparts_0.96.dsc
dbf8745e46d1cc1d6c4e753a0c06563f 270182 devel optional piuparts_0.96.tar.gz
6edff9bd6a45f44cfee419c526229425 8309 devel optional
piuparts_0.96_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAlw7YAgACgkQCRq4Vgaa
qhxerRAAmXLPxVX2/KJGLwZVuRqmtilo8fmZqJpL/Xqiohc5XdazaeYhuJZdqdyr
6Z38wJfyPb3pA2wTSunDqUvn0lfUQP1CkmvZm8FifhsGbB3UVYUS9Mnl+P0IK0GG
gN2smCbynaD1IkZRx9pCQ3JAmAsvZQxIrM7BDh6Vd85W1RII0HYYVjrbGS8X19eJ
UDYjoGOGOn3M7UJvjOWaSCUE4pj55MBtuO1MuDpjrueBRR3nxLy8otWfxZtPERrH
8uu/3vC7I16TSo0EKPp5M4ozAla46AP7M/h8TibO3v87ZijWaYQy6DBBvLqRq7wZ
HOGjxXfT4Qt4qUh+njDXPqU9L8txrsfXgR0JEP+XbIJgxhRfeI+4UJ7/xeh3WGhd
usXqPKj21Rzli/SK0ktpYzisuVskSKLVVR5xSj2d7TPJ33xOG7nA2zaVK0XCGEAe
1SqXJmMsfLjZj3L/m5FlVFqXmveIo77UckJl/aZ5L93ySIvlqdhk936ZuiE7Ai4h
QVMRGyLjO94cGCM6mWcDZ7tZlXw6kGqspK54Ogl+RfMTwKhHNco7HDJ837JEczpM
nO2meXq/Q59ZD+LA0Q4rS6LpWZSHsuzTTX5qDhWMW/lb1p3zd/L328N05i4dBwPN
SsXaZgJi/pYtfv5fq7L0CtLB5oD7UW2e4ASCO2VPBwB30DYTOhA=
=aZ7w
-----END PGP SIGNATURE-----
--- End Message ---
