Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add Debian packaging #71

Conversation

enneamer
Copy link

I have tried to build it with git-buildpackage on Debian Bookworm, and it works. Maybe it needs some linting, but I think we can save it for later.

Copy link
Owner

@gsauthof gsauthof left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you plan to integrate such a package into the debian distribution?

What are the steps to build such a package?

debian/copyright Show resolved Hide resolved
debian/copyright Show resolved Hide resolved
debian/copyright Show resolved Hide resolved
debian/watch Outdated Show resolved Hide resolved
debian/control Outdated Show resolved Hide resolved
@enneamer
Copy link
Author

enneamer commented Aug 20, 2023

Thank you for your review, @gsauthof .

Do you plan to integrate such a package into the debian distribution?

Sorry that I did not make my intention clear. In this pull request, I merely add necessary code for Debian packaging. This can help people who wish to build a Debian/Ubuntu package to deploy on their own machines, especially when they have many machines to manage and wish to share a system package for easier deployment. In addition, in case this project is to adopt GitHub Actions to offer pre-built packages in the future, this PR might be helpful. (I am aware that there are solutions to packages for many distros. I am not sure how well they would work for system packages like this, which might need distro-specific modifications.)

What are the steps to build such a package?

I should have included information like this. Do you mind me putting it in README.md in the PR?

@enneamer enneamer force-pushed the upstream-pr/feat/add-debian-packaging branch 2 times, most recently from c39f9ef to b475090 Compare August 20, 2023 05:47
@enneamer
Copy link
Author

I have added a packaging guide in README.md.

README.md Outdated Show resolved Hide resolved
@gsauthof
Copy link
Owner

Say I'll merge your pull-request - would you be available to help out with issues/pull-request reported on that debian packaging (in case there are any)?

Ideally, having the debian packaging stuff in this repository would be just a temporary solution until a debian packager adds a dracut-sshd package to the official Debian repository.
Then the debian packaging files could be maintained outside of this repository.

FWIW, I packaged some software for debian more than a decade ago but repressed most memories.
Especially the debian way of splitting the packaging specification over a multitude of files annoyed me very much.

For Fedora and other RPM distributions (where dracut-sshd isn't an official package yet) I'm using the COPR service.
Is there something similar for debian?

@enneamer enneamer force-pushed the upstream-pr/feat/add-debian-packaging branch from b475090 to d3d8f1e Compare August 27, 2023 00:08
@enneamer
Copy link
Author

I'll be glad to deal with issues and PRs related to Debian packaging. I have added relavant information in debian/README.md.

And I agree that it would be better to have a Debian maintainer to take on the work. Yet I haven't seen a packaging request on bugs.debian.org , so I guess it won't happen very soon.

As for third-party package hosting, Debian itself does not have an official platform similar to COPR to my best knowledge. Ubuntu has PPAs, and many contributors publish their Debian packages there as well. For non-official ones, packagecloud.io provides unified hosting across many distros, including DEB and RPM.

@gsauthof
Copy link
Owner

Ok, I came to the conclusion that this repository isn't the best place for debian packaging files.

If not already present I would even put the RPM packaging into a separate repository, today.

So the alternatives are:

  1. try to get dracut-sshd into the official Debian package repository
  2. create a separate github repository for debian packaging

Either way, I'm happy to link any such effort from the README, if something materializes.

@gsauthof gsauthof closed this Jul 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants