public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, cedric.hombourger@siemens.com,
	adriaan.schmidt@siemens.com, christoph.steiger@siemens.com
Subject: Re: [PATCH 1/2] dpkg-raw: add files to source package
Date: Fri, 3 Oct 2025 14:09:42 +0300	[thread overview]
Message-ID: <5da617f1-ea5a-4838-91ff-da5b18c7e14a@ilbers.de> (raw)
In-Reply-To: <20250820124140.281190-2-felix.moessbauer@siemens.com>

20/08/2025 15:41, 'Felix Moessbauer' via isar-users wrote:
> In dpkg-raw, the user can place files in ${D} which are then installed
> into the resulting binary package. Hereby, ${D} is a directory outside
> of ${S} (since b19cd25) to not interfere with other data added to ${S}.
> However, by that the files are not added to the source package. This
> remained unnoticed, as the directory dh_install installs from is set
> to absolute path, hence the installed files actually came from the
> absolute path and not from the extracted source package. In case of
> ${PN} == ${BPN}, this path was always there as it has been created by
> previous tasks. However, with the switch in 2ca3a7e5 to only build the
> source package once, the path is not always there.
>
> We fix this by adding the files to the source package (under image) and
> install from a relative base. We further use a sub-path (image) in ${S}
> as a temporary location to not run into the issue solved in b19cd25.
>
> Fixes: 2ca3a7e5 ("dpkg-source: Build source package only once")
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
p1 was applied to next, thanks.

-- 
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/5da617f1-ea5a-4838-91ff-da5b18c7e14a%40ilbers.de.

  reply	other threads:[~2025-10-03 11:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20 12:41 [PATCH 0/2] handle DPKG_ARCH=all case for transitive deps 'Felix Moessbauer' via isar-users
2025-08-20 12:41 ` [PATCH 1/2] dpkg-raw: add files to source package 'Felix Moessbauer' via isar-users
2025-10-03 11:09   ` Anton Mikanovich [this message]
2025-08-20 12:41 ` [PATCH 2/2] handle DPKG_ARCH=all case for transitive deps 'Felix Moessbauer' via isar-users
2025-09-10 11:00   ` Andreas Naumann
2025-09-11 10:20     ` 'MOESSBAUER, Felix' via isar-users
2025-09-12 15:50       ` Andreas Naumann
2025-09-15  7:55         ` 'MOESSBAUER, Felix' via isar-users
2025-09-15 17:49   ` Andreas Naumann
2025-09-16  7:16     ` 'MOESSBAUER, Felix' via isar-users
2025-09-19  7:15       ` Andreas Naumann
2025-10-06 14:05         ` 'MOESSBAUER, Felix' via isar-users
2025-10-07 10:57           ` 'Andreas Naumann' via isar-users
2025-10-07 12:31   ` Zhihang Wei

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=5da617f1-ea5a-4838-91ff-da5b18c7e14a@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=adriaan.schmidt@siemens.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=christoph.steiger@siemens.com \
    --cc=felix.moessbauer@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