From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Lisicki, Raphael" <raphael.lisicki@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: do_adjust_git in dpkg-base.class
Date: Thu, 7 Feb 2019 18:51:03 +0100 [thread overview]
Message-ID: <20190207185103.67521697@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <AM5PR10MB1843112B9D56AD2BAC144085EC680@AM5PR10MB1843.EURPRD10.PROD.OUTLOOK.COM>
I never was a fan of that messing with git step. Unfortunately my patch
against bitbake was never merged, one that would use true clones and
eliminate the problem with the "link".
At the moment you have to live with that. Maybe we can find a way of
patching the git argv from within the fetcher implementation of Isar.
Henning
Am Thu, 7 Feb 2019 13:03:58 +0000
schrieb "[ext] Lisicki, Raphael" <raphael.lisicki@siemens.com>:
> Hello everybody,
>
> the function do_adjust_git in dpkg-base.class breaks git for all
> operations outside of the buildchroot. E.g. it is not possible to use
> git in a prepare_build command, as it is not yet done in the
> buildchroot, but the git adjustment has already been done. I would
> suggest to move the call to do_adjust_git into dpkg_do_mounts and
> maybe even undo it afterwards, so that targets that run after build
> can also have access to a working git repo.
>
> Best regards
> Raphael Lisicki
>
next prev parent reply other threads:[~2019-02-07 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 13:03 Lisicki, Raphael
2019-02-07 15:31 ` Jan Kiszka
2019-02-07 17:51 ` Henning Schild [this message]
2019-02-07 18:19 ` 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=20190207185103.67521697@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=raphael.lisicki@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