On Sat, 26 Mar 2005 03:58:41 +0000, Ricardo wrote in message <[EMAIL PROTECTED]>:
> On Sat, Mar 26, 2005 at 02:24:08AM +0100, Arnt Karlsen wrote: > > ...apt-get update ;apt-get -u upgrade ;apt-get clean worked ok, but > > <snip> > > The entire sip/PyQt/PyKDE suite is being upgraded to the latest > version, but there are NEW packages in them so it's being a lengthy > process. New sip is now on unstable, but it's incompatible with the > current PyQt. I'm uploading PyQt now and it will be on unstable on a > week or two. On the meanwhile, please revert to the previous sip > version (you can get it from testing). > > A hint: in the future, please don't upgrade blindly. apt-get was > telling you what was going to happen: > > The following packages will be REMOVED: > kodos python-qt3 python2.3-qt3 python2.3-qt3-gl > > You can hold individual packages so they're not upgraded while you > know they're going to give problems. ..that was dist-upgrade, and hey, I do these stunts to try help _find_ bugs, so I get to see some smoke. ;o) ..I used to know my way around rpm, still learning apt 'n dpkg. .._simple_ fixes like a patch to test for the existance for a file so it can either ln -s to it if it exists or "overwrite" if it doesn't and not whine when a namespace owner package "comes home from the vacation" owerwriting the "owerwritten" file, where do I find the cluewhack? ..#295663 is _annoyingly_ easy, but the guy told me he has decided to yank "the SuperLU v3.0 code for the Quadrilateral meshing part", appearantly a _major_ overhaul, and _instead_, rather than _afterwards_. Doing one thing at the time, I could tell him whether that SuperLU v3.0 code breaks k3d running, if it works, he can wait out an upstream fix. ..I'm trying to talk him into doing it my way, and I dunno yet whether my luck has that happening to be the Debian Policy way too. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
