On 28.09.19 11:04, Daniel Golle wrote:
Hi Paul,
On Sat, Sep 28, 2019 at 10:44:48AM -1000, Paul Spooren wrote:
Main motivation for this commit is the introduction of
`-ffile-prefix-map=` which alows reproducible build path.
Imho definitely a good reason to move forward with the switch to GCC 8
Signed-off-by: Paul Spooren
---
config/Config-build.in | 2 --
.../patches/120-strip-cflags-from-binary.patch | 2 +-
rules.mk | 8
toolchain/gcc/Config.in| 8 ++--
toolchain/gcc
Aloha,
I'm currently working on the reproducibility of OpenWrt snapshot images
and packages and came across the following problem:
Some of the ath79 images have a signature attached to the factory images
which is pointless as stock roms wont evaluate those anyway. However, as
these factory i
piled and the signature is (obviously) gone, perfect!
Can't do any runtime tests, but I guess it's good for merging!
Thanks for the quick response!
Paul
Ref: http://lists.infradead.org/pipermail/openwrt-devel/2019-October/019205.html
Reported-by: Paul Spooren
Signed-off-b
images which
contains metadata which are causing image reproducibility issues, so
let's build factory images from the scratch. While at it, refactor the
shared vars into common base as well.
Ref: http://lists.infradead.org/pipermail/openwrt-devel/2019-October/019205.html
Reported-by: Paul Sp
Hi,
On 10/7/19 6:38 PM, Petr Štetiar wrote:
as discussed on IRC, this issue is caused by your custom build step[1] and
doesn't exist in the tree, so the proposed patch can be seen just a workaround
and not proper fix so I've rejected it and not going to apply.
Fine for me if the enhancements men
.
Compiling tested without errors on the following targets:
* ath79
* brcm2708
* brcm63xx
* ixp4xx
* ramips
* sunxi
* x86
CC: Andre Heider
CC: Petr Štetiar
Thanks to Andre for the iremap fixup
Thanks to Petr for his patience on helping which screws to tweak
Signed-off-by: Paul Spooren
---
v3
g in build path independent
reproducible builds.
Signed-off-by: Paul Spooren
---
include/kernel.mk | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/kernel.mk b/include/kernel.mk
index 73645330fe..439e910ebf 100644
--- a/include/kernel.mk
+++ b/include/kernel.mk
@@ -104,6 +104,
Hi team,
there are two recent patches introducing reproducibility of most
packages and firmware images. Applying them to 19.07 would only change
timestamps and shorten debug information (of buildpath), therefore
fairly secure to merge.
Please consider backporting:
4ed356fa71 kernel.mk: add
: Paul Spooren
---
phase1/master.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/phase1/master.cfg b/phase1/master.cfg
index f0151f6..0aaa079 100644
--- a/phase1/master.cfg
+++ b/phase1/master.cfg
@@ -920,7 +920,7 @@ for target in targets:
factory.addStep(ShellCommand
On 9/25/19 3:24 PM, Scott wrote:
‐‐‐ Original Message ‐‐‐
On Tuesday, September 24, 2019 1:13 AM, Paul Spooren wrote:
I think that's a good idea! As it doesn't need to be directly integrated
in any existing workflow nor requires privileges on any Git, it's
basical
This commit changes the behaviour of UUID generation. Instead of using
the rand module of perl, generating a random UUID per compile, it now
hashes the SOURCE_DATE_EPOCH, resulting in a reproducible UUID.
Signed-off-by: Paul Spooren
---
target/linux/x86/image/Makefile | 2 +-
1 file changed, 1
SIGNATURE valuess over multiple build with the same commit.
This is another step in the direction of reproducible OpenWrt images.
Signed-off-by: Paul Spooren
---
I'm currently trying to step up my commit message game, please comment
if the message is unclear or confusing!
include/ima
Thanks for debugging this!
On 11/5/19 1:23 PM, Petr Štetiar wrote:
Commit 881ed09ee6e2 ("build: create JSON files containing image info")
has removed the crucial empty new line from the image copy step
resulting in the following errors during make function expansion:
GZ_SUFFIX :=
bash: GZ_S
) root (0) 33 2019-11-05 23:43:08.00
v_0.0.0.md5
Signed-off-by: Paul Spooren
---
I could not runtime test this, I guessed the changed owner shouldn't be
a problem for the device.
target/linux/ramips/image/mt7620.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
) root (0) 33 2019-11-05 23:43:08.00
v_0.0.0.md5
Signed-off-by: Paul Spooren
---
v2: rename mt7520 to mt7620
target/linux/ramips/image/mt7620.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/ramips/image/mt7620.mk
b/target/linux/ramips/image
Oh thanks, updated...
On 11/5/19 10:01 PM, Bjørn Mork wrote:
subject typo. I was curious about that new chip :-)
Bjørn
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Thank you for reworking this! Daniel already told me that a fallback is
required if SOURCE_DATE_EPOCH is unset, this looks like a clean solution.
On 11/7/19 4:09 AM, Petr Štetiar wrote:
From: Paul Spooren
x86, mvebu and tegra targets are currently using more or less same
SIGNATURE variable
same as for the original
script as the latter does not sort the targets before printing, as the
Python implementation does.
CC: Jo-Philipp Wich
[0]:
https://git.openwrt.org/?p=buildbot.git;a=blob;f=scripts/dumpinfo.pl;h=aa97f8d60379076a41b968402e9337cea824ece5;hb=HEAD
Signed-off-by: Paul
Looks good to me, I ran into this issue before and would appreciate
moving forward to 6.
On 11/11/19 10:16 PM, Petr Štetiar wrote:
Currently minimal GNU supported GCC version is 7 (from May 2, 2017), buildbots
are using default GCC version 6 on Debian 9 (old stable), current Debian
stable 10 ha
buildbot.git contains some hacks to create images that
have signature verification capabilities while not storing private keys
on buildbot slaves. This commit allows to disable these steps for the
buildbots and only perform signing on the master.
Signed-off-by: Paul Spooren
---
v2: fix missing endif if
buildbot.git contains some hacks to create images that
have signature verification capabilities while not storing private keys
on buildbot slaves. This commit allows to disable these steps for the
buildbots and only perform signing on the master.
Signed-off-by: Paul Spooren
---
v3: set "y if !BUI
LGTM
On 11/13/19 10:09 AM, Thomas Weißschuh wrote:
Signed-off-by: Thomas Weißschuh
---
include/prereq-build.mk | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/prereq-build.mk b/include/prereq-build.mk
index 4c59910056..65baf1f5e5 100644
--- a/include/prereq-build.mk
+++ b/inclu
/763e1148f68f03cb2fa85d022500acf8c66af222
Signed-off-by: Paul Spooren
---
Tested and working on Debian 10
https://buildmaster.aparcar.org/#/builders/79/builds/4/steps/64/logs/stdio
scripts/signall.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/signall.sh b/scripts/signall.sh
index 269375f
Bump
On 11/12/19 12:04 AM, Paul Spooren wrote:
This separates the options for signature creation and verification
* SIGNED_PACKAGES create Packages.sig
* SIGNED_IMAGES add ucert signature to created images
* CHECK_SIGNATURE add verification capabilities to images
* INSTALL_LOCAL_KEY add local
Hi Yousong,
A few months ago, I started working on bringing up k3s on OpenWrt. I
managed to have a small k8s cluster with nodes running centos and
openwrt. Likely other linux distros will also do, but I didn't test
combination of different architectures yet.
Cool! That looks like an interestin
verification capabilities while not storing private keys
on buildbot slaves. This commit allows to disable these steps for the
buildbots and only perform signing on the master.
Signed-off-by: Paul Spooren
---
v4: replace ifdef with ifneq - Makefile magic
-ifdef CONFIG_SIGNED_PACKAGES
+ifneq
+1
11 Dec 2019 15:22:44 Daniel Golle :
> Hi Tomislav,
>
> On Wed, Dec 11, 2019 at 11:24:21AM +0100, Tom Psyborg wrote:
>
> > suck it
> >
>
> As a community, we decided to give our self a set of minimal rules[1].
> And even though it is in the last position, rule #12 "Be nice to each
> ot
Hi all,
some time ago I created a (now outdated) device overview[0] based on
YAML meta data. This approach could simplify maintaining an device
overview and device specific pages[1].
All commits adding new devices already include most relevant information
for creating the overview. However i
Hi,
On 1/12/20 1:05 PM, Martin Blumenstingl wrote:
Hi Paul,
On Sun, Jan 12, 2020 at 10:47 PM Paul Spooren wrote:
Hi all,
some time ago I created a (now outdated) device overview[0] based on
YAML meta data. This approach could simplify maintaining an device
overview and device specific pages
st,
Paul
On 1/13/20 3:03 AM, Thomas Endt wrote:
-Ursprüngliche Nachricht-
Von: openwrt-devel Im
Auftrag von Paul Spooren
Gesendet: Sonntag, 12. Januar 2020 22:47
An: 'OpenWrt Development List'
Betreff: [OpenWrt-Devel] [RFC] commit message in YAML format for new
devices
An illus
Hi,
I added a device pages project idea. That could come in handy with the
page refresh and all. Also I'm trying to setup a devices.git repository
storing all relevant metadata. That could be an additional project or I
just do it on my own and leave the rendering to a student.
Best,
Paul
On
On 4/19/21 9:45 AM, Hauke Mehrtens wrote:
Since OpenWrt 21.02 we use https for our download server, detect these
URLs too.
Signed-off-by: Hauke Mehrtens
---
Can't you kick out anything lede-project related while at it?
To use the https URLs I have to provide the URL manually now:
./maketag
On 4/24/21 1:01 AM, Gaurav Pathak wrote:
Modified inittab.c to use "/dev/console" as preferred console if exists.
Signed-off-by: Gaurav Pathak
---
Could you please elaborate why this is useful?
Edited inittab.c to check and use "/dev/console" as the first
console device before parsing "/s
Apr 25, 2021 8:34:06 AM Gaurav Pathak :
inittab.c: Use "/dev/console" character device (5,1) if it
is present, before trying "/sys/class/tty/console/active" in
case if console kernel command line is not provided during boot
and to allow container environment to use it as login PTY console.
Sig
On 4/20/21 1:08 AM, Bas Mevissen wrote:
OpenWRT requires a number of Perl modules to be installed. It wasn't checking
on all of them.
This patch adds checks for Perl FindBin, File::Copy, File::Compare and
Thread::Queue modules.
Failing to install these, will have the build break at some poin
On 5/4/21 3:23 PM, Daniel Danzberger wrote:
When a UCI fstab mount config doesn't contain a target option,
a 'block mount' call segfaults when comparing a mount's target (NULL)
to a found mount point returned by find_mount_point()
Signed-off-by: Daniel Danzberger
---
Ac
On 5/4/21 5:28 PM, e...@daloft.com wrote:
From: eric
---
Hi Eric,
thank you very much for your contribution!
Please read the following guide, there are some formal issues with this
patch:
https://openwrt.org/submitting-patches
Patches should always include the full and real name of th
ly.
References:
https://lists.infradead.org/pipermail/openwrt-devel/2021-May/035056.html
Acked-by: Hauke Mehrtens
Signed-off-by: Petr Štetiar
---
Acked-by: Paul Spooren
inventories/prod/group_vars/all/02-openwrt-prod.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/inventories/prod/gr
Hi,
On 5/13/21 1:32 AM, Hauke Mehrtens wrote:
Instead of adding all public signature keys from the openwrt-keyring
repository only add the key which is used to sign the master feeds.
If one of the other keys would be compromised this would not affect
users of master snapshot builds.
Signed-off
would not affect
users of 19.07 release builds.
Signed-off-by: Hauke Mehrtens
---
Acked-by: Paul Spooren
package/system/openwrt-keyring/Makefile | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/package/system/openwrt-keyring/Makefile
b/package/system/openwrt-keyring
On 5/16/21 6:01 PM, Robert Marko wrote:
Update ethtool to newly released 5.12 version.
Signed-off-by: Robert Marko
---
Could this be moved to packages.git?
package/network/utils/ethtool/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/network/utils
Hello,
after some back and forth I'd like to request some more opinions on what
kind of Docker containers to offer containing the OpenWrt rootfs. This
is not about the SDK or ImageBuilder Docker containers.
tl;dr:
Should we ship `slim` containers only, running a OpenWrt shell (ash) and
noth
May 17, 2021 21:53:01 Hauke Mehrtens :
On 5/17/21 8:10 PM, Paul Spooren wrote:
On 5/16/21 3:57 PM, Hauke Mehrtens wrote:
On 5/16/21 3:26 PM, Hauke Mehrtens wrote:
Instead of adding all public signature keys from the openwrt-keyring
repository only add the key which is used to sign the
use AUTORELEASE since BusyBox is often updaten and PKG_RELEASE is not
consistently bumped. Also use SPDX license headers to be machine
readable and bump the copyright year to 2021.
Signed-off-by: Paul Spooren
---
I'd like to see this backported as well.
package/utils/busybox/Makefil
On 17/05/2021 15:39, Paul Spooren wrote:
Hello,
after some back and forth I'd like to request some more opinions on
what kind of Docker containers to offer containing the OpenWrt
rootfs. This is not about the SDK or ImageBuilder Docker containers.
tl;dr:
Should we ship `slim` containers only
Hi,
On 5/18/21 11:52 PM, Philip Prindeville wrote:
Hi all,
I noticed that there are several AX routers from TP-Link, Netgear, D-Link, etc.
and some of them have even had OpenWRT ported to them.
Which of these various platforms has the most CPU/RAM/FLASH? A few are discussed, but I'm
not seei
The SRV was added some time ago and should be mentioned in the short
help message to avoid confusion about missing features.
Signed-off-by: Paul Spooren
---
Already sent to upstream:
http://lists.busybox.net/pipermail/busybox/2021-May/088849.html
.../540-nslookup-mention-QUERY_TYPE-SRV.patch
These two variables where missing in the definition of
DEFAULT_DEVICE_VARS which caused them to contain wrong values, messing
up the resuling JSON files.
This patch add the two variables IMAGE_PREFIX and DEFAULT_PACKAGES to
DEFAULT_DEVICE_VARS.
Suggested-by: Baptiste Jonglez
Signed-off-by: Paul
The variable was missing in the definition of DEFAULT_DEVICE_VARS which
caused it to contain wrong values, messing up the resulting JSON files.
This patch adds the variable DEVICE_PACKAGES to DEFAULT_DEVICE_VARS.
Suggested-by: Baptiste Jonglez
Signed-off-by: Paul Spooren
---
include/image.mk
These two variables were missing in the definition of
DEFAULT_DEVICE_VARS which caused them to contain wrong values, messing
up the resulting JSON files.
This patch adds the two variables IMAGE_PREFIX and DEVICE_PACKAGES to
DEFAULT_DEVICE_VARS.
Suggested-by: Baptiste Jonglez
Signed-off-by: Paul
Sounds good to me. Do you mind investigate what other packages are affected
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ImageBuilder which always create the file and also increases the files
visibility for downstream projects.
Signed-off-by: Paul Spooren
---
config/Config-build.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config/Config-build.in b/config/Config-build.in
index 342859b7c0..f0e1aaa695
On 6/20/21 6:56 AM, Adrian Schmutzler wrote:
sysupgrade metadata is not flashed to the device, so check-size
should be called _before_ adding metadata to the image.
While at it, do some obvious wrapping improvements.
Signed-off-by: Adrian Schmutzler
---
Acked-by: Paul Spooren
I&#
The `squashfs-tools-ng` is a reimplementation of `squashfs-tools` of
which a fork called `squashfskit` is currently used withn OpenWrt.
Signed-off-by: Paul Spooren
---
tools/squashfs-tools-ng/Makefile | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 tools
github.com/squashfskit/squashfskit
[3]: https://github.com/AgentD/squashfs-tools-ng
Paul Spooren (3):
squashfs-tools-ng: add package
build,squashfs: switch to squashfs-tools-ng
squashfskit4: Remove obsolete package
include/image.mk | 23 +++---
tool
Let the newly added `squasfs-tools-ng` handle the squashfs file
creation.
Signed-off-by: Paul Spooren
---
include/image.mk | 23 ---
tools/Makefile | 6 +++---
2 files changed, 19 insertions(+), 10 deletions(-)
diff --git a/include/image.mk b/include/image.mk
index
With the introduction of `squashfs-tools-ng` the `squashfskit4` fork is
no longer required.
Signed-off-by: Paul Spooren
---
tools/squashfskit4/Makefile | 41 --
.../patches/0001-fix-version.sh.patch | 21 -
...002-fix-build-failure-against-gcc
Not sure but is this PR related?
"base-files: bring up vlan interface too #2734"
https://github.com/openwrt/openwrt/pull/2734
On 6/19/21 8:36 AM, Hauke Mehrtens wrote:
Adapt the preinit_config_board() to the board.json network changes. It
now looks for the device and the ports variables to con
Rather than maintaining it in core, move it to packages.git where it's
maintained by a community.
CC: Jo-Philipp Wich
Signed-off-by: Paul Spooren
---
A new maintainer stepped up and like to take over the work over at
packages.git, see https://github.com/openwrt/packages/pull/15939
pa
Hi,
if I'm not mistaken this patch doesn't quite do the trick: You removed
the removal of /tmp/TZ which seem to be preferred by `hwclock`, meaning
even if $zonename (aka $zname) is found, /tmp/TZ is still there. As a
result both /tmp/TZ and /tmp/localtime exists both, allowing the user no
lon
On 6/23/21 1:14 PM, Rosen Penev wrote:
On Wed, Jun 23, 2021 at 3:40 PM Paul Spooren wrote:
Hi,
if I'm not mistaken this patch doesn't quite do the trick: You removed
the removal of /tmp/TZ which seem to be preferred by `hwclock`, meaning
even if $zonename (aka $zname) is found,
Hi,
On 6/21/21 9:54 PM, Rui Salvaterra wrote:
Instead of assuming /sbin contains the correct BusyBox symlinks, directly invoke
the busybox executable. The required utilities are guaranteed to be present,
since the zram-swap package selects them. Additionally, don't assume busybox
resides in /bin
On 6/28/21 8:53 AM, Piotr Dymacz wrote:
Hi John,
On 28.06.2021 20:32, John Crispin wrote:
On 28.06.21 19:26, Piotr Dymacz wrote:
I might be wrong here but I think we don't include packages from
external feeds inside 'DEVICE_PACKAGES' (not sure/don't remember why).
I am in favour of movin
On 6/28/21 9:53 AM, John Crispin wrote:
On 28.06.21 21:14, Paul Spooren wrote:
I'm in favor of this too but if it's a core feature (i.e. SIM card
support) we should provide the package by default to, not?
this should be explained in the wiki,
Agree, APU boards etc also need
On 6/29/21 3:22 PM, Daniel Golle wrote:
As x86/64 and x86/generic may be using UEFI, mounting the FAT-32 /boot
is necessary in order not to loose configuration files accross
sysupgrades. Include kmod-fs-vfat by default to make sure /boot can
always be mounted.
Signed-off-by: Daniel Golle
---
On 7/1/21 3:09 AM, Petr Štetiar wrote:
From: Hannu Nyman
Mark uci, ubus, libubox, lua, libnl-tiny and libjson-c
as nonshared packages. This helps to keep coherent dependencies
if these ABI versioned packages are later updated.
Before this commit it is possible to get missing dependencies
in t
On 7/1/21 9:50 AM, Arjun AK wrote:
Signed-off-by: Arjun AK
---
Could you please add a brief commit message describing why this package
isn't needed in core?
I'm all for moving it, don't get me wrong, we just try to have commit
messages everywhere to keep context over time.
package/n
On 7/1/21 9:51 AM, Petr Štetiar wrote:
Paul Spooren [2021-07-01 07:45:02]:
+++ b/package/libs/libjson-c/Makefile
@@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk
PKG_NAME:=json-c
PKG_VERSION:=0.12.1
-PKG_RELEASE:=3.1
+PKG_RELEASE:=3.2
I've never seen a non integer release, is th
On 7/5/21 8:45 PM, Enrico Mioso wrote:
Hello all!!
I would like to know your opinion on a topic I know has already been
discussed: enabling Wi-Fi on first boot.
I would very very much like to see this feature present in OpenWRt:
because I find myself in a scenario where plugging an Ethernet
On 7/5/21 8:45 PM, Enrico Mioso wrote:
Hello all!!
I would like to know your opinion on a topic I know has already been
discussed: enabling Wi-Fi on first boot.
I would very very much like to see this feature present in OpenWRt:
because I find myself in a scenario where plugging an Ethernet
I'd argue that it merely completes the OEM options. If that isn't a valid
argument we should drop all of VERSIONOPTs since it can be all modified
via /files.
--
Jul 7, 2021 21:39:59 Petr Štetiar :
Paul Spooren [2021-07-07 15:10:59]:
Hi,
Feel free to check this out, it'
On 7/24/21 8:08 PM, Hauke Mehrtens wrote:
On 7/16/21 12:44 AM, Sven Roederer wrote:
* SSH agent forwarding might cause security issues, locally and on
the jump
machine (https://defn.io/2019/04/12/ssh-forwarding/). So allow to
completely disabling it.
* separate options for client and ser
Signed-off-by: Paul Spooren
---
docker/buildmaster/Dockerfile | 2 +-
docker/buildworker/Dockerfile | 12 ++--
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/docker/buildmaster/Dockerfile b/docker/buildmaster/Dockerfile
index 28dc9ed..b2134ce 100644
--- a/docker
x86 targets allow the creation of ISO images, however this is not
possible because the `mkisofs` is missing. Install it.
Signed-off-by: Paul Spooren
---
docker/buildworker/Dockerfile | 1 +
1 file changed, 1 insertion(+)
diff --git a/docker/buildworker/Dockerfile b/docker/buildworker
See changelog:
https://github.com/buildbot/buildbot/releases/tag/v3.3.0
Signed-off-by: Paul Spooren
---
.gitlab-ci.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 07a0407..5b6f6eb 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
These images are of interested for some cloud/VM people, build them by
default when running the buildbot.
Signed-off-by: Paul Spooren
---
config/Config-images.in | 3 +++
1 file changed, 3 insertions(+)
diff --git a/config/Config-images.in b/config/Config-images.in
index 92720fb84d..ea50d7d399
Seems to be working fine in Docker containers.
Signed-off-by: Paul Spooren
---
target/linux/x86/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/x86/Makefile b/target/linux/x86/Makefile
index 0ab322d8bc..14cfba777c 100644
--- a/target/linux/x86/Makefile
On 9/7/21 11:31, Rui Salvaterra wrote:
Hi, Daniel,
On Tue, 7 Sept 2021 at 22:09, Daniel Golle wrote:
I'd remove the KERNEL_TESTING_PATCHVER line then until we add 5.14 or
whatever it's going to be.
Sure, I didn't know what the usual procedure was, so I just mimicked aparcar. ;)
V2 coming up
Seems to be working fine in Docker containers.
Signed-off-by: Paul Spooren
---
v2: Remove redundant TESTING_PATCHVER
target/linux/x86/Makefile | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/target/linux/x86/Makefile b/target/linux/x86/Makefile
index 0ab322d8bc
On 9/7/21 11:39, Paul Spooren wrote:
Seems to be working fine in Docker containers.
Signed-off-by: Paul Spooren
---
Of course I mean QEMU not Docker (which uses the host Kernel)
v2: Remove redundant TESTING_PATCHVER
target/linux/x86/Makefile | 3 +--
1 file changed, 1 insertion(+), 2
On 9/8/21 02:50, Florian Eckert wrote:
The file `/etc/os-release` is currently a relative link to
`../usr/lib/os-release`.
The follwing links on my `/etc` are also absolute:
* localtime -> /tmp/localtime
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this sho
partly the same files.
Signed-off-by: Paul Spooren
---
package/base-files/Makefile | 42 ++---
1 file changed, 21 insertions(+), 21 deletions(-)
diff --git a/package/base-files/Makefile b/package/base-files/Makefile
index 58ad08c63a..af5c0e6b00 100644
--- a/package
On 9/9/21 19:53, Florian Eckert wrote:
* resolv.conf -> /tmp/resolv.conf
* /tmp/TZmtab -> /proc/mounts
For consistency, this should also apply to `/usr/lib/os-release`.
Is there any other reason than consistency to change this?
Yes, I have to elaborate on that.
I have a small script that b
The *Firmware Selector* was build to simplify users finding suitable
images for their devices. Let's give it more visibility so unleashing
your home router becomes an easier thing.
Signed-off-by: Paul Spooren
---
This is a cross post[1] but since it's quite a public change I want it
to
The `sed`-script shouldn't be called multiple times, especially not with
the same files.
This commit merges all files together in a single `sed`-script call.
Signed-off-by: Paul Spooren
---
package/base-files/Makefile | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --
`/etc/` explicitly after subfolders of `/etc/` were
already created.
Signed-off-by: Paul Spooren
---
package/base-files/Makefile | 36 +++-
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/package/base-files/Makefile b/package/base-files/Makefile
On 1/12/21 12:05, Sven Roederer wrote:
Am Dienstag, 12. Januar 2021, 13:01:45 CET schrieb Adrian Schmutzler:
Hello,
You don't have to run such complicated script. Just restore /etc/rc.d/
directory after upgrade.
Well, that depends on how we want to deal with new services. If I upgrade
from 19.0
On 9/30/21 10:01, Nick wrote:
On 9/30/21 21:43, Daniel Golle wrote:
On Thu, Sep 30, 2021 at 09:18:06PM +0300, Stijn Tintel wrote:
On 30/09/2021 01:19, Nick wrote:
On 9/29/21 22:28, Hauke Mehrtens wrote:
kernel 5.10:
We should get all targets to kernel 5.10. All targets which are not
on ke
Hi all,
based on my overview[1] things are moving forward and being tested,
great! What about the targets that did not see any 5.10 ambitions yet?
Specifically:
- arc770
- archs38
- ath25
- bcm47xx
- bcm4908
- ipq807x
- layerscape
- pistachio
- uml
Is anyone aware of people working on those
> On 5. Oct 2021, at 12:33, Robert Marko wrote:
>
> On Wed, 6 Oct 2021 at 00:08, Paul Spooren wrote:
>>
>> Hi all,
>>
>> based on my overview[1] things are moving forward and being tested,
>> great! What about the targets that did not see
On 9/29/21 10:28, Hauke Mehrtens wrote:
Hi,
The OpenWrt 21.02 release is done and we should plan the next release.
We already talked about this in the last meeting, see
https://openwrt.org/meetings/20210920
To monitor the current state I created this wiki page based on the
wiki page from t
Hi,
as previously posted on GitHub[1] I'd like to remove the UML target
since it seems broken, isn't offered by our buildbots and it's purpose
for testing can be replaced by using qemu.
Is anyone here actively using UML and would like to keep it?
Best,
Paul
[1]: https://github.com/openwrt/o
On 10/7/21 8:31 AM, Hauke Mehrtens wrote:
On 10/7/21 8:51 AM, Paul Spooren wrote:
On 9/29/21 10:28, Hauke Mehrtens wrote:
Hi,
The OpenWrt 21.02 release is done and we should plan the next release.
We already talked about this in the last meeting, see
https://openwrt.org/meetings/20210920
Hi,
--- %< ---
based on my overview[1] things are moving forward and being tested,
great! What about the targets that did not see any 5.10 ambitions
yet?
Specifically:
- arc770
- archs38
I just got an email from synopsys and they'll contribute Kernel 5.10
patches for
On 10/8/21 5:54 AM, Sergey Ryazanov wrote:
Hello Paul,
thank you for posting this to ML.
On Fri, Oct 8, 2021 at 12:05 PM Paul Spooren wrote:
as previously posted on GitHub[1] I'd like to remove the UML target
since it seems broken, isn't offered by our buildbots and it
On 10/9/21 9:57 PM, Russell Senior wrote:
"Sergey" == Sergey Ryazanov writes:
Sergey> I am in the process of migrating ath25 to the 5.10
Sergey> kernel. Initial build was trivial. But I need to restore the
Sergey> Marvel swconfig driver that was lost during the initial 5.10
Sergey> kernel int
On 10/5/21 12:32 PM, camden lindsay wrote:
Is - ipq807x a typo? i don't see this target in the snapshots... is
it really ipq806x?
many thanks
On Tue, Oct 5, 2021 at 3:14 PM Paul Spooren <mailto:m...@aparcar.org>> wrote:
Hi all,
based on my overview[1] things are
Hi Martin,
On 10/19/21 7:26 PM, Martin Schiller wrote:
On 2021-10-20 04:47, Paul Spooren wrote:
For now layerscape is still on 5.4 without Kernel 5.10 support. Is
anyone planing to add support? Please reach out.
As I had already written on 08 October, I am already working on it.
Thereby I
Hi all,
Hauke an me plan to tag 21.02.1 this Friday.
Motivation is the recent breakage (and fix) of HTTPS secured by Let's
Encrypt certificates.
More information is available in the commit message[0] of the fix.
Please post your backport requests here so we can determine what's
possible to i
201 - 300 of 596 matches
Mail list logo
