Your message dated Wed, 27 Sep 2017 00:35:28 +0200
with message-id <4e860510-1a0f-ad27-c094-ec4bb4862...@debian.org>
and subject line Re: Bug#875403: nmu: why_2.39-1
has caused the Debian Bug report #875403,
regarding nmu: why_2.39-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 ow...@bugs.debian.org
immediately.)
--
875403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875403
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
nmu why_2.39-1 . ANY . unstable . -m "Rebuild against frama-c-base (=
20170501+phosphorus+dfsg-2)."
why has a very strict dependency on frama-c-base :-(
Andreas
--- End Message ---
--- Begin Message ---
On 11/09/17 10:33, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: binnmu
>
> nmu why_2.39-1 . ANY . unstable . -m "Rebuild against frama-c-base (=
> 20170501+phosphorus+dfsg-2)."
>
> why has a very strict dependency on frama-c-base :-(
Scheduled.
Emilio
--- End Message ---
