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 packaging - wrong debian changelog package name #213

Open
prahal opened this issue Sep 26, 2023 · 0 comments
Open

debian packaging - wrong debian changelog package name #213

prahal opened this issue Sep 26, 2023 · 0 comments

Comments

@prahal
Copy link

prahal commented Sep 26, 2023

The debian/changelog in the develop branch has NixNote as package name.
But Debian only allow lowercase in the package name.
Also, the package name in the debian/changelog has to match the one in the debian/control file (which is nixnote2).

LC_ALL=C dpkg-buildpackage -rfakeroot -b -us -uc -j4
dpkg-buildpackage: info: source package NixNote
dpkg-buildpackage: info: source version 2.1.10
dpkg-buildpackage: info: source distribution stable
dpkg-buildpackage: info: source changed by Robert Spiegel <[email protected]>
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
dpkg-source: error: source package name 'NixNote' is illegal: character 'N' not allowed
dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 255

once I lowercase to nixnote the package name in the changelog I get:

LC_ALL=C dpkg-buildpackage -rfakeroot -b -us -uc -j4
dpkg-buildpackage: info: source package nixnote
dpkg-buildpackage: info: source version 2.1.10
dpkg-buildpackage: info: source distribution stable
dpkg-buildpackage: info: source changed by Robert Spiegel <[email protected]>
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
dpkg-source: error: source package has two conflicting values - nixnote2 and nixnote
dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 255

I don't know the policy to migrate a package to a new name. I noticed that it could be via a transitional empty package with the old name that depends on the new name. I believe you also have to add conflicts/replaces to the new package control file to replace the old one properly.

Might be easier in the meantime to keep the name nixnote2. Or do you want to switch to nixnote?

https://www.debian.org/doc/debian-policy/ch-controlfields.html#source
Package names (both source and binary, see Package) must consist only of lower case letters (a-z), digits (0-9), plus (+) and minus (-) signs, and periods (.). They must be at least two characters long and must start with an alphanumeric character.

@prahal prahal changed the title debian pacakging - wrong debian changelog package name debian packaging - wrong debian changelog package name Oct 3, 2023
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

1 participant