Package Details: plymouth-git 24.004.60.r88.ga0e8b6cf-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: 275
Popularity: 0.42
First Submitted: 2009-05-02 09:53 (UTC)
Last Updated: 2024-12-20 00:13 (UTC)

Required by (174)

Sources (6)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 51 Next › Last »

Taijian commented on 2023-04-05 13:25 (UTC)

@qtmax: OK, I've added it back. Could you raise an issue about this on the bug tracker for the community package?

qtmax commented on 2023-04-05 12:10 (UTC)

@Taijian, this bug has nothing to do with my use case. Moreover, I don't even have /etc/vconsole.conf, I don't use it.

Disk encryption seems to work for me as is

Disk encryption itself still works, I never said it stopped working.

What happened after the upgrade is that Plymouth no longer shows the graphical password prompt. Instead, I get the password prompt in the terminal.

I compared the old and the new initramfs contents and pinpointed it to /dev/pts being missing from the new one. Adding it back fixes the bug. The fix is as simple as adding this line back - could you apply it?

Taijian commented on 2023-04-05 11:52 (UTC)

@qtmax: Disk encryption seems to work for me as is - could you check if you might be affected by this bug: https://bugs.archlinux.org/task/78052 ?

qtmax commented on 2023-04-05 11:40 (UTC)

The last update removed /dev/pts from initrd, which broke systemd-askpass support in Plymouth. Could you readd the following line to plymouth.initcpio_install, so that users could enter the disk encryption password in Plymouth as before?

add_dir /dev/pts

eternalfloof commented on 2023-04-02 23:56 (UTC)

One note, if using systemd for your initrd, I found that using the plymouth hook and the sd-encrypt hooks works for me after the latest round of changes. (wasn't sure about the latter)

eternalfloof commented on 2023-04-02 23:32 (UTC)

Just to wade in here a little bit. For the debian/ubuntu example - It's worth noting that ubuntu has its own repository list (/etc/apt/sources.list), because installing packages is fundamentally a distro-specific task. So even if in this case, the "arch specific" cookbook may feel like it's just the logo, actually everything in all AUR packages is arch specific. Maybe you get lucky and it happens to work, but that's just happenstance.

One thing I personally appreciate about the PKGBUILD system is that it's straightforward for me as a user to understand how packages are created (and not just the final tarball). Thus, if I need to make a downstream tweak, it's something I can do (and e.g. rua can even maintain my personal patches for me).

The solutions to this problem are (in no particular order): 1. Downstream distros should maintain downstream repositories 2. Use a distro-agnostic package (e.g. flatpak) 3. Roll the dice and try to use packages for a different distro on your machine 3a. Write and share the documentation so other interested parties can follow in your footsteps

michaldybczak commented on 2023-04-02 17:22 (UTC)

Ah, I thought that was a change you added. Thanks for explanation. Now I get how the additional code got there. Community is an Arch repo, so Arch specific changes are perfectly fine, no argument here. However, I don't get why plymouth-git is still mirroring plymouth that became community/plymouth. So what is the point of having plymouth-git? I mean, the community one is already compiled and git is compiled by us (which can have various perks), but the name suggests it is just a git version, no more, no less, but in reality it's not. Do you plan to change it? I know that you explained that "the expectation is that the -git package does not modify the 'base' package as found in the Arch repos" but is it really? I always thought that the git is just pure git. The assumption you posted would make all git packages “vulnerable” to any community changes, which doesn't make sense. There could be some reasons why someone may want to have pure git instead of a modified version. If it's simply mirroring community, it forces for manual cleaning of PKGBUILD, which not every use will know he/she has to do, because again - the name doesn't tell you that, which is misleading.

Taijian commented on 2023-04-02 14:57 (UTC) (edited on 2023-04-02 14:58 (UTC) by Taijian)

@michaldybczak: OK, I'll try to spell this out for you as clearly as I can (although I really shouldn't bother, because you could find this out yourself if you were willing to spend just one iota of effort on educating yourself instead of just having a tantrum).

  1. AUR/plymouth-git is mirroring AUR/plymouth
  2. AUR/plymouth is moved to community/plymouth
  3. In the process community/plymouth changes
  4. AUR/plymouth-git continues mirroring community/plymouth

So like I already said: So if you have an issue with this, please feel free to take things up with the plymouth maintainer in community. Oh, and do make sure to remind them of their obligation to make sure their package also works for all the Arch derived distros. I'm sure they'd love to hear about that.

michaldybczak commented on 2023-04-02 14:19 (UTC)

@Taijian, you said "package does not modify the 'base' package as found in the Arch repos beyond what is necessary to make it work/build as a -git version". I'm confused. The base package already worked for years, and your modification is an extra addition that just gets in the way for some users. Modification was unnecessary and stands in contradiction to what you just said. Or maybe I misunderstood something, but the problem came because there was added a script that builds Arch specific plymouth theme. Without it and without it referencing to Arch specific files, all works like in the base package. Again, this was without warning and explanation. People were using this package for years, and you just made it harder to install for some.

Taijian commented on 2023-04-02 10:26 (UTC)

@michaldybczak: Thank you for your long and insightful comment. I learned a lot about your way of thinking. Please allow me to comment.

  1. I strikes me as a somewhat unusual approach to accuse someone - whom you want to do you a favor - of being 'ignorant'(2x), 'arrogant'(2x), 'motivated by egoism', 'following bad practice and abusive of AUR customs'. But hey, I'm just a behavioural psychologist, what do I know about how to motivate people. Do let me know how your approach works out!

  2. You seem quite sure of yourself and of your judgement. Have you ever stopped to think and consider that maybe there are reasons for my behaviour that you have just never considered so far? That - shockingly - there might be thoughts and concepts out there in the world that you have so far never encountered? Maybe people disagreeing with you are not just ignorant or malicious, but are looking at the world from a diffent point of view that you have just not considered so far?

  3. You rightly state that the name of an AUR package should reflect whether or not there have been any modifications to the 'base' package in making the AUR package. Where you seem to be confused is in what the 'base' is in relation to plymouth-git. In general, when a -git version of a package that is already in the Arch repos is added to the AUR, the expectation is that the -git package does not modify the 'base' package as found in the Arch repos beyond what is necessary to make it work/build as a -git version. And this is exactly what is happening here. Plymouth-git is mirroring community/plymouth, because that is the 'base' package it is supposed to be mirroring. I'm sure, if you give it a bit of thought, you will understand why this is so.

  4. So if you have an issue with this, please feel free to take things up with the plymouth maintainer in community. Oh, and do make sure to remind them of their obligation to make sure their package also works for all the Arch derived distros. I'm sure they'd love to hear about that.

  5. I am very much looking forward to your complaint to the TUs about my bad packaging practices and my abuse of AUR customs!

« First ‹ Previous 1 2 3 4 5 6 7 .. 51 Next › Last »