From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package/python-rtslib-fb: bump version to 2.1.58
Date: Fri, 7 Oct 2016 22:26:19 +0200 [thread overview]
Message-ID: <20161007222619.1a5f7701@free-electrons.com> (raw)
In-Reply-To: <20161007181627.7ff94cb3@trantor>
Hello,
On Fri, 7 Oct 2016 18:16:27 +0200, Christophe Vu-Brugier wrote:
> Sorry for commenting a patch after it has been applied.
No problem, it's never too late to fix things up.
> > -PYTHON_RTSLIB_FB_VERSION = v2.1.fb57
> > -PYTHON_RTSLIB_FB_SITE = $(call github,agrover,rtslib-fb,$(PYTHON_RTSLIB_FB_VERSION))
> > +PYTHON_RTSLIB_FB_VERSION = 2.1.58
> > +PYTHON_RTSLIB_FB_SOURCE = rtslib-fb-$(PYTHON_RTSLIB_FB_VERSION).tar.gz
> > +PYTHON_RTSLIB_FB_SITE = https://pypi.python.org/packages/c8/26/ae0ff9a721d046bef78c457d8fc19287f7dbe36f98f5e190b017f0d9e9b7
>
> The home of rtslib-fb is still on GitHub but its maintainer, Andy
> Grover, has moved the repository ownership to the open-iscsi
> organization [1].
>
> So the homepage of rtslib-fb, configshell-fb and targetcli-fb is now :
>
> https://github.com/open-iscsi/{rtslib,configshell,targetcli}-fb
>
> The old URL still works though.
OK. A patch updating the upstream URL in Config.in would be good.
> Moreover, version 2.1.58 is not the latest version since 2.1.60 was
> released a few days ago [2].
Right, but the latest version available from Pypi is 2.1.58, see
https://pypi.org/project/rtslib-fb/. If you don't want a Python package
to be changed to fetch from Pypi, I think a comment in the .mk file
should be added.
> Note that targetcli-fb, configshell-fb and rtslib-fb are released at
> the same time because they are closely related (targetcli-fb imports
> both rtslib-fb and configshell-fb).
>
> So for Buildroot, it makes sense to upgrade rtslib-fb, configshell-fb
> and targetcli-fb at the same time but upgrading only one of them is a
> bit risky because you end up shipping versions of the packages that
> were not tested together by upstream developers.
OK. I think this should be mentioned in a comment above the _VERSION
field of those packages. This way, it is clearly visible when bumping
the version of those packags.
> IIRC, I tried to bump targetcli-fb and its dependencies locally several
> month ago but encountered problems since targetcli-fb now depends
> on DBUS. I was also reluctant to upgrade rtslib-fb because it now
> depends on pyudev and I usually run targetcli without systemd/udev in
> Buildroot.
Those problems are due to upstream decisions, and we should not stop
from upgrading because of such decisions. If you dislike those
decisions, the solution is not to stop upgrading. The solution is to
contact upstream and complain (possibly by submitting patches).
Buildroot's policy is to follow what upstream decides... even if you
don't like it :)
> I may resume work on upgrading targetcli-fb, configshell-fb
> and rtslib-fb though.
OK. However, it is not clear from your e-mail if you think Bernd's
patch should be reverted. Could you clarify this?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-07 20:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 13:15 [Buildroot] [git commit] package/python-rtslib-fb: bump version to 2.1.58 Thomas Petazzoni
2016-10-07 16:16 ` Christophe Vu-Brugier
2016-10-07 16:19 ` Christophe Vu-Brugier
2016-10-07 20:26 ` Thomas Petazzoni [this message]
2016-10-07 21:10 ` Christophe Vu-Brugier
2016-10-07 21:30 ` Thomas Petazzoni
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=20161007222619.1a5f7701@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox