From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
"Mingyu Wang (Fujitsu)" <wangmy@fujitsu.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Subject: Re: [OE-core] [PATCH 14/22] ptest-runner: upgrade 2.4.5 -> 2.5.1
Date: Tue, 29 Oct 2024 22:34:08 +0000 [thread overview]
Message-ID: <46c758350449ee0da44519d8575c5e245aafd8de.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj89yS92RVWiu1q+AXpfCdBL7e1RF8MkQxybHY+2qhObZQ@mail.gmail.com>
On Tue, 2024-10-29 at 12:56 +0100, Alexander Kanavin wrote:
> On Mon, 28 Oct 2024 at 20:46, Alexander Kanavin via
> lists.openembedded.org
> <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
> >
> > On Sun, 27 Oct 2024 at 04:12, Mingyu Wang (Fujitsu)
> > <wangmy@fujitsu.com> wrote:
> > > It was indeed done using devtool upgrade, but the version number
> > > of the resulting bb file is 2.5.1.
> > > Although the version number is recorded as 2.4.5.1 in the bb
> > > file, I deleted that line when modifying the content of the bb
> > > file.
> > > When modifying the patch, I forgot that the actual version number
> > > was 2.4.5.1, so I made a mistake.
> >
> > That's fine. But why did you have to modify the file? Did devtool
> > change something that you had to fix afterwards?
>
> This has now merged in master :( I'll send a quick fixup.
Sorry, and thanks!
Cheers,
Richard
next prev parent reply other threads:[~2024-10-29 22:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 5:39 [OE-core] [PATCH 01/22] autoconf-archive: upgrade 2023.02.20 -> 2024.10.16 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 02/22] bash: upgrade 5.2.32 -> 5.2.37 wangmy
2024-10-25 9:10 ` Alexander Kanavin
2024-10-25 5:39 ` [OE-core] [PATCH 03/22] epiphany: upgrade 47.0 -> 47.1 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 04/22] i2c-tools: upgrade 4.3 -> 4.4 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 05/22] less: upgrade 661 -> 668 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 06/22] libarchive: upgrade 3.7.6 -> 3.7.7 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 07/22] libubootenv: upgrade 0.3.5 -> 0.3.6 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 08/22] libunistring: upgrade 1.2 -> 1.3 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 09/22] libuv: upgrade 1.49.0 -> 1.49.2 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 10/22] libxmlb: upgrade 0.3.19 -> 0.3.21 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 11/22] llvm: upgrade 19.1.0 -> 19.1.2 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 12/22] meson: upgrade 1.5.2 -> 1.6.0 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 13/22] ofono: upgrade 2.10 -> 2.11 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 14/22] ptest-runner: upgrade 2.4.5 -> 2.5.1 wangmy
2024-10-25 9:12 ` Alexander Kanavin
2024-10-27 3:12 ` Mingyu Wang (Fujitsu)
2024-10-28 19:46 ` Alexander Kanavin
[not found] ` <1802B5823947D89C.18751@lists.openembedded.org>
2024-10-29 11:56 ` Alexander Kanavin
2024-10-29 22:34 ` Richard Purdie [this message]
2024-10-25 5:39 ` [OE-core] [PATCH 15/22] python3-jsonschema-specifications: upgrade 2023.12.1 -> 2024.10.1 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 16/22] python3-poetry-core: upgrade 1.9.0 -> 1.9.1 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 17/22] python3-psutil: upgrade 6.0.0 -> 6.1.0 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 18/22] python3-rdflib: upgrade 7.0.0 -> 7.1.0 wangmy
2024-10-29 9:40 ` Mathieu Dubois-Briand
2024-10-31 8:36 ` Mingyu Wang (Fujitsu)
2024-10-25 5:39 ` [OE-core] [PATCH 19/22] python3-sphinx-rtd-theme: upgrade 3.0.0 -> 3.0.1 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 20/22] python3-xmltodict: upgrade 0.13.0 -> 0.14.2 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 21/22] systemd: upgrade 256.6 -> 256.7 wangmy
2024-10-25 5:39 ` [OE-core] [PATCH 22/22] xtrans: upgrade 1.5.0 -> 1.5.1 wangmy
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=46c758350449ee0da44519d8575c5e245aafd8de.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.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