On Tue, Sep 27, 2011 at 12:51 PM, Michael Nelson <michael.nel...@canonical.com> wrote: > > Not that I'm aware of (see below), but it is possible that I've sudo'd > a symlink at some point - I don't remember doing so, and don't see why > I would have (we do most our dev work in a virtualenv), but I guess > I'm trying to say don't spend too much time on this if it's likely to > be something stupid I've done on my box (which is entirely possible.
Hi Martin, if no one else is seeing this, and you can't reproduce it, it is entirely possible that I'd added a symlink at some point to test something and failed to remove it. If that looks likely from the current state, then I'm happy to remove whichever symlink is incorrect and update my system again :) Sorry for possibly having wasted your time :/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/854622 Title: Could not install libglib2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/854622/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
