Debian Bug report logs - #860237
piuparts: Improve debugging experience in case of dpkg failure

Package: piuparts; Maintainer for piuparts is piuparts developers team <[email protected]>; Source for piuparts is src:piuparts (PTS, buildd, popcon).

Reported by: Bastien ROUCARIÈS <[email protected]>

Date: Thu, 13 Apr 2017 09:48:01 UTC

Severity: wishlist

Reply or subscribe to this bug.

Display info messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to [email protected], Piuparts Developers <[email protected]>:
Bug#860237; Package piuparts.debian.org. (Thu, 13 Apr 2017 09:48:04 GMT) (full text, mbox, link).

Acknowledgement sent to Bastien ROUCARIÈS <[email protected]>:
New Bug report received and forwarded. Copy sent to Piuparts Developers <[email protected]>. (Thu, 13 Apr 2017 09:48:04 GMT) (full text, mbox, link).

Message #5 received at [email protected] (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Package: piuparts.debian.org
Severity: normal

Hi,

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.

Bastien

[signature.asc (application/pgp-signature, inline)]

Information forwarded to [email protected], Piuparts Developers <[email protected]>:
Bug#860237; Package piuparts.debian.org. (Thu, 13 Apr 2017 10:03:06 GMT) (full text, mbox, link).

Acknowledgement sent to Andreas Beckmann <[email protected]>:
Extra info received and forwarded to list. Copy sent to Piuparts Developers <[email protected]>. (Thu, 13 Apr 2017 10:03:06 GMT) (full text, mbox, link).

Message #10 received at [email protected] (full text, mbox, reply):

On 2017-04-13 11:44, 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.

Do you have a concrete example of a failure you want to debug?


Andreas

Information forwarded to [email protected], Piuparts Developers <[email protected]>:
Bug#860237; Package piuparts.debian.org. (Thu, 13 Apr 2017 10:06:05 GMT) (full text, mbox, link).

Acknowledgement sent to roucaries bastien <[email protected]>:
Extra info received and forwarded to list. Copy sent to Piuparts Developers <[email protected]>. (Thu, 13 Apr 2017 10:06:05 GMT) (full text, mbox, link).

Message #15 received at [email protected] (full text, mbox, reply):

On Thu, Apr 13, 2017 at 12:02 PM, Andreas Beckmann <[email protected]> wrote:
> On 2017-04-13 11:44, 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.
>
> Do you have a concrete example of a failure you want to debug?

Yes here https://piuparts.debian.org/wheezy222testing/bugged/imagemagick-doc_8:6.9.7.4+dfsg-3.log

>
> Andreas

Information forwarded to [email protected], Piuparts Developers <[email protected]>:
Bug#860237; Package piuparts.debian.org. (Thu, 13 Apr 2017 10:15:02 GMT) (full text, mbox, link).

Message #20 received at [email protected] (full text, mbox, reply):

On 2017-04-13 12:03, roucaries bastien wrote:
> On Thu, Apr 13, 2017 at 12:02 PM, Andreas Beckmann <[email protected]> wrote:
>> On 2017-04-13 11:44, 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.
>>
>> Do you have a concrete example of a failure you want to debug?
> 
> Yes here https://piuparts.debian.org/wheezy222testing/bugged/imagemagick-doc_8:6.9.7.4+dfsg-3.log

rerunning it with --shell-on-error (and without timeout prefix) would
give you a shell in the chroot - would this help?


Andreas

Information forwarded to [email protected], Piuparts Developers <[email protected]>:
Bug#860237; Package piuparts.debian.org. (Thu, 13 Apr 2017 10:15:04 GMT) (full text, mbox, link).

Acknowledgement sent to Holger Levsen <[email protected]>:
Extra info received and forwarded to list. Copy sent to Piuparts Developers <[email protected]>. (Thu, 13 Apr 2017 10:15:04 GMT) (full text, mbox, link).

Message #25 received at [email protected] (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

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

[signature.asc (application/pgp-signature, inline)]

Bug reassigned from package 'piuparts.debian.org' to 'piuparts'. Request was from Holger Levsen <[email protected]> to [email protected]. (Thu, 13 Apr 2017 10:15:05 GMT) (full text, mbox, link).

Severity set to 'wishlist' from 'normal' Request was from Holger Levsen <[email protected]> to [email protected]. (Thu, 13 Apr 2017 10:15:06 GMT) (full text, mbox, link).

Added blocking bug(s) of 860237: 860238 Request was from Holger Levsen <[email protected]> to [email protected]. (Thu, 13 Apr 2017 10:15:07 GMT) (full text, mbox, link).

Changed Bug title to 'piuparts: Improve debugging experience in case of dpkg failure' from '[piuparts.debian.org] Improve debugging experience in case of dpkg failure'. Request was from Holger Levsen <[email protected]> to [email protected]. (Thu, 13 Apr 2017 10:24:03 GMT) (full text, mbox, link).

Information forwarded to [email protected], piuparts developers team <[email protected]>:
Bug#860237; Package piuparts. (Thu, 13 Apr 2017 13:33:03 GMT) (full text, mbox, link).

Acknowledgement sent to roucaries bastien <[email protected]>:
Extra info received and forwarded to list. Copy sent to piuparts developers team <[email protected]>. (Thu, 13 Apr 2017 13:33:03 GMT) (full text, mbox, link).

Message #38 received at [email protected] (full text, mbox, reply):

On Thu, Apr 13, 2017 at 12:12 PM, Andreas Beckmann <[email protected]> wrote:
> On 2017-04-13 12:03, roucaries bastien wrote:
>> On Thu, Apr 13, 2017 at 12:02 PM, Andreas Beckmann <[email protected]> wrote:
>>> On 2017-04-13 11:44, 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.
>>>
>>> Do you have a concrete example of a failure you want to debug?
>>
>> Yes here https://piuparts.debian.org/wheezy222testing/bugged/imagemagick-doc_8:6.9.7.4+dfsg-3.log
>
> rerunning it with --shell-on-error (and without timeout prefix) would
> give you a shell in the chroot - would this help?


Yes but without dpkg option it is too late. dpkg tried to recover...
>
>
> Andreas
>

Removed blocking bug(s) of 860237: 860238 Request was from Guillem Jover <[email protected]> to [email protected]. (Thu, 20 Apr 2017 08:03:06 GMT) (full text, mbox, link).

Information forwarded to [email protected], piuparts developers team <[email protected]>:
Bug#860237; Package piuparts. (Thu, 05 Oct 2017 13:57:02 GMT) (full text, mbox, link).

Acknowledgement sent to Holger Levsen <[email protected]>:
Extra info received and forwarded to list. Copy sent to piuparts developers team <[email protected]>. (Thu, 05 Oct 2017 13:57:02 GMT) (full text, mbox, link).

Message #45 received at [email protected] (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi,

#860238 was blocking this bug and has been fixed in the meantime. What's left
to do on the piuparts side, if anything?


-- 
cheers,
	Holger

[signature.asc (application/pgp-signature, inline)]

Message sent on to Bastien ROUCARIÈS <[email protected]>:
Bug#860237. (Thu, 05 Oct 2017 13:57:04 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.

Debian bug tracking system administrator <[email protected]>. Last modified: Tue May 13 05:26:31 2025; Machine Name: bembo

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU General Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Debian Bug report logs - #860237 piuparts: Improve debugging experience in case of dpkg failure

Debian Bug report logs - #860237
piuparts: Improve debugging experience in case of dpkg failure