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

roucaries bastien roucaries.bastien+debian at gmail.com
Thu Apr 13 13:29:02 UTC 2017


On Thu, Apr 13, 2017 at 12:12 PM, Andreas Beckmann <anbe at debian.org> wrote:
> On 2017-04-13 12:03, roucaries bastien wrote:
>> On Thu, Apr 13, 2017 at 12:02 PM, Andreas Beckmann <anbe at debian.org> 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
>



More information about the Piuparts-devel mailing list