Package Details: breeze-plymouth 5.17.3-1

Git Clone URL: https://aur.archlinux.org/breeze-plymouth.git (read-only)
Package Base: breeze-plymouth
Description: Breeze theme for plymouth
Upstream URL: https://projects.kde.org/breeze-plymouth
Licenses: LGPL
Submitter: ImNtReal
Maintainer: ImNtReal
Last Packager: ImNtReal
Votes: 15
Popularity: 0.000000
First Submitted: 2016-03-27 23:07
Last Updated: 2019-11-12 19:35

Pinned Comments

ImNtReal commented on 2019-03-13 12:47

I've added the cpio hoook to the package. You may need to remove it from your filesystem if you added it manually.

ImNtReal commented on 2019-03-04 21:59

For users who have trouble validating the GPG keys used to sign the source package, this thread may be helpful: https://bbs.archlinux.org/viewtopic.php?id=191954

ctrlX commented on 2019-02-18 11:36

The breeze-plymouth theme utilizes the Plymouth label plugin (label.so) along with its dependencies (i.e. Pango). For some reason, this is not included into the initramfs image on Arch. Hence text labels and such is not displayed during boot.

To solve this, copy the following custom hook to /etc/initcpio/install/ : https://gitlab.com/pwyde/monochrome-plymouth/blob/master/hooks/breeze-plymouth

Then add the custom build hook breeze-plymouth to the HOOKS array in the /etc/mkinitcpio.conf configuration file.

HOOKS=(... breeze-plymouth)

Regenerate the initial ramdisk with mkinitcpio -p linux.

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

I-amGodBro commented on 2019-01-27 15:57

Please enter the command: gpg --recv-keys EC94D18F7F05997E
To avoid such a stupid "error"

edarblanco commented on 2018-10-18 12:40

GPG error, fix please, thanks breeze-plymouth-5.14.0.tar.xz ... HA FALLADO (clave pública desconocida 11968C44928CAEFC) ==> ERROR: ¡No se ha podido verificar alguna de las firmas PGP!

Archange commented on 2018-02-08 21:23

The correct GPG fix is not to remove the validpgpkeys array, but to add the correct one inside it: 0AAC775BB6437A8D9AF7A3ACFE0784117FBCE11D

Archange commented on 2018-01-12 13:54

What tool do you use to build? The only thing I could imagine is that your helper, if any, use a different keyring for building packages than your user keyring (which would be a good practice btw, but not really deployed by anyone AFAIK).

Zell_89 commented on 2018-01-12 11:08

@ArchangelGabriel pub rsa2048 2016-09-06 [SC] 2D1D5B0588357787DE9EE225EC94D18F7F05997E uid [ unknown] Jonathan Riddell jr@jriddell.org sub rsa2048 2016-09-06 [E]

And yes, it still not works.

Archange commented on 2017-12-05 18:15

Zell_89: So you have run gpg --recv-key EC94D18F7F05997E and it still does not work? What does gpg --list-keys EC94D18F7F05997E returns?

Zell_89 commented on 2017-11-30 19:14

@ArchangelGabriel
==> Validation of source signatures with gpg in progress ...
breeze-plymouth-5.11.4.tar.xz ... NON RIUSCITO (unknown public key EC94D18F7F05997E)
==> ERROR: One or more PGP signatures can not be verified!

Archange commented on 2017-11-25 15:17

@Zell_89: Exact error message please.

Zell_89 commented on 2017-11-23 18:21

That damn gpg key continue to give error, I imported it and refreshed the database but cannot be verified because it is unknown. It is strictly necessary?

egrupled commented on 2017-10-29 13:23

Can you add gpg verification to PKGBUILD? It can look like this:

# Maintainer: Jameson Pugh <imntreal@gmail.com>

pkgname=breeze-plymouth
pkgver=5.11.2
pkgrel=1
pkgdesc="Breeze theme for plymouth"
arch=(any)
url='https://projects.kde.org/breeze-plymouth'
license=(LGPL)
depends=(plymouth)
makedepends=(extra-cmake-modules)
source=("http://download.kde.org/stable/plasma/${pkgver}/${pkgname}-${pkgver}.tar.xz"{,.sig})
sha256sums=('4d934d4c11eb923d4cf69135a77cca3b4f84452c4578a078d6fc7fe053f983ec'
'SKIP')
validpgpkeys=('2D1D5B0588357787DE9EE225EC94D18F7F05997E')

prepare() {
mkdir -p "${srcdir}/${pkgname}-${pkgver}/build"
}

build() {
cd "${srcdir}/${pkgname}-${pkgver}/build"
cmake ..
make
}

package() {
cd "${srcdir}/${pkgname}-${pkgver}/build"
make DESTDIR="${pkgdir}" install
}