FS#31795 - [schroot] - Requires /etc/rc.conf to work which is problematic on pure systemd systems

Attached to Project: Community Packages
Opened by John (graysky) - Wednesday, 03 October 2012, 20:21 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 19 November 2012, 14:31 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Running on a pure systemd system, schroot does not work without /etc/rc.conf present. This is moved to /etc/rc.conf.pacsave upon installation of core/systemd-sysvcompat for example. The problem is caused by line 5 in the included /etc/schroot/arch32/copyfiles but I do not know what the best way to circumvent this is for users running a pure systemd setup short of having them edit the file by hand.

Just wanted to bring this to your attention.

Output:
% schroot -p -- uname -a
E: 15binfmt: which: no update-binfmts in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)
E: 20copyfiles: error: Not copying nonexistent file: /etc/rc.conf
E: 15binfmt: which: no update-binfmts in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin)
E: Arch32-be10d24c-3849-473f-a2d1-b512f0d841e9: Chroot setup failed: stage=setup-start

Additional info:
* package version(s) 1.6.3-1.

Steps to reproduce:

Run a schroot command on a pure systemd system.
This task depends upon

Closed by  Sergej Pupykin (sergej)
Monday, 19 November 2012, 14:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  in 1.6.3-2
Comment by Greg (dolby) - Monday, 19 November 2012, 07:29 GMT
Is this fixed in the systemd units rebuild?

Loading...