** Changed in: apt (Ubuntu)
Status: In Progress = Triaged
** Changed in: apt (Ubuntu Lucid)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/559582
Title:
Jeez, really? You've abandoned apt-get as a valid upgrade path? That
constitutes a major change to ubuntu, if not a complete detachment from
Debian. It fundamentally alters the path that Ubuntu sysadmins can plan
around. This needs to be VERY clear to people, like a big red box above
any
The do-release-upgrade script is not an option for us (and hence a
number of our clients) running high availability clusters - since
pacemaker-openais has been removed in favour of pacemaker/cluster-glue,
the do-release-upgrade kills the node in the cluster by removing
pacemaker-openais, making
One of the other workarounds would have been a lot better. This bug bit
me with the released version of lucid, and I don't really appreciate
having to spend however many hours hacking around it to fix package
dependencies. It bit me because instead of doing a dist-upgrade, I just
did apt-get
Sam,
I am sorry to tell you that for Ubuntu the upgrade process as documented at
http://www.ubuntu.com/getubuntu/releasenotes/1004overview#Upgrading%20from%20Ubuntu%209.10%20or%20Ubuntu%208.04%20LTS
is to use do-release-upgrade or update-manager, using apt-get install or
dist-upgrade is not one
that's ok for dumb users but not for people like me - so I will switch
back to Debian. I'm sorry to leave ubuntu, because I thought it was a
really good distro, but if you don't get the package dependencies right,
there's not much point trying to make a distro at all.
--
Upgrade from karmic to
I feel a bit sad about people which classifies others which read and respect
the instructions as dumb.
Next time please try to be more constructive and read the actual bug report
before adding uninformed comments, if you read Michael's comments you will
notice that the problem is related to a
I've tried do-release-upgrade -d from jaunty lucid
it failed and now gives a Segmentation fault for every command I try to use.
I have tried to access the system with a rescue disk but via the terminal I get
the mountall error when trying to apt-get install -f. I cant seem to do
anything.
Thanks,
just tested on virtualized server at linode with kernel 2.6.32 paravirt,
do-release-upgrade -d worked great,
Andrea
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received
Thanks Michael,
I can confirm on an identical setup, bare metal virtual server image, upgrading
from karmic to lucid, do-release-upgrade -d worked perfectly this time.
Tom.
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
I can reproduce the problem and it is caused by a feature in apt that
tries to ensure that all important packages gets ocnfigured immediately
to minimize the risks if somethng goes wrong (pkg failure, power loss
etc)
** Changed in: mountall (Ubuntu)
Status: Confirmed = In Progress
**
** Also affects: mountall (Ubuntu Lucid)
Importance: Medium
Status: In Progress
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received this bug notification because you
** Attachment added: apt debug log of the failure
http://launchpadlibrarian.net/44414325/apt-debug.log
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received this bug
So the problem is that libpng12-0 requires libc6 (= 2.11) and at the
point apt tries to configure it its not ready yet and the pre-configure
code fails. That is a bug in this code.
I would not want to change this code at this point of the release though
but instead add a workaround to help apt to
A alternative workaround is to build libpng12-0 so that it works with
libc6 2.10, it appears that the only used symbol from 2.11 is
__longjmp_chk
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
Next option is to try to make mountall not part of the immediate-
configure set or to run with -o Apt::Immediate-Configure=false
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You
** Package changed: mountall (Ubuntu Lucid) = apt (Ubuntu Lucid)
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Lucid)
Status: New = Fix Committed
--
Upgrade from karmic to lucid failes with Internal Error,
Probably too late to debug the apt issue for lucid, but with the files
it should be possible to fix early in maverick.
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received this
To reproduce, unpack in a chroot and run:
# apt-get dist-upgrade
or
# apt-get dist-upgrade --simulate
** Attachment added: tarball of the required files to reproduce the failure
http://launchpadlibrarian.net/44421820/apt-configure-error-state.tar.gz
--
Upgrade from karmic to lucid failes
This bug was fixed in the package initramfs-tools - 0.92bubuntu74
---
initramfs-tools (0.92bubuntu74) lucid; urgency=low
* debian/control, debian/rules:
- force libc6 dependency to = 2.11 (and libc6.1 on ia64, the libc6
has a different packages name on this architecture)
** Branch linked: lp:ubuntu/initramfs-tools
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Added /var/log/dist-upgrade/system_state.tar.gz from an affected system
as per request of mvo from #ubuntu+1 =)
** Attachment added: system_state.tar.gz
http://launchpadlibrarian.net/44273097/system_state.tar.gz
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
Me too. Upgrade from karmic-lucid on bare metal.
$ sudo do-release-upgrade -d
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool
Done downloading
extracting 'lucid.tar.gz'
authenticate 'lucid.tar.gz' against 'lucid.tar.gz.gpg'
tar: Removing leading `/'
i too am affected by this. for my setup its not a virtualized setup but
on a physical machine.
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
Likewise, this affects me too, karmic-lucid beta on a virtual machine,
/etc/fstab:
proc/proc procdefaults0 0
/dev/xvda / ext3noatime,errors=remount-ro 0 1
/dev/xvdb noneswapsw 0 0
#
I had this problem too, with Ubuntu Karmic server. I was able to upgrade
the desktop version painlessly (with update manager).
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You
I've also upgraded 3 desktops with the update manager to lucid beta with no
problems.
I have tried downgrading to the mountall karmic 1.0 package with: sudo apt-get
install mountall=1.0 and it downgraded fine, however I still get the same error
from do-release-upgrade -d
--
Upgrade from
anyone have any ideas for a work around?
On Mon, Apr 12, 2010 at 3:58 PM, Tom Worley t...@worley.co.uk wrote:
I've also upgraded 3 desktops with the update manager to lucid beta with no
problems.
I have tried downgrading to the mountall karmic 1.0 package with: sudo
apt-get install
I'm considering replacing karmic with lucid in /etc/apt/sources.list and
then apt-get dist-upgrade
Is there any more than that that do-release-upgrade actually does?
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
im not 100% sure. but the error is with mount all i did a query to the bot
on irc and thats for filesystem mounting. ill try and do some more digging
but i would be apprehensive if that is buggy to upgrade.
On Mon, Apr 12, 2010 at 4:29 PM, Tom Worley t...@worley.co.uk wrote:
I'm considering
I've managed to around this by doing the following:
sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list
sudo apt-get update
wget
http://mirrors.kernel.org/ubuntu/pool/main/m/mountall/mountall_2.11_amd64.deb
sudo dpkg --force-all -i /var/cache/apt/archives/mountall_2.11_amd64.deb
sudo apt-get -f
will try this out to confirm
On Mon, Apr 12, 2010 at 5:04 PM, Tom Worley t...@worley.co.uk wrote:
I've managed to around this by doing the following:
sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list
sudo apt-get update
wget
tom can confirm that this method works :) on a physical machine if someone
would confirm for those having an issue with upgrading virtual machines.
On Mon, Apr 12, 2010 at 5:17 PM, Jonathan Aquilina
eagles051...@gmail.comwrote:
will try this out to confirm
On Mon, Apr 12, 2010 at 5:04 PM,
The above workaround was on a linode virtual server and worked first time.
There's a slight amendment to the above instructions, the dpkg line should read:
sudo dpkg --force-all -i mountall_2.11_amd64.deb
I used the local copy that I got dist-upgrade to download while doing
testing
--
Upgrade
for me your original way worked.
On Mon, Apr 12, 2010 at 6:28 PM, Tom Worley t...@worley.co.uk wrote:
The above workaround was on a linode virtual server and worked first time.
There's a slight amendment to the above instructions, the dpkg line should
read:
sudo dpkg --force-all -i
Tom's workaround worked for me too - thanks. Bare metal server.
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received this bug notification because you are a member of Ubuntu
Manually running sudo mountall gives:
swapon: /dev/vda2: swapon failed: Device or resource busy
mountall: swapon /dev/vda2 [11295] terminated with status 255
mountall: Problem activating swap: /dev/vda2
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate
Using do-release-upgrade gives the same error (just takes much longer;-)
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received this bug notification because you are a member of
Using 'swapoff /dev/vda2' allows me to run mountall without an error
exactly once. On a further call, it spits out the above error again. It
looks like the swap disk doesn't get added to /etc/mtab...
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate
Doing swapoff /dev/vda2 doesn't help with upgrading, same error...
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received this bug notification because you are a member of Ubuntu
Disabling the swap in /etc/fstab does fix the error on multiple calls to
mountall, but upgrading still fails...
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate configuration (2) on mountall
https://bugs.launchpad.net/bugs/559582
You received this bug
Installing mountall 2.10 using dpkg -i gives dependency errors. A
succinct apt-get -f install gives the following error:
E: Internal Error, Could not perform immediate configuration (2) on
plymouth
--
Upgrade from karmic to lucid failes with Internal Error, Could not perform
immediate
I somehow did get it to upgrade now:-)
From my mind:
* Fixed the manual installation of mountall 2.10 by re-installing 1.0
* I did run apt-get upgrade which did seem to work:
sudo apt-get upgrade
Reading package lists... Done
43 matches
Mail list logo
