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 name conflicts with official repository package #91

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

Debian package name conflicts with official repository package #91

cdhowie opened this issue Jan 17, 2024 · 3 comments

Comments

@cdhowie
Copy link

cdhowie commented Jan 17, 2024

The name of the Debian package is opentracker which conflicts with this package from the official Debian repository. This makes it impossible to have both packages installed at the same time.

If possible, please consider changing the name of the Debian package to resolve this conflict.

@trippsc2
Copy link
Owner

This doesn't appear to be able to be fixed without a different packaging method, as the "dotnet deb" command always creates a package named after the project.

I have very limited time to maintain the project at present. If you have ideas of how the app should be packages for Debian-based systems, I'd be happy to consider it. At present, I don't have to time research alternative build systems on my own.

I'm going to leave this open in case you or someone else has suggestions.

@cdhowie
Copy link
Author

cdhowie commented Dec 25, 2024

I suspect it also won't be as simple as changing the name of the package. I haven't checked, but it's likely that some files in both packages will also conflict, rendering one uninstallable while the other is.

I've built Debian packages by hand before (I had a package in the official repos for some years) and if I can find some time over the next few months I might try to build one by hand, assuming that you'd be open to merging that tooling and possibly maintaining it if I'm unable to maintain it for whatever reason.

@cdhowie
Copy link
Author

cdhowie commented Dec 25, 2024

For what it's worth, renaming the package without addressing the conflicting files is still vastly preferable to the current situation.

This is because installing this package while one already has opentracker installed from the official repos will replace the upstream package with this one, effectively uninstalling a program from the system. Having a differently-named package with conflicting files will cause the package installation to simply fail. The system administrator will then be aware that they can only install one or the other, but without clobbering software they've already installed without any warning.

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