Is this a new report?
Yes
System Info
Void 6.18.49_1 x86_64 GenuineIntel notuptodate hold rrrrmDDDDDDDFFF
Package(s) Affected
dhcpcd-10.3.2_2.x86_64
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
No error messages on boot screen regarding resolvconf as is was with dhcpcd-10.3.2_1.x86_64
Actual behaviour
Ever since the the changes to dhcpcd I'm getting lots of error messages regarding resolvconf.
Maybe the change unmasked an existing error or it introduced an error.
The issue seems to be that resolvconf seems to look for /etc/resolvconf.conf, but there's only /etc/resolv.conf.
Apparently, this change was introduced by this commit (+conf_files="/etc/resolvconf.conf").
I would advocate for changing it back to resolv.conf, as that was the file name used back when I installed my system and it seems to be file name used by other distros, too.
Update:
Even after fixing the openresolv bug (yes, for me it is a bug :-)), dhcpcd still prinsts stuff on tty1. Maybe that's intended, but I don't think that dhcpcd is so special that is should direct it messages to tty1 when other programs don't. It should just put its log into /var/log/ as other programs do.
Steps to reproduce
- "Update" dhcpcd to dhcpcd-10.3.2_2.x86_64
- Reboot
- See error messages on boot screen / tty1.
Is this a new report?
Yes
System Info
Void 6.18.49_1 x86_64 GenuineIntel notuptodate hold rrrrmDDDDDDDFFF
Package(s) Affected
dhcpcd-10.3.2_2.x86_64
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
No error messages on boot screen regarding resolvconf as is was with dhcpcd-10.3.2_1.x86_64
Actual behaviour
Ever since the the changes to dhcpcd I'm getting lots of error messages regarding resolvconf.
Maybe the change unmasked an existing error or it introduced an error.
The issue seems to be that resolvconf seems to look for /etc/resolvconf.conf, but there's only /etc/resolv.conf.
Apparently, this change was introduced by this commit (
+conf_files="/etc/resolvconf.conf").I would advocate for changing it back to resolv.conf, as that was the file name used back when I installed my system and it seems to be file name used by other distros, too.
Update:
Even after fixing the openresolv bug (yes, for me it is a bug :-)), dhcpcd still prinsts stuff on tty1. Maybe that's intended, but I don't think that dhcpcd is so special that is should direct it messages to tty1 when other programs don't. It should just put its log into /var/log/ as other programs do.
Steps to reproduce