Package Details: linux-firmware-git 20150924.f88e5c2-2

Git Clone URL: (read-only)
Package Base: linux-firmware-git
Description: Firmware files for Linux
Upstream URL:;a=summary
Licenses: GPL2, custom, GPL3
Conflicts: linux-firmware
Provides: linux-firmware=20150924.f88e5c2
Submitter: xduugu
Maintainer: MRWITEK
Last Packager: MRWITEK
Votes: 63
Popularity: 0.077214
First Submitted: 2010-05-19 22:50
Last Updated: 2015-09-27 15:18

Dependencies (1)

Required by (90)

Sources (1)

Latest Comments

haagch commented on 2016-09-04 11:17

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

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

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)"

FadeMind commented on 2015-09-27 13:42

One a typo:


Should be


and list so on

MRWITEK commented on 2015-09-27 13:37

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

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

Disowned linux-git and linux-firmware-git.

dgbaley27 commented on 2013-08-18 18:36

What's the point of this PKGBUILD? The package in [core] is git-based.

xduugu commented on 2013-04-09 20:25

Updated. Thanks.

WorMzy commented on 2013-04-08 21:25

Please update the PKGBUILD to make use of pacman 4.1 CVS PKGBUILD features. Here's one I made earlier, feel free to use it:

xduugu commented on 2013-03-09 08:30

Thanks. Removed to external carl9170 firmware.

seblu commented on 2013-03-09 01:03

carl9170 is now part of the main tree.

xduugu commented on 2011-10-25 09:59

Switched back to repository.

Anonymous comment on 2011-10-17 12:19

thanks for fixing this package!

xduugu commented on 2011-10-13 13:52

I've found the repository at the repo owner's site. This package will use this source until the sources at are restored. Thanks for your patience.

Anonymous comment on 2011-10-07 09:13

the source is still broken, but works. Unfortunately, the git repo (git:// is either gone or still not restored after the problems they had... :(

xduugu commented on 2011-10-04 12:42

Hmm... I get an "550 Failed to change directory." for this url. But anyway, is the repository for this package already up again? I couldn't find it at

Anonymous comment on 2011-10-03 23:25

The source is broken :S You can replace it with

That now is working again :D

xduugu commented on 2010-12-06 15:51

Thanks, never noticed that since I usually remove the src folder before/after building. Should be fixed now.

xyproto commented on 2010-12-06 15:27

Hello, I get:
==> Connecting to GIT server....
You asked to pull from the remote 'origin', but did not specify
a branch. Because this is not the default configured remote
for your current branch, you must specify a branch on the command line.
error: Build failed

xduugu commented on 2010-10-07 16:38

Would you mind elaborating why you think it is required?

Anonymous comment on 2010-10-07 15:49

Add 'namcap' to build dependencies:

makedepends=('git' 'namcap')