Rerunning do-release-upgrade ran successfully, the machine was upgraded
to Gutsy. It didn't boot, but that is due to other, known bugs.
--
cupsys failure during do-release-upgrade from 7.04 to 7.10
https://bugs.launchpad.net/bugs/243887
You received this bug notification because you are a member
Public bug reported:
Binary package hint: update-manager
While remotely upgrading an x86 Ubuntu Gutsy desktop machine, do-
release-upgrade fails because apt/dpkg tried to remove ubuntu-desktop to
resolve a broken dependency w/ pulseaudio-esound-compat and esound. Logs
attached.
** Affects: updat
** Attachment added: "apt.log"
http://launchpadlibrarian.net/15699712/apt.log
--
7.10->8.04 attempts to remove ubuntu-desktop due to broken dep on
pulseaudio-esound-compat
https://bugs.launchpad.net/bugs/244368
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "main.log"
http://launchpadlibrarian.net/15699714/main.log
--
7.10->8.04 attempts to remove ubuntu-desktop due to broken dep on
pulseaudio-esound-compat
https://bugs.launchpad.net/bugs/244368
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Attachment added: "main_pre_req.log"
http://launchpadlibrarian.net/15699731/main_pre_req.log
--
7.10->8.04 attempts to remove ubuntu-desktop due to broken dep on
pulseaudio-esound-compat
https://bugs.launchpad.net/bugs/244368
You received this bug notification because you are a member of
The problem had been resolved on that machine as noted above by
rerunning the upgrader. I was able to reproduce the issue on a (nearly)
identical installation. Here is the output of the requested commands
directly after the upgrade fails, I had hoped to see a more of a clue as
to why the problem oc
Adding --mode=desktop allowed the upgrade to commence. I thought do-
release-upgrade was supposed to auto-detect the mode, I recall seeing a
note to that effect in the changelog.
--
7.10->8.04 attempts to remove ubuntu-desktop due to broken dep on
pulseaudio-esound-compat
https://bugs.launchpad.
Public bug reported:
Binary package hint: update-manager
Using do-release-upgrade to remotely upgrade x86 Ubuntu Feisty desktop install
failed.
Attached are the files in /var/log/dist-upgrade/ and the terminal output.
update-manger/update-manager-core version 1:0.81.3 is installed after the
fai
** Attachment added: "terminal output"
http://launchpadlibrarian.net/15672056/terminal-output.log
--
cupsys failure during do-release-upgrade from 7.04 to 7.10
https://bugs.launchpad.net/bugs/243887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Attachment added: "main.log"
http://launchpadlibrarian.net/15672064/main.log
--
cupsys failure during do-release-upgrade from 7.04 to 7.10
https://bugs.launchpad.net/bugs/243887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "main_pre_req.log"
http://launchpadlibrarian.net/15672066/main_pre_req.log
--
cupsys failure during do-release-upgrade from 7.04 to 7.10
https://bugs.launchpad.net/bugs/243887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Oops, when pasting the errors into the bug description I put the
installArchives() failed message above the others, as indicated by the
timestamp.
--
cupsys failure during do-release-upgrade from 7.04 to 7.10
https://bugs.launchpad.net/bugs/243887
You received this bug notification because you ar
This is definitely reproducible here too. I'm bootstrapping new domUs
and seeing the bug rear it's head in the form shown in Bug #207774. The
patch in this thread completely eliminates the bug here. I have not seen
the oops in weeks of use since applying the patch, creating quite a few
domU's in th
Public bug reported:
Binary package hint: amavisd-new
I had a working amavis-new installation in dapper. I let upgrade-
manager rename/replace the config files in the edgy upgrade, and then
proceeded to upgrade to feisty. The package failed during the feisty
upgrade, the automated error info sho
hmm. I know I followed this up, I guess I forgot to submit the
comment...
The problem occurred because I did not remove amavisd.conf.disabled I
had planned to deal with the config changes after upgrading to feisty.
Once I removed the file in question dpkg was able to successfully
configure amavis
15 matches
Mail list logo