On Mon, Jan 14, 2008 at 09:41:23PM +0100, Olaf van der Spek wrote: > > Hi,
hi, > # apt-get -f dist-upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Correcting dependencies... Done > Calculating upgrade... Done > The following NEW packages will be installed: > libboost-date-time1.34.1 libboost-filesystem1.34.1 libboost-iostreams1.34.1 > libboost-program-options1.34.1 libboost-python1.34.1 libboost-regex1.34.1 > libboost-serialization1.34.1 libboost-signals1.34.1 libboost-test1.34.1 > libboost-thread1.34.1 > libboost-wave1.34.1 > 0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded. > 14 not fully installed or removed. > Need to get 0B/2252kB of archives. > After this operation, 7270kB of additional disk space will be used. > Do you want to continue [Y/n]? > (Reading database ... 34325 files and directories currently installed.) > Unpacking libboost-date-time1.34.1 (from > .../libboost-date-time1.34.1_1.34.1-4+b1_i386.deb) ... > dpkg: error processing > /var/cache/apt/archives/libboost-date-time1.34.1_1.34.1-4+b1_i386.deb > (--unpack): > trying to overwrite `/usr/lib/libboost_date_time-gcc42-1_34_1.so.1.34.1', > which is also in package libboost-date-time1.34.1-2 both libboost-date-time1.34.1 and libboost-date-time1.34.1-2 provide /usr/lib/libboost_date_time-gcc42-1_34_1.so.1.34.1 without conflicting each other. same applies to the other libboost packages. since libboost-*1.34.1-2 have always been only in experimental, i'm not really sure if such conflic should be deployed. cheers, Domenico -----[ Domenico Andreoli, aka cavok --[ http://www.dandreoli.com/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
