Your message dated Sun, 10 Jun 2018 20:22:36 +0200
with message-id <[email protected]>
and subject line Re: Bug#900514: nmu: gnucobol_2.2-1
has caused the Debian Bug report #900514,
regarding nmu: gnucobol_2.2-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 [email protected]
immediately.)
--
900514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900514
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
Another case of a package which was uploaded before the ncurses
transition and got stuck in NEW for too long.
nmu gnucobol_2.2-1 . amd64 . unstable . -m "Rebuild against libncurses6."
--- End Message ---
--- Begin Message ---
On 2018-05-31 19:09 +0200, Sven Joachim wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
>
> Another case of a package which was uploaded before the ncurses
> transition and got stuck in NEW for too long.
>
> nmu gnucobol_2.2-1 . amd64 . unstable . -m "Rebuild against libncurses6."
Looks like this has been done in the meantime.
--- End Message ---
