From: Anton Mikanovich <amikan@ilbers.de>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>,
isar-users <isar-users@googlegroups.com>
Cc: "henning.schild@siemens.com" <henning.schild@siemens.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: New mount logic breaks DEBIAN_BUILD_DEPENDS
Date: Wed, 23 Jun 2021 15:00:13 +0300 [thread overview]
Message-ID: <d26042d3-c19d-41db-cb9e-5cab133427d1@ilbers.de> (raw)
In-Reply-To: <AM9PR10MB4869CA345FC584A4ABB5219B89099@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2120 bytes --]
I have an idea about possible reason of this issue. Did you experience
build fail before that?
Reference counters are not cleared in case unsuccessful build happens.
Please look at `[PATCH] mount: Cleanup reference counters before build`
just pushed to the maillist.
22.06.2021 13:45, Moessbauer, Felix wrote:
>
> 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
>
> --
> 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
> <mailto:isar-users+unsubscribe@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/AM9PR10MB4869CA345FC584A4ABB5219B89099%40AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM
> <https://groups.google.com/d/msgid/isar-users/AM9PR10MB4869CA345FC584A4ABB5219B89099%40AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>.
--
Anton Mikanovich
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
[-- Attachment #2: Type: text/html, Size: 4676 bytes --]
next prev parent reply other threads:[~2021-06-23 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 10:45 Moessbauer, Felix
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 [this message]
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=d26042d3-c19d-41db-cb9e-5cab133427d1@ilbers.de \
--to=amikan@ilbers.de \
--cc=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