Ralf Mardorf wrote: > rosea grammostola wrote: > >> Hi, >> >> >> After a lit of experimenting in vbox, it seems I bumped up against an >> serious issue :) >> >> libc6-dev from Ubuntu seems to conflict with linux-libc-dev from >> 64studio (jaunty backport) >> >> Need to get 0B/3453kB of archives. >> After this operation, 13.7MB of additional disk space will be used. >> (Reading database ... 164776 files and directories currently installed.) >> Unpacking libc6-dev (from .../libc6-dev_2.9-4ubuntu6.1_i386.deb) ... >> dpkg: error processing >> /var/cache/apt/archives/libc6-dev_2.9-4ubuntu6.1_i386.deb (--unpack): >> trying to overwrite `/usr/include/scsi/scsi.h', which is also in >> package linux-libc-dev >> dpkg-deb: subprocess paste killed by signal (Broken pipe) >> Errors were encountered while processing: >> /var/cache/apt/archives/libc6-dev_2.9-4ubuntu6.1_i386.deb >> E: Sub-process /usr/bin/dpkg returned an error code (1) >> >> >> I don't know if reporting this will helps the devs. I don't know if it's >> 'supposed' to conflict. >> >> Is it possible to avoid this conflict? >> >> What does make this conflict happen? >> >> Can this also happen on 64studio hardy? >> >> >> Kind regards, >> >> \r >> > > For packages were you can ensure that they won't break your system, you > can run "dpkg -i --force-overwrite PACKAGE.deb". In this case you should > diff "/usr/include/scsi/scsi.h" of the two packages, maybe they don't > diff, then you can use --force-overwrite. In other cases you are able to > see that --force-overwrite won't damage your system, e.g. if there is > such a conflict because of firmware you aren't using. > > Thanks, good to know!
Regards, _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
