public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2] dpkg: Account for empty local apt cache after package build
Date: Wed, 25 Oct 2023 09:44:09 +0300	[thread overview]
Message-ID: <f2d3e5dfb90e579218b4d64e18456bf4e3a549aa.camel@ilbers.de> (raw)
In-Reply-To: <47a6c8a9-cbb5-4ef2-ba47-c7a320f9da6e@siemens.com>

On Thu, 2023-10-19 at 06:39 +0200, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> A build dependency-free package combined with sstate caching and
> cleared
> deb cache can trigger
> 
> > cp -Ln --no-preserve=owner /var/cache/apt/archives/*.deb -t
> > /home/builder/example-raw/rootfs/var/cache/apt/archives/
> > -------------------------------------------------------------------
> > -------------------------------------------------
> > 
> > cp: cannot stat '/var/cache/apt/archives/*.deb': No such file or
> > directory
> > 
> > E: Command 'cp -Ln --no-preserve=owner
> > /var/cache/apt/archives/*.deb -t /home/builder/example-
> > raw/rootfs/var/cache/apt/archives/' failed to run.
> 
> Account for that.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> 
> Changes in v2:
>  - avoid returning error via negativ [ -n ] result
> 
>  meta/classes/dpkg.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 

Applied to next, thanks.

  parent reply	other threads:[~2023-10-25  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  4:39 Jan Kiszka
2023-10-25  6:26 ` MOESSBAUER, Felix
2023-10-25  6:44 ` Uladzimir Bely [this message]
2023-12-22  9:43 ` Uladzimir Bely

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=f2d3e5dfb90e579218b4d64e18456bf4e3a549aa.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --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