[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#785256: marked as done (libpam-slurm: pam_slurm.so installed as libpam_slurm.so)



Your message dated Sat, 1 Mar 2025 23:15:15 +0100
with message-id <Z8OG80gdGNwZ63+O@careca>
and subject line Re: Bug#785256: libpam-slurm: pam_slurm.so installed as libpam_slurm.so
has caused the Debian Bug report #785256,
regarding libpam-slurm: pam_slurm.so installed as libpam_slurm.so
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
785256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785256
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libpam-slurm
Version: 14.03.9-5
Severity: important

Somehow, the file intended for /lib/<multiarchbit>/security/pam_slurm.so ends
up being named libpam_slurm.so.  The libpam-slurm.list entry is correctly
lacking the lib part, but the file's name is not.  Uninstalling does remove
libpam_slurm.so.

(Separately, it still does not seem to work, but that could be user error.
Adding the debug option outputs nothing I can find.  I haven't straced sshd
yet.)

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (800, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.19.0-hpclab-compute (SMP w/32 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-slurm depends on:
ii  libc6       2.19-18
ii  libslurm27  14.03.9-5

libpam-slurm recommends no packages.

libpam-slurm suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
I was never able to reproduce this bug and nobody else notified it
therefore I am closing this bug.
Feel free to reopen if you experience this issue again
Best regards
-- 
Gennaro Oliva

--- End Message ---

Reply to: