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 19:19:41 +0100 [thread overview]
Message-ID: <20190207191941.52a473a5@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <AM5PR10MB1843112B9D56AD2BAC144085EC680@AM5PR10MB1843.EURPRD10.PROD.OUTLOOK.COM>
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.
Even if the patching was done later, you would see the same problem in
the first rebuild. Since the patching does not get undone.
If you need to use git you can enter the buildchroot and call it with
"mount; sudo chroot -E ..." ... the repeating pattern. Or you might get
away with "git -C somewhere/in/dldir" ... hack, or "git clone
file://somewhere/in/dldir ${WORKDIR}/git_host". Now thinking about that
we might enable adjust_git to keep a host copy for you, if you ask
for it ... somehow. Or you write your own _prepend it with "cp -r git
git_host" ;).
Henning
> Best regards
> Raphael Lisicki
>
prev parent reply other threads:[~2019-02-07 18:19 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
2019-02-07 18:19 ` 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=20190207191941.52a473a5@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