From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/perl: bump version to 5.24.0
Date: Tue, 4 Oct 2016 09:18:51 +0200 [thread overview]
Message-ID: <20161004091851.65884a72@free-electrons.com> (raw)
In-Reply-To: <CAB0FRstXs7JNhBzmYqRyOddDdBLNvHvwU=AkYFR6UfsFLvJZKg@mail.gmail.com>
Hello,
On Tue, 4 Oct 2016 06:02:49 +0200, Fran?ois Perrad wrote:
> perl-cross 1.1.0 is not mature (11 issues opened on september), it is
> a full refactor, there are already 19 commits after this tag.
>
> I never bump a perl version 5.x.0, I always wait the version 5.x.1
>
> If you really need a perl 5.24.0, cross-compiled it with
> perl-5.24.0-cross-1.0.3.
>
> When I bump a perl version, I run on target the full Perl test suite
> (~ 800 000 tests), and failures are not expected.
> With cross-perl 1.0.3 and 1.1.0 tags, there have failures described in
> https://github.com/arsv/perl-cross/issues/33
OK, thanks for the explanations.
> Please, revert this commit.
I've reverted the commit.
Bernd, could you start using the get-developers script to ensure you
are CC'ing the right developers depending on the package you're
patching. This would have CC'ed Fran?ois in the case of this perl
related patch.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-04 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 14:17 [Buildroot] [PATCH 1/1] package/perl: bump version to 5.24.0 Bernd Kuhls
2016-10-03 21:10 ` Thomas Petazzoni
2016-10-04 4:02 ` François Perrad
2016-10-04 7:18 ` Thomas Petazzoni [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=20161004091851.65884a72@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