Bug#860528: Acknowledgement (nmu: libev_1:4.22-1)

2017-04-20 Thread Niels Thykier
SJ Zhu: >> I have scheduled the binNMU, but binNMUs cannot close bugs. Please >> verify that the binNMU works, appears in testing and then close the bug. >> > > Hi, > Could you check why it still haven't appeared in sid? > > Thanks > Shengjing Zhu > I had typo'ed the command; I have

Bug#860528: Acknowledgement (nmu: libev_1:4.22-1)

2017-04-20 Thread SJ Zhu
> I have scheduled the binNMU, but binNMUs cannot close bugs. Please > verify that the binNMU works, appears in testing and then close the bug. > Hi, Could you check why it still haven't appeared in sid? Thanks Shengjing Zhu

Bug#860528: Acknowledgement (nmu: libev_1:4.22-1)

2017-04-18 Thread Jérémy Lal
2017-04-18 11:32 GMT+02:00 Adam D. Barratt : > 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

Bug#860528: Acknowledgement (nmu: libev_1:4.22-1)

2017-04-18 Thread Adam D. Barratt
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. Regards,

Bug#860528: Acknowledgement (nmu: libev_1:4.22-1)

2017-04-18 Thread Jérémy Lal
My mistake, i meant to ask a binNMU in testing/unstable nmu libev_1:4.22-1 . ANY . stretch . -m "Rebuild to Close #860301"