Hi Grigori, the RFS is already fine and you are just missing the ITP. ITP means "I want to package this foo for Debian" and you close it in your changelog
RFS (this bug #799268) means: I want to find a sponsor, because I'm not able to directly upload on Debian. this RFS is closed by your sponsor when the upload is performed, the other bug (*A NEW BUG*) needs to be opened and closed in the upload in this way: * Initial Release (Closes: #XXXXX) where XXXXX is the ITP bug. cheers, G. Il Martedì 10 Novembre 2015 10:09, Grigori Fursin <grigori.fur...@ctuning.org> ha scritto: Hi Lucas, Do you mean that I should open a separate ticket (RFS)? Or since the package now seems to be okeish, should I just continue searching for a sponsor? Thanks, Grigori -----Original Message----- From: Lucas Nussbaum Sent: Tuesday, November 10, 2015 9:38 AM To: Grigori Fursin Cc: Gianfranco Costamagna ; 799...@bugs.debian.org Subject: Bug#799268: RFS: ck/1.6.2 [ITP] On 07/11/15 at 16:21 +0100, Grigori Fursin wrote: > Hi Gianfranco, > > After hacking various guides I managed to update python-ck > based on what you mentioned: > > >https://mentors.debian.net/package/python3-ck > >this is a nack for me. > > > >You can build two binaries with the same source package, look e.g. to > >https://sources.debian.net/src/python-esmre/0.3.1-3/ > > I have done that and deleted separate python3-ck package. > > >this includes: > >compat level --> 9 > >debhelper >= 9 > > Done. > > >ITP bug? > I changed it as ITP bug. It still complains and I guess > this can only be fixed when I find a sponsor ... you need both an ITP bug (because it's a new package) and an RFS bug (because you are looking for a sponsor) Lucas
