From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: Khem Raj <raj.khem@gmail.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] #yocto #kernel
Date: Thu, 14 Jan 2021 17:31:33 +0000 [thread overview]
Message-ID: <MADEUP.165A298C367D3856.8149@lists.yoctoproject.org> (raw)
In-Reply-To: <20210114171809.joferqzcexsonuik@qschulz>
Do we know why it was disabled ?
I will look into this, thanks...
-----Original Message-----
From: Quentin Schulz <quentin.schulz@streamunlimited.com>
Sent: Thursday, January 14, 2021 12:18 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>
Cc: Khem Raj <raj.khem@gmail.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] #yocto #kernel
*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.
Hi Steve,
On Thu, Jan 14, 2021 at 05:11:29PM +0000, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
>
> Khem:
>
> Should have waited for build to complete... this just delays where the error occurs.
>
> Now rather than upfront, it fails on packaging with the following error:
>
> ERROR: aiox-defaultfs-1.0-r0 do_rootfs: Unable to install packages. Command '/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/aiox_default-poky-linux/aiox-defaultfs/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/aiox_default-poky-linux/aiox-defaultfs/1.0-r0/opkg.conf -t /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/aiox_default-poky-linux/aiox-defaultfs/1.0-r0/temp/ipktemp/ -o /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/aiox-default/tmp/work/aiox_default-poky-linux/aiox-defaultfs/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version install base-files bash bc binutils bridge-utils coreutils crush cs-hdlc dhcp-server dhcp-server-config e2fsprogs ethtool haveged hdparm i2c-tools inetutils inetutils-rsh iperf3 iproute2 iptables iputils iputils-ping kernel-modules key-helper kmod libpci3 module-init-tools mtd-utils mtd-utils-ubifs nano ncurses ncurses-dev net-tools netcat nfs-utils nfs-utils-stats ntfs-3g ntfsprogs openssh openssh-sftp-server packagegroup-base-vfat packagegroup-core-boot pciutils pciutils-ids peekpoke perl plx8000 plx8000nt plxsvc pub-key python python-stringold python-subprocess rsync run-postinsts sg3-utils swig tar tcpdump tftp-hpa tftp-hpa-server traceroute usbutils util-linux wolfssl xinetd' returned 255:
> Collected errors:
> * opkg_prepare_url_for_install: Couldn't find anything to satisfy 'inetutils-rsh'.
>
> What has changed in the build process ?, under rocko I do not see an issue adding inetutils-rsh...
>
http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-connectivity/inetutils?h=zeus&id=9e13dad6ea76dd036098ef62427804e4138bf83b
It's disabled by default now.
You can probably re-enable it by appending --enable-rsh again I guess?
Quentin
next prev parent reply other threads:[~2021-01-14 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 16:24 [yocto] #yocto #kernel Monsees, Steven C (US)
2021-01-14 16:59 ` Monsees, Steven C (US)
2021-01-14 17:11 ` Monsees, Steven C (US)
2021-01-14 17:18 ` Quentin Schulz
2021-01-14 17:31 ` Monsees, Steven C (US) [this message]
[not found] <52181919-28a0-a134-687e-b24c8bd8b470@gmail.com>
2021-01-15 18:42 ` Monsees, Steven C (US)
[not found] <60007037.1c69fb81.20ade.fe01SMTPIN_ADDED_MISSING@mx.google.com>
2021-01-14 18:37 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2021-01-13 13:16 Monsees, Steven C (US)
2021-01-13 19:24 ` Monsees, Steven C (US)
2021-01-14 18:36 ` Khem Raj
2021-01-14 18:46 ` Monsees, Steven C (US)
2021-01-12 20:09 Monsees, Steven C (US)
2021-01-12 23:12 ` [yocto] " Khem Raj
2021-01-13 12:15 ` Monsees, Steven C (US)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=MADEUP.165A298C367D3856.8149@lists.yoctoproject.org \
--to=steven.monsees@baesystems.com \
--cc=quentin.schulz@streamunlimited.com \
--cc=raj.khem@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.