Package Details: grub-git 2.12.rc1.r106.g7c8ae7dcb-1

Git Clone URL: https://aur.archlinux.org/grub-git.git (read-only, click to copy)
Package Base: grub-git
Description: GNU GRand Unified Bootloader (2)
Upstream URL: https://www.gnu.org/software/grub/
Licenses: GPL3
Conflicts: grub
Provides: grub
Submitter: ka2107
Maintainer: WoefulDerelict
Last Packager: WoefulDerelict
Votes: 17
Popularity: 0.000044
First Submitted: 2013-10-22 18:55 (UTC)
Last Updated: 2023-12-18 22:58 (UTC)

Dependencies (21)

Required by (315)

Sources (7)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 18 Next › Last »

jonathon commented on 2018-03-29 19:03 (UTC) (edited on 2018-03-29 19:03 (UTC) by jonathon)

That may well be because there's no immediately obvious way to open a bug report... it's hidden in a drop-down under the Bug navigation bar item... -.-

Reported: https://savannah.gnu.org/bugs/?53517

WoefulDerelict commented on 2018-03-27 17:45 (UTC)

jonathon: No, unfortunately, I don't think anyone has reported the issue upstream.

jonathon commented on 2018-03-27 09:01 (UTC)

Has anyone reported the issue upstream? This page is the only one found via a web search which references the issue.

starfry commented on 2018-03-14 11:39 (UTC)

The build failure resulting in "grub_reboot in reboot is duplicated in kernel" only happens if the EFI version is built. If you don't need the EFI version (e.g. you're using BIOS) then you can disable it by setting _GRUB_IA32_EFI_ARCH_X64="0" in the PKGBUILD.

@WoefulDerelict - I would say this is probably something that the PKGBUILD will need to address at some point because the change looks like it was made on purpose rather than as a bug. I note that the core grub package doesn't address this either, but that's because it builds a version prior to this change being introduced.

I have tried to work out how to make it build, without success. For me, disabling EFI is an acceptible workaround until the correct fix is known.

WoefulDerelict commented on 2018-01-27 01:35 (UTC) (edited on 2018-06-14 04:41 (UTC) by WoefulDerelict)

This appears to be an issue introduced by upstream commit 0ba90a7f017889d32a47897d9107ef45cc50a049. One is able to build the previous commit b4d709b6ee789cdaf3fa7a80fd90c721a16f48c2 just fine.

timofonic: -git packages generally pull from the upstream 'master' branch. Upstream developers can introduce breaking changes at any time without warning. This is not an indication the PKGBUILD is out of date.

Please report your issues upstream where they can be addressed properly.

ArchLinuxTux commented on 2018-01-24 10:37 (UTC)

@timofonic It doesn't work for me too! Same error message "grub_reboot in reboot is duplicated in kernel" with up to date packages.

timofonic commented on 2017-11-11 04:57 (UTC)

sd.module linux16.module multiboot2.module multiboot.module linux.module xnu.module random.module macho.module appleldr.module chain.module mmap.module normal.module part_acorn.module part_amiga.module part_apple.module part_gpt.module part_msdos.module part_sun.module part_plan.module part_dvh.module part_bsd.module part_sunpc.module part_dfly.module msdospart.module at_keyboard.module gfxterm.module gfxterm_background.module serial.module terminfo.module usb_keyboard.module video_cirrus.module video_bochs.module functional_test.module exfctest.module strtoull_test.module setjmp_test.module signature_test.module sleep_test.module xnu_uuid_test.module pbkdf2_test.module legacy_password_test.module div.module div_test.module mul_test.module shift_test.module cmp_test.module ctz_test.module bswap_test.module videotest_checksum.module gfxterm_menu.module cmdline_cat_test.module bitmap.module bitmap_scale.module efi_gop.module efi_uga.module jpeg.module png.module tga.module video_fb.module video.module video_colors.module datehook.module net.module tftp.module http.module efinet.module legacycfg.module syslinuxcfg.module test_blockarg.module xzio.module lzopio.module testload.module backtrace.module keylayouts.module priority_queue.module time.module cacheinfo.module boottime.module adler32.module crc64.module mpi.module all_video.module gdb.module testspeed.module tr.module progress.module file.module gcry_arcfour.module gcry_blowfish.module gcry_camellia.module gcry_cast5.module gcry_crc.module gcry_des.module gcry_dsa.module gcry_idea.module gcry_md4.module gcry_md5.module gcry_rfc2268.module gcry_rijndael.module gcry_rmd160.module gcry_rsa.module gcry_seed.module gcry_serpent.module gcry_sha1.module gcry_sha256.module gcry_sha512.module gcry_tiger.module gcry_twofish.module gcry_whirlpool.module ; do \ sh gensyminfo.sh $m >> syminfo.lst.new || exit 1; \ done mv syminfo.lst.new syminfo.lst cat syminfo.lst | sort | gawk -f ./genmoddep.awk > moddep.lst || (rm -f moddep.lst; exit 1) grub_reboot in reboot is duplicated in kernel make[3]: *** [Makefile:43574: moddep.lst] Error 1 make[3]: Leaving directory '/home/timofonic/.cache/pacaur/grub-git/src/grub-efi-i386/grub-core' make[2]: *** [Makefile:24062: all] Error 2 make[2]: Leaving directory '/home/timofonic/.cache/pacaur/grub-git/src/grub-efi-i386/grub-core' make[1]: *** [Makefile:10906: all-recursive] Error 1 make[1]: Leaving directory '/home/timofonic/.cache/pacaur/grub-git/src/grub-efi-i386' make: *** [Makefile:3132: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... :: failed to build grub-git package(s)

WoefulDerelict commented on 2017-09-04 20:13 (UTC)

tyler274: This appears to be an issue introduced by upstream commit [21e4a6fa039bb7dc6be42e1e4c171ddc398b8431]. One is able to build the previous commit [6662372053bb7f580cf1b6a56b11e1190d81a40c] just fine. jcstryker: -git packages generally pull from the upstream 'master' branch. Upstream developers can introduce breaking changes at any time without warning. This is not an indication the PKGBUILD is out of date. Please report your issues upstream where they can be addressed properly.

tyler274 commented on 2017-08-30 22:05 (UTC)

fails to build with recent changes loader/multiboot.c:32:10: fatal error: grub/multiboot2.h: no such file or directory

WoefulDerelict commented on 2017-03-20 15:41 (UTC)

sulaweyo: I don't have a definitive answer. This is simply how it was designed to function upstream. linguas.sh is part of the build system pulled in from the grub git repository. Generally to avoid breakage we follow the manual and use the tools we are given. It might be possible to fetch them via another method; however, I haven't explored it as fiddling with a working build system and breaking it for everyone attempting to fix an edge case is more Debian territory than Arch territory. This is essentially a mirror of the PKGBUILD used in [Core] with a pkgver function.