From: Henning Schild <henning.schild@siemens.com>
To: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [RFC PATCH 2/2] recipes-core: Add recipe for base-files
Date: Wed, 24 Feb 2021 12:54:01 +0100 [thread overview]
Message-ID: <20210224125401.406f62c2@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <b334fb9c-127e-4bfa-b47a-f402e7a1165dn@googlegroups.com>
Am Wed, 24 Feb 2021 03:40:48 -0800 (PST)
schrieb "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>:
> On Wednesday, February 24, 2021 at 2:51:43 PM UTC+5:30 Jan Kiszka
> wrote:
>
> > On 24.02.21 10:20, vijaikumar....@gmail.com wrote:
> > >
> > >
> > > On Tuesday, February 23, 2021 at 2:11:02 PM UTC+5:30
> > > vijaikumar....@gmail.com wrote:
> > >
> > > On Monday, February 22, 2021 at 6:10:08 PM UTC+5:30
> > > ami...@ilbers.de wrote:
> > >
> > > 19.02.2021 22:57, Vijai Kumar K wrote:
> > > > /etc/os-release is a symlink to /usr/lib/os-release and
> > > belongs to
> > > > the base-files package.
> > > >
> > > > ISAR has been modifying the /etc/os-release during
> > > > postprocessing to inject custom data onto it.
> > > >
> > > > Since this file belongs to base-files, an update/reinstall of
> > > > the package would overwrite the file with the one provided by
> > > base-files.
> > > >
> > > > Instead of modifying the contents of /etc/os-release during
> > > > post-processing, provide a modified base-files recipe in ISAR
> > > which
> > > > provides the similar changes in os-release.
> > > >
> > > > Signed-off-by: Vijai Kumar K <Vijaikumar_...@mentor.com>
> > >
> > > Hello, base-files package failed to build for qemuarm64-focal
> > > target
> > > during CI:
> > >
> > > 15:12:37 dh_strip
> > > 15:12:37 aarch64-linux-gnu-objcopy: Unable to recognise the
> > > format of
> > > the input file `debian/base-files/usr/bin/locale-check'
> > > 15:12:37 dh_strip: error: aarch64-linux-gnu-objcopy
> > > --only-keep-debug
> > > --compress-debug-sections debian/base-files/usr/bin/locale-check
> > >
> > debian/.debhelper/base-files/dbgsym-root/usr/lib/debug/.build-id/71/aa3df0a7e05817cb7e212513aeae7db21d8593.debug
> >
> > >
> > > returned exit code 1
> > > 15:12:37 dh_strip: error: Aborting due to earlier error
> > > 15:12:37 make: *** [debian/rules:15: binary] Error 25
> > > 15:12:37 dpkg-buildpackage: error: fakeroot debian/rules binary
> > > subprocess returned exit status 2
> > > 15:12:37 WARNING: exit code 2 from a shell command.
> > >
> > > Full log:
> > > http://ci.isar-build.org:8080/job/isar_am_devel_fast/89/console
> > > <http://ci.isar-build.org:8080/job/isar_am_devel_fast/89/console>
> > >
> > >
> > > Thank you Anton, for quickly running this through our CI. I will
> > > try to replicate the issue in my local build and will fix it in
> > > next version.
> > >
> > >
> > > This seems to be like a qemu issue.
> > > https://www.mail-archive.com/debian...@lists.debian.org/msg59230.html
> > >
> > <https://www.mail-archive.com/debian-glibc@lists.debian.org/msg59230.html>
> >
> > >
> > > We could work around it by setting ISAR_CROSS_COMPILE. But ubuntu
> > > base-files cross compilation is failing.
> > > That needs to be fixed first. Maybe should raise an issue in
> > > ubuntu.
> >
> > Are we running qemu-user-static from bullseye here already? That is
> > what we do in kas-isar for a while.
>
>
> Just now tried in kas. It works as expected. Maybe we might need to
> update ISAR
> docs to denote the need for the latest qemu?
>
> That leaves the cross-building issue.
> Raised a bug report in ubuntu for that.
> https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1916714
> I will also see if I can send a patch for this. Till then we might
> need to disable
> ISAR_CROSS_COMPILE for base-files for ubuntu.
Nice to see those reports and doc updates coming out (vijai, please
send that doc patch)
But the general approach of this packages seems to be a dead end
https://groups.google.com/g/isar-users/c/maMS_p5Ep2o/m/lWSgTr7TAgAJ
Henning
> Thanks,
> Vijai Kumar K
>
>
> >
> >
> > Jan
> >
> > --
> > Siemens AG, T RDA IOT
> > Corporate Competence Center Embedded Linux
> >
>
prev parent reply other threads:[~2021-02-24 11:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 19:57 [RFC PATCH 0/2] Custom base-files Vijai Kumar K
2021-02-19 19:57 ` [RFC PATCH 1/2] dpkg-base: Handle custom source directory in do_apt_fetch Vijai Kumar K
2021-02-20 8:07 ` Henning Schild
2021-02-22 7:11 ` vijai kumar
2021-03-03 12:49 ` Henning Schild
2021-03-03 13:49 ` Kanagarajan, Vijaikumar
2021-03-03 14:53 ` Henning Schild
2021-02-19 19:57 ` [RFC PATCH 2/2] recipes-core: Add recipe for base-files Vijai Kumar K
2021-02-20 8:28 ` Henning Schild
2021-02-23 8:38 ` vijai kumar
2021-02-24 12:12 ` Henning Schild
2021-02-25 3:57 ` vijai kumar
2021-02-25 5:08 ` vijaikumar....@gmail.com
2021-02-25 8:20 ` Jan Kiszka
2021-02-25 8:40 ` Jan Kiszka
2021-02-25 9:06 ` vijaikumar....@gmail.com
2021-02-25 16:32 ` Henning Schild
2021-03-01 5:07 ` vijaikumar....@gmail.com
2021-03-01 7:35 ` Henning Schild
2021-03-01 8:04 ` vijaikumar....@gmail.com
2021-02-25 8:10 ` Henning Schild
2021-02-25 8:26 ` vijaikumar....@gmail.com
2021-02-22 12:39 ` Anton Mikanovich
2021-02-23 8:41 ` vijaikumar....@gmail.com
2021-02-24 9:20 ` vijaikumar....@gmail.com
2021-02-24 9:21 ` Jan Kiszka
2021-02-24 11:40 ` vijaikumar....@gmail.com
2021-02-24 11:54 ` Henning Schild [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=20210224125401.406f62c2@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=vijaikumar.kanagarajan@gmail.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