Soory.

No currently I can not reproduce it again.
At least not with my current system.

I think I could reproduce installing from a clean stable, and add
testing to apt.
Now install etckeeper, init etckeeper, change someting, and update
another package from testing.

But I assume this is to much work for this little problem, right?
Unless you are interested I think you can close the bug.

Achim

Joey Hess wrote:
> Achim Schaefer wrote:
>   
>> Hi,
>>
>> just one observation.
>>
>> With newer versions of ?? the problem seems to be fixed.
>> After upgrading my testing box the problem did not appear any more.
>> So I assume something migrated from unstable to testing, solving the
>> problem.
>>     
>
> There have been no changes in debconf or whiptail or git, unless you
> somehow had a much older one than the current versions in testing when
> you filed the bug report. None of the changes in etckeeper relate to
> this bug as far as I can tell. So I don't know what could have changed.
>
>   
>> Attached the typescript. (before upgrade)
>>     
>
> From the typescript, it looks like you:
>
> * ran apt-get install sudo at the command line
> * saw the dialog box about uncommitted changes, and pressed enter
> * only then saw the message about failure to open the terminal
>
> This suggests that either whiptail displays the dialog box and then
> displays the failure message, or that a second dialog run is the one
> that failed. The only way there can be a second dialog displayed is if
> the git commit of the changes failed for some reason. Then it would try
> to display an error dialog, which might be the one that's failing. Are
> you able to tell from the git log if it successfully committed during
> the installation you sent the typescript of?
>
> (That commit included adding apt/apt.conf.d/typescript, which you may
> want to remove. :-)
>
> If you were still able to reproduce it I'd ask you to
> export DEBCONF_DEBUG=. and send another typescript.
>
>   



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to