Comment 23 for bug 987502

Revision history for this message
Andrew (mescalito) wrote : Re: [Bug 987502] Re: libxml2-dev: /usr/bin/xml2-config isn't identical across all arch

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.
>