* google-chrome-stable_80.0.3987.106-1_amd64.deb BLAKE2B SHA512 size ;-) ... [ ok ] * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 4.19.104-r11 * Checking for suitable kernel configuration options... [ ok ] >>> Unpacking source... >>> Source unpacked in /tmp/portage/www-client/google-chrome-80.0.3987.106/work >>> Preparing source in /tmp/portage/www-client/google-chrome-80.0.3987.106/work ... >>> Source prepared. >>> Configuring source in /tmp/portage/www-client/google-chrome-80.0.3987.106/work ... >>> Source configured. >>> Compiling source in /tmp/portage/www-client/google-chrome-80.0.3987.106/work ... >>> Source compiled. >>> Test phase [not enabled]: www-client/google-chrome-80.0.3987.106 >>> Install www-client/google-chrome-80.0.3987.106 into /tmp/portage/www-client/google-chrome-80.0.3987.106/image/ >>> Unpacking google-chrome-stable_80.0.3987.106-1_amd64.deb to /tmp/portage/www-client/google-chrome-80.0.3987.106/image >>> Unpacking data.tar.xz to /tmp/portage/www-client/google-chrome-80.0.3987.106/image >>> Completed installing www-client/google-chrome-80.0.3987.106 into /tmp/portage/www-client/google-chrome-80.0.3987.106/image/ * Final size of build directory: 0 KiB * Final size of installed tree: 200792 KiB (196.0 MiB) * * This package seems to install metainfo files into the following * location(s): * * /usr/share/appdata * * This location is deprecated, it should not be used anymore by new software. * Appdata/Metainfo files should be installed into /usr/share/metainfo directory. * For more details, please see the freedesktop Upstream Metadata guidelines at * https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html * * Gentoo Tracker bug: https://bugs.gentoo.org/709450 * >>> Done. Reproducible: Always
Same problem exists with www-client/google-chrome-beta-84.0.4147.38
(In reply to Piotr from comment #1) > Same problem exists with www-client/google-chrome-beta-84.0.4147.38 Thanks, but this comment is not particularly helpful. If upstream fixes the issue, please let me know.
*** Bug 732918 has been marked as a duplicate of this bug. ***
Created attachment 882471 [details, diff] usr_share_appdata.patch Sorting out old bugs of mine, 4 years is enough ripening time ;-) The upstream issue https://bugs.chromium.org/p/chromium/issues/detail?id=1055146 hasn't moved, so I am suggesting we fix it on our end. Since this affects all 3 ebuilds www-client/google-chrome{,-beta,-unstable} and they are essentially the same (just KEYWORDS are different), I suggest a proper Gentoo dev adds this change in one commit. Not sure if that affects also www-client/chromium ? Iff deemed appropriate, of course. Closes: https://bugs.gentoo.org/710290 Reported-by: Kalin KOZHUHAROV <kalin@thinrope.net> Signed-off-by: Kalin KOZHUHAROV <kalin@thinrope.net>
I don’t see any reason to move the files downstream.