From: Henning Schild <henning.schild@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: isar-users <isar-users@googlegroups.com>,
Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: Re: [PATCH 0/7] "apt-get source" fetch/unpack support
Date: Wed, 30 Jan 2019 10:15:47 +0100 [thread overview]
Message-ID: <20190130101547.28d7f41d@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <d3ad4e08-1815-f26b-0c1f-807cc6de4227@ilbers.de>
On Wed, 30 Jan 2019 07:43:24 +0100
"Maxim Yu. Osipov" <mosipov@ilbers.de> wrote:
> I've rebased the patchset against current 'next' (I've dropped patch
> #6 from the series) and ran the "quick" test (with cross-compilation)
> - 'ci_build.sh -q -f'. build of 'hello' package failed:
> http://isar-build.org:8080/job/isar_mosipov_develop/14/console
Thanks. Cant quickly spot what happened there. Seems like the compile
went fine and the execution in the testsuite says "file not found". I
am guessing the binary is there but some shared object is missing.
Might actually be a problem in upstream, but i will try to reproduce
this.
Henning
> FYI: native build ('ci_build.sh -q') passed OK:
> http://isar-build.org:8080/job/isar_mosipov_next/133/console
>
> Maxim.
>
> On 1/28/19 5:57 PM, Henning Schild wrote:
> > ping
> >
> > Am Thu, 17 Jan 2019 17:04:20 +0100
> > schrieb Henning Schild <henning.schild@siemens.com>:
> >
> >> From: Henning Schild <henning.schild@siemens.com>
> >>
> >> This series includes support for fetching upstream sources with
> >> "apt-get source". This will make sure we fetch exactly what matches
> >> out distro, without rewriting debian fetch/unpack logic.
> >> I did consider implementing it as an "apt://" extension to the
> >> regular fetcher but decided against that. You have to set SRC_APT
> >> and effectively pass arguement to apt-get. That fetcher can only
> >> work in packages and depends on buildchroot and mounting, so it
> >> can not be part of the general fetcher. But maybe the general
> >> fetcher could ignore "apt://" lines and this task will ignore
> >> anything but "apt://" so we can still use SRC_URI instead of
> >> SRC_APT. Let us talk about the interface. The documentation is
> >> still missing, but i thing it is ready for a first review.
> >>
> >> The idea and parts of the code came from Mentor.
> >>
> >> Henning Schild (7):
> >> conf: add deb-src entries to all our distro configs
> >> dpkg-base: introduce an "apt-get source" fetch/unpack step
> >> meta: move debianization code into a class and into dpkg-base
> >> debianize: allow changlog version change
> >> meta-isar/recipes-app: add upstream hello rebuild example
> >> local.conf: remove example-hello from the default build
> >> local.conf: enable rebuilding "hello" for all distros
> >>
> >> meta-isar/conf/distro/debian-buster.list | 3 +
> >> meta-isar/conf/distro/debian-jessie.list | 3 +
> >> .../conf/distro/debian-stretch-backports.list | 1 +
> >> meta-isar/conf/distro/debian-stretch.list | 3 +
> >> meta-isar/conf/distro/raspbian-jessie.list | 1 +
> >> meta-isar/conf/local.conf.sample | 2 +-
> >> meta-isar/recipes-app/hello/hello.inc | 19 +++++
> >> meta-isar/recipes-app/hello/hello_2.10.bb | 8 ++
> >> meta-isar/recipes-app/hello/hello_2.9.bb | 8 ++
> >> meta/classes/debianize.bbclass | 82
> >> +++++++++++++++++++ meta/classes/dpkg-base.bbclass |
> >> 20 +++++ meta/classes/dpkg-raw.bbclass | 76
> >> ----------------- 12 files changed, 149 insertions(+), 77
> >> deletions(-) create mode 100644
> >> meta-isar/recipes-app/hello/hello.inc create mode 100644
> >> meta-isar/recipes-app/hello/hello_2.10.bb create mode 100644
> >> meta-isar/recipes-app/hello/hello_2.9.bb create mode 100644
> >> meta/classes/debianize.bbclass
> >
>
>
next prev parent reply other threads:[~2019-01-30 9:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 16:04 Henning Schild
2019-01-17 16:04 ` [PATCH 1/7] conf: add deb-src entries to all our distro configs Henning Schild
2019-01-17 16:04 ` [PATCH 2/7] dpkg-base: introduce an "apt-get source" fetch/unpack step Henning Schild
2019-01-28 17:06 ` Jan Kiszka
2019-01-28 17:12 ` Hombourger, Cedric
2019-01-28 17:13 ` Jan Kiszka
2019-01-30 13:57 ` [PATCHv2 " Henning Schild
2019-01-30 13:58 ` Henning Schild
2019-01-17 16:04 ` [PATCH 3/7] meta: move debianization code into a class and into dpkg-base Henning Schild
2019-01-17 16:04 ` [PATCH 4/7] debianize: allow changlog version change Henning Schild
2019-01-17 16:04 ` [PATCH 5/7] meta-isar/recipes-app: add upstream hello rebuild example Henning Schild
2019-01-30 13:06 ` [PATCHv2 " Henning Schild
2019-01-30 13:07 ` Henning Schild
2019-01-17 16:04 ` [PATCH 6/7] local.conf: remove example-hello from the default build Henning Schild
2019-01-28 17:08 ` Jan Kiszka
2019-01-29 11:14 ` Maxim Yu. Osipov
2019-01-17 16:04 ` [PATCH 7/7] local.conf: enable rebuilding "hello" for all distros Henning Schild
2019-01-29 11:20 ` Maxim Yu. Osipov
2019-01-30 13:04 ` Henning Schild
2019-01-17 16:38 ` [PATCH 0/7] "apt-get source" fetch/unpack support Henning Schild
2019-01-21 9:29 ` Claudius Heine
2019-01-28 17:17 ` Jan Kiszka
2019-01-28 16:57 ` Henning Schild
2019-01-30 6:43 ` Maxim Yu. Osipov
2019-01-30 9:15 ` Henning Schild [this message]
2019-01-30 12:24 ` Henning Schild
-- strict thread matches above, loose matches on Subject: below --
2019-01-17 16:02 Henning Schild
2019-01-17 16:05 ` Henning Schild
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=20190130101547.28d7f41d@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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