* Re: Move to versioned pam-gnupg
[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
` (4 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: daniel-eys @ 2020-03-01 1:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 276 bytes --]
New comment by daniel-eys on void-packages repository
https://github.com/void-linux/void-packages/pull/19645#issuecomment-593028911
Comment:
You can add `replaces="pam-gnupg-git>=0"` to the new template. This should do the migration without the transitional meta-package.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Move to versioned pam-gnupg
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19645@inbox.vuxu.org>
` (4 preceding siblings ...)
2020-03-01 15:03 ` xtraeme
@ 2020-03-03 10:40 ` xtraeme
5 siblings, 0 replies; 6+ messages in thread
From: xtraeme @ 2020-03-03 10:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/19645#issuecomment-593883226
Comment:
Anyway, next time we should be more careful when adding pkgs with git commits...
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Move to versioned pam-gnupg
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19645@inbox.vuxu.org>
` (3 preceding siblings ...)
2020-03-01 14:22 ` daniel-eys
@ 2020-03-01 15:03 ` xtraeme
2020-03-03 10:40 ` xtraeme
5 siblings, 0 replies; 6+ messages in thread
From: xtraeme @ 2020-03-01 15:03 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 227 bytes --]
New comment by xtraeme on void-packages repository
https://github.com/void-linux/void-packages/pull/19645#issuecomment-593107023
Comment:
Right, the meta pkg allows you to upgrade it even with incompatible version upgrades.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Move to versioned pam-gnupg
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19645@inbox.vuxu.org>
` (2 preceding siblings ...)
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
5 siblings, 0 replies; 6+ messages in thread
From: daniel-eys @ 2020-03-01 14:22 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
New comment by daniel-eys on void-packages repository
https://github.com/void-linux/void-packages/pull/19645#issuecomment-593102702
Comment:
Right, I see now. Only an explicit `xpbs-install pam-gnupg` would pick up the changes in the case when `pam-gnupg-git` is already installed.
Then indeed, having a metapackage should be the proper choice here.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Move to versioned pam-gnupg
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19645@inbox.vuxu.org>
2020-03-01 1:44 ` Move to versioned pam-gnupg daniel-eys
2020-03-01 3:11 ` ahesford
@ 2020-03-01 3:30 ` ahesford
2020-03-01 14:22 ` daniel-eys
` (2 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: ahesford @ 2020-03-01 3:30 UTC (permalink / raw)
To: ml
[-- 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Move to versioned pam-gnupg
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19645@inbox.vuxu.org>
2020-03-01 1:44 ` Move to versioned pam-gnupg daniel-eys
@ 2020-03-01 3:11 ` ahesford
2020-03-01 3:30 ` ahesford
` (3 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: ahesford @ 2020-03-01 3:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/19645#issuecomment-593047034
Comment:
> You can add `replaces="pam-gnupg-git>=0"` to the new template. This should do the migration without the transitional meta-package.
This was my first inclination, but @Duncaen didn't think `replaces` was sufficient and recommended the meta-package approach. It would be great to get his feedback on the matter here.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-03-03 10:40 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-19645@inbox.vuxu.org>
2020-03-01 1:44 ` Move to versioned pam-gnupg daniel-eys
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
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).