From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Move to versioned pam-gnupg
Date: Tue, 03 Mar 2020 11:41:11 +0100 [thread overview]
Message-ID: <20200303104111.e1-yPQhhjAOUHKi8PtQuFXuURupk4OyxvEIe324UC-U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19645@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
There's a merged pull request on the void-packages repository
Move to versioned pam-gnupg
https://github.com/void-linux/void-packages/pull/19645
Description:
This PR makes pam-gnupg-git a meta-package that depends on the new pam-gnupg package, which is a proper release version of the pam-gnupg module. The migration does not seem to work when pam-gnupg-git is a subpackage of pam-gnupg because the change from date-based versioning (20191206_1) to release versioning (0.1_1) is not properly ordered and XBPS will not recognize that the new meta-package is an upgrade to the earlier version.
The plan is to keep the pam-gnupg-git meta-package around for awhile---maybe until the next upstream release (I do not suspect that this is a popular package), then remove it and continue only with the new release-based package.
prev parent reply other threads:[~2020-03-03 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19645@inbox.vuxu.org>
2020-03-01 3:11 ` ahesford
2020-03-01 3:30 ` ahesford
2020-03-01 14:22 ` daniel-eys
2020-03-01 15:03 ` xtraeme
2020-03-03 10:40 ` xtraeme
2020-03-03 10:41 ` xtraeme [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200303104111.e1-yPQhhjAOUHKi8PtQuFXuURupk4OyxvEIe324UC-U@z \
--to=xtraeme@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).