On Sun, 5 Nov 2006 13:53:01 +0100, Eduard wrote in message <[EMAIL PROTECTED]>:
> #include <hallo.h> > * Arnt Karlsen [Sun, Nov 05 2006, 12:52:02PM]: > > On Sun, 5 Nov 2006 11:01:03 +0100, Eduard wrote in message > > <[EMAIL PROTECTED]>: > > > > > #include <hallo.h> > > > > > > Independent of the question of who is cheating here, please tell > > > which cdrecord version you are upgrading from. Because we have > > > already met precautions to avoid such cases of kind collisions. > > > AFAICS that could only have happened if you installed other > > > unofficial versions of cdrecord package. > > > > > > Eduard. > > > > > > > ..I have??? I have: > > [EMAIL PROTECTED]:~# dpkg -l cdrecord > > ii cdrecord 1.0~pre4-1.1 Dummy package for transition to > > wodim [EMAIL PROTECTED]:~# > > [EMAIL PROTECTED]:/var/www/mmc/BT/2006.0625 $ dpkg -l cdrecord > > ii cdrecord 1.0~pre4-1.1 Dummy package for transition to > > wodim > > > > ..on having a45 fail to burn a cd, I fired up 2p3, as it had been > > sitting idle 'n shut down since June. > > Hm? We are talking about your bug description: > > dpkg: error processing > /var/cache/apt/archives/wodim_5%3a1.0~pre4-1.1_i386.deb (--unpack): > trying to overwrite `/usr/share/man/man1/readcd.1.gz', which is also > in package cdrecord ..yup, those came as I tried to aptitude upgrade at least one of my 2 Sid boxes. (2? 4! ;o)) > But there is no readcd.1.gz in the cdrecord dummy package. ..correct, and I was in a hurry and got pissed: ;o) 474 aptitude update 475 aptitude update 476 aptitude dist-upgrade 477 dpkg -l k3b k3b-i18n wodim cdrecord 478 dpkg -r cdrecord 479 dpkg -r --force-all cdrecord 480 dpkg -r --force-all --force-deps cdrecord 481 dpkg --force-help 482 dpkg -r --force-all,depends cdrecord 483 dpkg -r --force-all,depends,remove-essential cdrecord 484 dpkg -P --force-all,depends,remove-essential cdrecord 485 aptitude dist-upgrade 486 df -h ;aptitude clean ;df -h > And wodim package does conflict with older versions of cdrecord > package so they cannot be installed together, only with the dummy > package. So where does the conflicting file come from? ..for a45 I dunno, for 2p3 most likely the old (June 2006) cdrecord version, both these boxes are Sid, a45 is my conflict finder and main workstation, 2p3 is a _noisy_ old server box I use for FlightGear cvs stunts. ..a wee bit of dpkg brutality will fix it though, but you will wanna automate that fix and a chk for it, trivial for us but might scare off newbies. > And what exactly fails to burn a CD? How? Any error messages? ..a45 upgraded to wodim fine from cdrecord, but wodim would not burn from the k3b gui on a45 when I reported this conflict, cdrecord burned a cd fine from k3b on 2p3, but honked the conflict horn on it's first update since June, which is why-n-when I filed this conflict bug. ..I'll need to try burn another cd, and then file a bug for that no-burn problem, if it remains, I don't see any relation between these 2 bugs, just a likely trivial failure on wodim where cdrecord used to work, might be some dirty wee trick. -- ..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]
