Your message dated Sun, 08 Nov 2020 21:45:53 +0000
with message-id <e1kbsvv-000iv7...@fasolo.debian.org>
and subject line Bug#973479: Removed package(s) from unstable
has caused the Debian Bug report #941614,
regarding /usr/share/clang/scan-build-8/bin/scan-build: scan-build fails to 
find scan-view
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 ow...@bugs.debian.org
immediately.)


-- 
941614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clang-tools-8
Version: 1:8.0.1-3+b1
Severity: normal
File: /usr/share/clang/scan-build-8/bin/scan-build
Control: affects -1 src:wireguard

I'm running scan-build as part of "make check" in src/ of the
wireguard package.  It terminates with this message:

    Use of uninitialized value $ScanView in exec at /usr/bin/scan-build line 
1920.
    Can't exec "": No such file or directory at /usr/bin/scan-build line 1920.

As far as i can tell, this is due to weird path shenanigans:

   1917       my $ScanView = Cwd::realpath("$RealBin/scan-view");
   1918       if (! -x $ScanView) { $ScanView = "scan-view"; }
   1919       if (! -x $ScanView) { $ScanView = 
Cwd::realpath("$RealBin/../../scan-view/bin/scan-view"); }
   1920       exec $ScanView, "$Options{OutputDir}";

Note that debian puts these binaries in places that don't necessarily
line up with the above due to injected version numbers:

0 dkg@alice:~$ for x in build view; do printf '%s: %s\n' scan-$x $(readlink -f 
$(which scan-$x) ); done
scan-build: /usr/share/clang/scan-build-8/bin/scan-build
scan-view: /usr/share/clang/scan-view-8/bin/scan-view
0 dkg@alice:~$ 

Can't it just search in $PATH?

Thanks for maintaining clang-tools in debian!

       --dkg

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (200, 'unstable-debug'), (200, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages clang-tools-8 depends on:
ii  clang-8      1:8.0.1-3+b1
ii  libc6        2.29-2
ii  libclang1-8  1:8.0.1-3+b1
ii  libgcc1      1:9.2.1-8
ii  libllvm8     1:8.0.1-3+b1
ii  libstdc++6   9.2.1-8
ii  python3      3.7.3-1

clang-tools-8 recommends no packages.

clang-tools-8 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1:8.0.1-10+rm

Dear submitter,

as the package llvm-toolchain-8 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/973479

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Joerg Jaspert (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to