Your message dated Sun, 21 Oct 2018 20:44:08 +0200
with message-id <20181021184407.4vegzsczwigxs...@debian.org>
and subject line Re: nmu: octave-nlopt_2.4.2+dfsg-8~bpo9+1
has caused the Debian Bug report #911518,
regarding nmu: octave-nlopt_2.4.2+dfsg-8~bpo9+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.)
--
911518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911518
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 octave-nlopt_2.4.2+dfsg-8~bpo9+1 . ANY . stretch-backports . -m "Rebuild
against octave-4.4.1/liboctave6 in stretch-backports."
The octave backport has been updated since the octave-nlopt backport was
uploaded.
Andreas
--- End Message ---
--- Begin Message ---
Hi,
On Sun, Oct 21, 2018 at 11:08:05AM +0200, Andreas Beckmann wrote:
> nmu octave-nlopt_2.4.2+dfsg-8~bpo9+1 . ANY . stretch-backports . -m "Rebuild
> against octave-4.4.1/liboctave6 in stretch-backports."
The source package is nlopt, not octave-nlopt. Scheduled.
> The octave backport has been updated since the octave-nlopt backport was
> uploaded.
Thanks,
Ivo
--- End Message ---
