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
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
** 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
Server Team, which is subscribed to vm-builder in ubuntu.
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
