Hi Paul,
Following our brief discussion on IRC, here are my remarks again, so
others can also comment on them. I'm still pretty new to this packaging
stuff, so some arguments may already have been made in the past.
On Fri, 2020-08-07 at 12:32 -1000, Paul Spooren wrote:
> Hi team,
>
> currently e
Op 24 feb. 2020, om 17:08 heeft Adrian Schmutzler
het volgende geschreven:
>
> In the package guidelines, PKG_VERSION is supposed to be used
> as "The upstream version number that we're downloading", while
> PKG_RELEASE is referred to as "The version of this package Makefile".
> Thus, the variab
On Mon, Aug 03, 2020 at 07:11:13PM +0300, Etienne Champetier wrote:
> Le lun. 3 août 2020 à 00:04, Rosen Penev a écrit :
>> The remerged OpenWrt project is legally represented by the Software
>> in the Public Interest (SPI) - an US 501(c)(3) non-profit
>> organization which is managing our OpenWrt
On 09/08/2020 03:35, Henrique de Moraes Holschuh wrote:
On 08/08/2020 17:56, Rosen Penev wrote:
On Sat, Aug 8, 2020 at 1:37 PM Mauro Mozzarelli
wrote:
Since OpenWrt is NOT US Based and in fact it appears to be mostly
supported with EU contributions, we should be following the more
liberal
Mauro Mozzarelli writes:
> On 09/08/2020 03:35, Henrique de Moraes Holschuh wrote:
>
>> I believe OpenWrt should not even *consider* placing its umbrella
>> organization(s) -- which are based on the U.S. -- in legal risk
>> without at least contacting them first and getting their approval.
>>
>> H
On Fri, Aug 07, 2020 at 02:57:54PM -1000, Paul Spooren wrote:
> On 07.08.20 09:47, Daniel Golle wrote:
> > Dear community,
> >
> > in the past couple of months I've been working on implementing the
> > Open Container Initiative Runtime Specification [1] in procd by
> > extending the already existi
On Sun, Aug 09, 2020 at 10:55:37AM +0100, Sam Kuper wrote:
> On Mon, Aug 03, 2020 at 07:11:13PM +0300, Etienne Champetier wrote:
>> Le lun. 3 août 2020 à 00:04, Rosen Penev a écrit :
>>> Whenever discussion about patents arise, I usually point to Fedora
>>> whose parent company is Red Hat, which is
There was a typo in the patch which breaks compiling binutils on
MIPS63EL.
make[7]: *** No rule to make target 'elf64ltsmip.o', needed by 'ld-new'. Stop.
Fixes: FS#3276
Fixes: 53470bdf3212 ("toolchain/binutils: Add binutils 2.34")
Signed-off-by: Hauke Mehrtens
---
.../2.34/500-Change-default-em
readelf is linked against this library on MIPS64BE
This fixes a build problem on MIPS64BE.
In addition also explicitly activate it in the configure command.
Fixes: 60f595daab45 ("binutils: update to version 2.34")
Signed-off-by: Hauke Mehrtens
---
package/devel/binutils/Makefile | 5 +++--
1 fi
It is deactivated everywhere, just set this in the generic config.
Signed-off-by: Hauke Mehrtens
---
target/linux/armvirt/64/config-5.4 | 1 -
target/linux/bcm27xx/bcm2710/config-5.4 | 1 -
target/linux/bcm27xx/bcm2711/config-5.4 | 1 -
target/linux/generic/config-5.4
This refreshes the kernel configuration on top of kernel 5.4.
It now builds without asking to select some kernel options on all 4
subtargets.
It still does not boot up, there is a different problem.
Signed-off-by: Hauke Mehrtens
---
target/linux/malta/be/config-default | 8
target/lin
Hi,
please keep the current configuration. The Subject header ist typcially
configured to be included in dkim signatures.
Therefore mangling the subject breaks the signature, which might lead to
rejected mails or higher spam scores.
Best regards,
Fabian
On 09.08.20 02:36, Brian Norris wrote:
>
On Sun, Aug 9, 2020 at 6:09 AM Sam Kuper wrote:
>
> On Sun, Aug 09, 2020 at 10:55:37AM +0100, Sam Kuper wrote:
> > On Mon, Aug 03, 2020 at 07:11:13PM +0300, Etienne Champetier wrote:
> >> Le lun. 3 août 2020 à 00:04, Rosen Penev a écrit :
> >>> Whenever discussion about patents arise, I usually po
Branch: refs/heads/master
Home: https://github.com/sdwalker/sdwalker.github.io
Commit: f5a1c4a53482e1c68a2b73c049d723df1a786a40
https://github.com/sdwalker/sdwalker.github.io/commit/f5a1c4a53482e1c68a2b73c049d723df1a786a40
Author: Stephen Walker
Date: 2020-08-09 (Sun, 09 Aug 2
On 07.08.20 20:18, Felix Fietkau wrote:
On 2020-08-07 23:12, Paul Spooren wrote:
From: Thomas Petazzoni
SELinux support requires setting the appropriate SELinux security context
to files and directories, which needs to happen at build time in order
to support read-only root filesystem scenar
On 07.08.20 11:13, Paul Spooren wrote:
Instead of INSTALL_SUID the PKG_FILE_MODES variable should be used
Signed-off-by: Paul Spooren
---
rules.mk | 1 -
1 file changed, 1 deletion(-)
diff --git a/rules.mk b/rules.mk
index 45d96d6be4..d535e57266 100644
--- a/rules.mk
+++ b/rules.mk
@@ -281
On 8/08/2020 01:54, Paul Spooren wrote:
> Fix shellcheck SC2230
>> which is non-standard. Use builtin 'command -v' instead.
> Once applied to everything concerning OpenWrt we can disable the busybox
> feature `which` and save 3.8kB.
Maybe mention `command -v` is POSIX compliant, and `which` is not
On Sun, Aug 9, 2020 at 4:33 PM Stijn Tintel wrote:
>
> On 8/08/2020 01:54, Paul Spooren wrote:
> > Fix shellcheck SC2230
> >> which is non-standard. Use builtin 'command -v' instead.
> > Once applied to everything concerning OpenWrt we can disable the busybox
> > feature `which` and save 3.8kB.
>
The `which` command returns the first found path to a binary specified.
It's behaviour is identical to the shell built in `command -v`.
Shellcheck even prints a warning if `which` is used (SC2230).
Once neither `openwrt.git` nor related repositories make use of `which`,
the command should be disab
From: Thomas Petazzoni
In order to support SELinux in OpenWrt, this commit introduces minimal
support for loading the SELinux policy in the init code. The logic is
very much inspired from what Busybox is doing: call
selinux_init_load_policy() from libselinux, and then re-execute init
so that it r
Fix shellcheck SC2230
> which is non-standard. Use builtin 'command -v' instead.
Using `command -v` is POSIX compliant while `which` is not. Also to
mention, `command -v` is a shell builtin whereas `which` is a separate
busybox applet.
Once applied to everything concerning OpenWrt we can disable
[...]
> This is part of a bigger PR on GitHub[1], however this patch should be
> added directly to `procd` rather than as a patch in openwrt.git.
[...]
I will update the GitHub pull request once this is merged. Thank you,
Paul!
--
Mike
:wq
___
open
On Mon, 10 Aug 2020 at 00:17, Hauke Mehrtens wrote:
>
> It is deactivated everywhere, just set this in the generic config.
>
> Signed-off-by: Hauke Mehrtens
Acked-by: Yousong Zhou
Regards,
yousong
___
openwrt-devel mailing list
openw
On Mon, 10 Aug 2020 at 00:17, Hauke Mehrtens wrote:
>
> This refreshes the kernel configuration on top of kernel 5.4.
> It now builds without asking to select some kernel options on all 4
> subtargets.
> It still does not boot up, there is a different problem.
malta/be boots fine with this applie
On Mon, 10 Aug 2020 at 00:01, Hauke Mehrtens wrote:
>
> There was a typo in the patch which breaks compiling binutils on
> MIPS63EL.
> make[7]: *** No rule to make target 'elf64ltsmip.o', needed by 'ld-new'.
> Stop.
>
> Fixes: FS#3276
> Fixes: 53470bdf3212 ("toolchain/binutils: Add binutils 2.34
Hi,
On 08.08.20 22:40, Sander Vanheule wrote:
Hi Paul,
Following our brief discussion on IRC, here are my remarks again, so
others can also comment on them. I'm still pretty new to this packaging
stuff, so some arguments may already have been made in the past.
On Fri, 2020-08-07 at 12:32 -1000
From: "W. Michael Petullo"
Building the binutils package produced the following error:
Package binutils is missing dependencies for the following libraries:
libctf-nobfd.so.0
This changes the glob for the libctf subpackage so that it catches
libctf-nobfd.so.0.
Signed-off-by: W. Michael Petullo
27 matches
Mail list logo
