Your message dated Mon, 2 May 2016 13:28:28 +0200
with message-id 
<cak0odpyxz7jzdfuvihagd6+pzmpp4owxhmhr+d8si3am5u2...@mail.gmail.com>
and subject line Re: Bug#823206: gb: armhf kodi_16.1+dfsg1-1
has caused the Debian Bug report #823206,
regarding gb: armhf kodi_16.1+dfsg1-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.)


-- 
823206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823206
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
User: [email protected]
Usertags: binnmu
Severity: normal
X-Debbugs-CC: [email protected]

Hi,

Build of kodi failed on buildd, but I have successfully rebuilt it
on debomatic from the same source:
http://debomatic-armhf.debian.net/distribution#unstable/kodi/16.1+dfsg1-1/buildlog

Please trigger a rebuild to have official builds for the package.

 gb kodi_16.1+dfsg1-1 . armhf

Thanks,
Balint

--- End Message ---
--- Begin Message ---
Hi Adam,

2016-05-02 13:08 GMT+02:00 Adam D. Barratt <[email protected]>:
> On Mon, 2016-05-02 at 10:17 +0200, Bálint Réczey wrote:
>> Package: release.debian.org
>> User: [email protected]
>> Usertags: binnmu
> [...]
>> Build of kodi failed on buildd, but I have successfully rebuilt it
>> on debomatic from the same source:
>> http://debomatic-armhf.debian.net/distribution#unstable/kodi/16.1+dfsg1-1/buildlog
>>
>> Please trigger a rebuild to have official builds for the package.
>>
>>  gb kodi_16.1+dfsg1-1 . armhf
>
> "Usertags: binnmu"
>
> As explained previously:
>
> That's not a binNMU, it's a give-back - hence "gb". Please don't use
> binNMU requests for wanna-build actions that aren't binNMUs - other
> actions should be directed to [email protected] or
> [email protected], as per
> http://lists.debian.org/debian-project/2009/03/msg00096.html

Sorry, closing this bug.

Thanks,
Balint

--- End Message ---

Reply via email to