[stork-users] Debian packaging problem with isc-stork-server
Slawek Figiel
slawek at isc.org
Mon Sep 12 10:09:51 UTC 2022
Hello Kevin!
I opened [#860](https://gitlab.isc.org/isc-projects/stork/-/issues/860)
to track and resolve your problem.
Our package scripts are quite old and require a bit of refactoring.
Maybe, we should split them and have dedicated files for each package
type instead of single, multi-distro scripts?
You're welcome if you want to look at the problem on your own. You can
find all needed files in the Stork repository.
The install and remove hook scripts are located in the /etc directory.
See also the .gitlab-ci.yml file and "build_debs", "build_rpms", and
"build_apks" to exact commands that we use to build packages.
Best regards
Slawek
On 10/09/2022 16:14, Kevin P. Fleming wrote:
> On Sat, Sep 10, 2022 at 9:57 AM Kevin P. Fleming <kevin at km6g.us> wrote:
>> I think this script's logic for determining which tool to use for
>> managing groups and users might need to be re-thought. I was able to
>> complete the installation by de-installing busybox.
> It looks like this script is an attempt to be multi-platform and is
> used in all of the various packages (RPMs, DEBs, FreeBSD, etc.). Given
> that, I'd suggest that it should trigger Debian-specific behavior
> based on the presence of /etc/debian_version (like it does for Red
> Hat-style systems).
>
> There's also another problem with this packaging: the 'prerm' script
> disables and stops the server process if 'systemctl' is present, but
> nothing enables and starts the service after installation (in
> 'postinst'). During a package upgrade the old version is removed and
> the new version is installed, and the result is that after the upgrade
> the server is not running and not even enabled to run.
>
> I'd be quite happy to help clean up this stuff for Debian systems if
> the packaging repository was visible to me :-)
More information about the Stork-users
mailing list