Your message dated Wed, 05 Aug 2015 03:50:54 +0200
with message-id <[email protected]>
and subject line dragonegg was removed from Debian
has caused the Debian Bug report #694925,
regarding llvm-gcc-4.7: line 2: exec: gcc-4.7-4.7: not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
694925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694925
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: llvm-gcc-4.7
Version: 3.1-3
Severity: important
$ llvm-gcc-4.7
/usr/bin/llvm-gcc-4.7: line 2: exec: gcc-4.7-4.7: not found
llvm-gcc without -4.7 works fine.
Thanks
Brice
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages llvm-gcc-4.7 depends on:
ii dragonegg-4.7 3.1-3
ii g++-4.7 4.7.1-7
ii gcc-4.7 4.7.1-7
llvm-gcc-4.7 recommends no packages.
llvm-gcc-4.7 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
dragonegg was removed from unstable (see https://bugs.debian.org/794473
for details), but closing the bugs was forgotten.
Andreas
--- End Message ---
