From: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 0/2] Custom ${S} series
Date: Mon, 29 Mar 2021 23:20:10 -0700 (PDT) [thread overview]
Message-ID: <3c6914fa-1235-44ec-9183-c75b564a425fn@googlegroups.com> (raw)
In-Reply-To: <9ada5293-7069-b8ea-fe59-400320d9ac5d@ilbers.de>
[-- Attachment #1.1: Type: text/plain, Size: 1882 bytes --]
On Monday, March 29, 2021 at 2:44:28 PM UTC+5:30 ami...@ilbers.de wrote:
> 04.03.2021 20:41, Vijai Kumar K wrote:
> > Changes since V2:
> > - Introduce P2 to demonstrate apt:// without ${PV} set.
> > - Address review comment from Henning.
> > - Fix issue where do_apt_unpack is triggered for non apt://
> > SRC_URIs.
> >
> > CI build going on: http://ci.isar-build.org:8080/job/isar_vkk_devel/93/
> >
> > Changes since V1:
> >
> > - Introduce a separate do_apt_unpack task
> >
> > Vijai Kumar K (2):
> > dpkg-base: Introduce do_apt_unpack
> > Modify hello to demonstrate apt:// without ${PV}
> >
> > .../recipes-app/hello/{hello.inc => hello.bb} | 0
> > meta-isar/recipes-app/hello/hello_2.10.bb | 11 -------
> > meta-isar/recipes-app/hello/hello_2.9.bb | 8 -----
> > meta/classes/dpkg-base.bbclass | 29 ++++++++++++++++---
> > 4 files changed, 25 insertions(+), 23 deletions(-)
> > rename meta-isar/recipes-app/hello/{hello.inc => hello.bb} (100%)
> > delete mode 100644 meta-isar/recipes-app/hello/hello_2.10.bb
> > delete mode 100644 meta-isar/recipes-app/hello/hello_2.9.bb
> >
> Hello, did you try it with ISAR_CROSS_COMPILE = "0"?
> I see it failed on qemumipsel-stretch:
>
> >ERROR: mc:qemumipsel-stretch:hello-1.0-r0 do_apt_unpack: Execution of
> 'build/tmp/work/debian-stretch-mipsel/hello/1.0-r0/temp/run.do_apt_unpack.3153'
>
> failed with exit code 2:
> dpkg-source: error: cannot read hello_2.10-1.dsc: No such file or directory
Found the issue. v4 coming up after this[1] pipeline succeeds(hopefully).
[1] http://ci.isar-build.org:8080/job/isar_vkk_devel/95/
Thanks,
Vijai Kumar K
>
> --
> Anton Mikanovich
> Promwad Ltd.
> External service provider of ilbers GmbH
> Maria-Merian-Str. 8
> 85521 Ottobrunn, Germany
> +49 (89) 122 67 24-0
> Commercial register Munich, HRB 214197
> General Manager: Baurzhan Ismagulov
>
>
[-- Attachment #1.2: Type: text/html, Size: 4196 bytes --]
prev parent reply other threads:[~2021-03-30 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 17:41 Vijai Kumar K
2021-03-04 17:41 ` [PATCH v3 1/2] dpkg-base: Introduce do_apt_unpack Vijai Kumar K
2021-03-04 17:41 ` [PATCH v3 2/2] Modify hello to demonstrate apt:// without ${PV} Vijai Kumar K
2021-03-04 18:56 ` [PATCH v3 0/2] Custom ${S} series Henning Schild
2021-03-04 20:53 ` Henning Schild
2021-03-29 9:14 ` Anton Mikanovich
2021-03-30 6:20 ` vijaikumar....@gmail.com [this message]
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=3c6914fa-1235-44ec-9183-c75b564a425fn@googlegroups.com \
--to=vijaikumar.kanagarajan@gmail.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