Description of problem: ... Installing : systemd-219-13.fc22.x86_64 17/19 grep: /etc/vconsole.conf: No such file or directory sed: can't read /etc/vconsole.conf: No such file or directory ... Version-Release number of selected component (if applicable): systemd-219-13.fc22.x86_64 How reproducible: Always. Steps to Reproduce: 1. mock -r fedora-22-x86_64 --init 2. mock -r fedora-22-x86_64 --install systemd Actual results: c.f. above.
http://pkgs.fedoraproject.org/cgit/systemd.git/commit/?h=f22&id=7f8958cefa3c7930516e80d8620794f90fb842ee
IMO, this change is an ugly cludge, which only hides away the issue, without fixing it. How about writing a clean and proper shell script instead?
systemd-219-14.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/systemd-219-14.fc22
Package systemd-219-14.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-219-14.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-8121/systemd-219-14.fc22 then log in and leave karma (feedback).
(In reply to Ralf Corsepius from comment #2) > IMO, this change is an ugly cludge, which only hides away the issue, without > fixing it. > > How about writing a clean and proper shell script instead? What exactly is wrong with the script? What would you propose instead?
systemd-219-14.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.