Your message dated Sun, 16 Oct 2016 12:39:35 +0200 with message-id <6aa8a158-64f8-0a25-1c74-5f7b0558d...@debian.org> and subject line Re: libarchive12: ldconfig warns that libarchive.so.12 is not a symbolic link has caused the Debian Bug report #838243, regarding libarchive12: ldconfig warns that libarchive.so.12 is not a symbolic link 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.) -- 838243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: libarchive12 Version: 3.0.4-3+wheezy3 Severity: normal Dear Maintainer, After installing a recent security update for libarchive12:amd64 (3.0.4-3+wheezy3), the following message was displayed: Preparing to replace libarchive12:amd64 3.0.4-3+wheezy2 (using .../libarchive12_3.0.4-3+wheezy3_amd64.deb) ... Unpacking replacement libarchive12:amd64 ... Setting up libarchive12:amd64 (3.0.4-3+wheezy3) ... ldconfig: /usr/lib/x86_64-linux-gnu/libarchive.so.12 is not a symbolic link The ldconfig message regarding libarchive.so.12 now appears any time that ldconfig is run, e.g. by aptitude. The problem may be related to the updated .deb containing the libarchive.so.12 file rather than a link to libarchive.so.12.0.4, as in the previous package. Here is a debdiff for the current version and its predecessor: ======================================= $ debdiff old/libarchive12_3.0.4-3+wheezy2_amd64.deb new/libarchive12_3.0.4-3+wheezy3_amd64.deb [The following lists of changes regard files as different if they have different names, permissions or owners.] Files in second .deb but not in first ------------------------------------- -rw-r--r-- root/root /usr/lib/x86_64-linux-gnu/libarchive.so.12 Files in first .deb but not in second ------------------------------------- lrwxrwxrwx root/root /usr/lib/x86_64-linux-gnu/libarchive.so.12 -> libarchive.so.12.0.4 Control files: lines which differ (wdiff format) ------------------------------------------------ Installed-Size: [-671-] {+1290+} Version: [-3.0.4-3+wheezy2-] {+3.0.4-3+wheezy3+} ======================================= -- System Information: Debian Release: 7.11 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libarchive12 depends on: ii libacl1 2.2.51-8 ii libattr1 1:2.4.46-8 ii libbz2-1.0 1.0.6-4 ii libc6 2.13-38+deb7u11 ii liblzma5 5.1.1alpha+20120614-2 ii libnettle4 2.4-3+deb7u1 ii libxml2 2.8.0+dfsg1-7+wheezy6 ii multiarch-support 2.13-38+deb7u11 ii zlib1g 1:1.2.7.dfsg-13 libarchive12 recommends no packages. libarchive12 suggests no packages.
--- End Message ---
--- Begin Message ---Version: 3.0.4-3+wheezy4 On 19/09/16 17:58, Jonas Meurer wrote: > Hello Bruce, > > Am 19.09.2016 um 14:47 schrieb Bruce Toll: >> I reported a bug with the recent (Sept. 10) libarchive12 security update >> (Debian BTS 838243) and heard back from Andreas Henriksson that I should >> reach out to the package uploader and Debian LTS team directly. >> >> I appreciate the great work that you and the LTS team are doing to keep >> wheezy secure. The issue seems fairly minor and is described in the bug >> tracker, https://bugs.debian.org/838243. Thanks! > > Thanks for your bugreport. Indeed, it looks like, something went wrong > with the build of libarchive12 3.0.4-3+wheezy3 on amd64. For the other > supported archs, everything seems fine. > > I suspect that this is due to me building the amd64 binaries inside a > virtualbox VM with the build directory mounted as vboxsf share mount. > Apparently, symlinks get screwed up up on vboxsf mounts. > > Another LTS update of libarchive is underway anyway, Emilio Pozuelo > Monfort is working on it. I suggest to wait until his upload, which will > fix the bug (except if he builds on a vboxsf share as well) :) Heh, I didn't. Sorry for the delay, but this is finally fixed. I forgot to mention this in the new DLA. I don't think sending another announcement is needed, as this was only causing a warning, but things were still working fine. Let me know if that was not the case and we can send a regression announcement. Thanks, Emilio
--- End Message ---
