From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Felix Lechner <felix.lechner@gmail.com>
Cc: 55762@debbugs.gnu.org
Subject: [bug#55762] [PATCH] Upgrade linux-pam to 1.5.2
Date: Thu, 02 Jun 2022 20:16:27 +0200 [thread overview]
Message-ID: <87bkva9aat@nckx> (raw)
In-Reply-To: <CAFHYt54vnWZRi59GkkUuqebNdS6NYs9gu=0q6EsFUvMXWP1-bQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]
Felix,
Felix Lechner 写道:
> For my work in making PAM configurable in Guile, I rely on the
> foreign
> function interface (FFI). The automatic generation of that
> interface
> requires Pkgconfig files. Those files are not available in Guix.
> Linux-PAM started shipping them in the release after the one we
> have.
> The attached patch upgrades linux-pam to version 1.5.2.
Thanks for working on both!
> The changes are further documented in the commit message.
And thanks for writing a clear commit message. A few thoughts:
- The ‘gnu: foo: Update to x.y.z’ messages you see in the Guix
commit history are standardised. The format's documented in the
GNU ‘(standards)Change Logs’ info page, but just take a stroll
through the history to get a feel for the majority of cases.
- Don't feel obligated to explain why you're upgrading a package,
although you're free to do so if you like (it was interesting
and I learnt something).
Assuming no regressions, we always prefer to ship newer versions
of things.
- And finally, a personal windmill of mine:
> 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>.
As you might now, this update rebuilds a good part of the world
and will have to pass through the core-updates branch…
$ guix refresh -l linux-pam | cut -d: -f1
> I am new to Guix and already use the new version of linux-pam
> locally
> (via Guix System) but I was unable to test the patch according
> to the
> requirements and recommendations listed for this submission. [1]
…so it's impressive if you rebuilt most of your entire system
based on the new nyacc/linux-pam packages.
What still needs to be done, and which problems did you encounter?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-06-02 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 12:09 [bug#55762] [PATCH] Upgrade linux-pam to 1.5.2 Felix Lechner
2022-06-02 18:16 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-06-03 16:25 ` Felix Lechner
2022-09-30 15:37 ` [bug#55762] [PATCH core-updates] " Felix Lechner
2022-10-07 0:36 ` Felix Lechner via Guix-patches via
2022-10-20 20:48 ` bug#55762: [PATCH core-updates] linux-pam: Update " Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bkva9aat@nckx \
--to=guix-patches@gnu.org \
--cc=55762@debbugs.gnu.org \
--cc=felix.lechner@gmail.com \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).