From Sertonix to ~sircmpwn/alpine-devel
On Tue Mar 18, 2025 at 9:59 PM CET, Jim Pryor wrote: > I'm building some binaries on an ARMv7 build of Alpine, and getting errors about the symbol `__stack_chk_fail` being missing. > > Adding `-fno-stack-protector` to my build command solves the issue. > > But I wonder if there's a way to get stack protection? I notice that when I do `nm -D /usr/lib/libc.so | grep __stack_chk_fail` I get the output: > > ``` > 0003cc48 T __stack_chk_fail > ``` > > So the symbol is there, just not getting linked. > > I tried adding each of these to my build command, but none of them seemed to fix the issue (that is, let me build without disabling stack protection):
From Sertonix to ~sircmpwn/alpine-devel
On Fri Mar 14, 2025 at 9:31 PM CET, Jim Pryor wrote: > I have an issue where `apk` can't see a local repository. I have an > unprivileged user who created some packages, created an APKINDEX file and > signed the index. That user's public key is installed in `/etc/apk/keys`. > The unprivileged user and root both belong to the `abuild` group. As best I > can tell, the permissions on the repository, index, and package files look > correct. But when I do `apk update` I get a message that the > repository `/var/lib/packages` can't be found. Any ideas? > > > main0:~# ls -l /var/lib/packages/ > > total 532 >
From Sertonix to ~ser/claptrap
> Hi! > > On Fri Dec 13, 2024 at 4:06 AM CST, Sertonix wrote: > > The order of commands in the rook manpage is shuffled around each time > > them manpage is generated. Sort them so the output is stable and commands > > are easier to find with the alphabeth. > > Thanks for this; it's been applied and pushed as v2.4.4. > > The patch was perfect. It got committed with me as the author, and I wasn't sure if you wanted your full email in the commit message, so I credited you as "sertonix". Thanks for the quick merge! Full email would have been fine aswell. > --- SER
From Sertonix to ~ser/claptrap
The order of commands in the rook manpage is shuffled around each time them manpage is generated. Sort them so the output is stable and commands are easier to find with the alphabeth. (I don't know how Mercurial works so I hope this patch format is ok) --- a/cmd/makeclapman/main.go +++ b/cmd/makeclapman/main.go @@ -83,6 +83,7 @@ } //claptrap.HelpTemplate = ManTempl allCommands := getAllCommands(ct.RootCommand, []string{}, []string{}) + sort.Strings(allCommands) writeOut(cmds.String("out-dir"), []string{}, ct.RootCommand, additional, allCommands, cmds.String("date"), cmds.String("version"))
From Sertonix to ~rjarry/aerc-discuss
Hi, When I reply to a mail that I wrote myself to someone else I noticed that aerc adds my own mail to the To header. Additionally when using multiple aliases aerc uses my default mail for the From header instead of the alias I write my previous mail with. Would it be possible to change that so aerc doesn't include my own mail in the To header and uses the alias in the From header? Thanks!
From Sertonix to ~mcf/cproc
> > In 4f206ac1ea (Implement variable length arrays) arrays with the length 0 > > were considered to be variable length arrays. This may not be true and > > caused cproc to segfault when parsing for example sizeof(int[0]). Using > > t->prop & PROPVM as check for variable length arrays should always work > > correctly. > > Thanks for the patch! > > However, the distinction between variably modified type and variably > length array is important here. > > Consider this example: > > #include <stdio.h>
From Sertonix to ~mcf/cproc
In 4f206ac1ea (Implement variable length arrays) arrays with the length 0 were considered to be variable length arrays. This may not be true and caused cproc to segfault when parsing for example sizeof(int[0]). Using t->prop & PROPVM as check for variable length arrays should always work correctly. --- expr.c | 2 +- init.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/expr.c b/expr.c index aef6fe9..ee570b4 100644 [message trimmed]
From Sertonix to ~kennylevinsen/seatd-devel
> This is dangerous when seatd is suid-root, I believe.
Where do people actually set seatd to to suid-root?! That sounds dangerous
even without this patch.
From Sertonix to ~kennylevinsen/seatd-devel
This makes it for example possible to move the socket into a directory that seatd can write to when seatd is not run as root. --- man/seatd.1.scd | 5 +++-- seatd-launch/seatd-launch.c | 2 +- seatd/seatd.c | 21 +++++++++++++-------- 3 files changed, 17 insertions(+), 11 deletions(-) diff --git a/man/seatd.1.scd b/man/seatd.1.scd index 92f8e4b..4663153 100644 --- a/man/seatd.1.scd +++ b/man/seatd.1.scd @@ -28,6 +28,9 @@ seatd - A seat management daemon [message trimmed]
From Sertonix to ~lattis/muon
> Hey, > > Sorry for not replying to this for quite awhile. I think it is okay for > muon to support `muon meson compile`, but I don't like the modification > of `muon samu`. I think `muon meson compile` should point to its own > subcommand, perhaps `muon internal meson-compile`, that simply calls > ninja. Sounds reasonable. The change was a bit of a hack. Unfortunatly I currently don't have time to change the patch. Feel free to change the patch if you want. Otherwise I may finish it some day. > Thanks, > Stone