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

Reinstate support for Debian Buster #266

Closed
apyrgio opened this issue Nov 25, 2022 · 2 comments
Closed

Reinstate support for Debian Buster #266

apyrgio opened this issue Nov 25, 2022 · 2 comments
Labels

Comments

@apyrgio
Copy link
Contributor

apyrgio commented Nov 25, 2022

Dangerzone originally supported Debian Buster, but support got dropped once it switched to Podman on Linux (d50b0c1), which is not available on Debian Buster.

We have previously fixed this issue for Ubuntu Focal (#206) by relying to external repos for installing Podman. We can do the same for Debian Buster, and we have a WIP branch for that (support-buster-kudu). However, the installation fails with:

The following packages have unmet dependencies:
 podman : Depends: libseccomp2 (>= 2.4.3-1) but 2.3.3-4 is to be installed
          Recommends: slirp4netns (>= 100:1.1.8-3) but it is not going to be installed
          Recommends: containernetworking-plugins (>= 100:1.0.0-1) but it is not going to be installed
          Recommends: uidmap but it is not going to be installed
          Recommends: fuse-overlayfs but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

(see also this failing build)

So, besides adding an external repo, we need to handle the libseccomp2 incompatibility.

@apyrgio
Copy link
Contributor Author

apyrgio commented Nov 25, 2022

I propose not including this in the 0.4.0 release, as the schedule is tight.

@apyrgio apyrgio mentioned this issue Nov 25, 2022
33 tasks
@apyrgio apyrgio mentioned this issue Feb 23, 2023
35 tasks
@deeplow
Copy link
Contributor

deeplow commented Mar 7, 2024

Debian buster is already EOL from the security standpoint. So I'll close the issue.

@deeplow deeplow closed this as completed Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants