jellyfin-git not updated on AUR #1146

Closed
opened 2025-12-21 18:08:16 +01:00 by backuprepo · 8 comments
Owner

Originally created by @anthonylavado on GitHub (Dec 19, 2019).

From a user report about a separate issue, it looks like jellyfin-git has stopped updating, but I’m not sure.

@z3ntu are you able to check it out?

Originally created by @anthonylavado on GitHub (Dec 19, 2019). From a user report about a separate issue, it looks like `jellyfin-git` has stopped updating, but I’m not sure. @z3ntu are you able to check it out?
backuprepo 2025-12-21 18:08:16 +01:00
Author
Owner

@z3ntu commented on GitHub (Dec 19, 2019):

"stopped updating"? I've updated the package several days ago and it worked fine back then. If there's something not right in the packaging process, the package should be flagged out-of-date in the AUR with a reason why.

@z3ntu commented on GitHub (Dec 19, 2019): "stopped updating"? I've updated the package several days ago and it worked fine back then. If there's something not right in the packaging process, the package should be flagged out-of-date in the AUR with a reason why.
Author
Owner

@dkanada commented on GitHub (Dec 19, 2019):

Yeah, I think git packages on the AUR don't show users when the git repository has updated, only when the package itself has been updated. The user is probably seeing no updates when they check and think it means the package isn't working, but they have to manually update again for the latest commit to get used.

@dkanada commented on GitHub (Dec 19, 2019): Yeah, I think git packages on the AUR don't show users when the git repository has updated, only when the package itself has been updated. The user is probably seeing no updates when they check and think it means the package isn't working, but they have to manually update again for the latest commit to get used.
Author
Owner

@z3ntu commented on GitHub (Dec 19, 2019):

Yes, that's how -git packages work in the AUR ¯\_(ツ)_/¯

Quote from the Arch Wiki:

Because these packages only download the latest available source when you execute makepkg, their pkgver() in the AUR does not reflect upstream changes.

@z3ntu commented on GitHub (Dec 19, 2019): Yes, that's how `-git` packages work in the AUR ¯\\\_(ツ)\_/¯ Quote from [the Arch Wiki](https://wiki.archlinux.org/index.php/Arch_User_Repository#What_is_the_difference_between_foo_and_foo-git_packages?): > Because these packages only download the latest available source when you execute makepkg, their pkgver() in the AUR does not reflect upstream changes.
Author
Owner

@anthonylavado commented on GitHub (Dec 19, 2019):

It’s confusing when a user says they’re running “10.4.0.r318.g831d1daa68” but I guess they were just looking at the wrong place. I don’t know enough sadly

@anthonylavado commented on GitHub (Dec 19, 2019): It’s confusing when a user says they’re running “10.4.0.r318.g831d1daa68” but I guess they were just looking at the wrong place. I don’t know enough sadly
Author
Owner

@telans commented on GitHub (Dec 19, 2019):

Actually regarding this specific package, it fails to be auto-updated when using an aur helper, and when a commit is pushed to this repo, for some reason. Other git packages such as winetricks, lutris, etc update fine when a commit is pushed to their repos. I have to manually trigger an update for jellyfin-git for it to well, update. I think it may be due to there being multiple git sources in the pkgbuild but not sure on that one.

It’s confusing when a user says they’re running “10.4.0.r318.g831d1daa68” but I guess they were just looking at the wrong place.

What do you mean by this? That version was correct as supplied supplied by pacman -Qi (just not updated for a few days)

@telans commented on GitHub (Dec 19, 2019): Actually regarding this specific package, it fails to be auto-updated when using an aur helper, and when a commit is pushed to this repo, for some reason. Other git packages such as winetricks, lutris, etc update fine when a commit is pushed to their repos. I have to manually trigger an update for jellyfin-git for it to well, update. I think it may be due to there being multiple git sources in the pkgbuild but not sure on that one. > It’s confusing when a user says they’re running “10.4.0.r318.g831d1daa68” but I guess they were just looking at the wrong place. What do you mean by this? That version was correct as supplied supplied by `pacman -Qi` (just not updated for a few days)
Author
Owner

@z3ntu commented on GitHub (Dec 19, 2019):

A user can rebuild the package every day and they will get a fresh package every time (assuming something has changed in the jellyfin git repo). The pkgver displayed in the AUR web interface is not accurate because it displays more or less a random value for pkgver (when the packager has last updated the PKGBUILD and uploaded it). The AUR does not do any dynamic updating of pkgvers automatically (because that would require either cloning repos or running any code which it doesn't do).
A user using AUR packages (and especially -git) packages is responsible for rebuilding the packages when needed (in the case of -git packages rebuild when they want to get a new version).
Changes to the PKGBUILD of -git packages only have to happen when something packaging-wise has changed (e.g. a new dependency, different build procedure, etc).

@z3ntu commented on GitHub (Dec 19, 2019): A user can rebuild the package every day and they will get a fresh package every time (assuming something has changed in the jellyfin git repo). The pkgver displayed in the AUR web interface is not accurate because it displays more or less a random value for pkgver (when the packager has last updated the PKGBUILD and uploaded it). The AUR does not do any dynamic updating of pkgvers automatically (because that would require either cloning repos or running any code which it doesn't do). A user using AUR packages (and especially -git) packages is responsible for rebuilding the packages when needed (in the case of -git packages rebuild when they want to get a new version). Changes to the PKGBUILD of -git packages only have to happen when something packaging-wise has changed (e.g. a new dependency, different build procedure, etc).
Author
Owner

@telans commented on GitHub (Dec 19, 2019):

Usually that process is streamlined when using an aur helper (works for other git packages, just not jellyfin-git). Updated my comment saying so. Would you have any idea as to why? I'm assuming that if you use an aur helper, it works for you

@telans commented on GitHub (Dec 19, 2019): Usually that process is streamlined when using an aur helper (works for other git packages, just not jellyfin-git). Updated my comment saying so. Would you have any idea as to why? I'm assuming that if you use an aur helper, it works for you
Author
Owner

@z3ntu commented on GitHub (Dec 19, 2019):

jellyfin-git has two git repos as source, so that might be the reason why the AUR helper is confused. Anyways, if you want that fixed, file a bug report for your AUR helper.

@z3ntu commented on GitHub (Dec 19, 2019): `jellyfin-git` has two git repos as source, so that might be the reason why the AUR helper is confused. Anyways, if you want that fixed, file a bug report for your AUR helper.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: starred/jellyfin#1146
No description provided.