Bug 14836 - Resolvconf missing normalize-resolvconf file since it is moved to a separate file since version 1.90
Summary: Resolvconf missing normalize-resolvconf file since it is moved to a separate ...
Status: RESOLVED NOTABUG
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: connectivity (show other bugs)
Version: 4.0
Hardware: All Multiple
: Medium+ normal
Target Milestone: 4.2 M1
Assignee: Qorin
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2022-06-10 17:48 UTC by Qorin
Modified: 2022-10-13 15:53 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
patch to fix the resolvconf issue (1.49 KB, patch)
2022-06-10 17:48 UTC, Qorin
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Qorin 2022-06-10 17:48:19 UTC
Created attachment 4883 [details]
patch to fix the resolvconf issue

After upgrading to kirkstone resolvconf is not working properly.

In /var/log/boot or when /etc/init.d/networking is called this error message appears "/sbin/resolvconf: line 173: /lib/resolvconf/normalize-resolvconf: No such file or directory" 

According to https://launchpad.net/debian/+source/resolvconf/+changelog the normalization script is moved to normalize-resolvconf. However, this file is not included in the resolvconf_1.91.bb recipe.

I have added the patch to fix the recipe in the attachment.
Comment 1 Ross Burton 2022-06-16 15:51:37 UTC
Hi Qorin,

Can you send that patch to the mailing list for review?  bugzilla is just for bugs, not patches.

The long version of the documentation is at https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded, but the short version is just `git send-email --to openembedded-core@lists.openembedded.org -1 HEAD`.
Comment 2 Qorin 2022-06-20 08:10:12 UTC
(In reply to comment #1)
> Hi Qorin,
> 
> Can you send that patch to the mailing list for review?  bugzilla is just
> for bugs, not patches.
> 
> The long version of the documentation is at
> https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded, but
> the short version is just `git send-email --to
> openembedded-core@lists.openembedded.org -1 HEAD`.

done!
Comment 3 Qorin 2022-06-20 08:12:12 UTC
(In reply to comment #1)
> Hi Qorin,
> 
> Can you send that patch to the mailing list for review?  bugzilla is just
> for bugs, not patches.
> 
> The long version of the documentation is at
> https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded, but
> the short version is just `git send-email --to
> openembedded-core@lists.openembedded.org -1 HEAD`.

done!
Comment 4 Ross Burton 2022-06-20 11:14:21 UTC
Thanks!
Comment 5 Robert Berger 2022-10-13 15:42:05 UTC
This is still not upstream and resolvconf does not seem to work without it.

The patch I am currently using on langdale/master is:

diff --git a/meta/recipes-connectivity/resolvconf/resolvconf_1.91.bb b/meta/recipes-connectivity/resolvconf/resolvconf_1.91.bb
index 94fd2c1a70..dba58ad2d6 100644
--- a/meta/recipes-connectivity/resolvconf/resolvconf_1.91.bb
+++ b/meta/recipes-connectivity/resolvconf/resolvconf_1.91.bb
@@ -25,6 +25,10 @@ UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/r/resolvconf/"
 
 inherit allarch
 
+# The normalize-resolvconf sed script uses /bin/sed on the shebang line.
+# Ignore the file-rdeps test to avoid having to add a runtime dependency on sed.
+INSANE_SKIP:${PN} += "file-rdeps"
+
 do_compile () {
        :
 }
@@ -46,6 +50,7 @@ do_install () {
        chown -R root:root ${D}${sysconfdir}/
        install -m 0755 bin/resolvconf ${D}${base_sbindir}/
        install -m 0755 bin/list-records ${D}${base_libdir}/${BPN}
+       install -m 0755 bin/normalize-resolvconf ${D}${base_libdir}/${BPN}
        install -d ${D}/${sysconfdir}/network/if-up.d
        install -m 0755 debian/resolvconf.000resolvconf.if-up ${D}/${sysconfdir}/network/if-up.d/000resolvconf
        install -d ${D}/${sysconfdir}/network/if-down.d
Comment 6 Ross Burton 2022-10-13 15:48:10 UTC
Not sure how that got missed.  I've pulled it into a staging branch and we'll test it.