[bug#55762] [PATCH] Upgrade linux-pam to 1.5.2

[Felix Lechner]

Hi,

On Thu, Jun 2, 2022 at 11:42 AM Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>
> - The ‘gnu: foo: Update to x.y.z’ messages you see in the Guix
>   commit history are standardised.

The commit message was adjusted to the community standards.

> - Don't feel obligated to explain why you're upgrading a package,

I removed the explanation.

> > The extra argument to ./configure is needed to sidestep an issue
> > upstream.[1]
>
>   belongs in the code, where your fellow hackers can see it, not
>   buried in the commit log where $nobody will:
>
>   ;; Work around
>   <https://github.com/linux-pam/linux-pam/issues/466>.

Good idea! The comment was dropped from the commit message. Instead, I
added your note to the code.

> As you might now, this update rebuilds a good part of the world
> and will have to pass through the core-updates branch…
>
> …so it's impressive if you rebuilt most of your entire system
> based on the new nyacc/linux-pam packages.

Actually, my installation did not rebuild much at all, perhaps because
my local desktop runs few servers that would use PAM for
authentication.

Looking through the long list of consuming packages, my sense is that
one of the build systems may pull it in, perhaps via fakeroot or sudo.
I am not sure why cl-css or cl-uglify-js would otherwise need PAM.

> What still needs to be done, and which problems did you encounter?

I encountered no problems locally, but cannot speculate how Guix's
numerous build systems might react to the presence of the three new
Pkgconfig files. It was a reason why I mentioned the files in my
original commit message. My thought was that someone triangulating a
build issue elsewhere could perhaps find the information helpful.

An updated patch, which was also rebased, was attached. Thank you!

Kind regards,
Felix Lechner

0001-gnu-linux-pam-Update-to-1.5.2.patch
Description: Text Data