[packager@rpm-builder etc]$ env | grep PATH
PATH=/home/packager/.local/bin:/home/packager/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
I guess /user/local/bin or /usr/local/sbin is our first choice? Do we need
--enable-pedantic-posix for /usr/local/bin or /usr/local/sbin?
And yes, since execline-provided cd, umask and wait, when called via a
PATH search (not that a shell will ever do that, but execvp() can), will
substitute themselves to Fedora-provided POSIX binaries, it is necessary
to build execline with --enable-pedantic-posix in order to prevent
trouble
After check the installed package of execline on alpine. I choose to
install main part of execline to /usr/bin.
Create /usr/sbin directory, create relative symbol link for cd, umask
and wait to /usr/bin/execline.
Does that mean you're using --enable-multicall? You can, it's just
RHEL and Fedora have an alternatives system:
* https://docs.fedoraproject.org/en-US/packaging-guidelines/Alternatives/
* https://www.linux.org/docs/man8/alternatives.html
Then it looks like the correct way to proceed, if Eric can coordinate
with
the maintainers of the filesystem and bash
file /usr/bin from install of execline-2.9.4.0-1.fc39.x86_64 conflicts
with file from package filesystem-3.18-6.fc39.x86_64
file /usr/bin/cd from install of execline-2.9.4.0-1.fc39.x86_64
conflicts with file from package bash-5.2.26-1.fc39.x86_64
file /usr/bin/umask from
In my (admittedly ugly) package, I simply delete execline's `cd' and
`umask'; `wait' is renamed to `execline-wait', just like `execline-cd'
and `execline-umask' (which are not conflicting and so not deleted).
This means that your execline package cannot run execline scripts that
use cd, umask
Yes, skalibs, execline are different projects. The GitHub site is just a
central and temporary place to hold the spec files.
For skalibs project, I build 4 rpm packages: skalibs, skalibs-devel,
skalibs-devel-static, skalibs-doc.
skalibs-devel depends on skalibs. Just follow the aports
I haven't looked in detail, but I'm not sure why you want everything
in one single RPM.
skalibs, utmps, execline and s6 are different projects. A package
should
be one project, not a set of projects. A package manager will handle
dependencies between packages and install all the rpms that
One last question: do we need the s6-openrc rpm package? I know systemd is more
popular for Redhat and Fedora. Any suggestion?
I doubt anyone is going to run openrc on Fedora. If you're going to
package
s6 for a given distribution, you should integrate it properly with that
distribution,
Hi Wang,
Your e-mail client seems to be broken. It sends HTML entities as
text/plain,
and it makes the content of your mail unreadable. Please fix this, if
you can.
From what I can understand, you're looking for rpm packages for skalibs
and utmps. I don't know if there are any; I
my first question is: does skalibs support glibc? alpine only support
musl.
Yes. skalibs supports everything that makes a good attempt to be
POSIX-conformant, so that includes glibc.
--
Laurent
I notice s6-svscanboot is the start script for s6-svscan. I am not an execline
expert, but I can see that s6-svscanboot prepare log directories and start
s6-svscan. If systemd provides log service for s6-svscan. Do we need
s6-svscanboot for rpm package?
No, you don't.
As I said in a
Since your s6-svscan doesn't run as pid 1, you don't need a finish or a
crash script. Not creating the .s6-svscan directory at all is good: the
default behaviour is suitable for running s6-svscan as a normal service.
The answer to the rest of your questions implies policy decisions. In
other
I prefer this way. Some packages prefer s6 as their process supervisor,
some
packages prefer systemd. With the help of s6 rpm package, other rpm
packages
who depend on s6 can install their service in s6’s service directory.
We just pave
for the community, the choice is in their hands.
Please note that this list isn't meant for real-time debugging.
If you want real-time help, please join IRC (#s6 on OFTC), that's what
it is for.
Apr 10 22:06:53 rpm-builder s6.systemd-boot[15235]: s6-supervise s6-svscan-log:
warning: unable to spawn ./run (waiting 60 seconds): No such
1. Run btmpd, utmpd, wtmpd as s6 service. But this option will add s6 as extra
dependency.
2. Run btmpd, utmpd, wtmpd as systemd service. The dependency is minimal. Only
depends on s6-ipcserver.
On Alpine, s6-ipcserver is in a separate package because Alpine is very
careful about disk
Thank you! Sorry for the rather bare initial report - was very much
one of trying to work out what had gone wrong initially!
It's all good - I'm supposed to catch these things and I failed,
so the next best thing is to get them fixed as quickly as possible :)
--
Laurent
Fixed, thanks!
(I assume you meant in the s6 package. :))
--
Laurent
backtick -E A_LONGISH_NAME { s6-echo foo }
It fails with:
Huh. I must have missed something. Thanks for the report, will
investigate and fix.
--
Laurent
1. example/s6/httpd-4/run script. In this script, it use 's6-tcpserver -v2 -1
-U -c 512 -- $ip 80’, but -v2 is not
a valid options for s6-tcpserver. After change -v2 to -v, s6-tcpserver works.
Whoops, I'll change that, thanks.
2. example/s6/httpd-4/log/run script. Here the problem is
Hello,
New versions of some skarnet.org packages are available.
A very light update this time, just keeping the lights on.
skalibs-2.14.1.1(release)
execline-2.9.5.0(minor)
s6-2.12.0.4 (release)
tipidee-0.0.4.0 (minor)
skalibs and s6 get tiny bugfixes.
I would like to package an example service for s6. Could you suggest one?
tipidee would be a good one. I plan to release tipidee-0.4.0.0 very
soon
and have an Alpine package for it early next week, if you want to have
example scripts.
So, is s6-rc a good candidate for rpm package? I am
Hey. Thanks for your work.
If you're looking for a more community-oriented hosting service
than GitHub, you could try Codeberg (https://codeberg.org) or
Sourcehut (https://sr.ht/). But it's all up to you.
--
Laurent
I'm disappointed, I thought that mail contained a patch that would
fix the lack of unix-transactional.h documentation! :)
--
Laurent
That was... the best possible answer to my ribbing :D
Applied, thanks!
--
Laurent
I can confirm that the patch worked:
Thanks, execline-2.9.5.1 is out now.
--
Laurent
Running backtick with gdb reveals that the crash is caused by the
`memcpy' at line 63 of src/libexecline/el_modifs_and_exec.c
Thanks for doing my work for me :D
(these are the bugs I usually catch before release, but, laziness.)
The latest execline git head should fix it. If it works for
Maybe something like Zig's SegmentedList[1] would fit?
Something like "stop trying to be too smart and just use malloc" fits
perfectly ;)
(I normally wouldn't do this, but the ftrigio structure already
includes a ftrig1_t, a stralloc and a regex_t, all of which call
malloc, so the trade-off
If a single s6-ftrigrd is requested to listen on many listeners, the
genalloc_readyplus may have to move the ftrigio's to a new memory area,
causing the char* inside their buffer to get outdated, overwriting
unrelated memory areas when filling the buffers and possibly triggering
a SIGSEGV.
I have a setup where sometimes a root process will s6-svwait on a
s6-supervise that is running as another UID.
Unless I s6-applyuidgid -u $svscan_uid s6-svwait ..., the svwait never
returns and the pipe it creates just stands there in the event/ folder
until I `sudo rm` it.
If it helps, the
The cause for this is the weird dance we have to do with fifodirs and
fifo permissions in order to grant the correct filesystem rights
The model was actually correct, it was just a bug, that nobody
noticed because it's rare that root has to wait for a notification
from user-owned services.
-- Original Message --
From "Carlos Eduardo"
To supervis...@list.skarnet.org
Cc "Carlos Eduardo"
Date 2024-05-04 21:58:21
Subject [PATCH] Add adoption to trap
With this patch, trap(1) is able to accept an existing PID as prog...,
if given the new -P option.
I'm sending this as
While we're at it, may I ask about s6's versioning scheme? I noticed
there was an ABI change in skalibs (env_mergen becoming a macro), but
the Gentoo package for skalibs is currently set up to only trigger
rebuilds of dependant packages if the second number changes (e.g. from
2.14.x to 2.15.x).
To complete my previous answer, I update the minor (the third number)
when new symbols are added. So the ABI changes, but no rebuild is
necessary because the old symbols are still there (with the same
signature and semantics).
However, new versions of software such as s6, including bugfix
501 - 534 of 534 matches
Mail list logo
