From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] bitbake: Update to 1.46.2 release
Date: Mon, 17 Aug 2020 21:20:56 +0530 [thread overview]
Message-ID: <CALLGG_L3U+TVBnOJ7WoJkur20Ph9oMQP_iD32WOvNdOShF7LHw@mail.gmail.com> (raw)
In-Reply-To: <8116d4bf-871c-0dda-d7c6-d60603b47197@siemens.com>
On Mon, Aug 17, 2020 at 9:01 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:
>
> On 17.08.20 16:54, Vijai Kumar K wrote:
> > Update bitbake to the latest 1.46.2 release.
> >
>
> ...
>
> > diff --git a/bitbake/bin/bitbake b/bitbake/bin/bitbake
> > index 66d08f8..6c73710 100755
> > --- a/bitbake/bin/bitbake
> > +++ b/bitbake/bin/bitbake
> > @@ -26,7 +26,7 @@ from bb.main import bitbake_main, BitBakeConfigParameters, BBMainException
> > if sys.getfilesystemencoding() != "utf-8":
> > sys.exit("Please use a locale setting which supports UTF-8 (such as LANG=en_US.UTF-8).\nPython can't change the filesystem locale after loading so we need a UTF-8 when Python starts or things won't work.")
> >
> > -__version__ = "1.44.0"
> > +__version__ = "1.46.0"
>
> Sure that this is 1.46.2 then? Or did upstream forget to update?
>
I think upstream did not update.
https://github.com/openembedded/bitbake/blob/1.46.2/bin/bitbake
https://github.com/openembedded/bitbake/blob/cc11dfa4eb3616547a8a3909f89da0cc4f35dc57/bin/bitbake#L29
I will capture the commit hash in the commit message to avoid confusions.
Thanks,
Vijai Kumar K
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>
> --
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/isar-users/8116d4bf-871c-0dda-d7c6-d60603b47197%40siemens.com.
next prev parent reply other threads:[~2020-08-17 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-17 14:54 Vijai Kumar K
2020-08-17 15:31 ` Jan Kiszka
2020-08-17 15:50 ` vijai kumar [this message]
2020-08-17 16:00 ` [PATCH v2] " Vijai Kumar K
2020-08-19 19:35 ` Henning Schild
2020-08-19 20:48 ` vijai kumar
2020-10-05 17:01 ` vijaikumar....@gmail.com
2020-10-23 10:31 ` Baurzhan Ismagulov
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=CALLGG_L3U+TVBnOJ7WoJkur20Ph9oMQP_iD32WOvNdOShF7LHw@mail.gmail.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=Vijaikumar_Kanagarajan@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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