[elbe-devel] [PATCH v2 06/27] debian: rename pkg elbe-daemon to python3-elbe-daemon

[Bastian Germann]

Am 25.09.20 um 08:59 schrieb Torben Hohn:
> On Thu, Sep 24, 2020 at 07:21:57PM +0200, Bastian Germann wrote:
>> Am 24.09.20 um 16:56 schrieb Torben Hohn:
>>> Somehow dh_install installs python modules to /usr/lib/python3
>>> when a package name starts with python3-.
>>> This was not the case for elbe-daemon and the files were installed
>>> to /usr/lib/python3.7/. That prevents elbe from finding the "daemon"
>>> command, and the daemon in the initvm can not start.
>>>
>>> Rename all packages containeing commands to python3-* and adjust depends.
>>
>> containing
>>
>>> Also fix the packagenames to be installed into the initvm in
>>> elbepack/version.py and change the defaults filename in the service file.
>>>
>>> Signed-off-by: Torben Hohn <torben.hohn at linutronix.de>
>>
>> First off: The commit title has to be changed, because it is not only
>> elbe-daemon that is changed.
> 
> agreed.
> 
>>
>>
>> I guess you can make pybuild/dh_python3
>> install the packages somehow without the second version info.
> 
> i hoped that too. but could no find anything.

I also took a look and did not find anything.

>>
>> Actually, especially for python modules with an executable the
>> convention is not to have the python3- pkg prefix.
> 
> the commands are no executables.
> the only existing executable is /usr/bin/elbe 
> 
> 
>>
>> If you do not find info on that, please change the install files to have
>> the right paths in place.
> 
> i have looked around, and did not find out, why this is happening,
> and how it can be controlled.
> 
> I would need to look into the sourcecode to find out, why
> this is happening.

Just leave the files as they are right now. The install files are okay
as well.

With the title change:
Reviewed-by: Bastian Germann <bage at linutronix.de>