Sorry for losing this bug, I was kinda overwhelmed for a while and
confused this with the ssh signalling bugs; then I promptly forgot it.
Pinging old bugs is good, it forces me to de-rust my brain!

  What I'm a bit puzzled about is why aptitude does the second
--configure run at all.  This is a very old line of code, and I think
it's probably because dselect did.  However, I just did a quick check
and neither apt-get nor synaptic calls dpkg a second time after a
failure.  It might be sensible to just remove that system() call
entirely, rather than getting into messy details of how dpkg expects its
environment to be set up.

  Daniel


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

Reply via email to