From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12726] systemctl preset-all failed for ctrl-alt-del.target
Date: Sat, 11 Apr 2020 19:14:12 +0000 [thread overview]
Message-ID: <bug-12726-163-QbnMwAdHxw@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12726-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=12726
Melanie <melanie@trash-mail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Melanie <melanie@trash-mail.com> ---
Okay, during further troubleshooting I realized that the problem was caused by
my custom configuration, which modifies the target directory (deletes all
preset-configuration-files) after the 'finalizing target directory' phase where
the 'systemctl preset-all' command runs (this explains why a full rebuild had
succeeded but subsequent partial rebuild attempts have failed).
The fact that the 'systemctl preset-all' command fails when there are no
preset-configuration-files at all on the target file system, is a systemd
issue, so I'm closing this bug report here as invalid.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-11 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 12:43 [Buildroot] [Bug 12726] New: systemctl preset-all failed for ctrl-alt-del.target bugzilla at busybox.net
2020-04-01 18:09 ` [Buildroot] [Bug 12726] " bugzilla at busybox.net
2020-04-11 19:14 ` bugzilla at busybox.net [this message]
2020-04-11 19:19 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-12726-163-QbnMwAdHxw@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.