[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#980832: marked as done (nmu: tor_0.4.4.6-1)

Your message dated Sun, 7 Feb 2021 11:54:32 +0200
with message-id <CAM8zJQtaheSSC-KkorD-haRRZqrx4JPL_h2KoadScN7Y01=7Jw@mail.gmail.com>
and subject line Re: Bug#980832: nmu: tor_0.4.4.6-1
has caused the Debian Bug report #980832,
regarding nmu: tor_0.4.4.6-1
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 owner@bugs.debian.org
immediately.)


-- 
980832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980832
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

Hi!
The tor package is paranoid about version of libzstd, and currently says:

[warn] Tor was compiled with zstd 1.4.5, but is running with zstd 1.4.8.
↪ For safety, we'll avoid using advanced zstd functionality.

Whether or not this warning is dubious (#963151), for the lifetime of
Bullseye we can assume the upstream version of libzstd won't change.
Thus, a simple rebuild against bullseye's libzstd is a good enough
workaround.

nmu tor_0.4.4.6-1 . ANY . unstable . -m "Rebuild against libzstd 1.4.8"


Meow!
-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.11.0-rc4-00014-gc9b56d9c1053 (SMP w/64 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

--- End Message ---
--- Begin Message --- 
Hi Adam

On Sat, 23 Jan 2021 at 00:36, Adam Borowski <kilobyte@angband.pl> wrote:
> The tor package is paranoid about version of libzstd, and currently says:
>
> [warn] Tor was compiled with zstd 1.4.5, but is running with zstd 1.4.8.
> ↪ For safety, we'll avoid using advanced zstd functionality.
>
> Whether or not this warning is dubious (#963151), for the lifetime of
> Bullseye we can assume the upstream version of libzstd won't change.
> Thus, a simple rebuild against bullseye's libzstd is a good enough
> workaround.

I see tor 0.4.5.5-rc-1 was uploaded, so I presume a binNMU is no longer needed.

Regards
Graham

--- End Message ---
Reply to: