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

Bug#875483: marked as done (nmu: why_2.39-1)

Your message dated Wed, 27 Sep 2017 00:35:49 +0200
with message-id <1d122ae9-d502-e821-4f6c-694f1ddab1fb@debian.org>
and subject line Re: Bug#875483: nmu: why_2.39-1
has caused the Debian Bug report #875483,
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 owner@bugs.debian.org
immediately.)


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

Hi, why needs a bin NMU against the latest version of frama-c:

nmu why_2.39-1 . ANY -m 'rebuild against frama-c 20170501+phosphorus+dfsg-2'

Thanks -Ralf.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 11/09/17 20:35, Ralf Treinen wrote:
> Package: release.debian.org
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> Severity: normal
> 
> Hi, why needs a bin NMU against the latest version of frama-c:
> 
> nmu why_2.39-1 . ANY -m 'rebuild against frama-c 20170501+phosphorus+dfsg-2'

Scheduled, see #875403.

Emilio

--- End Message ---
Reply to: