On Vi, 27 iun 14, 22:12:45, Ralf Treinen wrote: > Package: llvm-gcc,llvm-gcc-4.7 > Version: llvm-gcc/3.4-1 > Version: llvm-gcc-4.7/3.3-2 ... > Selecting previously unselected package llvm-gcc. > Preparing to unpack .../llvm-gcc_3.4-1_amd64.deb ... > Unpacking llvm-gcc (3.4-1) ... > Selecting previously unselected package llvm-gcc-4.7. > Preparing to unpack .../llvm-gcc-4.7_3.3-2_amd64.deb ... > Unpacking llvm-gcc-4.7 (3.3-2) ... > dpkg: error processing archive > /var/cache/apt/archives/llvm-gcc-4.7_3.3-2_amd64.deb (--unpack): > trying to overwrite '/usr/bin/llvm-cpp', which is also in package llvm-gcc > 3.4-1 > Processing triggers for man-db (2.6.7.1-1) ... > Errors were encountered while processing: > /var/cache/apt/archives/llvm-gcc-4.7_3.3-2_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > cow-shell unlink .ilist: No such file or directory
Hi, The package llvm-gcc-4.7 isn't known to the BTS, the PTS, rmadison or NEW. Normally I would just leave this bug as is, because it is assigned against an existing package (llvm-gcc), but given the nature of the bug I have to ask: where does the llvm-gcc-4.7 package come from? Kind regards, Andrei (looking after bugs filed against unknown packages) -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt
signature.asc
Description: Digital signature
