From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 11 Oct 2017 23:22:59 +0200 Subject: [Buildroot] [PATCH v1] wiringpi: bump version to 96344ff7125182989f98d3be8d111952a8f74e15 (the real 2.44) In-Reply-To: <20171011222124.4d9e0756@gmx.net> References: <20171011131539.19407-1-ps.report@gmx.net> <20171011155932.01b6cf48@windsurf.lan> <20171011222124.4d9e0756@gmx.net> Message-ID: <20171011232259.16581f9a@windsurf.lan> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Wed, 11 Oct 2017 22:21:24 +0200, Peter Seiderer wrote: > > I don't think it really fixes bug 10391. Bug 10391 is bogus by itself. > > The update to 96344ff7125182989f98d3be8d111952a8f74e15 doesn't fix > > anything, it only adds support for RPi Zero W. > > Saving a download as wiringpi-2.44.tar.gz containing something > identifying itself as 2.42? I would call it a bug (not on the buildroot > side but in the original git repository). The release identified as 2.42 is in fact 2.44, since both tags point to exactly the same commit. > The suggested patch fixes the original complain of Bug 10391: > 'WiringPi retrieves wrong (old) version' > > Any suggestion on how to reference the bug report otherwise? I'll try to find a reasonable wording when applying, no need to respin. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com