Your message dated Mon, 15 Jul 2019 16:36:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#931629: nmu: rebuild packages for binutils 2.32.51.x
has caused the Debian Bug report #931629,
regarding nmu: rebuild packages for binutils 2.32.51.x
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.)
--
931629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931629
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
Please binNUM these packages for the recent binutils upload to unstable:
boinc-app-eah-brp 0.20170426+dfsg-10
naev 0.7.0-2
tulip 4.8.0dfsg-2
wcc 0.0.2+dfsg-3 (amd64 only)
--- End Message ---
--- Begin Message ---
Hi Matthias,
On 08-07-2019 14:57, Matthias Klose wrote:
> Please binNUM these packages for the recent binutils upload to unstable:
>
> boinc-app-eah-brp 0.20170426+dfsg-10
> naev 0.7.0-2
> tulip 4.8.0dfsg-2
> wcc 0.0.2+dfsg-3 (amd64 only)
boinc-app-eah-brp can't be rebuild (#887880).
tulip can't be rebuild (#853688, filed by you).
binNMU'ed wcc and naev.
Thanks.
Just one request, can you enlighten me as to where these strict
dependencies on libutils come from?
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
