[Bug 1894622] Re: Missing manpage for systemd-resolve
Brian Murray
1894622 at bugs.launchpad.net
Thu Jul 8 23:14:33 UTC 2021
Hello Fabrizio, or anyone else affected,
Accepted systemd into groovy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/246.6-1ubuntu1.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: systemd (Ubuntu Groovy)
Status: In Progress => Fix Committed
** Tags added: verification-needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1894622
Title:
Missing manpage for systemd-resolve
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
In Progress
Status in systemd source package in Groovy:
Fix Committed
Status in systemd source package in Hirsute:
Fix Committed
Status in systemd source package in Impish:
Fix Released
Bug description:
[impact]
'man systemd-resolve' fails
[test case]
$ man systemd-resolve
No manual entry for systemd-resolve
[regression potential]
incorrect man page result for resolvectl or resolvconf, or possibly
users using deprecated systemd-resolve longer than they should
[scope]
this is needed in f and later
systemd-resolve was replaced with resolvectl between b and f, so the
man page exists in b
[other info]
the systemd-resolve binary is a symlink to the real binary resolvectl, and users should use resolvectl for all new uses. A patch to the upstream man page was proposed and merged in this PR:
https://github.com/systemd/systemd/pull/20064
however that is being discussed and may be reverted in this PR:
https://github.com/systemd/systemd/pull/20077
as discussed in the revert PR, it's ok for upstream to elide docs
about deprecated tooling; however distros should include deprecation
info and thus I believe it's appropriate to include the man page
symlink so users trying 'man systemd-resolve' will get the correct
'resolvectl' man page, which includes doc about how they shoudl start
using 'resolvectl' instead
[original description]
On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz
This means that man systemd-resolve fails.
http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd-
resolve.1.html exists and has a link on top to 20.04LTS: it points to
http://manpages.ubuntu.com/manpages/focal/en/man1/systemd-
resolve.1.html , that however 404's, and one ends up being redirected
to Bionic's.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1894622/+subscriptions
More information about the foundations-bugs
mailing list