-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. > The problem does not occur on a stock 64Studio install. It looks like the naming nomenclature is different for this package with that backports repository. Your only real option if you must use 3rd party repositories is to do something called apt pinning.
You may wish to ask the maintainers of the jaunty-backports if it is supposed to conflict. > Is it possible to avoid this conflict? > Yes, do not mix your sources. If it still happens then you have found a bug. In this case what is happening is a result of one of the sources that you added. One option to reduce the chance of seeing this error is to use a method called apt pinning. Use google to find the details. > What does make this conflict happen? Commonly this happens when a 3rd party package is named differently than a package that is already installed or you grab a package from a newer version and the naming nomenclature has changed. Sometimes packagers make mistakes and they include a file that is also included in a different package. You tend to see these "conflicts" when mixing distros or distro versions. > > Can this also happen on 64studio hardy? > It can happen on any Debian based distro. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFK5yWbwRXgH3rKGfMRArcEAJwLRBaogUpW+/2iTw+Af4V08hdMnQCeP0jC 2HcPuobHxPJlC6KuXMUCbv4= =0Rrw -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
