From: Baurzhan Ismagulov <ibr@radix50.net>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2 00/10] Introduce local apt repo to cache upstream debian packages for offline usage
Date: Mon, 19 Nov 2018 09:48:00 +0100 [thread overview]
Message-ID: <20181119084800.GD15618@yssyq.m.ilbers.de> (raw)
In-Reply-To: <02e2e7d3-e470-03fd-32b1-9fb9fa716bde@ilbers.de>
Hello Jan,
On Tue, Oct 23, 2018 at 12:56:11PM +0300, Maxim Yu. Osipov wrote:
> > > Could it be we have some regression here? After updating to current
> > > next, a build without the cache enabled fails during do_rootfs with
> > >
> > > | (Reading database ... 9600 files and directories currently installed.)
> > > | Removing isar-cfg-localepurge (1.0+isar) ...
> > > | find: '/build/tmp/work/debian-stretch-armhf/isar-image-base/rootfs/var/cache/apt/archives/partial': Permission denied
> > > | chown: invalid user: '/build/tmp/work/debian-stretch-armhf/isar-image-base/apt_cache/adduser_3.115_all.deb'
> > > | WARNING: exit code 1 from a shell command.
> > > | ERROR: Function failed: do_rootfs (log file is located at /build/tmp/work/debian-stretch-armhf/isar-image-base/temp/log.do_rootfs.5627)
...
> I've built (cross compiled from the scratch) the
> multiconfig:qemuarm-stretch:isar-image-base, after that I've checkouted
> 'next' branch and ran again 'bitbake
> multiconfig:qemuarm-stretch:isar-image-base' in the same build directory.
> Build was OK. Did you have another test case?
This issue blocks reproducibility. How can we reproduce it?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2018-11-19 8:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 16:52 Maxim Yu. Osipov
2018-10-11 16:52 ` [PATCH v2 01/10] base-apt: Add helper class Maxim Yu. Osipov
2018-10-23 16:01 ` Henning Schild
2018-10-11 16:52 ` [PATCH v2 02/10] meta: Unify path names to local repositories Maxim Yu. Osipov
2018-10-11 16:52 ` [PATCH v2 03/10] base-apt: Introduce base implementation Maxim Yu. Osipov
2018-10-11 16:52 ` [PATCH v2 04/10] isar-boot-strap: Add option to keep cache Maxim Yu. Osipov
2018-10-23 16:06 ` Henning Schild
2018-10-25 14:28 ` Henning Schild
2018-10-11 16:53 ` [PATCH v2 05/10] image: Add cache_base_repo task Maxim Yu. Osipov
2018-10-11 16:53 ` [PATCH v2 06/10] isar-bootstrap: Make possible to reuse the cache Maxim Yu. Osipov
2018-10-23 16:30 ` Henning Schild
2018-10-11 16:53 ` [PATCH v2 07/10] buildchroot: Make it buildable from base-apt Maxim Yu. Osipov
2018-10-11 16:53 ` [PATCH v2 08/10] workaround: Use --allow-unauthenticated working with base-apt Maxim Yu. Osipov
2018-10-23 16:09 ` Henning Schild
2018-10-25 14:33 ` Henning Schild
2018-10-11 16:53 ` [PATCH v2 09/10] local.conf: Add option to use cached base repository Maxim Yu. Osipov
2018-10-11 16:53 ` [PATCH v2 10/10] doc: Creation of local apt repo caching upstream Debian packages Maxim Yu. Osipov
2018-10-17 12:13 ` [PATCH v2 00/10] Introduce local apt repo to cache upstream debian packages for offline usage Maxim Yu. Osipov
2018-10-17 17:11 ` Jan Kiszka
2018-10-17 18:15 ` Maxim Yu. Osipov
2018-10-23 9:56 ` Maxim Yu. Osipov
2018-11-19 8:48 ` Baurzhan Ismagulov [this message]
2018-11-19 8:58 ` Jan Kiszka
2018-10-23 16:14 ` Henning Schild
2018-10-29 12:28 ` Baurzhan Ismagulov
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=20181119084800.GD15618@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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