Your message dated Tue, 25 Apr 2017 12:22:21 +0200
with message-id <20170425102219.ga3...@ugent.be>
and subject line Re: clang-3.8: broken symlink: /usr/bin/scan-build-py-3.8 -> 
../share/clang/scan-build-py-3.8/bin/scan-build
has caused the Debian Bug report #860580,
regarding clang-3.8: broken symlink: /usr/bin/scan-build-py-3.8 -> 
../share/clang/scan-build-py-3.8/bin/scan-build
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.)


-- 
860580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clang-3.8
Version: 1:3.8.1-20
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m39.1s ERROR: FAIL: Broken symlinks:
  /usr/bin/scan-build-py-3.8 -> ../share/clang/scan-build-py-3.8/bin/scan-build

Looks like a change was unneccessarily backported from 3.9, since that was
previously working correctly in 3.8


cheers,

Andreas

Attachment: clang-3.8_1:3.8.1-20.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Version: 1:3.8.1-21

Hi,

On Tue, Apr 18, 2017 at 11:42:34PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
> 
> >From the attached log (scroll to the bottom...):
> 
> 0m39.1s ERROR: FAIL: Broken symlinks:
>   /usr/bin/scan-build-py-3.8 -> 
> ../share/clang/scan-build-py-3.8/bin/scan-build
> 
> Looks like a change was unneccessarily backported from 3.9, since that was
> previously working correctly in 3.8

This is fixed in 1:3.8.1-21.

Ivo

--- End Message ---

Reply via email to