[ckan-dev] python-ckanclient on Debian Sid (unstable) and dpm packaging issues
Rufus Pollock
rufus.pollock at okfn.org
Tue Feb 21 09:34:24 UTC 2012
On 20 February 2012 00:03, J. Félix Ontañón <fontanon at emergya.es> wrote:
> El día 14 de febrero de 2012 16:52, J. Félix Ontañón
> <fontanon at emergya.es> escribió:
>>
>>>> Nowadays I'm working on dpm packaging[4] but got some issues:
>>>> * dpm package name is already used by Disk Pool Manager[5], part of
>>>> the gLite middleware suite.
>>>
>>> Hmm, I'd noticed that. What do you suggest? Is there an actual
>>> conflict in script name or just in package name. If the latter we
>>> could tweak the package name. If the former we have a trickier time.
>>
>> The point is that this two packages ..
>> * dpm-mysql
>> * dpm-postgresql
>> ... installs an exec on /usr/bin/dpm via update-alternatives method
>>
>> This means a conflict with the script name. A third solution would be
>> to tweak the script name at debian source package, maintaining dpm
>> name for the script at upstream. Anyway, i'll ask some debian
>> developers for solutions with similar scenarios.
>
> I've been asking some debian develpers. I'm afraid the suggested
> solution is to rename the dpm script at debian package building.
> This way dpm script at upstream remains the original name, and debian
> package name could be named dpm too.
I think that's fine. We can try and think of something. As a stop gap
let's just use the verbose datapackagemanager ....
Rufus
More information about the ckan-dev
mailing list