public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: Ignore a dependency
Date: Sun, 2 Oct 2022 01:10:03 +0200	[thread overview]
Message-ID: <CAJGKYO4i4+6p3pzhgdKF0bRV7d26YrPO_11w-=tmSYmUGhTMqw@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO4ubza2bfSsjnz_8hm5zZoHty7foNeeva39fA2Bf4RLeQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3179 bytes --]

Il giorno dom 2 ott 2022 alle ore 00:14 Roberto A. Foglietta <
roberto.foglietta@gmail.com> ha scritto:
>
> Il giorno mer 14 set 2022 alle ore 10:34 Henning Schild <
henning.schild@siemens.com> ha scritto:
> >
> > You can always use dpkg-prebuilt where you download that package,
> > binary patch it and later installed the modified copy with isar.
> > However if you have a sources.list entry and that package can
> > potentially get updated, you will not be able to make that hack stable.
> >
> > That is a pattern for a broken binary package which i had to get into
> > a layer.
> >
> > do_binary_patch[cleandirs] += "${WORKDIR}/blabla-package"
> > do_binary_patch() {
> >         sudo dpkg-deb -R ${WORKDIR}/blabla-package.deb
${WORKDIR}/blabla-package
> >         # do something funny with the control file, i.e. sed -i -e ...
Depends
> >         sudo dpkg-deb -b ${WORKDIR}/blabla-package
> > }
> > addtask binary_patch after do_unpack before do_deploy_deb
>
> I am trying to fetch the package but I cannot, could you help me?
>
> SRC_URI = "apt://pippo-fs"
> addtask apt_fetch before do_binary_patch
>
> ERROR: pippo-fs-1.0-r0 do_apt_fetch:
ExecutionError('/build/tmp/work/debian-bullseye-amd64/pippo-fs/1.0-r0/temp/run.do_apt_fetch.100',
100, None, None)
> ERROR: Logfile of failure stored in:
/build/tmp/work/debian-bullseye-amd64/pippo-fs/1.0-r0/temp/log.do_apt_fetch.100
> Log data follows:
> | DEBUG: Executing shell function do_apt_fetch
> | Reading package lists...
> | E: Unable to find a source package for pippo-fs
> | ERROR:
ExecutionError('/build/tmp/work/debian-bullseye-amd64/pippo-fs/1.0-r0/temp/run.do_apt_fetch.100',
100, None, None)
> ERROR: Task (/build/../repo/recipes-support/nvidia-repack/pippo-fs.bb:do_apt_fetch)
failed with exit code '1'
> NOTE: Tasks Summary: Attempted 30 tasks of which 29 didn't need to be
rerun and 1 failed.
>
> pippo-fs is a legit package that could be fetch if put into
IMAGE_PREINSTALL
>
> Using do_fetch complains about checksum file
>
> bb.data_smart.ExpansionError: Failure expanding variable
do_fetch[file-checksums], expression was
${@bb.fetch.get_checksum_file_list(d)} which triggered exception
MalformedUrl: The URL: 'pippo-fs' is invalid and cannot be interpreted

Even more interesting this simple recipe

inherit dpkg-base
SRC_URI = "apt://${PN}"

download the package ONLY if the package is into the debian repository but
NOT if the package is in a external repository defined into conf/ but
available with IMAGE_PREINSTALL

I have also tried to change the repository but it did not work either

diff --git a/meta/classes/sbuild.bbclass b/meta/classes/sbuild.bbclass
index a29b745..4fa6a46 100644
--- a/meta/classes/sbuild.bbclass
+++ b/meta/classes/sbuild.bbclass
@@ -55,7 +55,7 @@ EOF
         cp -rf "${SCHROOT_CONF}/sbuild" "${SBUILD_CONF_DIR}"
         sbuild_fstab="${SBUILD_CONF_DIR}/fstab"

-        fstab_baseapt="${REPO_BASE_DIR} /base-apt none rw,bind 0 0"
+        fstab_baseapt="${REPO_ISAR_DIR} /base-apt none rw,bind 0 0"
         grep -qxF "${fstab_baseapt}" ${sbuild_fstab} || echo
"${fstab_baseapt}" >> ${sbuild_fstab}

         fstab_pkgdir="${WORKDIR} /home/builder/${PN} none rw,bind 0 0"

[-- Attachment #2: Type: text/html, Size: 3917 bytes --]

      reply	other threads:[~2022-10-01 23:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 11:55 Roberto A. Foglietta
2022-09-13 12:53 ` Uladzimir Bely
2022-09-13 12:58   ` Roberto A. Foglietta
2022-09-13 13:09     ` Baurzhan Ismagulov
2022-09-13 13:09     ` Uladzimir Bely
2022-09-13 13:53     ` Henning Schild
2022-09-13 18:59       ` Roberto A. Foglietta
2022-09-14  8:34         ` Henning Schild
2022-09-14 18:42           ` Roberto A. Foglietta
2022-09-15  9:35             ` Henning Schild
2022-10-01 22:14           ` Roberto A. Foglietta
2022-10-01 23:10             ` Roberto A. Foglietta [this message]

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='CAJGKYO4i4+6p3pzhgdKF0bRV7d26YrPO_11w-=tmSYmUGhTMqw@mail.gmail.com' \
    --to=roberto.foglietta@gmail.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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