Public bug reported:

---Problem Description---
Package dependencies wrong/missing in s390-tools.

debootstrap fails to build minimal image with s390-tools package included
 
 
---Steps to Reproduce---
 debootstrap --variant=minbase \
            
--include=udev,kmod,s390-tools,s390-tools-zkey,,systemd,linux-image-generic \
            --exclude=man,bash-completion \
            --verbose \
            resolute ./target

This fails

LOG OUTPUT:
Setting up s390-tools (2.41.0-0ubuntu3) ...
/var/lib/dpkg/info/s390-tools.postinst: 11: addgroup: not found
dpkg: error processing package s390-tools (--configure):
 old s390-tools package postinst maintainer script subprocess failed with exit 
status 127
 
---uname output---
Linux hurlnxlr 6.8.0-117-generic #117-Ubuntu SMP Thu May  7 21:01:36 UTC 2026 
s390x s390x s390x GNU/Linux
 
Machine Type = 9175-7F0 
 
The userspace tool has the following bit modes: both 

Userspace package: s390-tools 
 
Userspace tool common name: s390-tools package  
 


Docker containers running Ubuntu 25.10 are affected too.
s390-tools cannot be installed without manually adding the adduser package as a 
dependency.

** Affects: linux (Ubuntu)
     Importance: Undecided
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: New


** Tags: architecture-s39064 bugnameltc-219458 severity-high 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-219458 severity-high
targetmilestone-inin---

** Changed in: ubuntu
     Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2162891

Title:
  Package dependencies wrong/missing in s390-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162891/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to