Bug#799268: RFS: ck/1.6.2 [ITP]
Dear colleagues,
I fixed all the issues with my package, added the latest
upstream release, and uploaded the new version to Debian mentors:
http://mentors.debian.net/package/python-ck
The only problem is that I have an error message there
"Bug #799268 does not belong to this package"
Can it be because I originally submitted a request
for package 'ck' and not 'python-ck'?
Is there a way to change it?
Thanks a lot and have a good week,
Grigori
-----Original Message-----
From: Grigori Fursin
Sent: Saturday, September 19, 2015 11:18 AM
To: Gianfranco Costamagna ; Lucas Nussbaum ; 799268@bugs.debian.org
Subject: Bug#799268: RFS: ck/1.6.2 [ITP]
Actually, it's done more or less like that.
ck is a batch script that sets environment and calls python module.
So, it should be easy to change the name if will be required.
However, I made some search and didn't not find obvious conflicts so far ;)
...
Thanks,
Grigori
-----Original Message-----
From: Gianfranco Costamagna
Sent: Friday, September 18, 2015 4:02 PM
To: Lucas Nussbaum ; Grigori Fursin ; 799268@bugs.debian.org
Subject: Bug#799268: RFS: ck/1.6.2 [ITP]
Oh, I didn't know that :( . Will it really be a problem (I didn't see any
tool called ck yet)? The problem is that our users now share some
artifacts
in this format and they use this name (in scripts or internal calls),
so changing this name now will be a nightmare :( ...
I'm not sure if there's an official policy about that. It's probably
worth trying to upload with a ck binary, and see if someone complains :)
I guess you can always install a longer name and create a symlink to ck.
(and bother upstream about it)
this way people can move to the new binary, and if somebody complain you can
"safely" drop the symlink.
(or use some "update-alternative" tools I don't remember how)
Just my .02$
G.
Reply to: