VMBuilder may have put it there, but a user could have also done taht on
his own. I don't see any reason why this should fail. glibc should
handle this case gracefully.
** Changed in: glibc (Ubuntu)
Status: Invalid => New
--
hardy2lucid: hwcap index 0 already defined
https://bugs.launchpa
Marking 'Invalid' for glibc right now. glibc didn't write the
problematic file. We could potentiall fix it there, though with a work
around.
** Changed in: glibc (Ubuntu)
Status: New => Invalid
** Changed in: vm-builder (Ubuntu)
Status: New => Triaged
--
hardy2lucid: hwcap index
My guess is that vmbuilder is writing 'hwcap 0 nosegneg' is written by
vmbuilder because of bug 246625 and other similar/duplicate bugs there.
However, as far as I can tell there is no affect of writing that file
other than that it breaks the upgrade as I reported here.
Ie:
$ sudo rm /etc/ld.so.c
** Also affects: vm-builder (Ubuntu)
Importance: Undecided
Status: New
--
hardy2lucid: hwcap index 0 already defined
https://bugs.launchpad.net/bugs/562787
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The source of /etc/ld.so.conf.d/libc6-xen.conf is vmbuilder:
$ cat VMBuilder/plugins/ubuntu/templates/xen-ld-so-conf.tmpl
hwcap 0 nosegneg
Then, in ./VMBuilder/plugins/ubuntu/hardy.py
def install_ec2(self):
...
if self.context.arch == 'i386':
self.install_from_template('/etc/ld.so.con
I found 2 things:
a.) after installation/upgrade 'sudo /sbin/ldconfig' will show the problem
b.) /etc/ld.so.conf.d/libc6-xen.conf has
hwcap 0 nosegneg
That should be 'hwcap 1 nosegneg', as is duplicated in
/etc/ld.so.conf.d/xen.conf . My guess is that libc6-xen.conf is written by the
automated
