@ melcharios
I do not really see the point in getting the details out of the
logfiles. The upgrade crashed because a cron job also ran apt, and
managed to hijack the lock on the apt system. It would be of little
general use to see the specifics for this case - it could have been any
package.
As f
@ Jon
Your suggestion is verry helpfull.
I adapt the summary to your intentnion.
Could you copy out the specific lines(polease keep the ammout small for
readability) from the logs out here to the comments, so that I am able
to follow completely.
best
melchiaros
** Summary changed:
- Fatal er
It is not best practice to attach the logs as archive, but acceptable.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10706
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
The entire error is a red herring, I now think.
A cron job was running that started an "apt-get upgrade" while the dist-
upgrade was running. Ouch.
Edited the .postinst file that subsequently crashed, stopped
cron, did a dist-upgrade, then removed and reinstalled the package in
question. Everythi
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please add the log files from '/var/log/dist-upgrade/'
to this bug report as separate attachments and not tar/gzipped files?
Thanks in advance.
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu)
