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

Debian package uninstallable on Bookworm due to missing dependencies #92

Closed
cdhowie opened this issue Jan 17, 2024 · 3 comments
Closed

Comments

@cdhowie
Copy link

cdhowie commented Jan 17, 2024

The Debian package has the following two dependencies that cannot be satisfied on Debian Bookworm (the current stable release):

  • libssl1.1 | libssl1.0.2 | libssl1.0.1 | libssl1.0.0 | libssl0.9.8
  • libicu70 | libicu69 | libicu68 | libicu67 | libicu66 | libicu65 | libicu64 | libicu63 | libicu62 | libicu61 | libicu60 | libicu59 | libicu58 | libicu57 | libicu56 | libicu55 | libicu54 | libicu53 | libicu52

Bookworm provides libssl3 and libicu72 only.

@cdhowie
Copy link
Author

cdhowie commented Jan 17, 2024

Note that I would be happy to submit a PR for this and #91 but I cannot find any tooling or build scripts to build the Debian package in the code repository, so I'm unsure how the packages were built in the first place or how I might submit these fixes.

@trippsc2
Copy link
Owner

I apologize for not giving this issue the attention it deserves.

The tool I used to build the Debian, RPM, and tarball packages is https://github.com/quamotion/dotnet-packaging. This tool, however, was not packaged for .NET 8 until recently. Another user has packaged them for .NET 8 on NuGet. https://www.nuget.org/profiles/digitalhigh

The tool uses the name of the project as the name of the package and that doesn't appear to be configurable. I think I should add a note to the README regarding the conflict and those users should use the tarball instead.

The reason the libssl and libicu packages are referenced as dependencies is due to me specifying the runtime identifier ("debian-x64" for Debian on x64). If that is not specified, no dependencies are added and that does not appear to cause problems launching the application, so I will fix that for the next release.

@trippsc2
Copy link
Owner

The latest package fixes this issue.

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

No branches or pull requests

2 participants