Hi darko, Thanks for your help again!
I do believe I don't need this anyway as you say. Yep I'm running low on HDD space atm and have used the repair broken packages in boot mode. I will have more space when I defrag the drive which has windows on it so I can safely erase Windows and then use Gparted or similar to rearrange things. Last time I went to do this, Windows played up and I got some message saying it was a non registered version?? Was never like that before so will have to look into that. I haven't used windows since my first run of the previous version of Ubuntu. I guess the best is to go offline to start windows,then see if I can defrag maybe even in safe-mode? Windows is so foreign to me now LOL yet I knew it inside out once. Any simple command to remove the offending library? I've searched and cannot understand the lingo, a bit deep for me. I have sudo'd all commands and the 'apt-get-update' many times with reboot without success. Thanks again mate for the support. Andrew On 13/09/13 19:18, Darko Lombardo wrote: > Hi Andrew. > > I do not think your issue is related to this bug at all. > > As a user you probably have no need for a libxml2-dev package, only > libxml2. > > I posted notes in reference to this bug due to a deliberate request by the > user (developer) for libxml2-dev:i386 on a 64-bit Ubuntu, which is not > something users are likely to try to install. > Like said before, both versions of the library are needed if one needs > multiple architecture building option on a 64-bit Ubuntu. > > Regarding your problem it is hard to say from the posted information, but > more of an apt (Update Manager) issue than libxml2 package issue. > I have seen your message sometimes: > - (maybe) command was not called with 'sudo' > - running out of space on HDD partition > - broken/damaged package > > Try to call 'sudo apt-get update' and restart the Update Manager (or the > system). > Then retry to upgrade again using the Update Manager. > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/987502 Title: libxml2-dev: /usr/bin/xml2-config isn't identical across all arch Status in “libxml2” package in Ubuntu: Fix Released Status in “libxml2” source package in Precise: Triaged Bug description: [Background] In the M-A implementation of version 2.7.8.dfsg-5.1ubuntu1, /usr/bin/xml2-config still contains M-A tripples, which is troublesome when the package libxml2-dev is marked as M-A: same. The problem is caused by the sed call in debian/rules says "usr/lib/<tripple>", while it wasn't like that in xml2-config script itself. [Impact] libxml2-dev is not M-A co-installable [Development Fix] libxml2 version 2.7.8.dfsg-9 in Debian Sid [Stable Fix] Change required is trivial, in debian/rules: - sed -i -e 's,/usr/lib/$(DEB_HOST_MULTIARCH),/usr/lib,' debian/libxml2-dev/usr/bin/xml2-config + sed -i -e 's,/lib/$(DEB_HOST_MULTIARCH),/lib,' debian/libxml2-dev/usr/bin/xml2-config [Test Case] Enable M-A in testing environment (amd64 for instance), and try to install both libxml2-dev:i386 and libxml2-dev:amd64 which were newly built with the mentioned patch. If the action failed with something like './usr/bin/xml2-config' is different from the same file on the system, then the bug was not fixed. [Regression Potential] xml2-config reports the libdir is /usr/lib, while the actual ones are /usr/lib/<triplets>. This might break applications whose build system can't find libraries correctly in the previous path but relies on xml2-config's output. I recommend to use pkg-config instead of this script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/987502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
