Hi Jason, On Fri, May 15, 2015 at 10:53:02AM -0400, Jason Riedy wrote: > > root@pequin:~# aptitude purge libpam-slurm > > The following packages will be REMOVED: > > libpam-slurm{p} libslurm27{u} > > 0 packages upgraded, 0 newly installed, 2 to remove and 7 not upgraded. > > Need to get 0 B of archives. After unpacking 1,414 kB will be freed. > > Do you want to continue? [Y/n/?] > > (Reading database ... 284440 files and directories currently installed.) > > Removing libpam-slurm (14.03.9-5) ... > > (Reading database ... 284434 files and directories currently installed.) > > Removing libslurm27 (14.03.9-5) ... > > Processing triggers for libc-bin (2.19-18) ... > > > > root@pequin:~# ls -l /lib/x86_64-linux-gnu/security/*slurm* > > ls: cannot access /lib/x86_64-linux-gnu/security/*slurm*: No such file or > > directory > > root@pequin:~# aptitude install libpam-slurm > > The following NEW packages will be installed: > > libpam-slurm libslurm27{a} > > 0 packages upgraded, 2 newly installed, 0 to remove and 7 not upgraded. > > Need to get 469 kB of archives. After unpacking 1,414 kB will be used. > > Do you want to continue? [Y/n/?] > > Get: 1 http://ftp.debian.org/debian/ stable/main libslurm27 amd64 14.03.9-5 > > [450 kB] > > Get: 2 http://ftp.debian.org/debian/ stable/main libpam-slurm amd64 > > 14.03.9-5 [19.1 kB] > > Fetched 469 kB in 0s (474 kB/s) > > Selecting previously unselected package libslurm27. > > (Reading database ... 284428 files and directories currently installed.) > > Preparing to unpack .../libslurm27_14.03.9-5_amd64.deb ... > > Unpacking libslurm27 (14.03.9-5) ... > > Selecting previously unselected package libpam-slurm. > > Preparing to unpack .../libpam-slurm_14.03.9-5_amd64.deb ... > > Unpacking libpam-slurm (14.03.9-5) ... > > Setting up libslurm27 (14.03.9-5) ... > > Setting up libpam-slurm (14.03.9-5) ... > > Processing triggers for libc-bin (2.19-18) ... > > > > root@pequin:~# ls -l /lib/x86_64-linux-gnu/security/*slurm* > > -rw-r--r-- 1 root root 14360 Nov 12 2014 > > /lib/x86_64-linux-gnu/security/libpam_slurm.so > > So something in the multi-arch renaming incorrectly moves it to > libpam_slurm.so.
did you experienced this bug in a more recent version of libpam-slurm? I was never able to reproduce it. Best regards -- Gennaro Oliva