New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 709347 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Cannot emerge chromeos-fonts on kevin and bob

Project Member Reported by marc...@chromium.org, Apr 7 2017

Issue description

Try:

emerge-kevin chromeos-fonts 

or

emerge-bob chromeos-fonts 

neither works.

I'm assigining to the last people who touched the package, doesn't necessarily mean it's your fault, but I'm hoping you at least maintain it somehow.
 
Labels: -Pri-3 Pri-1
Cc: chirantan@chromium.org
what do you mean by "neither works" ?  do you mean it failed ?  was there a log ?  or it just takes a while ?
 * ERROR: chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 509:  Called generate_font_cache
 *   environment, line 374:  Called qemu_run '/usr/bin/fc-cache' '-f' '-v'
 *   environment, line 502:  Called die
 * The specific snippet of code:
 *           sudo chroot "${ROOT}" "/tmp/${qemu[0]}" "${qemu[@]:1}" "$@" || die;
 * 
 * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos'`,
 * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos'`.
 * The complete build log is located at '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-fonts-0.0.1-r26:20170407-060421.log'.
 * For convenience, a symlink to the build log is located at '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/temp/build.log'.
 * The ebuild environment file is located at '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/temp/environment'.
 * Working directory: '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work'
 * S: '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work'

>>> Failed to emerge chromeos-base/chromeos-fonts-0.0.1-r26 for /build/kevin/, Log file:

>>>  '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-fonts-0.0.1-r26:20170407-060421.log'

 * Messages for package chromeos-base/chromeos-fonts-0.0.1-r26 merged to /build/kevin/:

 * ERROR: chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 509:  Called generate_font_cache
 *   environment, line 374:  Called qemu_run '/usr/bin/fc-cache' '-f' '-v'
 *   environment, line 502:  Called die
 * The specific snippet of code:
 *           sudo chroot "${ROOT}" "/tmp/${qemu[0]}" "${qemu[@]:1}" "$@" || die;
 * 
 * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos'`,
 * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos'`.
 * The complete build log is located at '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-fonts-0.0.1-r26:20170407-060421.log'.
 * For convenience, a symlink to the build log is located at '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/temp/build.log'.
 * The ebuild environment file is located at '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/temp/environment'.
 * Working directory: '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work'
 * S: '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work'

that is the tail of the log.  what shows up before it ?  or just attach the full log.
Here is the full log:

(cr) ((d343fe5...)) marcheu@marchesin ~/trunk/src/scripts $ emerge-kevin chromeos-fonts
!!! CONFIG_PROTECT is empty for '/build/kevin/'
Calculating dependencies... done!

>>> Emerging (1 of 1) chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos for /build/kevin/
 * Running stacked hooks for pre_pkg_setup
 *    sysroot_build_bin_dir ...                                                                                 [ ok ]
 * Running stacked hooks for pre_src_unpack
 *    python_multilib_setup ...                                                                                 [ ok ]
>>> Unpacking source...
>>> Source unpacked in /build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work
 * Running stacked hooks for post_src_unpack
 *    asan_init ...                                                                                             [ ok ]
>>> Preparing source in /build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work ...
>>> Source prepared.
>>> Configuring source in /build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work ...
>>> Source configured.
>>> Compiling source in /build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work ...
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
mount: mount(2) failed: No such file or directory
ERROR: ld.so: object 'libsandbox.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
/usr/share/fonts/ascender_licensed: caching, new cache contents: 36 fonts, 0 dirs
/usr/share/fonts/ascender_licensed: failed to write cache
/usr/share/fonts/croscore: caching, new cache contents: 12 fonts, 0 dirs
/usr/share/fonts/croscore: failed to write cache
/usr/share/fonts/crosextra: caching, new cache contents: 8 fonts, 0 dirs
/usr/share/fonts/crosextra: failed to write cache
/usr/share/fonts/dejavu: caching, new cache contents: 21 fonts, 0 dirs
/usr/share/fonts/dejavu: failed to write cache
/usr/share/fonts/droid-cros: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/droid-cros: failed to write cache
/usr/share/fonts/ja-ipafonts: skipping, no such directory
/usr/share/fonts/ja-motoyafonts: caching, new cache contents: 12 fonts, 0 dirs
/usr/share/fonts/ja-motoyafonts: failed to write cache
/usr/share/fonts/ko-nanum: caching, new cache contents: 4 fonts, 0 dirs
/usr/share/fonts/ko-nanum: failed to write cache
/usr/share/fonts/lohit-cros: caching, new cache contents: 9 fonts, 0 dirs
/usr/share/fonts/lohit-cros: failed to write cache
/usr/share/fonts/ml-anjali: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/ml-anjali: failed to write cache
/usr/share/fonts/noto: caching, new cache contents: 179 fonts, 0 dirs
/usr/share/fonts/noto: failed to write cache
/usr/share/fonts/notocjk: caching, new cache contents: 16 fonts, 0 dirs
/usr/share/fonts/notocjk: failed to write cache
/usr/share/fonts/roboto: caching, new cache contents: 12 fonts, 0 dirs
/usr/share/fonts/roboto: failed to write cache
/usr/share/fonts/sil-abyssinica: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/sil-abyssinica: failed to write cache
/usr/share/fonts/tibt-jomolhari: caching, new cache contents: 1 fonts, 0 dirs
/usr/share/fonts/tibt-jomolhari: failed to write cache
/usr/share/cache/fontconfig: cleaning cache directory
/usr/bin/fc-cache: failed
 * ERROR: chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 509:  Called generate_font_cache
 *   environment, line 374:  Called qemu_run '/usr/bin/fc-cache' '-f' '-v'
 *   environment, line 502:  Called die
 * The specific snippet of code:
 *           sudo chroot "${ROOT}" "/tmp/${qemu[0]}" "${qemu[@]:1}" "$@" || die;
 * 
 * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos'`,
 * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos'`.
 * The complete build log is located at '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-fonts-0.0.1-r26:20170407-060421.log'.
 * For convenience, a symlink to the build log is located at '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/temp/build.log'.
 * The ebuild environment file is located at '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/temp/environment'.
 * Working directory: '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work'
 * S: '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work'

>>> Failed to emerge chromeos-base/chromeos-fonts-0.0.1-r26 for /build/kevin/, Log file:

>>>  '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-fonts-0.0.1-r26:20170407-060421.log'

 * Messages for package chromeos-base/chromeos-fonts-0.0.1-r26 merged to /build/kevin/:

 * ERROR: chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos failed (compile phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  93:  Called src_compile
 *   environment, line 509:  Called generate_font_cache
 *   environment, line 374:  Called qemu_run '/usr/bin/fc-cache' '-f' '-v'
 *   environment, line 502:  Called die
 * The specific snippet of code:
 *           sudo chroot "${ROOT}" "/tmp/${qemu[0]}" "${qemu[@]:1}" "$@" || die;
 * 
 * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos'`,
 * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos'`.
 * The complete build log is located at '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-fonts-0.0.1-r26:20170407-060421.log'.
 * For convenience, a symlink to the build log is located at '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/temp/build.log'.
 * The ebuild environment file is located at '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/temp/environment'.
 * Working directory: '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work'
 * S: '/build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/work'

I was just able to run that successfully.  I wonder if it's something in your environment.  Shot in the dark: what is your umask in the chroot?
Before filing the bug, I asked Ilja to try and it also failed for him. Is there something wrong with both our environments?

Is your tree up to date? I synced yesterday.
My tree is currently in a bit of a fragile state so I created a completely fresh checkout, ran build_packages --board kevin, and then emerge-kevin chromeos-fonts.

It still completed successfully.
Where is this font cache? Is there a way I can clear things by hand and move on?
All the cache files should be in /build/$BOARD/usr/share/cache/fontconfig.

However, if you don't actually need to build the font cache yourself you can just download the pre-built package with 'emerge-kevin --getbinpkg --usepkg chromeos-fonts'.
(cr) ((d343fe5...)) marcheu@marchesin ~/trunk/src/scripts $ emerge-kevin --getbinpkg --usepkg chromeos-fonts
!!! CONFIG_PROTECT is empty for '/build/kevin/'

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.

Local copy of remote index is up-to-date and will be used.
15:49:46: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cp -v -- gs://chromeos-prebuilt/board/arm-generic/paladin-R59-9436.0.0-rc3/packages/Packages /tmp/tmpkwgKPy.tmp
15:49:48: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cp -v -- gs://chromeos-prebuilt/board/kevin/paladin-R59-9436.0.0-rc3/packages/Packages /tmp/tmpyyIfgO.tmp
15:49:49: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cp -v -- gs://chromeos-prebuilt/board/veyron_jerry/chrome-R59-9436.0.0-rc1/packages/Packages /tmp/tmp7YnW9k.tmp
Calculating dependencies... done!

>>> Emerging binary (1 of 1) chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos for /build/kevin/
15:49:53: INFO: RunCommand: /mnt/host/source/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cp -v -- gs://chromeos-prebuilt/board/kevin/paladin-R59-9425.0.0-rc1/packages/chromeos-base/chromeos-fonts-0.0.1-r26.tbz2 /build/kevin/packages/chromeos-base/chromeos-fonts-0.0.1-r26.tbz2.tmp
 * chromeos-fonts-0.0.1-r26.tbz2 MD5 SHA1 size ;-) ...                   [ ok ]
>>> Extracting info
 * Running stacked hooks for pre_pkg_setup
 *    sysroot_build_bin_dir ...                                                                                 [ ok ]
>>> Extracting chromeos-base/chromeos-fonts-0.0.1-r26
pbzip2: *WARNING: Trailing garbage after EOF ignored!

>>> Installing (1 of 1) chromeos-base/chromeos-fonts-0.0.1-r26::chromiumos to /build/kevin/
 * Removing /usr/lib*/*.la
 * Removing /etc/init.d
 * Removing /etc/conf.d
 * Removing /etc/logrotate.d
 * Removing /etc/sandbox.d
 * Removing /usr/share/bash-completion
 * Removing /usr/share/man
 * Removing /usr/share/info
 * Removing /usr/share/doc
 * Running stacked hooks for pre_pkg_preinst
 *    wrap_old_config_scripts ...                                                                               [ ok ]
!!! copy /build/kevin/tmp/portage/chromeos-base/chromeos-fonts-0.0.1-r26/image/usr/share/cache/fontconfig/923e285e415b1073c8df160bee08820f-le32d8.cache-4 -> /build/kevin/usr/share/cache/fontconfig/923e285e415b1073c8df160bee08820f-le32d8.cache-4 failed.
!!! [Errno 2] No such file or directory: '/build/kevin/usr/share/cache/fontconfig/923e285e415b1073c8df160bee08820f-le32d8.cache-4#new'

>>> Failed to install chromeos-base/chromeos-fonts-0.0.1-r26 to /build/kevin/, Log file:

>>>  '/build/kevin/tmp/portage/logs/chromeos-base:chromeos-fonts-0.0.1-r26:20170407-224954.log'

Status: WontFix (was: Available)
Ok I fixed it with:

sudo umount gvfsd-fuse

I suspect I had some lingering mounts, and this cleared them.

Sign in to add a comment