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

Bug#925898: marked as done ([t-p-u, pre-approval] unblock: highwayhash/0~git20181002.c5ee50b-4)

Your message dated Mon, 8 Apr 2019 17:30:13 +0200
with message-id <20190408153012.6ifrjekqmlpdifcm@debian.org>
and subject line Re: [t-p-u, pre-approval] unblock: highwayhash/0~git20181002.c5ee50b-4
has caused the Debian Bug report #925898,
regarding [t-p-u, pre-approval] unblock: highwayhash/0~git20181002.c5ee50b-4
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.)


-- 
925898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925898
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: unblock

Please unblock package highwayhash

(explain the reason for the unblock here)

The C++ symbols changed somehow since the -3 upload, which
renders dpkg-gensymbols failure. However, the newer snapshot
in sid FTBFS on arm* so it would not migrate even if I fixed
the symbol lists. That means, well unfortunately, I have to
go through testing-proposed-updates.

Does it worth the effort to save the package for Buster?
src:highwayhash's popcon is quite low (~ 10), and it has
no reverse dependency in the archive except src:tensorflow.

If RT doesn't bother dealing with such a t-p-u case,
please feel free to close this bug and I'm totally fine
with that.

(include/attach the debdiff against the package in testing)

The difference will be merely some C++ symbol updates.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924840

unblock highwayhash/0~git20181002.c5ee50b-4

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi,

On Thu, Mar 28, 2019 at 05:06:59AM +0000, Mo Zhou wrote:
> (explain the reason for the unblock here)
> 
> The C++ symbols changed somehow since the -3 upload, which
> renders dpkg-gensymbols failure. However, the newer snapshot
> in sid FTBFS on arm* so it would not migrate even if I fixed
> the symbol lists. That means, well unfortunately, I have to
> go through testing-proposed-updates.
> 
> Does it worth the effort to save the package for Buster?
> src:highwayhash's popcon is quite low (~ 10), and it has
> no reverse dependency in the archive except src:tensorflow.
> 
> If RT doesn't bother dealing with such a t-p-u case,
> please feel free to close this bug and I'm totally fine
> with that.

So I'll close this bug. I also added a removal hint for highwayhash.

Ivo

--- End Message ---
Reply to: