mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Debian unstable update/installation issue #3235
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ich777 on GitHub (Sep 8, 2021).
Describe the bug
Not sure but is something broken with the unstable builds for Debian or did I do something wrong? Every time I try to upgrade or install the necessary packages I get this:
This was working about 2 days ago flawlessly, did something change?
System (please complete the following information):
@aptalca commented on GitHub (Sep 11, 2021):
Same thing with the Ubuntu unstable repo:
@ich777 commented on GitHub (Sep 14, 2021):
Is there any information on this...
@joshuaboniface commented on GitHub (Sep 15, 2021):
Bullseye is now "stable", and we use the distro names in the repo.
Can you post your
sources.listentries?@ich777 commented on GitHub (Sep 15, 2021):
@joshuaboniface thank you for the response, here are the content from my
sources.list:This is how I added the Jellyfin source:
@joshuaboniface commented on GitHub (Sep 15, 2021):
OK that looks right to me. It does indeed look like something is borked on the repo side. We'll take a look.
@ich777 commented on GitHub (Sep 15, 2021):
Tried it again but still the same with the newest build:
@aptalca commented on GitHub (Sep 16, 2021):
@joshuaboniface just fyi, we see the same behavior with the ubuntu unstable repo as well
Here's a failed build: https://ci.linuxserver.io/blue/organizations/jenkins/Docker-Pipeline-Builders%2Fdocker-jellyfin/detail/nightly/1485/pipeline
And here's the Dockerfile: https://github.com/linuxserver/docker-jellyfin/blob/nightly/Dockerfile#L22
@joshuaboniface commented on GitHub (Sep 17, 2021):
So I've taken a look and it looks like it's just an issue with the metapackage
jellyfin. There's some versioning wonkiness with it compared to the others. I'm going to try to fix it, but that said, for right now (and for LSIO images, probably long-term too), a good workaround would be to ignore and remove thejellyfinmetapackage, and just manually installjellyfin-serverandjellyfin-webpackages. The metapackage was mostly for seamless upgrades when we first introduced that split but was kept for convenience.@ich777 commented on GitHub (Sep 17, 2021):
@joshuaboniface is it expected that
jellyfin-webis version 20210917.5 andjellyfin-serveris version 20210913.13?I've gone through a few old build logs and it worked just flawlessly there.
Also something seems to be wrong with the
jellyfinmeta package, the dependencies are wrong:Depends: jellyfin-server (>= 20210917.5-unstable), jellyfin-web (>= 20210917.5-unstable), jellyfin-ffmpeg (>= 4.2.1-2)This can't work because in the
jellyfinmeta it says thatjellyfin-serveris:and
jellyfin-webis:Also attached the file where you can see it:
jellyfin.txt
@jellyfin-bot commented on GitHub (Mar 25, 2022):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@jellyfin-bot commented on GitHub (Oct 8, 2023):
This issue was closed due to inactivity.