* package manager contamination in state?
@ 2018-03-15 20:12 Peter A. Bigot
2018-03-16 10:31 ` Alexander Kanavin
0 siblings, 1 reply; 2+ messages in thread
From: Peter A. Bigot @ 2018-03-15 20:12 UTC (permalink / raw)
To: yocto
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: package manager contamination in state?
2018-03-15 20:12 package manager contamination in state? Peter A. Bigot
@ 2018-03-16 10:31 ` Alexander Kanavin
0 siblings, 0 replies; 2+ messages in thread
From: Alexander Kanavin @ 2018-03-16 10:31 UTC (permalink / raw)
To: Peter A. Bigot, yocto
On 03/15/2018 10:12 PM, Peter A. Bigot wrote:
> 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"
Note that we don't test deb packaging all that well. I'm not even sure
images are regularly built with it on the autobuilder. It does seem like
apt has some kind of dependency problem where dnf sees none.
Alex
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-03-16 10:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-15 20:12 package manager contamination in state? Peter A. Bigot
2018-03-16 10:31 ` Alexander Kanavin
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.