Package Details: linux-firmware-nfp-git 20250305.a3e1417a-1

Git Clone URL: https://aur.archlinux.org/linux-firmware-git.git (read-only, click to copy)
Package Base: linux-firmware-git
Description: Firmware files for Linux - nfp / Firmware for Netronome Flow Processors
Upstream URL: https://gitlab.com/kernel-firmware/linux-firmware
Licenses: custom, GPL-2.0-only, GPL-2.0-or-later, GPL-3.0-only
Conflicts: linux-firmware, linux-firmware-nfp
Provides: linux-firmware-nfp
Submitter: xduugu
Maintainer: MRWITEK
Last Packager: MRWITEK
Votes: 74
Popularity: 0.001023
First Submitted: 2010-05-19 22:50 (UTC)
Last Updated: 2025-03-06 14:17 (UTC)

Dependencies (5)

Required by (1)

Sources (1)

Pinned Comments

MRWITEK commented on 2023-12-20 12:42 (UTC)

Upstream doesn't sign most commits anymore, so GPG signature check is disabled. They still sign every tag. Packages in the official repos package tags. You can check signatures with the following commands:

$ git log --format=raw --show-signature main
$ git tag -v $(git tag)

gbin commented on 2022-03-02 17:58 (UTC) (edited on 2022-03-02 18:07 (UTC) by gbin)

edit: found my problem the key server it could be useful for other people.

The default port is an high port and your ISP might filter it out!

use :80 in the ubuntu one and it should work:

pal ➜  ~  gpg --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 4CDE8575E547BF835FE15807A31B6BD72486CFD6
gpg: key A31B6BD72486CFD6: public key "Josh Boyer <jwboyer@fedoraproject.org>" imported
gpg: Total number processed: 1
gpg:               imported: 1

MRWITEK commented on 2020-04-08 14:47 (UTC) (edited on 2022-12-15 12:15 (UTC) by MRWITEK)

https://wiki.archlinux.org/title/Arch_User_Repository#ERROR%3A_One_or_more_PGP_signatures_could_not_be_verified%21%3B_what_should_I_do%3F

https://wiki.archlinux.org/title/PKGBUILD#validpgpkeys

https://wiki.archlinux.org/title/Makepkg#Signature_checking

https://wiki.archlinux.org/title/Arch_User_Repository#What_is_the_difference_between_foo_and_foo-git_packages%3F

Latest Comments

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

LinuxUserGD commented on 2020-04-08 14:15 (UTC)

Works after running gpg --recv-keys --keyserver hkp://pgp.mit.edu 4CDE8575E547BF835FE15807A31B6BD72486CFD6

m3thodic commented on 2019-09-16 23:38 (UTC)

I came here to comment on exactly what @haagch already posted, please update!

haagch commented on 2019-09-05 22:11 (UTC)

A new "build" fails at deleting some files by the way. I haven't really looked at it, just added -f

rm -f "${pkgdir}/usr/lib/firmware/"{Makefile,README,configure,GPL-3}

haagch commented on 2016-09-04 11:17 (UTC)

Hm... yaourt annoyingly tried to downgrade the package because it kept setting 2015-something as the version number. I just built the package completely fresh and got 20160831.c883a6b-1 so I guess there is just something wrong with repeatedly building the package from the same directory.

MRWITEK commented on 2016-09-03 14:05 (UTC)

To haagch: It doesn't matter when package is built because nothing is compiled. So I put commit date of last commit in pkgver because if there was no commits since last build you don't need to rebuild package. Also in ABS pkgver is described as "Commit date + git rev-parse --short origin/master".

haagch commented on 2016-09-03 11:12 (UTC)

The ABS pkgver actually uses the build date. Look at it: Build Date: 2016-07-30 14:25 UTC linux-firmware 20160730.6bc2c60-1 So pkgver should be something like this: pkgver() { # Mimics ABS pkgver described like this: # Build date + git rev-parse --short origin/master cd "${srcdir}/${pkgname}" echo "$(date +%Y%m%d).$(git rev-parse --short master)" }

MRWITEK commented on 2015-09-27 13:37 (UTC)

The fact that this package can't be built in paths with spaces is an upstream issue. Version number is created as described in ABS PKGBUILD file: 'Commit date + git rev-parse --short origin/master'. Version number of this package is similar to version number of official package because it does the same thing as the official one.

SBeaver commented on 2015-09-27 10:30 (UTC)

This package can't build in paths with spaces. Btw, how is the package version number derived and does it really make sense to use it? People might get confused about what they are getting.

xduugu commented on 2014-01-01 17:45 (UTC)

Disowned linux-git and linux-firmware-git.

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