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

RPM name collision on Fedora / Enterprise Linux #56

Open
lexpierce opened this issue Mar 28, 2024 · 1 comment
Open

RPM name collision on Fedora / Enterprise Linux #56

lexpierce opened this issue Mar 28, 2024 · 1 comment

Comments

@lexpierce
Copy link

There is a name collision in the default repo for Fedora / Enterprise Linux with an older archive utility. Here is the output of dnf5 info freeze. Due to the version number it will want to upgrade a manually installed RPM to the other package.

Name           : freeze
Epoch          : 0
Version        : 0.1.4
Release        : 1
Architecture   : i386
Download size  : 4.6 MiB
Installed size : 11.1 MiB
Source         :
Repository     : charm
Summary        : Generate images of code and terminal output.
URL            :
License        :
Description    : Generate images of code and terminal output.
Vendor         : <NULL>

Name           : freeze
Epoch          : 0
Version        : 2.5.0
Release        : 36.fc39
Architecture   : x86_64
Download size  : 35.1 KiB
Installed size : 59.7 KiB
Source         : freeze-2.5.0-36.fc39.src.rpm
Repository     : fedora
Summary        : freeze/melt/fcat compression utilities
URL            :
License        : GPL+
Description    : Freeze is an old file compressor and decompressor that is not in
               : common use anymore, but can be useful if the need ever arises to
               : dearchive files compressed with it.
Vendor         : Fedora Project

For this to be more easily redistributable to a dev team, it might be nice to change the package name, perhaps something like freeze-charm? We certainly don't have (the older) freeze installed anywhere, but this collision means I would need to distribute it outside the standard channels, or rebuild/rename the RPM.

@meowgorithm
Copy link
Member

Why don’t we go with charm-freeze; we had to do the same for Nixpkgs.

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