build_image error for --board=nautilus
119 views
Skip to first unread message
Umang Jain
Aug 22, 2022, 11:14:06 AM8/22/22
to ChromiumOS Development
Hi,
Following the developer guide for chromium OS, I am facing an issue in ./build_image... stage regarding the lsb_release.
Following is an excerpt build_image log showcasing the error:
>>> 14:17:09.829 Jobs: 612 of 612 complete Load avg: 6.76, 9.95, 8.35
* Messages for package sys-apps/dbus-1.12.20-r4 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-apps:dbus-1.12.20-r4:20220822-083927.log
* Some applications require a session bus in addition to the system
* bus. Please see `man dbus-launch` for more information.
*
* (Note: Above message is only printed the first time package is
* installed. Please look at /usr/share/doc/dbus-1.12.20-r4/README.gentoo*
* for future reference)
* Messages for package sys-apps/kmod-25-r2 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-apps:kmod-25-r2:20220822-083940.log
*
* You need to add kmod-static-nodes to the sysinit runlevel for
* kernel modules to have required static nodes!
* Run this command:
* rc-update add kmod-static-nodes sysinit
* Messages for package sys-apps/coreutils-8.32-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-apps:coreutils-8.32-r1:20220822-083950.log
* Make sure you run 'hash -r' in your active shells.
* You should also re-source your shell settings for LS_COLORS
* changes, such as: source /etc/profile
* Messages for package net-firewall/iptables-1.8.5 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-firewall:iptables-1.8.5:20220822-084025.log
* Current iptables implementation is unset, setting to xtables-legacy-multi
* Messages for package dev-libs/libxml2-2.9.13-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/dev-libs:libxml2-2.9.13-r1:20220822-084051.log
* Skipping XML catalog creation for stage building (bug #208887).
* Messages for package sys-libs/pam-1.3.1-r2 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-libs:pam-1.3.1-r2:20220822-084106.log
* Some software with pre-loaded PAM libraries might experience
* warnings or failures related to missing symbols and/or versions
* after any update. While unfortunate this is a limit of the
* implementation of PAM and the software, and it requires you to
* restart the software manually after the update.
*
* You can get a list of such software running a command like
* lsof / | egrep -i 'del.*libpam\.so'
*
* Alternatively, simply reboot your system.
* Messages for package chromeos-base/chromeos-base-1-r13 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/chromeos-base:chromeos-base-1-r13:20220822-084126.log
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at https://bugs.gentoo.org/ unless you report exactly
* which two packages install the same file(s). See
* https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
* to solve the problem. And once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/bin/sh
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
*
* Package 'chromeos-base/chromeos-base-1-r13' merged despite file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
* Messages for package sys-apps/util-linux-2.36.2-r3 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-apps:util-linux-2.36.2-r3:20220822-084139.log
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
* The agetty util now clears the terminal by default. You
* might want to add --noclear to your /etc/inittab lines.
* Messages for package app-admin/sudo-1.9.8_p2 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/app-admin:sudo-1.9.8_p2:20220822-084153.log
* Warning: tmpfiles.d not processed on ROOT != /. If you do not use
* a service manager supporting tmpfiles.d, you need to run
* the following command after booting (or chroot-ing with all
* appropriate filesystems mounted) into the ROOT:
*
* tmpfiles --create
*
* Failure to do so may result in missing runtime directories
* and failures to run programs or start services.
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
* Messages for package net-dialup/ppp-2.4.9-r6 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-dialup:ppp-2.4.9-r6:20220822-084147.log
* Unable to find kernel sources at /build/amd64-generic/usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Pon, poff and plog scripts have been supplied for experienced users.
* Users needing particular scripts (ssh,rsh,etc.) should check out the
* /usr/share/doc/ppp-2.4.9-r6/scripts directory.
* Messages for package dev-libs/glib-2.68.3-r2 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/dev-libs:glib-2.68.3-r2:20220822-084155.log
* Updating of GIO modules cache skipped due to cross-compilation.
* You might want to run gio-querymodules manually on the target for
* your final image for performance reasons and re-run it when packages
* installing GIO modules get upgraded or added to the image.
* Messages for package media-libs/fontconfig-2.13.0-r14 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/media-libs:fontconfig-2.13.0-r14:20220822-084208.log
* Please make fontconfig configuration changes using `eselect
* fontconfig`. Any changes made to /etc/fonts/fonts.conf will be
* overwritten. If you need to reset your configuration to upstream
* defaults, delete the directory /build/nautilus/etc/fonts/conf.d/ and
* re-emerge fontconfig.
*
* (Note: Above message is only printed the first time package is
* installed. Please look at /usr/share/doc/fontconfig-2.13.0-r14/README.gentoo*
* for future reference)
* Messages for package sys-auth/nss-mdns-0.13-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-auth:nss-mdns-0.13-r1:20220822-084258.log
* You have to modify your name service switch look up file to enable
* multicast DNS lookups. If you wish to resolve only IPv6 addresses
* use mdns6. For IPv4 addresses only, use mdns4. To resolve both
* use mdns. Keep in mind that mdns will be slower if there are no
* IPv6 addresses published via mDNS on the network. There are also
* minimal (mdns?_minimal) libraries which only lookup .local hosts
* and 169.254.x.x addresses.
*
* Add the appropriate mdns into the hosts line in /etc/nsswitch.conf.
* An example line looks like:
* hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
*
* If you want to perform mDNS lookups for domains other than the ones
* ending in .local, add them to /etc/mdns.allow.
* Messages for package sys-fs/lvm2-2.02.187-r4 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-fs:lvm2-2.02.187-r4:20220822-084304.log
* Make sure the "lvm" init script is in the runlevels:
* # rc-update add lvm boot
*
* Make sure to enable lvmetad in /etc/lvm/lvm.conf if you want
* to enable lvm autoactivation and metadata caching.
* Messages for package net-misc/dhcpcd-7.2.5-r5 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-misc:dhcpcd-7.2.5-r5:20220822-084259.log
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
*
* If you activate the lookup-hostname hook to look up your hostname
* using the dns, you need to install net-dns/bind-tools.
* Messages for package media-gfx/sane-backends-1.1.1-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/media-gfx:sane-backends-1.1.1-r1:20220822-084329.log
* If you are using a USB scanner, add all users who want
* to access your scanner to the "scanner" group.
* Messages for package net-fs/samba-4.15.5-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-fs:samba-4.15.5-r1:20220822-084346.log
* Warning: tmpfiles.d not processed on ROOT != /. If you do not use
* a service manager supporting tmpfiles.d, you need to run
* the following command after booting (or chroot-ing with all
* appropriate filesystems mounted) into the ROOT:
*
* tmpfiles --create
*
* Failure to do so may result in missing runtime directories
* and failures to run programs or start services.
* Be aware that this release contains the best of all of Samba's
* technology parts, both a file server (that you can reasonably expect
* to upgrade existing Samba 3.x releases to) and the AD domain
* controller work previously known as 'samba4'.
*
* For further information and migration steps make sure to read
* https://samba.org/samba/history/samba-4.15.5.html
* https://wiki.samba.org/index.php/Samba4/HOWTO
* Messages for package net-vpn/strongswan-5.9.4-r3 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-vpn:strongswan-5.9.4-r3:20220822-084531.log
* Linux kernel version: 5.17.5-300.fc36.x86_64
>>> Using system located in ROOT tree /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/
14:17:10.477 INFO : Running: sudo depmod -ae -F /build/nautilus/lib/modules/4.4.302-21531-g0ff2d4453733/build/System.map -b /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs 4.4.302-21531-g0ff2d4453733
14:17:10.619 INFO : Generating license credits page. Time:
14:17:10.624 INFO : Running: sudo /mnt/host/source/chromite/licensing/licenses --board=nautilus --log-level error --generate-licenses --output /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/opt/google/chrome/resources/about_os_credits.html
!!! The following installed packages are masked:
- media-libs/kbl-hotword-support-0.0.5-r1::chipset-kbl (masked by: Google-TOS license(s))
A copy of the 'Google-TOS' license is located at '/mnt/host/source/src/third_party/chromiumos-overlay/licenses/Google-TOS'.
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
real 0m22.052s
user 0m20.362s
sys 0m1.018s
14:17:32.679 INFO : Running: sudo /mnt/host/source/chromite/bin/gconv_strip /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs
14:17:32.874: INFO: Searching for unused gconv files defined in /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/usr/lib64/gconv/gconv-modules
14:17:33.968: INFO: Will search for 1137 strings in 42 files
14:17:34.944: INFO: Done. Using 3 gconv modules. Removed 244 unused modules (7180.7 KiB) and 6 unused dependencies (879.9 KiB)
14:17:35.081 INFO : Running: /mnt/host/source/chromite/bin/cros_set_lsb_release --sysroot=/mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs --board=nautilus --unibuild --keyset=devkeys --version_string=14790.4.0-d2022_08_22_140615 --auserver= --devserver= --buildbot_build=N/A --track=developer-build --branch_number=4 --build_number=14790 --chrome_milestone=103 --patch_number=0-d2022_08_22_140615
14:17:35.199: WARNING: please check your /etc/hosts file; resolving your hostname (192.168.1.101) failed: [Errno 2] Host name lookup failure
14:17:35.209: INFO: run: sudo -- setfattr -n security.selinux -v u:object_r:cros_conf_file:s0 /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/etc/lsb-release
setfattr: /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/etc/lsb-release: Invalid argument
cros_set_lsb_release: Unhandled exception:
Traceback (most recent call last):
File "/mnt/host/source/chromite/bin/cros_set_lsb_release", line 208, in <module>
DoMain()
File "/mnt/host/source/chromite/bin/cros_set_lsb_release", line 204, in DoMain
commandline.ScriptWrapperMain(FindTarget)
File "/mnt/host/source/chromite/lib/commandline.py", line 1037, in ScriptWrapperMain
ret = target(argv[1:])
File "/mnt/host/source/chromite/scripts/cros_set_lsb_release.py", line 210, in main
image_lib.WriteLsbRelease(opts.sysroot, fields)
File "/mnt/host/source/chromite/lib/image_lib.py", line 320, in WriteLsbRelease
'u:object_r:cros_conf_file:s0', path])
File "/mnt/host/source/chromite/lib/cros_build_lib.py", line 461, in sudo_run
return run(sudo_cmd, **kwargs)
File "/mnt/host/source/chromite/lib/cros_build_lib.py", line 915, in run
raise RunCommandError(msg, cmd_result)
chromite.lib.cros_build_lib.RunCommandError: return code: 1; command: sudo -- setfattr -n security.selinux -v u:object_r:cros_conf_file:s0 /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/etc/lsb-release
cmd=['sudo', '--', 'setfattr', '-n', 'security.selinux', '-v', 'u:object_r:cros_conf_file:s0', '/mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/etc/lsb-release']
Entering /mnt/host/source/src/scripts/mount_gpt_image.sh --unmount --from /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/chromiumos_base_image.bin --rootfs_mountpt /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs --stateful_mountpt /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/stateful --esp_mountpt /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/esp --delete_mountpts
14:17:35.369 INFO : Unmounting image from /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/stateful and /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs
14:17:35.370 INFO : Unmounting temporary rootfs /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs//build/rootfs.
Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/stateful/dev_image
14:17:35.402 INFO : Running sync -f /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/chromiumos_base_image.bin
partx: specified range <1:0> does not make sense
An error occurred in your build so your latest output directory is invalid.
Would you like to delete the output directory (y/N)? y
Deleted /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1
(cr) (stabilize-14790.B/(c97e8a1...)) uajain@192 ~/chromiumos/src/scripts $
* Messages for package sys-apps/dbus-1.12.20-r4 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-apps:dbus-1.12.20-r4:20220822-083927.log
* Some applications require a session bus in addition to the system
* bus. Please see `man dbus-launch` for more information.
*
* (Note: Above message is only printed the first time package is
* installed. Please look at /usr/share/doc/dbus-1.12.20-r4/README.gentoo*
* for future reference)
* Messages for package sys-apps/kmod-25-r2 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-apps:kmod-25-r2:20220822-083940.log
*
* You need to add kmod-static-nodes to the sysinit runlevel for
* kernel modules to have required static nodes!
* Run this command:
* rc-update add kmod-static-nodes sysinit
* Messages for package sys-apps/coreutils-8.32-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-apps:coreutils-8.32-r1:20220822-083950.log
* Make sure you run 'hash -r' in your active shells.
* You should also re-source your shell settings for LS_COLORS
* changes, such as: source /etc/profile
* Messages for package net-firewall/iptables-1.8.5 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-firewall:iptables-1.8.5:20220822-084025.log
* Current iptables implementation is unset, setting to xtables-legacy-multi
* Messages for package dev-libs/libxml2-2.9.13-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/dev-libs:libxml2-2.9.13-r1:20220822-084051.log
* Skipping XML catalog creation for stage building (bug #208887).
* Messages for package sys-libs/pam-1.3.1-r2 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-libs:pam-1.3.1-r2:20220822-084106.log
* Some software with pre-loaded PAM libraries might experience
* warnings or failures related to missing symbols and/or versions
* after any update. While unfortunate this is a limit of the
* implementation of PAM and the software, and it requires you to
* restart the software manually after the update.
*
* You can get a list of such software running a command like
* lsof / | egrep -i 'del.*libpam\.so'
*
* Alternatively, simply reboot your system.
* Messages for package chromeos-base/chromeos-base-1-r13 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/chromeos-base:chromeos-base-1-r13:20220822-084126.log
* This package will overwrite one or more files that may belong to other
* packages (see list below). You can use a command such as `portageq
* owners / <filename>` to identify the installed package that owns a
* file. If portageq reports that only one package owns a file then do
* NOT file a bug report. A bug report is only useful if it identifies at
* least two or more packages that are known to install the same file(s).
* If a collision occurs and you can not explain where the file came from
* then you should simply ignore the collision since there is not enough
* information to determine if a real problem exists. Please do NOT file
* a bug report at https://bugs.gentoo.org/ unless you report exactly
* which two packages install the same file(s). See
* https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
* to solve the problem. And once again, please do NOT file a bug report
* unless you have completely understood the above message.
*
* Detected file collision(s):
*
* /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/bin/sh
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* None of the installed packages claim the file(s).
*
* Package 'chromeos-base/chromeos-base-1-r13' merged despite file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
* Messages for package sys-apps/util-linux-2.36.2-r3 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-apps:util-linux-2.36.2-r3:20220822-084139.log
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
* The agetty util now clears the terminal by default. You
* might want to add --noclear to your /etc/inittab lines.
* Messages for package app-admin/sudo-1.9.8_p2 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/app-admin:sudo-1.9.8_p2:20220822-084153.log
* Warning: tmpfiles.d not processed on ROOT != /. If you do not use
* a service manager supporting tmpfiles.d, you need to run
* the following command after booting (or chroot-ing with all
* appropriate filesystems mounted) into the ROOT:
*
* tmpfiles --create
*
* Failure to do so may result in missing runtime directories
* and failures to run programs or start services.
* To use the -A (askpass) option, you need to install a compatible
* password program from the following list. Starred packages will
* automatically register for the use with sudo (but will not force
* the -A option):
*
* [*] net-misc/ssh-askpass-fullscreen
* net-misc/x11-ssh-askpass
*
* You can override the choice by setting the SUDO_ASKPASS environmnent
* variable to the program you want to use.
* Messages for package net-dialup/ppp-2.4.9-r6 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-dialup:ppp-2.4.9-r6:20220822-084147.log
* Unable to find kernel sources at /build/amd64-generic/usr/src/linux
* Unable to calculate Linux Kernel version for build, attempting to use running version
* Pon, poff and plog scripts have been supplied for experienced users.
* Users needing particular scripts (ssh,rsh,etc.) should check out the
* /usr/share/doc/ppp-2.4.9-r6/scripts directory.
* Messages for package dev-libs/glib-2.68.3-r2 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/dev-libs:glib-2.68.3-r2:20220822-084155.log
* Updating of GIO modules cache skipped due to cross-compilation.
* You might want to run gio-querymodules manually on the target for
* your final image for performance reasons and re-run it when packages
* installing GIO modules get upgraded or added to the image.
* Messages for package media-libs/fontconfig-2.13.0-r14 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/media-libs:fontconfig-2.13.0-r14:20220822-084208.log
* Please make fontconfig configuration changes using `eselect
* fontconfig`. Any changes made to /etc/fonts/fonts.conf will be
* overwritten. If you need to reset your configuration to upstream
* defaults, delete the directory /build/nautilus/etc/fonts/conf.d/ and
* re-emerge fontconfig.
*
* (Note: Above message is only printed the first time package is
* installed. Please look at /usr/share/doc/fontconfig-2.13.0-r14/README.gentoo*
* for future reference)
* Messages for package sys-auth/nss-mdns-0.13-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-auth:nss-mdns-0.13-r1:20220822-084258.log
* You have to modify your name service switch look up file to enable
* multicast DNS lookups. If you wish to resolve only IPv6 addresses
* use mdns6. For IPv4 addresses only, use mdns4. To resolve both
* use mdns. Keep in mind that mdns will be slower if there are no
* IPv6 addresses published via mDNS on the network. There are also
* minimal (mdns?_minimal) libraries which only lookup .local hosts
* and 169.254.x.x addresses.
*
* Add the appropriate mdns into the hosts line in /etc/nsswitch.conf.
* An example line looks like:
* hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
*
* If you want to perform mDNS lookups for domains other than the ones
* ending in .local, add them to /etc/mdns.allow.
* Messages for package sys-fs/lvm2-2.02.187-r4 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/sys-fs:lvm2-2.02.187-r4:20220822-084304.log
* Make sure the "lvm" init script is in the runlevels:
* # rc-update add lvm boot
*
* Make sure to enable lvmetad in /etc/lvm/lvm.conf if you want
* to enable lvm autoactivation and metadata caching.
* Messages for package net-misc/dhcpcd-7.2.5-r5 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-misc:dhcpcd-7.2.5-r5:20220822-084259.log
*
* dhcpcd has zeroconf support active by default.
* This means it will always obtain an IP address even if no
* DHCP server can be contacted, which will break any existing
* failover support you may have configured in your net configuration.
* This behaviour can be controlled with the noipv4ll configuration
* file option or the -L command line switch.
* See the dhcpcd and dhcpcd.conf man pages for more details.
*
* Dhcpcd has duid enabled by default, and this may cause issues
* with some dhcp servers. For more information, see
* https://bugs.gentoo.org/show_bug.cgi?id=477356
*
* If you activate the lookup-hostname hook to look up your hostname
* using the dns, you need to install net-dns/bind-tools.
* Messages for package media-gfx/sane-backends-1.1.1-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/media-gfx:sane-backends-1.1.1-r1:20220822-084329.log
* If you are using a USB scanner, add all users who want
* to access your scanner to the "scanner" group.
* Messages for package net-fs/samba-4.15.5-r1 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-fs:samba-4.15.5-r1:20220822-084346.log
* Warning: tmpfiles.d not processed on ROOT != /. If you do not use
* a service manager supporting tmpfiles.d, you need to run
* the following command after booting (or chroot-ing with all
* appropriate filesystems mounted) into the ROOT:
*
* tmpfiles --create
*
* Failure to do so may result in missing runtime directories
* and failures to run programs or start services.
* Be aware that this release contains the best of all of Samba's
* technology parts, both a file server (that you can reasonably expect
* to upgrade existing Samba 3.x releases to) and the AD domain
* controller work previously known as 'samba4'.
*
* For further information and migration steps make sure to read
* https://samba.org/samba/history/samba-4.15.5.html
* https://wiki.samba.org/index.php/Samba4/HOWTO
* Messages for package net-vpn/strongswan-5.9.4-r3 merged to /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/:
* Log file: /build/nautilus/tmp/portage/logs/net-vpn:strongswan-5.9.4-r3:20220822-084531.log
* Linux kernel version: 5.17.5-300.fc36.x86_64
>>> Using system located in ROOT tree /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/
14:17:10.477 INFO : Running: sudo depmod -ae -F /build/nautilus/lib/modules/4.4.302-21531-g0ff2d4453733/build/System.map -b /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs 4.4.302-21531-g0ff2d4453733
14:17:10.619 INFO : Generating license credits page. Time:
14:17:10.624 INFO : Running: sudo /mnt/host/source/chromite/licensing/licenses --board=nautilus --log-level error --generate-licenses --output /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/opt/google/chrome/resources/about_os_credits.html
!!! The following installed packages are masked:
- media-libs/kbl-hotword-support-0.0.5-r1::chipset-kbl (masked by: Google-TOS license(s))
A copy of the 'Google-TOS' license is located at '/mnt/host/source/src/third_party/chromiumos-overlay/licenses/Google-TOS'.
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.
real 0m22.052s
user 0m20.362s
sys 0m1.018s
14:17:32.679 INFO : Running: sudo /mnt/host/source/chromite/bin/gconv_strip /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs
14:17:32.874: INFO: Searching for unused gconv files defined in /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/usr/lib64/gconv/gconv-modules
14:17:33.968: INFO: Will search for 1137 strings in 42 files
14:17:34.944: INFO: Done. Using 3 gconv modules. Removed 244 unused modules (7180.7 KiB) and 6 unused dependencies (879.9 KiB)
14:17:35.081 INFO : Running: /mnt/host/source/chromite/bin/cros_set_lsb_release --sysroot=/mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs --board=nautilus --unibuild --keyset=devkeys --version_string=14790.4.0-d2022_08_22_140615 --auserver= --devserver= --buildbot_build=N/A --track=developer-build --branch_number=4 --build_number=14790 --chrome_milestone=103 --patch_number=0-d2022_08_22_140615
14:17:35.199: WARNING: please check your /etc/hosts file; resolving your hostname (192.168.1.101) failed: [Errno 2] Host name lookup failure
14:17:35.209: INFO: run: sudo -- setfattr -n security.selinux -v u:object_r:cros_conf_file:s0 /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/etc/lsb-release
setfattr: /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/etc/lsb-release: Invalid argument
cros_set_lsb_release: Unhandled exception:
Traceback (most recent call last):
File "/mnt/host/source/chromite/bin/cros_set_lsb_release", line 208, in <module>
DoMain()
File "/mnt/host/source/chromite/bin/cros_set_lsb_release", line 204, in DoMain
commandline.ScriptWrapperMain(FindTarget)
File "/mnt/host/source/chromite/lib/commandline.py", line 1037, in ScriptWrapperMain
ret = target(argv[1:])
File "/mnt/host/source/chromite/scripts/cros_set_lsb_release.py", line 210, in main
image_lib.WriteLsbRelease(opts.sysroot, fields)
File "/mnt/host/source/chromite/lib/image_lib.py", line 320, in WriteLsbRelease
'u:object_r:cros_conf_file:s0', path])
File "/mnt/host/source/chromite/lib/cros_build_lib.py", line 461, in sudo_run
return run(sudo_cmd, **kwargs)
File "/mnt/host/source/chromite/lib/cros_build_lib.py", line 915, in run
raise RunCommandError(msg, cmd_result)
chromite.lib.cros_build_lib.RunCommandError: return code: 1; command: sudo -- setfattr -n security.selinux -v u:object_r:cros_conf_file:s0 /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/etc/lsb-release
cmd=['sudo', '--', 'setfattr', '-n', 'security.selinux', '-v', 'u:object_r:cros_conf_file:s0', '/mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs/etc/lsb-release']
Entering /mnt/host/source/src/scripts/mount_gpt_image.sh --unmount --from /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/chromiumos_base_image.bin --rootfs_mountpt /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs --stateful_mountpt /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/stateful --esp_mountpt /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/esp --delete_mountpts
14:17:35.369 INFO : Unmounting image from /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/stateful and /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs
14:17:35.370 INFO : Unmounting temporary rootfs /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/rootfs//build/rootfs.
Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/stateful/dev_image
14:17:35.402 INFO : Running sync -f /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1/chromiumos_base_image.bin
partx: specified range <1:0> does not make sense
An error occurred in your build so your latest output directory is invalid.
Would you like to delete the output directory (y/N)? y
Deleted /mnt/host/source/src/build/images/nautilus/R103-14790.4.0-d2022_08_22_140615-a1
(cr) (stabilize-14790.B/(c97e8a1...)) uajain@192 ~/chromiumos/src/scripts $
Any ideas on resolving this. The --board is nautilus.
Mike Frysinger
Aug 22, 2022, 11:29:37 AM8/22/22
to Umang Jain, ChromiumOS Development
the error message / failure mode here is terrible. but the answer is simple. please review:
-mike
--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev
Reply all
Reply to author
Forward
0 new messages