If I try to install chromium-130.0.6723.116-r1; it does not unpack: * chromium-130.0.6723.116-gentoo.tar.xz BLAKE2B SHA512 size ;-) ... [ ok ] * chromium-patches-130-2.tar.bz2 BLAKE2B SHA512 size ;-) ... [ ok ] * Checking for at least 4 GiB RAM ... [ ok ] * Checking for at least 25 GiB disk space at "/var/tmp/portage/www-client/chromium-130.0.6723.116-r1/temp" ... [ ok ] * Checking for at least 4 GiB RAM ... [ ok ] * Checking for at least 25 GiB disk space at "/var/tmp/portage/www-client/chromium-130.0.6723.116-r1/temp" ... [ ok ] * USE=official selected and LTO not detected. * It is _highly_ recommended that LTO be enabled for performance reasons * and to be consistent with the upstream "official" build optimisations. * Using Rust 1.81.0 (source) * Using LLVM/Clang slot 18 to build * Using Rust slot 1.81.0, source to build * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 6.11.7 * Checking for suitable kernel configuration options ... [ ok ] >>> Unpacking source... * ERROR: www-client/chromium-130.0.6723.116-r1::gentoo failed (unpack phase): * unpack: chromium-130.0.6723.116.tar.xz does not exist * * Call stack: * ebuild.sh, line 136: Called src_unpack * environment, line 5044: Called unpack 'chromium-130.0.6723.116.tar.xz' * phase-helpers.sh, line 361: Called die * The specific snippet of code: * [[ ! -s ${srcdir}${x} ]] && die "unpack: ${x} does not exist" * * If you need support, post the output of `emerge --info '=www-client/chromium-130.0.6723.116-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=www-client/chromium-130.0.6723.116-r1::gentoo'`. * The complete build log is located at '/var/tmp/portage/www-client/chromium-130.0.6723.116-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/www-client/chromium-130.0.6723.116-r1/temp/environment'. * Working directory: '/var/tmp/portage/www-client/chromium-130.0.6723.116-r1/work' * S: '/var/tmp/portage/www-client/chromium-130.0.6723.116-r1/work/chromium-130.0.6723.116' It is even not downloaded. So I downloaded it from https://chromium-tarballs.distfiles.gentoo.org and put the files in /var/cache/distfiles with the appropriate owner and rights. But it does not work even if the file exists: 11:21 root@gentoo-elastic ~francois# ls -la /var/cache/distfiles/chr* -rw-rw-r-- 1 portage portage 4.4G 6 nov 04:20 /var/cache/distfiles/chromium-130.0.6723.116-gentoo.tar.xz -rw-rw-r-- 1 portage portage 4.4G 6 nov 04:20 /var/cache/distfiles/chromium-130.0.6723.116.tar.xz -rw-rw-r-- 1 portage portage 10K 2 nov 05:53 /var/cache/distfiles/chromium-patches-130-2.tar.bz2 -rw-rw-r-- 1 portage portage 210K 15 sep 2023 /var/cache/distfiles/chrono-0.4.31.crate -rw-rw-r-- 1 portage portage 229K 27 mar 2024 /var/cache/distfiles/chrono-0.4.37.crate -rw-rw-r-- 1 portage portage 216K 15 avr 2024 /var/cache/distfiles/chrono-0.4.38.crate Can somebody explain this ? Reproducible: Always
SRC_URI has: ``` SRC_URI="https://chromium-tarballs.distfiles.gentoo.org/${P}.tar.xz -> ${P}-gentoo.tar.xz ``` And src_unpack has: ``` src_unpack() { unpack ${P}.tar.xz [...] ``` src_unpack needs to be updated.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e12d576125edea8a37999939d36e1de550dd2c15 commit e12d576125edea8a37999939d36e1de550dd2c15 Author: Matt Jolly <kangie@gentoo.org> AuthorDate: 2024-11-09 11:18:22 +0000 Commit: Matt Jolly <kangie@gentoo.org> CommitDate: 2024-11-09 11:21:07 +0000 www-client/chromium: fix src_unpack To avoid Gentoo-generated tarballs colliding with (e.g.) downstream tarballs of ungoogled-chromium we rename the Gentoo tarballs. Unfortunately the corresponding change to src_unpack did not make it into the ebuild as published. Closes: https://bugs.gentoo.org/943115 Signed-off-by: Matt Jolly <kangie@gentoo.org> www-client/chromium/chromium-130.0.6723.116-r1.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
