public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: "henning.schild@siemens.com" <henning.schild@siemens.com>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: New mount logic breaks DEBIAN_BUILD_DEPENDS
Date: Tue, 22 Jun 2021 10:45:15 +0000	[thread overview]
Message-ID: <AM9PR10MB4869CA345FC584A4ABB5219B89099@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)

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

Hi,

The ref 3360b7d9ff85172dc3d2275c35caec71149b35ef breaks building packages that inherit from dpkg-raw and use DEBIAN_BUILD_DEPENDS like the minimal reproducer below.
During do_install_builddeps, the mount points are not mounted (or get unmounted).
Also latest next (591a537d3cc9f3ef35e008fdff0fe631714aa68d) is affected.

inherit dpkg-raw
DESCRIPTION = "Reproduce ISAR mount issues"
DEBIAN_BUILD_DEPENDS = "htop"

Build error:
Err:4 file:/isar-apt isar/main amd64 Packages
  File not found - /isar-apt/dists/isar/main/binary-amd64/Packages (2: No such file or directory)
Get:5 file:/isar-apt isar/main Translation-en
Ign:5 file:/isar-apt isar/main Translation-en
Reading package lists...
E: Failed to fetch file:/isar-apt/dists/isar/main/binary-amd64/Packages  File not found - /isar-apt/dists/isar/main/binary-amd64/Packages (2: No such file or directory)

Best regards,
Felix

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

             reply	other threads:[~2021-06-22 10:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 10:45 Moessbauer, Felix [this message]
2021-06-22 13:51 ` Henning Schild
2021-06-22 15:24 ` Henning Schild
2021-06-23  5:41 ` Jan Kiszka
2021-06-23  8:58   ` Baurzhan Ismagulov
2021-06-23 12:00 ` Anton Mikanovich
2021-06-24  6:30   ` Moessbauer, Felix

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=AM9PR10MB4869CA345FC584A4ABB5219B89099@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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