From: Anton Mikanovich <amikan@ilbers.de>
To: Amaia Gomez <agomez@ulmapackaging.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: Bug report: cache-deb-src fails with 'debsrc_undo_mounts: not found' on isar v1.1
Date: Fri, 22 May 2026 17:46:10 +0300 [thread overview]
Message-ID: <ba5aaf36-00c5-458b-8512-dba6b6930870@ilbers.de> (raw)
In-Reply-To: <86f710f342514234b8d7eab2c97bdbba@spc015.packaging.ulma.es>
Hello Amaia,
Thanks for the reporting, the function 'debsrc_undo_mounts' is leftover
after:
9ad502bb deb-dl-dir: optimize caching of source packages using apt natively
Will prepare a patch with removing it.
For the second point we need to have a look and will back soon.
21.05.2026 13:42, 'Amaia Gomez' via isar-users wrote:
>
> Hello isar-users,
>
> I am trying to use the cache-deb-src feature to cache upstream Debian
> source packages for long-term reproducibility. I am running isar v1.1
> (commit cc5a5d98) on Debian 13 (Trixie) amd64, building an image for
> an Intel Elkhart Lake (x86_64) target with Debian Trixie.
>
> Configuration in local.conf:
>
> BASE_REPO_FEATURES = "cache-deb-src"
>
> The build fails with:
>
> ERROR: No packages were found in apt cache
>
> run.do_cache_deb_src: debsrc_undo_mounts: not found
>
> WARNING: exit code 127 from a shell command.
>
> I found two issues:
>
> 1. The function 'debsrc_undo_mounts' is called in
> meta/classes-recipe/deb-dl-dir.bbclass (line ~150) when the apt cache
> is empty, but this function is not defined anywhere in the isar
> codebase. This causes exit code 127 (command not found).
>
> 2. Even with ROOTFS_FEATURES:remove = "clean-package-cache", the
> function rootfs_export_package_cache executes BEFORE
> rootfs_install_pkgs_install in the ROOTFS_INSTALL_COMMAND sequence.
> This means the apt cache is still empty when the export runs, because
> the packages have not been downloaded yet.
>
> The execution order observed in the log is:
>
> rootfs_export_package_cache (cache is empty at this point)
>
> rootfs_install_clean_files
>
> rootfs_install_pkgs_install (packages are downloaded here)
>
> Is there a workaround available? Is this a known issue?
>
> Thank you,
>
> Amaia Gomez
>
>
>
>
>
>
>
> http://www.ulmapackaging.com/imag/signature/logo_ulma.jpg
>
>
>
>
>
> *AMAIA GOMEZ * | Técnico/a de Desarrollo - Electrónico/a
> *ULMA Packaging**Headquarters*
> Barrio Garibai 28, 20560 OÑATI (Gipuzkoa)
> agomez@ulmapackaging.com <mailto:agomez@ulmapackaging.com> |
> *Tel.:*+34 943 034205 # 3035
> *ulmapackaging.com <http://www.ulmapackaging.com/>*
>
>
>
>
>
>
>
>
>
>
> http://www.ulmapackaging.com/imag/signature/youtube.jpg
> <https://www.youtube.com/channel/UCM4QMtxxQkul2s9R5m03tEQ>http://www.ulmapackaging.com/imag/signature/linkedin.jpg
> <https://www.linkedin.com/company/ulma-packaging>http://www.ulmapackaging.com/imag/signature/maps.jpg
> <https://www.google.es/maps/place/ULMA+Packaging/@43.0458129,-2.4284497,17z/data=!3m1!4b1!4m2!3m1!1s0xd5029a4239ea1d1:0x3dd710b1f7e012a5>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> http://www.ulmapackaging.com/imag/signature/hq/banner1.png
> <http://www.ulmapackaging.com/imag/signature/hq/link_banner_1>
>
>
>
>
> http://www.ulmapackaging.com/imag/signature/hq/banner2.png
> <http://www.ulmapackaging.com/imag/signature/hq/link_banner_2>
>
>
>
>
> http://www.ulmapackaging.com/imag/signature/hq/banner3.png
> <http://www.ulmapackaging.com/imag/signature/hq/link_banner_3>
>
> Mezu hau, eta hala bada, eransitako fitxategiak konfidentzialak dira,
> bereziki datu pertsonalei dagokienez, eta zehaztu den
> hartzailearentzat dira bakarrik. Zu ez bazara hartzailea eta nahi gabe
> jaso baduzu, edo beste arrazoi batengatik bere berri izan baduzu, bide
> honetatik guri jakinarazteko eta mezua suntsitzeko edo ezabatzeko
> eskatzen dizugu. Aldi berean, inondik inora, mezu hau eta erantsitako
> fitxategiak ez erabiltzeko, ez erreproduzitzeko, ez aldatzeko, ez
> artxibatzeko edo ez beste inori helerazteko eskatzen dizugu, hori
> guztia erantzunkizun legalak sor daitezkeela jakitun. Igorleak ez du
> bermatzen posta honen integritatea, azkartasuna edo segurtasuna, eta
> ez ditu bere arduratzat hartzen beste inork egindako atzemate, birus
> kutsatze eta beste edozein manipulaziotik eratorritako balizko kalteak.
> Este mensaje y, en su caso, los ficheros anexos son confidenciales,
> especialmente en lo que respecta a los datos personales, y se dirigen
> exclusivamente al destinatario referenciado. Si usted no lo es y lo ha
> recibido por error o tiene conocimiento del mismo por cualquier
> motivo, le rogamos que nos lo comunique por este medio y proceda a
> destruirlo o borrarlo, y que en todo caso se abstenga de utilizar,
> reproducir, alterar, archivar o comunicar a terceros el presente
> mensaje y ficheros anexos, todo ello bajo pena de incurrir en
> responsabilidades legales. El emisor no garantiza la integridad,
> rapidez o seguridad del presente correo, ni se responsabiliza de
> posibles perjuicios derivados de la captura, incorporaciones de virus
> o cualesquiera otras manipulaciones efectuadas por terceros.
> This message and any attached files transmitted with it, is
> confidential, especially as regards personal data and originals ideas.
> It is intended solely for the use of the individual or entity to whom
> it is addressed. If you are not the intended recipient and have
> received this information in error or have accessed it for any reason,
> please notify us of this fact by email reply and then destroy or
> delete the message, refraining from any reproduction, use, alteration,
> filing or communication to third parties of this message and attached
> files on penalty of incurring legal responsibilities. The sender does
> not guarantee the integrity, the accuracy, the swift delivery or the
> security of this email transmission, and assumes no responsibility for
> any possible damage incurred through data capture, virus incorporation
> or any manipulation carried out by third parties.
>
> --
> You received this message because you are subscribed to the Google
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion visit
> https://groups.google.com/d/msgid/isar-users/86f710f342514234b8d7eab2c97bdbba%40spc015.packaging.ulma.es
> <https://groups.google.com/d/msgid/isar-users/86f710f342514234b8d7eab2c97bdbba%40spc015.packaging.ulma.es?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/ba5aaf36-00c5-458b-8512-dba6b6930870%40ilbers.de.
next prev parent reply other threads:[~2026-05-22 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 10:42 'Amaia Gomez' via isar-users
2026-05-22 14:46 ` Anton Mikanovich [this message]
2026-05-25 11:12 ` Anton Mikanovich
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=ba5aaf36-00c5-458b-8512-dba6b6930870@ilbers.de \
--to=amikan@ilbers.de \
--cc=agomez@ulmapackaging.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