From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH 00/12] prserv: add support for an "upstream" server
Date: Fri, 29 Mar 2024 15:48:10 +0100 [thread overview]
Message-ID: <d9f7b03e-ed50-4796-8605-d6c1c253f4c7@bootlin.com> (raw)
In-Reply-To: <17C14331A9F4EAD6.31455@lists.openembedded.org>
On 3/29/24 at 15:39, Michael Opdenacker via lists.openembedded.org wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> This makes it possible to customize an "upstream" distribution
> by modifying local packages. If the "upstream" package bears
> revision "x", the local one will have revision "x.y", this
> having priority over the upstream one.
>
> Take advantage of this work to clean-up and update the prserv code too.
>
> Michael Opdenacker (12):
> prserv: simplify the PRServerClient() interface
> prserv: use double quotes by default
> bitbake-prserv: replace deprecated optparse by argparse
> prserv: use self.logger instead of logger directly
> asyncrpc: include parse_address from hashserv
> prserv: capitalization and spacing improvements
> prserv: fix read_only test
> prserv: add extra requests
> prserv: remove redundant exception handler
> prserv: correct error message
> prserv: remove unnecessary code
> prserv: add "upstream" server support
>
> bin/bitbake-prserv | 99 ++++++++++++-----
> lib/bb/asyncrpc/client.py | 23 ++++
> lib/hashserv/__init__.py | 27 +----
> lib/prserv/__init__.py | 21 +++-
> lib/prserv/client.py | 42 +++++--
> lib/prserv/db.py | 176 ++++++++++++++++++++---------
> lib/prserv/serv.py | 228 ++++++++++++++++++++++++++++----------
> 7 files changed, 434 insertions(+), 182 deletions(-)
Note that this code has a remaining issue that appears sometimes.
Even though the revision stored in the database was indeed "0.3", I
eventually got this package name:
tmp/deploy/ipk/core2-64/hello-dev_1.0-r0.0.30000000000000004_core2-64.ipk
This may be an issue in OE-core, in the way the "0.3" value can be
treated by default as a float by Python3, and then converted into an
incorrect string when creating the output package name. Investigating,
but if you already know where this happens, I'm interested!
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2024-03-29 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17C14331A9F4EAD6.31455@lists.openembedded.org>
2024-03-29 14:48 ` Michael Opdenacker [this message]
[not found] <17C57CE7C760AD01.4467@lists.openembedded.org>
2024-04-12 12:36 ` [bitbake-devel] [PATCH 00/12] prserv: add support for an "upstream" server Michael Opdenacker
2024-04-12 9:02 michael.opdenacker
2024-04-17 15:22 ` [bitbake-devel] " Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2024-03-29 14:39 michael.opdenacker
2024-04-03 15:09 ` [bitbake-devel] " Richard Purdie
2024-04-03 15:33 ` Michael Opdenacker
2024-04-03 15:54 ` Richard Purdie
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=d9f7b03e-ed50-4796-8605-d6c1c253f4c7@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).