All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Jens Rehsack <rehsack@gmail.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Postinstall scriptlets of ['coreutils'] have failed
Date: Mon, 10 Sep 2018 21:09:02 +0200	[thread overview]
Message-ID: <CA+chaQfCMR13hmEgERwX1CKjsb78uxHk=Y2EG4BZ2OkSs6H3LQ@mail.gmail.com> (raw)
In-Reply-To: <852E6AB4-06E1-4D95-BD2F-7AF00D0B3B94@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 9844 bytes --]

pn-buildlist isn't really useful in this case, building both coreutils and
busybox doesn't imply that both will be actually included in the image..

If you compare installed-package-names.txt in buildhistory you'll see that
only the core-image-minimal-dev has coreutils installed.

docker-shr qemux86-64@ ~/build/oe-core/buildhistory/images/qemux86_64/glibc
$ grep busybox core-image-minimal*/installed-package-names.txt
core-image-minimal-dev/installed-package-names.txt:busybox
core-image-minimal-dev/installed-package-names.txt:busybox-dev
core-image-minimal-dev/installed-package-names.txt:busybox-syslog
core-image-minimal-dev/installed-package-names.txt:busybox-udhcpc
core-image-minimal/installed-package-names.txt:busybox
core-image-minimal/installed-package-names.txt:busybox-syslog
core-image-minimal/installed-package-names.txt:busybox-udhcpc
docker-shr qemux86-64@ ~/build/oe-core/buildhistory/images/qemux86_64/glibc
$ grep coreutils core-image-minimal*/installed-package-names.txt
core-image-minimal-dev/installed-package-names.txt:coreutils
core-image-minimal-dev/installed-package-names.txt:coreutils-dev

That's why the issue is shown only in core-image-minimal-dev.

Do you have custom busybox defconfig which enables nice applet? It's not
enabled in default config:
meta/recipes-core/busybox/busybox/defconfig:# CONFIG_NICE is not set




On Mon, Sep 10, 2018 at 8:15 PM Jens Rehsack <rehsack@gmail.com> wrote:

>
>
> Am 09.09.2018 um 20:56 schrieb Martin Jansa <martin.jansa@gmail.com>:
>
> Does core-image-minimal include both busybox and coreutils? Maybe only
> -dev include both.
>
>
> Unfortunately both include coreutils, see attached pn-buildlist (I can
> send you the recipe-depends and the task-depends, either if you need them).
>
> I'll send fix for attr soon, waiting for some builds to finish testing it.
>
>
> Seems similar to my kind of soon :-)
>
> On Sun, Sep 9, 2018 at 8:47 PM Jens Rehsack <rehsack@gmail.com> wrote:
>
>> So far, so good.
>>
>> They way to fix that seems either to check why busybox uses
>> ${base_bindir} nowadays in favor of ${bindir} and fix either busybox or
>> coreutils or attr.
>>
>> What drives me nuts is not only the failure after the busybox update -
>> why does core-image-minimal builds successful while core-image-minimal-dev
>> fails?
>>
>> Cheers,
>> Jens
>>
>> Am 09.09.2018 um 19:27 schrieb Martin Jansa <martin.jansa@gmail.com>:
>>
>> busybox is most likely the one providing it in ${base_bindir}
>>
>> Recent busybox upgrade probably moved this file.
>>
>> There is also conflict on /usr/bin/setfattr between busybox and attr now.
>>
>> On Sun, Sep 9, 2018 at 7:22 PM Martin Jansa <martin.jansa@gmail.com>
>> wrote:
>>
>>> There are 2 packages using u-a for nice, but one is using {bindir} and
>>> 2nd one is using {base_bindir}
>>>
>>> coreutils is using bindir, find what's using ${base_bindir} and change
>>> one of them to use the same u-a link as the other one.
>>>
>>> On Sun, Sep 9, 2018 at 5:59 PM Jens Rehsack <rehsack@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> Am 09.09.2018 um 13:15 schrieb Alexander Kanavin <
>>>> alex.kanavin@gmail.com>:
>>>>
>>>> It's right in the message?
>>>>
>>>> ERROR: Logfile of failure stored in:
>>>>
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/temp/log.do_rootfs.27709
>>>>
>>>> Alex
>>>>
>>>>
>>>>
>>>> It's not much what stands there:
>>>>
>>>> Downloading
>>>> file:/home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/oe-rootfs-repo/core2-64/libcap-dev_2.25-r0_core2-64.ipk.
>>>> Installing coreutils-dev (8.30) on root
>>>> [...]
>>>> Configuring update-rc.d-deupdate-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/diff
>>>> to /usr/bin/diff.diffutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/cmp
>>>> to /usr/bin/cmp.diffutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/bin/umount
>>>> to /bin/umount.util-linux
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/[
>>>> to /usr/bin/lbracket.coreutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/arch
>>>> to /usr/bin/arch.coreutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/basename
>>>> to /usr/bin/basename.coreutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/chcon
>>>> to /usr/bin/chcon.coreutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/cksum
>>>> to /usr/bin/cksum.coreutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/comm
>>>> to /usr/bin/comm.coreutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/csplit
>>>> to /usr/bin/csplit.coreutils
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/cut
>>>> to /usr/bin/cut.coreutils
>>>> [...]
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/mkfifo
>>>> to /usr/bin/mkfifo.coreutils
>>>> update-alternatives: renaming nice link from /bin/nice to /usr/bin/nice
>>>> mv: cannot stat '/bin/nice': No such file or directory
>>>> update-alternatives: Linking
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/bin/bash
>>>> to /bin/bash.bash
>>>> [...]
>>>> Configuring libgmp10.
>>>> Configuring coreutils.
>>>> coreutils.postinst returned 1, marking as unpacked only, configuration
>>>> required on target.
>>>> Configuring acl.
>>>> [...]
>>>>
>>>> The postinst file of coreutils contains only a long list of
>>>> update-alternatives, as many other packages do either.
>>>>
>>>> core-image-minimal contains coreutils as well, but it doesn't fail the
>>>> same way.
>>>>
>>>> Any ideas?
>>>>
>>>> 2018-09-09 10:58 GMT+02:00 Jens Rehsack <rehsack@gmail.com>:
>>>>
>>>> Hi,
>>>>
>>>> I got following issue when building an image for live-debugging:
>>>>
>>>> ERROR: updatable-app-dev-image-1.0-r0 do_rootfs: Postinstall scriptlets
>>>> of ['coreutils'] have failed. If the intention is to defer them to first
>>>> boot,
>>>> then please place them into pkg_postinst_ontarget_${PN} ().
>>>> Deferring to first boot via 'exit 1' is no longer supported.
>>>> Details of the failure are in
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/updatable-app-dev-image/1.0-r0/temp/log.do_rootfs.
>>>> ERROR: updatable-app-dev-image-1.0-r0 do_rootfs: Function failed:
>>>> do_rootfs
>>>> ERROR: Logfile of failure stored in:
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/updatable-app-dev-image/1.0-r0/temp/log.do_rootfs.14358
>>>> ERROR: Task
>>>> (/home/sno/gpw-community-bsp/sources/meta-jens/recipes-images/images/updatable-app-dev-image.bb:do_rootfs)
>>>> failed with exit code '1'
>>>>
>>>> I can reproduce it using core-image-minimal-dev
>>>>
>>>> WARNING: core-image-minimal-dev-1.0-r0 do_rootfs: coreutils.postinst
>>>> returned 1, marking as unpacked only, configuration required on target.
>>>> ERROR: core-image-minimal-dev-1.0-r0 do_rootfs: Postinstall scriptlets
>>>> of ['coreutils'] have failed. If the intention is to defer them to first
>>>> boot,
>>>> then please place them into pkg_postinst_ontarget_${PN} ().
>>>> Deferring to first boot via 'exit 1' is no longer supported.
>>>> Details of the failure are in
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/temp/log.do_rootfs.
>>>> ERROR: core-image-minimal-dev-1.0-r0 do_rootfs: Function failed:
>>>> do_rootfs
>>>> ERROR: Logfile of failure stored in:
>>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/temp/log.do_rootfs.27709
>>>> ERROR: Task
>>>> (/home/sno/gpw-community-bsp/sources/poky/meta/recipes-core/images/core-image-minimal-dev.bb:do_rootfs)
>>>> failed with exit code '1'
>>>>
>>>> Any idea where to start debugging?
>>>>
>>>> Best regards
>>>> --
>>>> Jens Rehsack - rehsack@gmail.com
>>>>
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>>
>>>> --
>>>> Jens Rehsack - rehsack@gmail.com
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/yocto
>>>>
>>>
>> --
>> Jens Rehsack - rehsack@gmail.com
>>
>>
> --
> Jens Rehsack - rehsack@gmail.com
>
>

[-- Attachment #2: Type: text/html, Size: 14080 bytes --]

  reply	other threads:[~2018-09-10 19:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-09  8:58 Postinstall scriptlets of ['coreutils'] have failed Jens Rehsack
2018-09-09 11:15 ` Alexander Kanavin
2018-09-09 15:59   ` Jens Rehsack
2018-09-09 17:22     ` Martin Jansa
2018-09-09 17:27       ` Martin Jansa
2018-09-09 18:47         ` Jens Rehsack
2018-09-09 18:56           ` Martin Jansa
2018-09-10 18:15             ` Jens Rehsack
2018-09-10 19:09               ` Martin Jansa [this message]
2018-09-11 16:36                 ` Jens Rehsack

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='CA+chaQfCMR13hmEgERwX1CKjsb78uxHk=Y2EG4BZ2OkSs6H3LQ@mail.gmail.com' \
    --to=martin.jansa@gmail.com \
    --cc=rehsack@gmail.com \
    --cc=yocto@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.