All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Flávio Tapajós" <flavio.tapajos@newtesc.com.br>
Cc: James Hilliard <james.hilliard1@gmail.com>,
	Asaf Kahlon <asafka7@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/python-sqlalchemy: bump version to 2.0.25
Date: Thu, 4 Jan 2024 23:33:30 +0100	[thread overview]
Message-ID: <20240104233330.2d64b4e0@windsurf> (raw)
In-Reply-To: <20240103142831.901515-1-flavio.tapajos@newtesc.com.br>

Hello Flávio,

Thanks a lot for your patch, I have applied it, but after fixing a few
small things. See below!

On Wed,  3 Jan 2024 11:28:30 -0300
Flávio Tapajós <flavio.tapajos@newtesc.com.br> wrote:

> diff --git a/package/python-sqlalchemy/Config.in b/package/python-sqlalchemy/Config.in
> index f7ec3a6ad4..f05fee7ab1 100644
> --- a/package/python-sqlalchemy/Config.in
> +++ b/package/python-sqlalchemy/Config.in
> @@ -1,5 +1,6 @@
>  config BR2_PACKAGE_PYTHON_SQLALCHEMY
>  	bool "python-sqlalchemy"
> +	select BR2_PACKAGE_PYTHON_TYPING_EXTENSIONS

This a runtime dependency only, we don't need it at build-time. We like
to document such dependencies like this:

	select BR2_PACKAGE_PYTHON_TYPING_EXTENSIONS # runtime

which helps document that it is normal for this dependency to be in
Config.in, but not in the .mk file.

> diff --git a/package/python-sqlalchemy/python-sqlalchemy.hash b/package/python-sqlalchemy/python-sqlalchemy.hash
> index 9f479d8f7b..6a894bee24 100644
> --- a/package/python-sqlalchemy/python-sqlalchemy.hash
> +++ b/package/python-sqlalchemy/python-sqlalchemy.hash
> @@ -1,5 +1,5 @@
>  # md5, sha256 from https://pypi.org/pypi/sqlalchemy/json
> -md5  52318b83e8931c5f5a459f54fe4be3e8  SQLAlchemy-1.4.42.tar.gz
> -sha256  177e41914c476ed1e1b77fd05966ea88c094053e17a85303c4ce007f88eff363  SQLAlchemy-1.4.42.tar.gz
> +sha256 a2c69a7664fb2d54b8682dd774c3b54f67f84fa123cf84dda2a5f40dcaa04e08  SQLAlchemy-2.0.25.tar.gz
> +md5 7abfc2972d7e16315c8b7492ea0e0fdb SQLAlchemy-2.0.25.tar.gz

Here you changed the ordering of the two lines, which adds a bit of
"noise" and it not really needed. You also broke the spacing of the
different fields: we want two spaces between each field (yes that's a
pure convention, but it allows things to be consistent between
packages). If you run "make check-package", or "./utils/check-package
package/python-sqlalchemy/*", it checks such minor coding style issues.

>  # Locally computed sha256 checksums
>  sha256  859ded25da34c1eb73e6e736df4c5f8ce3ed2ed5290663176f06e7720d9c9a20  LICENSE

The final issue was related to the LICENSE file: it has changed between
the old version of sqlalchemy and this new version, so the hash was no
longer correct. So I have updated the hash, but more importantly, I
have documented in the commit log why the hash changed.

With all those changes, the final commit looks like this:

  https://gitlab.com/buildroot.org/buildroot/-/commit/0f2f090892914e3b04ff217d1ea10cceafc70515

Thanks again for your contribution!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-01-04 22:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 14:28 [Buildroot] [PATCH 1/2] package/python-sqlalchemy: bump version to 2.0.25 Flávio Tapajós
2024-01-03 14:28 ` [Buildroot] [PATCH 2/2] DEVELOPERS: add Flávio Tapajós for python-sqlalchemy Flávio Tapajós
2024-01-04 22:33   ` Thomas Petazzoni via buildroot
2024-01-04 22:33 ` Thomas Petazzoni via buildroot [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=20240104233330.2d64b4e0@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=flavio.tapajos@newtesc.com.br \
    --cc=james.hilliard1@gmail.com \
    --cc=thomas.petazzoni@bootlin.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 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.