On Wed, 21 Mar 2012 08:33:13 +0530 shirish शिरीष <[email protected]> wrote:
> For some reason your response on the bug didn't make the way to my > inbox hence subscribed to the bug. Thought that who starts the bug is > subscribed already. Oh well! I've had that happen to me a few times too. But subscribing might mean you end up with 2 copies (3 including the Cc!). > When I tried doing upgrading I understood that two more libraries > depend on it libglib2.0-bin and libglib2.0-dev . > > When I looked at why libglib2.0-dev was needed it points to something > else but don't wanna go there now. > > $ aptitude why libglib2.0-dev > i libpulse-dev Depends libglib2.0-dev That means you've also got libpulse-dev installed. Have you compiled something that involves audio? You could see what `aptitude why` says about that. > Anyways while I can install the three libraries together dunno if > there are any other implications. They seem to be able to install > okish if I wanna go that route (as in aptitude does not complain). > > $ sudo aptitude install libglib2.0-0=2.31.22-1 > libglib2.0-bin=2.31.22-1 libglib2.0-dev=2.31.22-1 > The following packages will be upgraded: > libglib2.0-0 libglib2.0-bin libglib2.0-dev > 3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. That's good, it isn't forcing anything else to be upgraded. I haven't had any problems since I upgraded glib. However, this version alone won't remove all the warnings, and it's the fact that there are warnings at all that make it a nuisance, not whether there are three or four instead of only one. But recompiling to use the patch takes a loooooooong time and requires a lot of other dev packages. I could upload the binary package I made too if amd64 is any use to you. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
