From: "Peter A. Bigot" <pab@pabigot.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: package manager contamination in state?
Date: Thu, 15 Mar 2018 15:12:46 -0500 [thread overview]
Message-ID: <a2bf42e9-7edf-afab-9abd-41f02161d832@pabigot.com> (raw)
While attempting to diagnose a package index problem visible on current
poky head I changed local.conf from:
PACKAGE_CLASSES ?= "package_rpm"
to
PACKAGE_CLASSES ?= "package_deb"
then removed tmp and buildhistory. Rebuilding the image produced:
ERROR: pabigot-image-cmdline-sdk-1.0-r0 do_rootfs: Unable to install
packages. Command
'/mnt/devel/yocto/build-rpi3-sumo/tmp/work/raspberrypi3-poky-linux-gnueabi/pabigot-image-cmdline-sdk/1.0-r0/recipe-sysroot-native/usr/bin/apt-get
install --force-yes --allow-unauthenticated git
packagegroup-core-full-cmdline packagegroup-core-standalone-sdk-target
kernel-modules apt dpkg packagegroup-core-boot oe-build-info
psplash-raspberrypi bluez5 bluez5-dev run-postinsts nodejs
bluez5-noinst-tools connman vim packagegroup-core-sdk bluez5-testtools
packagegroup-core-ssh-openssh packagegroup-base connman-client minicom
linux-firmware' returned 100:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
packagegroup-core-full-cmdline : Depends:
packagegroup-core-full-cmdline-initscripts but it is not going to be
installed
E: Unable to correct problems, you have held broken packages.
Reverting to package_rpm and doing a clean build worked fine, so it
appears something in the state that's dependent on the package manager
is not getting rebuilt. Based on the complaint the following additional
configuration settings in local.conf might be relevant:
# Section 4.24 Selecting an Initialization Manager
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
FYI only, I have no reason to switch between packaging systems like this
normally.
Peter
next reply other threads:[~2018-03-15 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 20:12 Peter A. Bigot [this message]
2018-03-16 10:31 ` package manager contamination in state? Alexander Kanavin
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=a2bf42e9-7edf-afab-9abd-41f02161d832@pabigot.com \
--to=pab@pabigot.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.