Your message dated Tue, 18 Apr 2017 10:43:00 +0000
with message-id <[email protected]>
and subject line Re: Bug#860528: Acknowledgement (nmu: libev_1:4.22-1)
has caused the Debian Bug report #860528,
regarding nmu: libev_1:4.22-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.)
--
860528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860528
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
nmu libev_1:4.22-1 . ANY . jessie . -m "Rebuild to Close #860301"
I don't really understand what's going on...
bug reporter says it's fixed when rebuilt. So let's rebuild !
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (1001, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Jérémy Lal:
> 2017-04-18 11:32 GMT+02:00 Adam D. Barratt <[email protected]>:
>> On 2017-04-18 10:15, Jérémy Lal wrote:
>>>
>>> My mistake, i meant to ask a binNMU in testing/unstable
>>>
>>> nmu libev_1:4.22-1 . ANY . stretch . -m "Rebuild to Close #860301"
>>
>>
>> For a rebuild in unstable, that's still wrong, I'm afraid - just drop the "
>> . stretch", as unstable is the default.
>
> Should the request be for unstable, and then an unblock request so it
> goes to stretch ?
>
> I'm confused.
> Jérémy
>
Just a binNMU request for unstable. binNMUs migrate automatically if
they can (e.g. same source version in unstable and testing).
I have scheduled the binNMU, but binNMUs cannot close bugs. Please
verify that the binNMU works, appears in testing and then close the bug.
Thanks,
~Niels
--- End Message ---
