Package: python3-lib389
Version: 2.3.1+dfsg1-1
Severity: important
Tags: patch
Dear maintaner,
when following the 389ds documentation [1] to enable TLS for 389ds I noticed
that the step
dsconf security rsa set \
--tls-allow-rsa-certificates on \
--nss-token "internal
Package: dracut
Version: 059-4
Severity: wishlist
Activity in dracut upstream has died down recently and though there is a version
60 of dracut in sid, upstream has not tagged such a release.
A fork of dracut has been started by some dracut developers at
Package: fai-client
Version: 6.0
Severity: normal
Tags: patch
Using a holds throws message
> Not an ARRAY reference at /usr/sbin/install_packages line 207, line 317.
because the data has a different form than the code assumes.
A fix is found upstream at
Package: slurm-wlm
Version: 20.11.7+really20.11.4-2
Followup-For: Bug #1010632
This bug is is also present in the package version released in bullseye and
fixed in upstream version 20.11.9.
bullseye should definitely receive this update.
-- System Information:
Debian Release: 11.3
APT
Package: samba
Version: 2:4.13.13+dfsg-1~deb11u2
Severity: important
X-Debbugs-Cc: t...@security.debian.org
The upstream samba commit 0a546be0 is included in the buster security release
2:4.9.5+dfsg-5+deb10u2 via the patch file bug-14901-v4-9.patch, but is missing
in the bullseye security release
Package: lmod
Version: 6.6-0.4
Followup-For: Bug #883911
The current upstream version is 8.5.8. It would be great if this package could
be updated to the current major release. It could then also bump the dependency
to lua 5.4.
-- System Information:
Debian Release: 11.0
APT prefers testing
Package: lua-md5
Version: 1.2+git+1+8d87fee-1.1
Followup-For: Bug #920556
It would be great if lua 5.3 could be added to the package and if the current
version (1.3) could be packaged as well, as right, I need to depend on luarocks
for this package.
-- System Information:
Debian Release: 11.0
So my race condition doesn't seem to be because of autofs not signalling
readiness itself, since my problem still occurs with systemd support
enabled in autofs and, as I noticed, also well after boot.
Still, building autofs with systemd support would be nice to have in
bookworm. It's time. :)
On Tue, Jun 15, 2021 at 09:00:36AM +, Mike Gabriel wrote:
> thanks for your contribution. To make an update possible for Debian bullseye
> (we are in deep freeze), I need a more dramatic description of things that
> might go wrong with the current .service file.
>
> Please explain the opposite
Package: autofs
Version: 5.1.7-1
Followup-For: Bug #960676
The current upstream version of autofs provides a sample service file that for
Debian would look like this
> [Unit]
> Description=Automounts filesystems on demand
> After=network.target ypbind.service sssd.service network-online.target
Thank you for your response!
On Mon, Dec 21, 2020 at 06:22:04PM +0100, Michael Biebl wrote:
> I still fail to see the use-case for homed, tbh and the current
> implementation still requires quite a few hacks (see the fosdem 2020
> talk of Lennart and the problems e.g. with SSH keys).
>
> Atm
and their use can be
completely avoided even when installed, as they are installed by default e.g. on
Arch Linux.
I think this these tools could be a great boon in enterprise settings for
mounting users' homes via SMB in a nicely portable fashion.
Thank you for your work!
best regards,
Jörg Behrmann
[1
wanting to use it.
Thank you for your work!
best regards,
Jörg Behrmann
[1]
https://salsa.debian.org/systemd-team/systemd/-/blob/debian/master/debian/rules
-- Package-specific info:
-- System Information:
Debian Release: 10.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500
Dear maintainers
I'd like to use systemd-firstboot in some custom bootstrapping work.
systemd-firstboot shouldn't interfere with anything else. Would it maybe
be possible to get it included now that Debian allows for stronger
integration with systemd?
sincerely,
Jörg Behrmann
signature.asc
Package: dracut
Version: 048+80-2
Severity: normal
The man page for dracut.conf says
> *.conf files are read from /usr/lib/dracut/dracut.conf.d and
> /etc/dracut.conf.d.
> Files with the same name in /etc/dracut.conf.d will replace files in
> /usr/lib/dracut/dracut.conf.d.
with the intention
On 01.07.20 09:14, Timo Aaltonen wrote:
> I'm not doing this, instead I'll add DEBUG_LOGGER template to
> /etc/default/sssd and mention that DAEMON_OPTS is only used for the
> initscript.
>
I would like to argue, that the total removal of the coupling of the
service file and /etc/defaults/sssd
Ah, sorry. I had only checked debian/master on salsa and had missed
debian/experimental.
signature.asc
Description: PGP signature
Package: autofs
Version: 5.1.2-4
Severity: wishlist
I have two small issues with the service file
1) The current service file for autofs on buster sets
PIDFile=/var/run/autofs.pid
I saw that it is changed to
PIDFile=/run/autofs.pid
on salsa, which is great, but ExecStart
I just wanted to open this very same bug.
Could this issue maybe be looked at again? /run seems to have now won and
/var/run only be used by legacy systems. systemd automatically updates the path
to /run even if /var/run is set, but logs a warning, that leads to quite a bit
of log spam in tje
Package: sssd
Version: 1.16.3-3.2
Severity: normal
Tags: patch
The service file for sssd seems to be the upstream one, but on Debian it has
some minor issues:
1. PIDFile is set to /var/run/sssd.pid via PIDFile=@pidpath@/sssd.pid during the
build, but systemd-analyze complains
Package: sssd
Version: 1.16.3-3.2
Severity: wishlist
According to the man page sssd can be run with
--logger=journald
This unfortunately produced the warnings
Unexpected logger: journald
Expected: stderr, files
I quickly looked at the upstream configure file and this seems to
Package: python3-lib389
Version: 1.4.0.22-1
Severity: normal
Tags: patch
When running
dsidm posixgroup create foo
to create the group foo, dsidm fails with a namespace error, saying that
args does not have the attribute extra.
The problem can be found in versions 1.4.0.21 and 1.4.0.22 and
On Thu, Mar 21, 2019 at 03:29:00PM +0200, Timo Aaltonen wrote:
> Thanks a lot for sending it upstream. I wonder if it should/could be
> pushed for buster too.
>
I got an answer from upstream and for the 1.4.1.X release cycle they revamped
that part of the code [1], since lib389 was merged into
Package: python3-lib389
Version: 1.4.0.21-1
Severity: normal
Tags: patch upstream
Running "dsctil remove --do-it" or "dsctl --remove-all" fail fails
in lib389/instance/remove.py:remove_ds_instance when asserting the existence
of its marker file, which on RH systems is in /etc/sysconfig/dirsrv-,
The version 1.5 of pip, fixing this bug [1] has incidentally been
released today.
best regards,
Joerg
[1] http://www.pip-installer.org/en/latest/news.html#id1
signature.asc
Description: OpenPGP digital signature
Control: tag + fixed-upstream
On Sun, Jun 02, 2013 at 01:21:53AM +0200, Stefano Rivera wrote:
Control: tag -1 upstream
Hi Joerg (2012.11.02_11:58:16_+0200)
pip install --install-option=--prefix=${HOME}/.mypython27
--ignore-installed module name
Since 1.3, this should be possible, using
26 matches
Mail list logo
