public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Moessbauer,
	Felix (T RDA IOT SES-DE)" <felix.moessbauer@siemens.com>,
	isar-users <isar-users@googlegroups.com>,
	Anton Mikanovich <amikan@ilbers.de>
Cc: "Schild, Henning (T RDA IOT SES-DE)" <henning.schild@siemens.com>
Subject: Re: New mount logic breaks DEBIAN_BUILD_DEPENDS
Date: Wed, 23 Jun 2021 07:41:47 +0200	[thread overview]
Message-ID: <d8457d94-0517-03d1-e94b-1c01f59f6625@siemens.com> (raw)
In-Reply-To: <AM9PR10MB4869CA345FC584A4ABB5219B89099@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>

[please no html on mailing lists. Not only because my mail client is
broken over - according to TB devs - broken html format outlook generates]

On 22.06.21 12:45, Moessbauer, Felix (T RDA IOT SES-DE) 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)
> 

I've see this error with a complex build yesterday as well. Was only
resolves by complete purging of build results.

I would strongly suggest to revert this series and rework it carefully,
even more as it was not fixing any kind of urgent issues (we were living
with the previous behavior for many years now).

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2021-06-23  5:41 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 [this message]
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=d8457d94-0517-03d1-e94b-1c01f59f6625@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=henning.schild@siemens.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