Re: How to change a symlink without breaking anything (problems with g++)
Marc Wilson [EMAIL PROTECTED] writes: The C++ transition has endlessly been debated and beaten to death in a variety of public fora... if you don't know about it, you're living under a rock [...] I have indeed lived under a rock, not participating nor reading any of the Debian public fora up until now. Sorry for my ignorance on this issue. and probably shouldn't be using anything other than stable. You are probably right. I developed the bad habit of considering testing as stable back at the later stages of when Woody was testing, and stable was more like green with fungus. ;-) Anyway, thanks for informing me. Thanks also to the other respondents, who pointed at dpkg-divert, which was the kind of solution I was initially looking for. My problem turned out in the end to be better solved by doing apt-get remove g++ followed with apt-get install g++/stable, as indicated by Marc.. ~# Morten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How to change a symlink without breaking anything (problems with g++)
Hi, this is probably a newbie question, but I didn't see it covered in any of the FAQs or HOW-TOs I found at debian.org/docs/ (and the list search facilities seems quite sloppy, and I had no luck there either): What is the correct manner of changing a symlink file belonging to a Debian package? Is it sufficient to just rm and re-link, or should I use any of the package-handling tools? (In case someone is interested, I'm asking because I just stumbled over a surprising issue with the g++ packages: doing an # apt-get install g++ installed g++-3.3 (I was expecting just an upgrade to the previously installed g++-2.95), and made /usr/bin/g++ into a symlink pointing to it. Just switching g++ versions like this is bound to cause mayhem for all development against any C++ libraries on the system already compiled with g++ v2.95, so I'm surprised that this happens just like that from the testing branch..? Removing the g++-3.3 package doesn't work either, as apt-get seems to now refuse to remove or install _either_ g++-2.95 or g++-3.3 -- it insists on having both? Weird.) ~# Morten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Forcing installation over unmet dependencies
Hi, probably another newbie question, but I couldn't find the answer in any doc: I wanted to upgrade the Qt development kit on my system, but on doing # apt-get install libqt3-dev I get Sorry, but the following packages have unmet dependencies: libqt3-dev: Depends: xlibmesa-glu-dev but it is not going to be installed or libglu1-mesa-dev but it is not going to be installed or libglu-dev E: Sorry, broken packages I don't want to install the GLU library from Mesa, as I already have the NVidia GLU library installed (make install'ed, not from a .deb). How can I force apt-get to ignore the unmet dependency, or otherwise get the libqt3-dev package installed? Is there a general mechanism for telling the package manipulation system don't bother with this package, I've already got what it provides covered from another source? ~# Morten -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
