Skip to content

Use resolvectl instead of systemd-resolve #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 8, 2022

Conversation

mbiebl
Copy link
Contributor

@mbiebl mbiebl commented Jan 20, 2021

The latter is a deprecated compat symlink.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979267

@mbiebl
Copy link
Contributor Author

mbiebl commented Jan 20, 2021

From the downstream bug report:

Hi,

systemd-resolve has been replaced by the resolvectl tool in systemd v239
(i.e. is available since buster). This is from the systemd release
notes:

* The systemd-resolve tool has been renamed to resolvectl (it also
  remains available under the old name, for compatibility), and its
  interface is now verb-based, similar in style to the other <xyz>ctl
  tools, such as systemctl or loginctl.

systemd-resolve is nowadays merely a symlink pointing at resolvectl and
we'd like to get rid of this compat symlink at some point.

Your package uses the old name like this:

$ grep -E "systemd-resolve\b" -R
run-tests:function systemd-resolve {
run-tests:  _log "systemd-resolve called with: ${@}"
README.md:`openvpn`, which will use the `update-systemd-resolve.conf` file instead:
README.md:$ systemd-resolve eu-central-1.console.aws.amazon.com
README.md:$ systemd-resolve eu-central-1.console.aws.amazon.com
update-systemd-resolved:    systemd-resolve --flush-caches

Attached is a patch which uses resolvectl instead.
Please review and consider applying it in your next upload.
It would be great if you can make this upload before the bullseye
release, so we can safely drop the symlink in bullseye+1.

@jonathanio jonathanio merged commit 57f3523 into jonathanio:master Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants