[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#857338: marked as done (systemd-sysv: pre-depends fails to resolve in cross-architecture debootstrap from jessie)

Your message dated Fri, 9 Mar 2018 22:49:03 +0900
with message-id <20180309224903.f8081c11d0be496f27e081be@debian.org>
and subject line 
has caused the Debian Bug report #857338,
regarding systemd-sysv: pre-depends fails to resolve in cross-architecture debootstrap from jessie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
857338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857338
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: systemd-sysv
Version: 232-19
Severity: important

On a Jessie amd64 system, install qemu-static-arm and run:

sudo debootstrap --arch=arm64 --foreign --include  systemd-sysv sid sid-arm64 http://localhost/debian
sudo cp /usr/bin/qemu-aarch64-static sid-arm64/usr/bin
sudo chroot sid-arm64 ./debootstrap/debootstrap --second-stage

Assigning the bug to systemd-sysv as this is the trigger package.

This fails but completes when run on arm64 natively or when using debootstrap from stretch or sid.

https://publishing-linaro-org.s3.amazonaws.com/snapshots/components/lava/standard/debian/sid/arm64/7/sid-arm64/debootstrap/debootstrap.log?Signature=vM7ptL1vb7vVaucnfd6wuto5uVU%3D&Expires=1489132875&AWSAccessKeyId=AKIAIJR2J6C42QCU7ITAi

Unpacking systemd (232-19) ...
Selecting previously unselected package systemd-sysv.
dpkg: regarding .../systemd-sysv_232-19_arm64.deb containing systemd-sysv, pre-dependency problem:
 systemd-sysv pre-depends on systemd
  systemd is unpacked, but has never been configured.

dpkg: error processing archive /var/cache/apt/archives/systemd-sysv_232-19_arm64.deb (--unpack):
 pre-dependency problem - not installing systemd-sysv

dpkg: regarding .../archives/init_1.47_arm64.deb containing init, pre-dependency problem:
 init pre-depends on systemd-sysv | sysvinit-core
  systemd-sysv is not installed.
  sysvinit-core is not installed.

dpkg: error processing archive /var/cache/apt/archives/init_1.47_arm64.deb (--unpack):
 pre-dependency problem - not installing init

dpkg: regarding .../systemd-sysv_232-19_arm64.deb containing systemd-sysv, pre-dependency problem:
 systemd-sysv pre-depends on systemd
  systemd is unpacked, but has never been configured.

dpkg: error processing archive /var/cache/apt/archives/systemd-sysv_232-19_arm64.deb (--unpack):
 pre-dependency problem - not installing systemd-sysv

dpkg: version 232-19 of systemd already installed, skipping
dpkg: regarding .../systemd-sysv_232-19_arm64.deb containing systemd-sysv, pre-dependency problem:
 systemd-sysv pre-depends on systemd
  systemd is unpacked, but has never been configured.

dpkg: error processing archive /var/cache/apt/archives/systemd-sysv_232-19_arm64.deb (--unpack):
 pre-dependency problem - not installing systemd-sysv

running dpkg --configure --pending seems to fix things



-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-sysv depends on:
ii  systemd  232-19

systemd-sysv recommends no packages.

systemd-sysv suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
It's already fixed in current version (and backports), so let's close it...

--- End Message ---
Reply to: