<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/chunkeey/scripts, branch v19.07.9</title>
<subtitle>Staging tree of Christian Lamparter</subtitle>
<id>https://git.openwrt.org/openwrt/staging/chunkeey/atom?h=v19.07.9</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/chunkeey/atom?h=v19.07.9'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/'/>
<updated>2022-02-01T11:52:20Z</updated>
<entry>
<title>build: store SOURCE_DATE_EPOCH in JSON info files</title>
<updated>2022-02-01T11:52:20Z</updated>
<author>
<name>Paul Spooren</name>
</author>
<published>2020-11-01T21:53:39Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=524cbcf6f5b07f3d9ee45e445da12760947e232e'/>
<id>urn:sha1:524cbcf6f5b07f3d9ee45e445da12760947e232e</id>
<content type='text'>
The source date epoch is the only reproducible date close to the actual
build date. It can be used for tooling like the firmware wizard to show
the image age.

Signed-off-by: Paul Spooren &lt;mail@aparcar.org&gt;
(cherry picked from commit 165f0b00cdd2f763c1d478c2f58c535fc19b13bd)
[store source_date_epoch as integer]
Signed-off-by: Paul Spooren &lt;mail@aparcar.org&gt;
</content>
</entry>
<entry>
<title>scripts: bundle-libraries.sh: fix broken SDK compiler</title>
<updated>2021-03-20T12:44:44Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2020-11-01T13:40:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=dce6b118eb9f9c43f93de3a4570d5b36f731e62e'/>
<id>urn:sha1:dce6b118eb9f9c43f93de3a4570d5b36f731e62e</id>
<content type='text'>
Recent versions (&gt; 5.33) of `file` report liblto_plugin.so as
executable:

 $ file liblto_plugin.so
 liblto_plugin.so.0.0.0: ELF 64-bit LSB pie executable ...

Which then leads to improper packaging of the plugin, resulting in the
broken compiler:

 configure: checking whether the C compiler works
 mips-openwrt-linux-musl/bin/ld: liblto_plugin.so: error loading plugin: liblto_plugin.so: invalid ELF header

As the LTO compiler plugin library is incorrectly packaged as SDK
executable:

 $ head -1 ~/staging_dir/toolchain...libexec/gcc/.../liblto_plugin.so
 #!/usr/bin/env bash

Fix this by filtering out shared libraries from the patching.

Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1296868
Acked-by: Jo-Philipp Wich &lt;jo@mein.io&gt;
Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
(cherry picked from commit 4b7165722cb0e2ba62ab68e8b90d4d4b0909744c)
</content>
</entry>
<entry>
<title>build/json: add filesystem information</title>
<updated>2020-12-17T21:16:36Z</updated>
<author>
<name>Paul Spooren</name>
</author>
<published>2020-12-14T00:36:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=42e478eb0dbfce71ba21d2a6ed7297ec6db8cc19'/>
<id>urn:sha1:42e478eb0dbfce71ba21d2a6ed7297ec6db8cc19</id>
<content type='text'>
Some images are created using different filesystems, most popular
squashfs and ext4. To allow downstream projects to distinguesh between
those, add the `filesystem` information to created json files.

Signed-off-by: Paul Spooren &lt;mail@aparcar.org&gt;
(cherry picked from commit bc0ffff36a0bd8043e958913f574cb8d2a79e93d)
</content>
</entry>
<entry>
<title>download.pl: properly cleanup intermediate .hash file</title>
<updated>2020-12-05T19:50:19Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2020-11-27T20:56:30Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=a47caacaf37e57389acc7618f23a7e64afaa9d8c'/>
<id>urn:sha1:a47caacaf37e57389acc7618f23a7e64afaa9d8c</id>
<content type='text'>
It seems like after a build the /dl dir seems to now contain a .hash
file for each source file due to inproper cleanup so fix it by removing
those intermediate files before leaving the download action.

Fixes: 4e19cbc55335 ("download: handle possibly invalid local tarballs")
Reported-by: Hannu Nyman &lt;hannu.nyman@iki.fi&gt;
Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
(cherry picked from commit 52a5d0d27f2557db99fc5435fbd7783b649cb9b2)
</content>
</entry>
<entry>
<title>download: handle possibly invalid local tarballs</title>
<updated>2020-12-05T19:50:19Z</updated>
<author>
<name>Petr Štetiar</name>
</author>
<published>2020-11-19T15:32:46Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=605adb1023efda0c29d160839fccc20801b717cd'/>
<id>urn:sha1:605adb1023efda0c29d160839fccc20801b717cd</id>
<content type='text'>
Currently it's assumed, that already downloaded tarballs are always
fine, so no checksum checking is performed and the tarball is used even
if it might be corrupted.

From now on, we're going to always check the downloaded tarballs before
considering them valid.

Steps to reproduce:

 1. Remove cached tarball

   rm dl/libubox-2020-08-06-9e52171d.tar.xz

 2. Download valid tarball again

   make package/libubox/download

 3. Invalidate the tarball

   sed -i 's/PKG_MIRROR_HASH:=../PKG_MIRROR_HASH:=ff/' package/libs/libubox/Makefile

 4. Now compile with corrupt tarball source

   make package/libubox/{clean,compile}

Signed-off-by: Petr Štetiar &lt;ynezz@true.cz&gt;
(cherry picked from commit 4e19cbc553350b8146985367ba46514cf50e3393)
</content>
</entry>
<entry>
<title>scripts: download.pl: retry download using filename</title>
<updated>2020-11-20T10:58:01Z</updated>
<author>
<name>David Bauer</name>
</author>
<published>2020-11-18T15:02:23Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=39c5635714aacac4e94f4ac60d191e9b0582d6b5'/>
<id>urn:sha1:39c5635714aacac4e94f4ac60d191e9b0582d6b5</id>
<content type='text'>
With this commit, the download script will try downloading source files
using the filename instead of the url-filename in case the previous
download attempt using the url-filename failed.

This is required, as the OpenWrt sources mirrors serve files using the
filename files might be renamed to after downloading. If the original
mirror for a file where url-filename and filename do not match goes
down, the download failed prior to this patch.

Further improvement can be done by performing this only for the
OpenWrt sources mirrors.

Signed-off-by: David Bauer &lt;mail@david-bauer.net&gt;
(cherry picked from commit d36999389890fb952fc7cc8c0db8e1bbb671af12)
</content>
</entry>
<entry>
<title>scripts: getver.sh: fix version based on stable branch</title>
<updated>2020-10-07T21:13:00Z</updated>
<author>
<name>Baptiste Jonglez</name>
</author>
<published>2020-09-03T21:19:07Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=891022918d55b565b49b7ecafc4ebf8a66461a13'/>
<id>urn:sha1:891022918d55b565b49b7ecafc4ebf8a66461a13</id>
<content type='text'>
When building from a local branch based off the "openwrt-19.07" branch,
version computation is wrong, for instance:

    r10194+1004-c53f62b111

The number of local commits (1004 in this case) is wrong because it is
computed against master.  As a result, it wrongly counts *all* commits
since the beginning of the openwrt-19.07 branch as local commits.

The fix is to compare to the openwrt-19.07 branch instead, which gives the
expected result such as:

    r11192+6-8b0278a17e

Signed-off-by: Baptiste Jonglez &lt;git@bitsofnetworks.org&gt;
[shorten commit title]
Signed-off-by: Adrian Schmutzler &lt;freifunk@adrianschmutzler.de&gt;
</content>
</entry>
<entry>
<title>Revert "scripts/download: add sources CDN as first mirror"</title>
<updated>2020-08-24T13:56:27Z</updated>
<author>
<name>Jo-Philipp Wich</name>
</author>
<published>2020-08-24T13:53:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=350883bb90e05433d755cbe87eb7c75a7af9a535'/>
<id>urn:sha1:350883bb90e05433d755cbe87eb7c75a7af9a535</id>
<content type='text'>
This reverts commit c737a9ee6a9c47b6e553ac81bf293b1161e59799.

The source CDN has been discontinued in its current form and will take a
while to be reestablished. Even then it makes little sense to put a CDN
before other CDNs such as kernel.org, apache.org, sourceforge etc.

Signed-off-by: Jo-Philipp Wich &lt;jo@mein.io&gt;
(cherry picked from commit bf96eb55c82191701030b68810e6f19adbb91eeb)
</content>
</entry>
<entry>
<title>scripts: Add Buildbot dump-target-info.pl script</title>
<updated>2020-08-09T23:43:15Z</updated>
<author>
<name>Paul Spooren</name>
</author>
<published>2020-08-03T17:31:43Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=7db09853a83b2feaf2604e4fcc074100be377280'/>
<id>urn:sha1:7db09853a83b2feaf2604e4fcc074100be377280</id>
<content type='text'>
The script comes from buildbot.git[0] and is used to print available
targets and architectures, which are then build.

As the buildbot clones openwrt.git anyway, the script might as well live
here to be used for other cases as well, e.g. determining what
architectures are available when building Docker containers or show
developers an overview which architectures are used by which target.

It's called with either the parameter `architectures` or `targets`,
showing architectures followed by supported targets or targets, followed
by the supported architectures:

$ ./scripts/dump-target-info.pl architectures
aarch64_cortex-a53 bcm27xx/bcm2710 mediatek/mt7622 mvebu/cortexa53 sunxi/cortexa53
aarch64_cortex-a72 bcm27xx/bcm2711 mvebu/cortexa72
...

$ ./scripts/dump-target-info.pl targets
apm821xx/nand powerpc_464fp
apm821xx/sata powerpc_464fp
...

In the future the the script could be removed from the buildbot
repository and maintained only here.

Rename `dumpinfo.pl` to `dump-target-info.pl` to improve verbosity of
filename.

[0]: https://git.openwrt.org/?p=buildbot.git;a=blob;f=scripts/dumpinfo.pl;h=aa97f8d60379076a41b968402e9337cea824ece5;hb=HEAD

Signed-off-by: Paul Spooren &lt;mail@aparcar.org&gt;
(cherry picked from commit 656b562aff36d92b0e8586833b59896a55b8a993)
</content>
</entry>
<entry>
<title>build,json: fix compatibility with Python 3.5</title>
<updated>2020-07-13T20:24:30Z</updated>
<author>
<name>Paul Spooren</name>
</author>
<published>2020-07-12T04:44:55Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/chunkeey/commit/?id=b9a89bf7b55d37ef750015e0be2378cf8e35285f'/>
<id>urn:sha1:b9a89bf7b55d37ef750015e0be2378cf8e35285f</id>
<content type='text'>
The f-string feature was introduced in Python 3.6. As Buildbots may run
on Debian 9, which comes per default with Python 3.5, this would cause
an issue. Instead of f-strings use the *legacy* `.format()` function.

Signed-off-by: Paul Spooren &lt;mail@aparcar.org&gt;
</content>
</entry>
</feed>
