hardy2lucid: hwcap index 0 already defined
Bug #562787 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
vm-builder (Ubuntu) |
Triaged
|
Undecided
|
Unassigned |
Bug Description
I tried do-release-upgrade on hardy ec2 in us-east-1
- ami-59b35f30 ubuntu-
That resulted in:
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
/sbin/ldconfig.
dpkg: subprocess installed post-installation script returned error exit status 1
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (2)
Could not install the upgrades
The upgrade is now aborted. Your system could be in an unusable
state. A recovery will run now (dpkg --configure -a).
To post a comment you must log in.
I found 2 things: upgrade 'sudo /sbin/ldconfig' will show the problem so.conf. d/libc6- xen.conf has
a.) after installation/
b.) /etc/ld.
hwcap 0 nosegneg
That should be 'hwcap 1 nosegneg', as is duplicated in so.conf. d/xen.conf . My guess is that libc6-xen.conf is written by the automated ec2 build, or some other non-package-managed mechanism.
/etc/ld.