Your message dated Wed, 29 Nov 2023 11:04:09 +0000
with message-id <[email protected]>
and subject line Bug#1056126: fixed in llvm-toolchain-17 1:17.0.6-1
has caused the Debian Bug report #1056126,
regarding libclang1-17: libclang-17.so.1 uses wrong SONAME
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.)


-- 
1056126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056126
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libclang1-17
Version: 1:17.0.5-1
Severity: normal
X-Debbugs-Cc: [email protected]

Dear Maintainer,

libclang-17.so.1 specifies the wrong SONAME,
namely the full revision like for example:
'libclang-17.so.17.0.5'

It should be 'libclang-17.so.1'.

Otherwise users of the library like doxygen will
need to be rebuilt for every patch release.



-- System Information:
Debian Release: 12.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libclang1-17 depends on:
ii  libc6       2.36-9+deb12u3
ii  libgcc-s1   12.2.0-14
ii  libllvm17   1:17.0.5-1
ii  libstdc++6  12.2.0-14

libclang1-17 recommends no packages.

libclang1-17 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-17
Source-Version: 1:17.0.6-1
Done: Sylvestre Ledru <[email protected]>

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-17, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sylvestre Ledru <[email protected]> (supplier of updated llvm-toolchain-17 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 28 Nov 2023 11:43:43 +0100
Source: llvm-toolchain-17
Architecture: source
Version: 1:17.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <[email protected]>
Changed-By: Sylvestre Ledru <[email protected]>
Closes: 1056126 1056580
Changes:
 llvm-toolchain-17 (1:17.0.6-1) unstable; urgency=medium
 .
   [ Matthias Klose ]
   * Further limit the number of parallel processes
   * Don't build-depend on llvm-spirv-17 on armel and mipsel (LLVM 17 is not
     yet built on these architectures).
   * Fix stripping build flags on Ubuntu/ppc64el.
   * libclang1-17: Only encode the major version in the soname. Closes: 
#1056126.
   * libclang1-17: Provide a symlink for the last soname with the full version.
   * Restore the patch for D148945, searching /usr/lib/llvm-17/lib by default.
     Closes: #1056580.
 .
   [ Sylvestre Ledru ]
   * New upstream release
   * Add a symlink for libc++experimental.a to /usr/lib/*/libc++experimental.a
     to fix https://github.com/llvm/llvm-project/issues/72753
   * try to relax the wasi-libc dep declaration for apt.llvm.org
   * add a check that, if we are going to build wasm, wasi-libc is installed
     on the system
 .
   [ John Paul Adrian Glaubitz ]
   * Don't install *clang_rt* on sparc and sparc64
Checksums-Sha1:
 a3450ba385c7ccfb083e14d989fede733ce53c3b 8059 llvm-toolchain-17_17.0.6-1.dsc
 87dbe5554a6f3e070c6e99771c9084db4cecc132 148234752 
llvm-toolchain-17_17.0.6.orig.tar.xz
 d51aeac61ef5fcde54b2f9a7de688b18f70d3b0b 170576 
llvm-toolchain-17_17.0.6-1.debian.tar.xz
 41a2ee3d793304d4ef35a80c9ab04a200cdbe1d6 34446 
llvm-toolchain-17_17.0.6-1_amd64.buildinfo
Checksums-Sha256:
 34e3a75d69e5725db857d79592cf5b986bf97e8257bc4fa06d8cd8ceca8b04a4 8059 
llvm-toolchain-17_17.0.6-1.dsc
 04c12edc1995d9bb15da30d69f0207dda43b7833eaa989176c099e465cd38aee 148234752 
llvm-toolchain-17_17.0.6.orig.tar.xz
 9e813430eb46998cd0e5e4bce44693fb18225dfd6bab4ae7c6d3403d2847be1a 170576 
llvm-toolchain-17_17.0.6-1.debian.tar.xz
 c65ceda88a43cc7175d97ff8a41baf67a531d03ed54d1a654bb725be5266f072 34446 
llvm-toolchain-17_17.0.6-1_amd64.buildinfo
Files:
 d7f128fa9f1360b22306386bfbdce8ae 8059 devel optional 
llvm-toolchain-17_17.0.6-1.dsc
 c8e30b4d7a52a4535e0a8e98df21c1e6 148234752 devel optional 
llvm-toolchain-17_17.0.6.orig.tar.xz
 f63f1d7d8680c2d17d7f0a95924c8179 170576 devel optional 
llvm-toolchain-17_17.0.6-1.debian.tar.xz
 6e33c052d4044d67dc052ca883ba74c7 34446 devel optional 
llvm-toolchain-17_17.0.6-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmVnEiAACgkQfmUo2nUv
G+HK6BAAkqLRSXlBOqLp2znV9xP2LYnybsIZE78/sWYK+l70dGQ9aAEYU7JW9Ql5
DtzUZzBKrluYaxnkoFepTIsxDcvjfq3LHEGIqs5v5IfcMVTDAHBRFdV3mPAcYna9
mp3ulK7kk192sVHBnh7dBX6S/DqxYfMZFJxQMUKAsczCU8eOevglW6C1CFF/CgC0
FWGZK3E8x1qj6EeubJlscUSktQUf4QUpQJcR7JXMaxsUV6ioESU47J9v1Sd9UcBn
/kkaMX+Ax/L5czL8Qk7v/I86idw+geLA3WPST7a9Od+nZIs5yiPbZbbW3NvMg0D3
mfSwPMB5ZedgH91U4iALYwLbGyC+x7ESz6Ep6AUhMj1YNL49FSBGXfESPERc5zkW
2J6jw8tsLU+X7wKVr4H8GXuULEK1IeluQyzFApV2066ENK7ZUBT+hYOJrZOiKHpe
qUsyjwFcH8wVuMZn/dk1U488a5zaH6iDnkFGQV2nuJNoYxPMt1szAJ2PuQ7CTSax
m+zNwtzt17599oIGvYXRfOnN57KTW6b6j1w5YtRIpkvzRnGoHt9DQkXjLEXyDL6r
6/spFlxl3HtIn3SWw19tooF8V3gOUzCR0cCjGNag2lB16oERXyK6vVREak+GDh9h
RabSEk4crwCAJcQGSN1qMSs5IXWxcDyQekQqkU/AQei6ab86THA=
=2XHW
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to