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

Bug#852693: marked as done (nmu: llvm-defaults_0.34)



Your message dated Fri, 27 Jan 2017 00:49:11 +0100
with message-id <9be4878d-fea6-98a8-a74c-11aa6818ac1c@debian.org>
and subject line Re: Bug#852693: nmu: llvm-defaults_0.34
has caused the Debian Bug report #852693,
regarding nmu: llvm-defaults_0.34
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.)


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

I messed up the version number in #851436, assume that's the
reason why no binNMU happened after it was scheduled.

nmu llvm-defaults_0.34 . armel . unstable . -m "llvm-toolchain-3.8 is now available on armel"

--- End Message ---
--- Begin Message ---
On 26/01/17 14:54, Adrian Bunk wrote:
> On Thu, Jan 26, 2017 at 03:46:21PM +0200, Adrian Bunk wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian.org@packages.debian.org
>> Usertags: binnmu
>>
>> I messed up the version number in #851436, assume that's the
>> reason why no binNMU happened after it was scheduled.
>>
>> nmu llvm-defaults_0.34 . armel . unstable . -m "llvm-toolchain-3.8 is now available on armel"
> 
> Looking at control and the m-a:same comment in #851995,
> this should be:
> 
> nmu llvm-defaults_0.34 . ANY . unstable . -m "llvm-toolchain-3.8 is now available on armel"

Scheduled.

Emilio

--- End Message ---

Reply to: