From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Subject: Re: rules.tmpl how to exec a cmd as root
Date: Tue, 27 Sep 2022 16:59:55 +0200 [thread overview]
Message-ID: <CAJGKYO5XwpCYgO8oGf8OX8v2zmymym-v_s_5XVL28WyUdhqEew@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO4_HdVGVWmuq3_2t3Gu5crf=TPwdbx4FnB1Afdkrt-E6w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 952 bytes --]
Il Mar 27 Set 2022, 15:20 Roberto A. Foglietta <roberto.foglietta@gmail.com>
ha scritto:
> Dear all,
>
> I found another corner case about compiling a 3rd party driver into ISAR
> and I need to execute a command at make level but as root. Unfortunately su
> cannot authenticate seamlessly and without the root permission the command
> fails. Suggestions?
>
> override_dh_auto_build:
> sudo cp -arf /usr/lib/modules/*/source/* /usr/lib/modules/*/build/
> cp -arf /usr/lib/modules/*/source/* /usr/lib/modules/*/build/
> $(MAKE) -n modules ${PARALLEL_MAKE}
>
The problem of Executing commands with root priviledge in the sbuild, I
have solved using chmod +s the command (cfr. the patch attached, in the
commented line a generalisation).
About the module compile, I should have checked what's wrong in the
makefile & Co. but at the moment the approach is not pointing the finger on
the lacks of others but manage it.
Cheers, R-
>
[-- Attachment #1.2: Type: text/html, Size: 1794 bytes --]
[-- Attachment #2: isar.patch --]
[-- Type: text/x-diff, Size: 1181 bytes --]
diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
index c92ea7d..6fb53bb 100644
--- a/meta/classes/dpkg.bbclass
+++ b/meta/classes/dpkg.bbclass
@@ -87,11 +87,14 @@ dpkg_runbuild() {
sh -c "cd ${WORKDIR}; dpkg-source -q -b ${PPS}"
DSC_FILE=$(find ${WORKDIR} -name "${DEB_SOURCE_NAME}*.dsc" -print)
+ # --chroot-setup-commands="chmod +s /bin/cp /bin/mv /bin/ln /bin/ls /bin/chmod /bin/chown" \
+ #
sbuild -A -n -c ${SBUILD_CHROOT} --extra-repository="${ISAR_APT_REPO}" \
--host=${PACKAGE_ARCH} --build=${SBUILD_HOST_ARCH} ${profiles} \
--no-run-lintian --no-run-piuparts --no-run-autopkgtest --resolve-alternatives \
--chroot-setup-commands="rm -f /var/log/dpkg.log" \
--chroot-setup-commands="cp -n --no-preserve=owner ${ext_deb_dir}/*.deb -t ${deb_dir}/ || :" \
+ --chroot-setup-commands="chmod +s /bin/cp" \
--finished-build-commands="rm -f ${deb_dir}/sbuild-build-depends-main-dummy_*.deb" \
--finished-build-commands="cp -n --no-preserve=owner ${deb_dir}/*.deb -t ${ext_deb_dir}/ || :" \
--finished-build-commands="cp /var/log/dpkg.log ${ext_root}/dpkg_partial.log" \
next prev parent reply other threads:[~2022-09-27 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM0PR10MB20205FF67C22F88DC3BE525BAA559@AM0PR10MB2020.EURPRD10.PROD.OUTLOOK.COM>
2022-09-27 13:20 ` Roberto A. Foglietta
2022-09-27 14:59 ` Roberto A. Foglietta [this message]
2022-09-27 21:13 ` Roberto A. Foglietta
2022-09-27 22:03 ` Roberto A. Foglietta
2022-09-28 9:37 ` Henning Schild
2022-09-28 14:45 ` Roberto A. Foglietta
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=CAJGKYO5XwpCYgO8oGf8OX8v2zmymym-v_s_5XVL28WyUdhqEew@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=isar-users@googlegroups.com \
/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