[pkg-bacula-devel] Revive bacula-python or add pything3 as Dependency?
Carsten Leonhardt
leo at debian.org
Sun Feb 18 22:35:04 GMT 2024
Hi Sven,
Sven Hartge <sven at svenhartge.de> writes:
> Hi!
>
> Because of the python scripts /etc/bacula/scripts/md5tobase64.py and
> /etc/bacula/scripts/key-manager.py, Lintian will now complain at the
> Error level with python3-script-but-no-python3-dep.
>
> So question now is:
>
> 1) Move those scripts (at whatever final location they end up) to
> something like bacula-python
>
> or
>
> 2) Just add python3 as dependency to bacula-sd and bacula-dir.
>
> I think 2) would be fine, python3 is basically "essential" now, with
> apt depending on it.
In all consequence option 1) would mean two more packages,
bacula-sd-python and bacula-dir-python. I don't like it.
I was wondering if a Recommends would be sufficient, otherwise a Depends
would be ok.
- Carsten
PS: I also saw the failed piuparts due to the database upgrade, I didn't
have time yet to look at it. I was hoping the database upgrade extractor
could be revived and gave it a shot without testing or verifying the
result.
More information about the pkg-bacula-devel
mailing list