Bug#799268: RFS: ck/1.6.2 [ITP]

["Grigori Fursin" <grigori.fursin@ctuning.org>]

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 ...

> rules --> export PYBUILD_NAME and use pybuild
> control --> add python3 dependencies and the package
Done.

> changelog --> rename it to ck?

I couldn't change it to ck, since I still release package
as python-ck ...

> and maybe something more.
>
> For sure you need to have the same codebase and two binaries.
> (mentors/lintian can give you hints about what you need to change).

It seems to be fine now.

> Since you are providing one binary and two libraries, you might want to 
> conflict them each other

Yeap, added that and tested - seems to be working fine!

> BTW
> copyright needs some care:
> ck/repo/module/web/php/openme.php: *No copyright* LGPL (v2.1 or later)

Thanks for noting that - I changed that to original CK license ...

There are just a few pedantic warnings about
* application-in-library-section
* library-package-name-for-application

But I can't change that - in fact I saw some notes suggesting
to just ignore (or override) this message in my case.

I hope it's ok now ;) ...

Thanks a lot again,
Grigori