FYI: The status of the systemd source package
in Debian's testing distribution has changed.
Previous version: 257.1-7
Current version: 257.2-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
On Thu, 16 Jan 2025, Luca Boccassi wrote:
>This is an anti-pattern, and best avoided. What's the problem if the
>script runs twice? If it just detects things it should be just fine,
Extra effort, though. And, in general, TOCTOU, but probably not
applicable here.
bye,
//mirabilos
--
den AGP ste
On Wed, 15 Jan 2025 at 23:12, Sven Geuer wrote:
>
> On Wed, 2025-01-15 at 20:28 +0100, Thorsten Glaser wrote:
> > On Wed, 15 Jan 2025, Sven Geuer wrote:
> >
> > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
> >
> > > Applying ExecCondition to me seems the most reasonable solutio
On Thu, 16 Jan 2025, Sven Geuer wrote:
>> If not, I’d lean towards one (which?) of the errorlevel-using ones,
>> because otherwise we’d have to run the detection code twice.
>
>Not sure what you mean by 'one of the errorlevel-using ones'. Please
>explain your idea in more details.
SuccessExitStat
On Wed, 2025-01-15 at 20:28 +0100, Thorsten Glaser wrote:
> On Wed, 15 Jan 2025, Sven Geuer wrote:
>
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
>
> > Applying ExecCondition to me seems the most reasonable solution to this
> > bug.
>
> Can the script behind ExecCondition p
On Wed, 15 Jan 2025, Sven Geuer wrote:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
>Applying ExecCondition to me seems the most reasonable solution to this
>bug.
Can the script behind ExecCondition pass variables to the script
behind ExecStart or, even better, the unit itself
On Wed, 2025-01-15 at 00:47 +0100, Thorsten Glaser wrote:
> On Tue, 14 Jan 2025, Luca Boccassi wrote:
>
> > It looks like this is doing some checks, and intends to skip. But just
> > exiting means the service is recorded as failed, and this will likely
> > trip other tests, hence the severity to s
Package: systemd-homed
Version: 257.2-1
Severity: normal
I expected that setting CAP_SYSLOG as AmbientCapability for a user
is enough to allow the usage of dmesg.
root@iris:~# homectl create --capability-ambient-set=CAP_SYSLOG testuser
Please enter new password for user testuser: ���
