From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 00/10] Introduce local apt repo to cache upstream debian packages for offline usage
Date: Tue, 23 Oct 2018 12:56:11 +0300 [thread overview]
Message-ID: <02e2e7d3-e470-03fd-32b1-9fb9fa716bde@ilbers.de> (raw)
In-Reply-To: <2c35941c-a17c-9fa7-e286-01e4fe786051@ilbers.de>
Hi Jan,
On 10/17/18 9:15 PM, Maxim Yu. Osipov wrote:
> On 10/17/18 8:11 PM, Jan Kiszka wrote:
>> On 11.10.18 18:52, Maxim Yu. Osipov wrote:
>>> Hello everybody,
>>>
>>> This series contains fixes/improvements suggested by Claudius Heine
>>> during v1 series review.
>>>
>>> Changes to v2:
>>> - Fixes/improvements found in base-apt-helper class
>>> - Unifies path names to local repositories
>>>
>>> 1) Introduces dedicated local apt (base-apt) repo for upstream Debian
>>> packages
>>>
>>> 2) Caches in base-apt repo upstream Debian packages during image
>>> generation.
>>>
>>> 3) After this step, image can be built offline using only base-apt repo.
>>>
>>> Usage instructions can be found in the last patch.
>>>
>>> TODO:
>>> Sign the repo with gpg
>>>
>>> Kind regards,
>>> Maxim.
>>>
>>> Alexander Smirnov (8):
>>> base-apt: Add helper class
>>> base-apt: Introduce base implementation
>>> isar-boot-strap: Add option to keep cache
>>> image: Add cache_base_repo task
>>> isar-bootstrap: Make possible to reuse the cache
>>> buildchroot: Make it buildable from base-apt
>>> workaround: Use --allow-unauthenticated working with base-apt
>>> local.conf: Add option to use cached base repository
>>>
>>> Maxim Yu. Osipov (2):
>>> meta: Unify path names to local repositories
>>> doc: Creation of local apt repo caching upstream Debian packages
>>>
>>> doc/user_manual.md | 39
>>> ++++++++++++++++
>>> meta-isar/conf/layer.conf | 10 ++--
>>> meta-isar/conf/local.conf.sample | 4 ++
>>> meta-isar/recipes-core/images/isar-image-base.bb | 3 +-
>>> meta/classes/base-apt-helper.bbclass | 54
>>> ++++++++++++++++++++++
>>> meta/classes/buildchroot.bbclass | 2 +-
>>> meta/classes/dpkg-base.bbclass | 10 ++--
>>> meta/classes/dpkg.bbclass | 2 +-
>>> meta/classes/image.bbclass | 25 +++++++++-
>>> meta/classes/isar-bootstrap-helper.bbclass | 17 +++++--
>>> .../isar-bootstrap/files/base-apt-sources | 1 +
>>> .../recipes-core/isar-bootstrap/isar-bootstrap.inc | 32 +++++++++----
>>> meta/recipes-devtools/base-apt/base-apt.bb | 31 +++++++++++++
>>> .../base-apt/files/distributions.in | 3 ++
>>> meta/recipes-devtools/buildchroot/files/deps.sh | 2 +-
>>> meta/recipes-devtools/isar-apt/isar-apt.bb | 8 ++--
>>> meta/recipes-kernel/linux/linux-custom.inc | 2 +-
>>> 17 files changed, 213 insertions(+), 32 deletions(-)
>>> create mode 100644 meta/classes/base-apt-helper.bbclass
>>> create mode 100644
>>> meta/recipes-core/isar-bootstrap/files/base-apt-sources
>>> create mode 100644 meta/recipes-devtools/base-apt/base-apt.bb
>>> create mode 100644
>>> meta/recipes-devtools/base-apt/files/distributions.in
>>>
>>
>> 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 do not have the time to bisect, will just jump back for now.
>
> Hmmm... Of course, I've run CI build before applying to the 'next'
> (see http://isar-build.org:8080/job/isar_mosipov_next/61).
>
> I'll check if your problem is reproduced when build is not started from
> the scratch.
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?
Kind regards,
Maxim.
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2018-10-23 9:56 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 [this message]
2018-11-19 8:48 ` Baurzhan Ismagulov
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=02e2e7d3-e470-03fd-32b1-9fb9fa716bde@ilbers.de \
--to=mosipov@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