Closed thegranddesign closed 4 months ago
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems.
Looks like issue with Packaging / CI cc @joshuaboniface
We've never signed our .deb
files in the past as far as I'm aware.
It's certainly something we can start doing though. I'll look into it.
Implemented!
My monthly donations put to good use! :heart: Thank you so much!!
Please describe your bug
Currently the DEB file is failing verification. It's been a while but based on my install scripts that I used, I'm fairly certain that the DEB file used to verify. The issue is that the DEB file itself is not being signed.
The solution is to add a step to the build process that runs something like:
This will add a file to the DEB file that includes a signature.
It should also be straightforward to sign the
.changes
and.dsc
files as well which would be useful for others. Although for my purposes I only really care about verifying the actual DEB that I'm going to install directly.Reproduction Steps
/usr/share/debsig/keyrings/49023CD01DE21A7B/debsig.gpg
/etc/debsig/policies/49023CD01DE21A7B/debsig.pol
debsig-verify ./<jellyfin_deb_file>.deb
Example
debsig.pol
file:Actual Behavior
Message stating:
Expected Behavior
I expect that there will be a message stating that the DEB file is valid.
Jellyfin Version
10.8.13
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct