Package Details: linux-firmware-bnx2x-git 20240312.3b128b60-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 - bnx2x / Firmware for Broadcom NetXtreme II 10Gb ethernet adapters
Upstream URL: https://gitlab.com/kernel-firmware/linux-firmware
Licenses: GPL2, custom, GPL3
Conflicts: linux-firmware, linux-firmware-bnx2x
Provides: linux-firmware-bnx2x
Submitter: xduugu
Maintainer: MRWITEK
Last Packager: MRWITEK
Votes: 76
Popularity: 1.16
First Submitted: 2010-05-19 22:50 (UTC)
Last Updated: 2024-03-15 11:25 (UTC)

Dependencies (3)

Required by (2)

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 »

SimPilotAdamT commented on 2021-03-08 22:41 (UTC)

@hugegameartgd strange as it worked for me without manually using another keyserver...

LinuxUserGD commented on 2020-04-20 09:52 (UTC)

@gardotd426 No, this didn't work for me as the default keyserver seems to not have the key. It only worked by manually using another keyserver for import.

gardotd426 commented on 2020-04-20 01:05 (UTC)

The correct command (at least the only one that currently actually works) is removing the --keyserver hkp://pgp.mit.edu part of the command hugegameartgd posted. So: 


gpg --recv-keys 4CDE8575E547BF835FE15807A31B6BD72486CFD6

gardotd426 commented on 2020-04-20 01:03 (UTC)

Actually, no, it doesn't: 


 gpg --recv-keys --keyserver hkp://pgp.mit.edu 4CDE8575E547BF835FE15807A31B6BD72486CFD6
gpg: keyserver receive failed: No keyserver available

gardotd426 commented on 2020-04-20 01:02 (UTC)

@hugegameartgd running that command doesn't work, it just sits there forever and never receives anything.

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

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.

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