Subject: Bug#860237: [Piuparts-devel] Bug#860237: [piuparts.debian.org] Improve debugging experience in case of dpkg failure

From: Holger Levsen <[email-masked]>
Date: Thu, 13 Apr 2017 10:13:29 +0000

reassign 860237 piuparts
severity 860237 wishlist
retitle 860238 [dpkg] Improve debugging experience for piuparts
block 860237 by 860238
thanks

On Thu, Apr 13, 2017 at 11:44:16AM +0200, Bastien ROUCARIÈS wrote:
> Actually dpkg try to recover from error state in order to get something safe.
> it is not really needed for piupart and moreover it detroy bug evidence.
> Safer will be to add  abort-after=1 to dpkg config thus keeping evidence.

more context from irc:

< broucaries> | h01ger: get this from guillem
< broucaries>  guillem: [23:44:51] for dpkg you can configure it in the config file with abort-after=1
< broucaries> | guillem: [23:45:02] dunno about piuparts
< broucaries> | h01ger: could we add this to piupart and get some script to list file contents ?
<     h01ger> | broucaries: i need more context
<     h01ger> | broucaries: and probably a bug report
< broucaries> | h01ger: for debugging the imagemagick-doc problem guillem suggests to set abort-after=1 for dpkg configuration, in order to stop in case of error instead to run recovery. Thus we could inspect the package state including file installed
< h01ger> | broucaries: also see #850917 and commit 285e9811cb in piuparts.git

-- 
cheers,
	Holger