From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13271] New: systemd-resolved: /etc/resolv.conf link broken on per-package build
Date: Tue, 13 Oct 2020 13:53:34 +0000 [thread overview]
Message-ID: <bug-13271-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13271
Bug ID: 13271
Summary: systemd-resolved: /etc/resolv.conf link broken on
per-package build
Product: buildroot
Version: 2020.08.1
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: posted at heine.so
CC: buildroot at uclibc.org
Target Milestone: ---
Issue:
systemd-resolved needs the /etc/resolv.conf entry like this:
/etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf
When using per-package build this isn't the case anymore. It still has the
default value from the skeleton:
/etc/resolv.conf -> ../tmp/resolv.conf
Analysis:
this is the code currently creating the link:
ifeq ($(BR2_PACKAGE_SYSTEMD_RESOLVED),y)
define SYSTEMD_INSTALL_RESOLVCONF_HOOK
ln -sf ../run/systemd/resolve/resolv.conf \
$(TARGET_DIR)/etc/resolv.conf
endef
As I learned on irc this doesn't work with per-package build as it is not
allowed to alter files from another package (even the skeleton). So this is why
it doesn't work.
Conclusion:
I'm not sure if this is properly fixable by the systemd package itself or if
this needs a removal from the skeleton with all its consequences.
Any Ideas welcome...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-10-13 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 13:53 bugzilla at busybox.net [this message]
2021-03-25 20:38 ` [Buildroot] [Bug 13271] systemd-resolved: /etc/resolv.conf link broken on per-package build bugzilla at busybox.net
2021-03-25 20:49 ` bugzilla at busybox.net
2021-03-27 21:11 ` bugzilla at busybox.net
2021-04-13 19:16 ` 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-13271-163@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox