All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Weihmann <kweihmann@outlook.com>
To: Pavel Zhukov <pavel@zhukoff.net>,
	openembedded-core@lists.openembedded.org
Cc: Pavel Zhukov <pavel.zhukov@huawei.com>
Subject: Re: [OE-core] [PATCH] patch.py: Initialize git repo before patching
Date: Wed, 1 Dec 2021 14:24:59 +0100	[thread overview]
Message-ID: <AS8PR09MB46459FA96A6FF09AD7C1F1CAA8689@AS8PR09MB4645.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <20211201131957.20901-1-pavel@zhukoff.net>

Could you please add a test case for that to the testing suite, as I'm 
having issues to understand under what circumstances we are getting into 
such kind of situation

On 01.12.21 14:19, Pavel Zhukov wrote:
> From: Pavel Zhukov <pavel.zhukov@huawei.com>
> 
> If PATCHTOOL="git" has been specified but workdir is not git repo
> bitbake fails to apply the patches. Fix this by initializing the repo
> before patching.
> This allows binary git patches to be applied.
> 
> Signed-off-by: Pavel Zhukov <pavel.zhukov@huawei.com>
> ---
>   meta/lib/oe/patch.py | 17 +++++++++++++++++
>   1 file changed, 17 insertions(+)
> 
> diff --git a/meta/lib/oe/patch.py b/meta/lib/oe/patch.py
> index fccbedb519..8326cb55bc 100644
> --- a/meta/lib/oe/patch.py
> +++ b/meta/lib/oe/patch.py
> @@ -56,6 +56,10 @@ def runcmd(args, dir = None):
>           if dir:
>               os.chdir(olddir)
>   
> +def getstatusoutput(cmd):
> +    import subprocess
> +    return subprocess.getstatusoutput(cmd.split())
> +
>   class PatchError(Exception):
>       def __init__(self, msg):
>           self.msg = msg
> @@ -298,6 +302,19 @@ class GitApplyTree(PatchTree):
>           PatchTree.__init__(self, dir, d)
>           self.commituser = d.getVar('PATCH_GIT_USER_NAME')
>           self.commitemail = d.getVar('PATCH_GIT_USER_EMAIL')
> +        if not self._isInitialized():
> +            self._initRepo()
> +
> +    def _isInitialized(self):
> +        cmd = "git rev-parse --show-toplevel"
> +        (status, output) = getstatusoutput(cmd)
> +        ## Make sure we're in builddir to not break top-level git repos
> +        return status == 0 and os.path.samedir(output, self.dir)
> +
> +    def _initRepo(self):
> +        runcmd("git init".split(), self.dir)
> +        runcmd("git add .".split(), self.dir)
> +        runcmd("git commit -a --allow-empty -m Patching_started".split(), self.dir)
>   
>       @staticmethod
>       def extractPatchHeader(patchfile):
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#159029): https://lists.openembedded.org/g/openembedded-core/message/159029
> Mute This Topic: https://lists.openembedded.org/mt/87426820/3647476
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [kweihmann@outlook.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


  reply	other threads:[~2021-12-01 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 13:19 [PATCH] patch.py: Initialize git repo before patching Pavel Zhukov
2021-12-01 13:24 ` Konrad Weihmann [this message]
2021-12-01 14:19   ` [OE-core] " Pavel Zhukov

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=AS8PR09MB46459FA96A6FF09AD7C1F1CAA8689@AS8PR09MB4645.eurprd09.prod.outlook.com \
    --to=kweihmann@outlook.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pavel.zhukov@huawei.com \
    --cc=pavel@zhukoff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.