On Sat, May 23, 2015 at 6:59 AM, Jens Adam wrote:
>
> information. If you're upgrading a bunch of packages (your usual -Syu)
> with 'pam' being one of many and it's not echoing any hint or warning
> about a soname change, well, duh. PAM is such an essential library
...coupled with the fact I work
Sat, 23 May 2015 13:39:00 +0200
This isn't about downgrading or rebuilding, but rather about sub-par
information. If you're upgrading a bunch of packages (your usual -Syu)
with 'pam' being one of many and it's not echoing any hint or warning
about a soname change, well, duh. PAM is such an essen
Sat, 23 May 2015 13:39:00 +0200
Alad Wenter :
> arch-general-requ...@archlinux.org schreef op 2015-05-19 14:00:
>
> > Anyone have a system they haven't upgraded in ~24hrs to give it a
> > further test, see if logins are broken after the pam upgrade?
> >
> > -te
>
> I've had similar issues, exce
arch-general-requ...@archlinux.org schreef op 2015-05-19 14:00:
Anyone have a system they haven't upgraded in ~24hrs to give it a
further test, see if logins are broken after the pam upgrade?
-te
I've had similar issues, except it broke systemctl --user functionality.
systemctl daemon-reexec
Heya all - so I ran a standard upgrade these evening, which upgraded
pam; I was headed for a reboot (since the new 4.0.3 kernel was also
updated) and checked my logs just because; my fcron daemon was failing
before the reboot. Huh.
pacman log:
[2015-05-18 18:28] [ALPM] upgraded pam (1.1.8-5 ->
1.
5 matches
Mail list logo