Your message dated Sat, 24 Aug 2019 11:03:14 +0200
with message-id <91e28875-132a-e721-ce72-8510c1245...@debian.org>
and subject line Re: nmu: Please binNMU the following packages that have not 
been built on a buildd
has caused the Debian Bug report #932702,
regarding nmu: Please binNMU the following packages that have not been built on 
a buildd
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.)


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

Hello,

So apparently I missed the memo and my first round of packages uploaded to 
unstable after the release have not been built on a buildd.

Could it be possible to binNMU them?

libsepol must probably be rebuilt first as other packages are statically
linking against it and are adding a Built-Using field:
nmu libsepol_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"

nmu checkpolicy_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
nmu libselinux_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
nmu mcstrans_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
nmu policycoreutils_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
nmu restorecond_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
nmu semodule-utils_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
nmu setools_4.2.2-1 . amd64 . unstable . -m "Rebuilt on a buildd"

nmu deja-dup_40.1-1 . amd64 . unstable . -m "Rebuilt on a buildd"

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

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

On Mon, 22 Jul 2019 02:13:38 +0200 Laurent Bigonville <bi...@debian.org>
wrote:
> Could it be possible to binNMU them?
> 
> libsepol must probably be rebuilt first as other packages are statically
> linking against it and are adding a Built-Using field:
> nmu libsepol_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
> 
> nmu checkpolicy_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
> nmu libselinux_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
> nmu mcstrans_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"

I checked till here. This was all done two weeks ago.

> nmu policycoreutils_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
> nmu restorecond_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
> nmu semodule-utils_2.9-2 . amd64 . unstable . -m "Rebuilt on a buildd"
> nmu setools_4.2.2-1 . amd64 . unstable . -m "Rebuilt on a buildd"
> 
> nmu deja-dup_40.1-1 . amd64 . unstable . -m "Rebuilt on a buildd"

I assume the rest was done as well.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to