Package Details: plymouth-git 24.004.60.r34.gedc7c3ea-1

Git Clone URL: https://aur.archlinux.org/plymouth-git.git (read-only, click to copy)
Package Base: plymouth-git
Description: Graphical boot splash screen (git version)
Upstream URL: https://www.freedesktop.org/wiki/Software/Plymouth/
Licenses: GPL-2.0-or-later
Conflicts: plymouth
Provides: plymouth
Submitter: PirateJonno
Maintainer: Taijian
Last Packager: Taijian
Votes: 274
Popularity: 0.000551
First Submitted: 2009-05-02 09:53 (UTC)
Last Updated: 2024-05-17 07:42 (UTC)

Required by (176)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 51 Next › Last »

Taijian commented on 2021-04-18 16:10 (UTC)

@asasione: Well, then my next question(s) would be:

a) are you running Arch or some derivative, and

b) what does pacman -V tell you?

asasione commented on 2021-04-18 16:03 (UTC) (edited on 2021-04-18 16:04 (UTC) by asasione) 

pacman -Qs plymouth-git
local/plymouth-git 0.9.5.r84.ge554475-1
    A graphical boot splash screen with kernel mode-setting support (Development version)

yay -Qs plymouth-git   
local/plymouth-git 0.9.5.r84.ge554475-1
    A graphical boot splash screen with kernel mode-setting support (Development version)

These are the results I'm getting even after having just installed the latest ge5544750-1 version. The update works correctly on your device but doesn't on ours it seems

Taijian commented on 2021-04-18 14:54 (UTC) (edited on 2021-04-18 14:57 (UTC) by Taijian) 

$ pacman -Qs plymouth-git
local/plymouth-git 0.9.5.r84.ge5544750-1
    A graphical boot splash screen with kernel mode-setting support (Development version)

So if your output is different from mine, you are not running the same version of pacman/makepkg as I am, and I really cannot help you with that.

Taijian commented on 2021-04-18 14:53 (UTC)

@michaldybczak: OK, please do the following:

  1. pacman -Qs plymouth-git

  2. $(your_aur_helper) -Qs plymouth-git

  3. Compare the output. If there is a difference, the problem lies in the way your AUR helper parses the pkgver. Then fiel a bug report with them and/or use a different AUR helper in the future, one that does not misreport package updates.

The problem is not the way you install the package. The problem is the way you check for available updates. And that is an issue with your helper program, not with pacman (which does not care for AUR packages) nor with this package.

michaldybczak commented on 2021-04-18 14:47 (UTC) (edited on 2021-04-18 14:49 (UTC) by michaldybczak)

But I told you that the same happens when installed manually via makepekg -i. And -Qs returns: local/plymouth-git 0.9.5.r84.ge554475-1, so no, pacman is not aware of the extra 0 in the version. So what should I do to avoid that issue?

Taijian commented on 2021-04-18 12:21 (UTC)

@michaldybczak & Depau:

Again, the problem is neither with this PKGBUILD, nor with pacman. Go ahead, do a proper pacman -Qs plymouth-git and you will see that pacman is well aware of the trailing 0 in the pkgver. The issue is with whatever AUR helper you are using. Complain there.

michaldybczak commented on 2021-04-18 11:54 (UTC) (edited on 2021-04-18 11:56 (UTC) by michaldybczak)

I'm not acquainted with technicalities. I'm just an average user. This may be some minor issue but it causes the update to be displayed endlessly, and it disturbs the whole system of showing if there is an update or not. Plus, the said package is repeatedly updated/recompiled with every update, so it prolongs the process. In overall, small issue but irritating as hell. That's said, what non-technical users as me should do about it? All I could do is to put plymouth-git on the ignore list, but there is surely a better solution to this. I already tried installing it manually (with makepkg -i) and the issue is the same, so this is not the aur-helper issue but how pacman reads the PKGBUILD.The additional 0 is omitted and not written to the pacman database, so it looks like there was no update, because on the other hand pacman sees the versioning difference (hence the update need) and then fails to write the whole version number. Isn't it a pacman issue that should be reported somewhere?

depau commented on 2021-04-18 09:48 (UTC) (edited on 2021-04-18 09:48 (UTC) by depau)

There's an extra 0 in the PKGBUILD version that triggers the AUR helpers. git describe --long uses the first 8 chars of the SHA1 but pkgver (the variable) contains 9.

Ultimately I think AUR helpers should be smarter than this, or users should just not really care. It's not a real issue.

michaldybczak commented on 2021-04-18 08:46 (UTC) (edited on 2021-04-18 08:59 (UTC) by michaldybczak)

I did the update with pamac. On your suggestion, I did the update via yay and the issue is still the same. Update is successful, but item is showed on the list to update. So the last resource would be to install it manually, So I copied the PKGBUILD and the rest of the files from AUR, and did makepkg -i. Again, that did not solve this problem. Here is the info of versions: The version on my system: 0.9.5.r84.ge554475-1 The version to update: 0.9.5.r84.ge5544750-1 The weird thing is, during update I get info: warning: plymouth-git-0.9.5.r84.ge554475-1 is in the newest version - reinstallation So maybe pacman's database is reading the info on the installed version incorrectly? Yay shows: aur/plymouth-git 0.9.5.r84.ge554475-1 -> 0.9.5.r84.ge5544750-1

Taijian commented on 2021-04-17 14:31 (UTC)

@michaldybczak: I'm sorry, but it seems to me that this is likely an issue with whatever AUR helper you are using.

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 51 Next › Last »