libgpg-error 1.48 does a lot of maintenance work on the yat2m tool it includes. One of these changes is to add the option --gnupgorg [0] This flag is used in the gnupg 2.4.6 build: /usr/bin/yat2m -I /mnt/scratch/portage/app-crypt/gnupg-2.4.6-r1/work/gnupg-2.4.6/doc --release "GnuPG 2.4.6" --source "GNU Privacy Guard 2.4" --store --html --gnupgorg \ --date "`cat $incd 2>/dev/null`" \ `test -f '$file' || echo '/mnt/scratch/portage/app-crypt/gnupg-2.4.6-r1/work/gnupg-2.4.6/doc/'`$file ;\ However, both the ebuild and gnupg 2.4.6 do not require a new enough libgpg-error to guarantee having this flag available. If gnupg 2.4.6 is built without first manually upgrading libgpg-error, the build fails. With libgpg-error 1.46-r1 still installed, my build failed with: yat2m: usage: yat2m [OPTION] [FILE] (try --help for more information) (repeated multiple times) gnupg was fixed upstream in July: https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blobdiff;f=configure.ac;h=3d31958ed48d0b735b8ef6f194a8a569fc278632;hp=71c061481411a67b184b85e367ed1afbe04b697d;hb=d78131490edd7f7db142702b8144bc30e65dbd8d;hpb=22072f635f3573d7f96a2bdd5441051f8387f719 It would be good if the current ebuilds could also be fixed as all (2.4.6-r1, 2.4.7, 2.5.1) only require 1.46. [0] https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgpg-error.git;a=blobdiff;f=doc/yat2m.c;h=0e368fcee58800eb1f650e1a9a81bee45917543b;hp=e5b81b119671d627eca04b2bcfdebe3d575c98d4;hb=93d764498895e4cc9bdf14ac4c0cb41431946066;hpb=43dcdbff50fa33728ab4717cacdf8ff600aea3b9 Reproducible: Always Steps to Reproduce: 1. Install libgpg-error < 1.48 (1.47-r1 is still in-tree) 2. Build gnupg 2.4.6-r1 or later 3. Actual Results: Build fails when running yat2m with the absent --gnupgorg option Expected Results: Build depends on libgpg-error >= 1.48 and so causes an upgrade of libgpg-error before attempting to build gnupg Portage 3.0.63 (python 3.11.9-final-0, default/linux/amd64/23.0/systemd, gcc-14, glibc-2.40-r5, 5.10.52-gentoo.hex x86_64) ================================================================= System uname: Linux-5.10.52-gentoo.hex-x86_64-AMD_Ryzen_9_3900X_12-Core_Processor-with-glibc2.40 KiB Mem: 65824120 total, 10343380 free KiB Swap: 124999672 total, 124988080 free Timestamp of repository gentoo: Sat, 21 Dec 2024 07:30:00 +0000 Head commit of repository gentoo: d1214f3abf7323fbc5482bb824683a03df80f0e8 sh bash 5.2_p37 ld GNU ld (Gentoo 2.43 p3) 2.43.1 distcc 3.4 x86_64-pc-linux-gnu [disabled] app-misc/pax-utils: 1.3.7::gentoo app-shells/bash: 5.2_p37::gentoo dev-build/autoconf: 2.13-r7::gentoo, 2.69-r9::gentoo, 2.71-r6::gentoo dev-build/automake: 1.16.5::gentoo dev-build/cmake: 3.28.3::gentoo dev-build/libtool: 2.4.7-r4::gentoo dev-build/make: 4.4.1-r100::gentoo dev-build/meson: 1.3.2::gentoo dev-java/java-config: 2.3.3-r1::gentoo dev-lang/perl: 5.38.2-r3::gentoo dev-lang/python: 3.10.14_p1-r1::gentoo, 3.11.9-r1::gentoo, 3.12.3-r1::gentoo, 3.13.0::gentoo dev-lang/rust: 1.81.0-r100::gentoo, 1.82.0-r101::gentoo llvm-core/clang: 15.0.7-r1::gentoo, 16.0.6::gentoo, 17.0.6::gentoo, 18.1.8::gentoo, 19.1.4::gentoo llvm-core/lld: 15.0.7::gentoo, 17.0.6::gentoo, 18.1.8::gentoo, 19.1.4::gentoo llvm-core/llvm: 14.0.6-r2::gentoo, 15.0.7::gentoo, 16.0.6::gentoo, 17.0.6::gentoo, 18.1.8-r4::gentoo, 19.1.4::gentoo sys-apps/baselayout: 2.17::gentoo sys-apps/sandbox: 2.29::gentoo sys-apps/systemd: 255.7-r1::gentoo sys-devel/binutils: 2.38-r2::gentoo, 2.40-r5::gentoo, 2.42-r2::gentoo, 2.43-r2::gentoo sys-devel/binutils-config: 5.3.2::gentoo sys-devel/gcc: 11.5.0::gentoo, 12.4.1_p20241114::gentoo, 13.3.1_p20241115::gentoo, 14.2.1_p20241116::gentoo sys-devel/gcc-config: 2.11::gentoo sys-kernel/linux-headers: 6.6::gentoo (virtual/os-headers) sys-libs/glibc: 2.40-r5::gentoo
