Debian package names seem not to follow Debian naming standards #1163
gavanderhoorn
started this conversation in
General
Replies: 2 comments 3 replies
-
It's not just the filenames actually. The It's not strictly necessary to include the codename in the version I believe, as long as the versions are unique (ie: But Debian versioning is complex, so I may be wrong. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I think this issue actually stems from the macros for using CPack defined in |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Not sure this isn't intentional, so I didn't want to open an issue immediately.
Debian packages are supposed to follow a rather strict naming scheme, otherwise various tools related to packaging and repository management can't process them correctly.
In practice, this means
<PackageName>_<VersionNumber>-<DebianRevisionNumber>_<DebianArchitecture>.deb
.But the
.deb
s distributed as part of the Tesseract Release archives don't appear to adhere to this. Example:tesseract-motion-planners-trajopt-ifopt_amd64_linux_0.29.1.deb
.The parts are there (except the OS in the version), but not in the right order and the 'punctuation' isn't the same.
It should be:
tesseract-motion-planners-trajopt-ifopt_0.29.1-0jammy_amd64.deb
.Is the current naming the result of using CPack in a certain way to package for both Windows and Linux? Could it perhaps be tweaked to generate 'correct' Debian package names?
I ran into this when trying to import the
.deb
s into a multi-distribution APT repository which didn't work because the package names for different distributions are identical.Beta Was this translation helpful? Give feedback.
All reactions