Package Details: grub-git 2.04.rc1.r19.g4e7b5bb3b-1

Git Clone URL: (read-only)
Package Base: grub-git
Description: GNU GRand Unified Bootloader (2)
Upstream URL:
Licenses: GPL3
Conflicts: grub
Provides: grub
Submitter: ridikulusrat
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 11
Popularity: 0.056560
First Submitted: 2013-10-22 18:55
Last Updated: 2019-06-12 22:49

Dependencies (20)

Required by (50)

Sources (6)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

WoefulDerelict commented on 2019-07-17 21:05

Peter_Littmann: rc1 was indeed to indicate release candidate 1 which was the tag present on the repository the last time this PKGBUILD required changes to cope with issues introduced upstream. As I stated earlier the -git suffix is intended to communicate that this PKGBUILD will always attempt to construct the software from the current git trunk and that pkgver will be generated at build time from data provided by the VCS. As upstream has already moved on past the 2.04 release the this PKGBUILD presently generates a pkgver of 2.04.r9.g8f6843ce6-1. Users are expected to have read the relevant documentation BEFORE they visit the AUR and should be familiar with VCS packaging conventions. The ONLY supported method for building and managing packages from PKGBUILDs hosted in the AUR is makepkg. Users are expected to have read and understood what the PKGBUILD does before they download and attempt to use it. The burden of knowing when changes have occurred upstream and when to rebuild a VCS package pulling from a project's git master branch is placed entirely on the end user.

The logic in pgkver() exists to reduce the maintenance burden of VCS packages. Cluttering the AUR with unnecessary updates every time there has been a commit upstream just to keep the pkgver current is generally frowned upon.

Peter_Littmann commented on 2019-07-17 06:38

But is the name grub-git 2.04.rc1.r19.g4e7b5bb3b-1 not misleading? I thought rc1 stands for release candidate 1 and now there is a real release published as I understand. May be makepkg is called by hand and fetches the latest version, but how does pamac or yay get informed that there is a new version to start makepkg for it when alreaady installed???

WoefulDerelict commented on 2019-07-16 16:16

Peter_Littmann: This is a VCS package. The -git suffix implies that it will fetch the latest (trunk) version from the upstream git server when makepkg is called. pkgver() automatically updates the package version when it is built.

Peter_Littmann commented on 2019-07-15 20:19

It looks like grub 2.04 is released on 05. July 2019, please check this:

Ranguvar commented on 2019-07-03 14:07

Fixed by completely re-syncing all source.

Ranguvar commented on 2019-07-01 03:40

Errors still for me:

WoefulDerelict commented on 2019-06-12 22:57

scurrvy2020: You are correct, it is an issue with the upstream source. The problem arises from a failure to properly fold in CFLAGS consistently.

I called in some help and we managed to work out what the problem was and generate a minimally invasive hack to work around it.

JohnKelley commented on 2019-05-08 02:52

Breakage is tracked by

Workaround: roll back to Grub commit f8f35acb5b05d40e3707a9d2db9ede60023e4cac Patch at

scurrvy2020 commented on 2019-04-30 14:49

I'm getting this error... looks like it is probably in the source and not your packaging, however.

In file included from ../../../../grub-core/lib/gnulib/argp-fmtstream.c:26: ./wchar.h:708:1: error: unknown type name ‘mbstate_t’ _GL_FUNCDECL_RPL (mbrtowc, size_t, ^~~~~~~~~~~~~~~~ ../../../../grub-core/lib/gnulib/argp-fmtstream.c: In function ‘add_width’: ../../../../grub-core/lib/gnulib/argp-fmtstream.c:125:3: error: unknown type name ‘mbstate_t’ mbstate_t ps; ^~~~~~~~~ ../../../../grub-core/lib/gnulib/argp-fmtstream.c:155:11: warning: implicit declaration of function ‘wcwidth’; did you mean ‘mbswidth’? [-Wimplicit-function-declaration] k = wcwidth (wc); ^~~~~~~ mbswidth

Ranguvar commented on 2019-04-22 17:53

For me, I'm hitting an error just using makepkg by itself.