From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Move to versioned pam-gnupg
Date: Sun, 01 Mar 2020 04:30:48 +0100 [thread overview]
Message-ID: <20200301033048.VbyFEhtiJGK1SvD2aW42FWXJH-jqqfhJvsHepkvGHVo@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: 869 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/19645#issuecomment-593048342
Comment:
A quick test suggests that adding a `replaces` directive is not sufficient to identify the upgrade path from `pam-gnupg-git` to `pam-gnupg`. With the new `pam-gnupg` package (with a `replaces` directive) available in a local repository, `xbps-install pam-gnupg` will properly cause removal of an installed `pam-gnupg-git-20191206_1`. However, `xbps-install -u` from the local repo will *not* attempt to replace the installed `pam-gnupg-git-20191206_1` with the new `pam-gnupg` whether or not the `replaces` directive is included.
By contrast, having an updated `pam-gnupg-git` metapackage in the local repo causes `xbps-install -u` to properly replace the existing installation, pulling in the new `pam-gnupg` by dependence.
next prev parent reply other threads:[~2020-03-01 3:30 UTC|newest]
Thread overview: 7+ 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 1:44 ` daniel-eys
2020-03-01 3:11 ` ahesford
2020-03-01 3:30 ` ahesford [this message]
2020-03-01 14:22 ` daniel-eys
2020-03-01 15:03 ` xtraeme
2020-03-03 10:40 ` xtraeme
2020-03-03 10:41 ` [PR PATCH] [Merged]: " xtraeme
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=20200301033048.VbyFEhtiJGK1SvD2aW42FWXJH-jqqfhJvsHepkvGHVo@z \
--to=ahesford@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).