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

Reported Upsteam: lintian: unknown-control-file [sha256sums] #152

Open
dcampbell24 opened this issue Nov 5, 2024 · 3 comments
Open

Reported Upsteam: lintian: unknown-control-file [sha256sums] #152

dcampbell24 opened this issue Nov 5, 2024 · 3 comments

Comments

@dcampbell24
Copy link
Contributor

FYI, I reported this issue upstream: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1086739

@dcampbell24 dcampbell24 changed the title Reported Upsteam: unknown-control-file [sha256sums] Reported Upsteam: lintian: unknown-control-file [sha256sums] Nov 5, 2024
@dcampbell24
Copy link
Contributor Author

Note: dpkg --debug=100 --verify package-name prints the md5sum values of all the files in the package. There are no other algorithms supported by dpkg.

@dcampbell24
Copy link
Contributor Author

To quote the dpkg manpage:

-V, --verify [package-name...]

Verifies the integrity of package-name or all packages if omitted, by comparing information from the files installed by a package with the files metadata information stored in the dpkg database (since dpkg 1.17.2). The origin of the files metadata information in the database is the binary packages themselves. That metadata gets collected at package unpack time during the installation process.

Currently the only functional check performed is an md5sum verification of the file contents against the stored value in the files database. It will only get checked if the database contains the file md5sum. To check for any missing metadata in the database, the --audit command can be used.

The output format is selectable with the --verify-format option, which by default uses the rpm format, but that might change in the future, and as such, programs parsing this command output should be explicit about the format they expect.


So it sounds like if you are going to include a hash file, you should include md5sum. I am waiting for a useful response from my upstream report.

@dcampbell24
Copy link
Contributor Author

Also the deb-md5sums man page.

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