[MacPorts] #52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -----------------------+------------------------------------ Reporter: rpgoldman | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: p5.24-module-signature -----------------------+------------------------------------ Currently, if one tries to install this port, it fails if one has gnupg21 installed, because it requires gnupg, which conflicts with gnupg21. Seems to work if I substitute `port:gnupg21` for `port:gnupg` in the portfile, but perhaps there's a better fix that is agnostic between the gnupg versions. -- Ticket URL: <https://trac.macports.org/ticket/52795> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+---------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: p5.24-module-signature | -------------------------------------+---------------------- Changes (by dbevans): * owner: macports-tickets@… => dbevans * status: new => accepted -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:1> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+---------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: p5.24-module-signature | -------------------------------------+---------------------- Comment (by dbevans): Checking Makefile.PL it appears that this module should configure and run with any of gnupg, gnupg2 or gnupg21. Will change the dependency to allow any of these and test to make sure that they all work. -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:2> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+---------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: p5.24-module-signature | -------------------------------------+---------------------- Changes (by dbevans): * cc: ionic@…, jann@… (added) Comment: Not so easy. The problem is that gnupg and gnupg2 do not install any common paths and so they can be installed at the same time. I think this is true for gnupg21 and gnupg although they are marked as conflicting. Of course, gnupg2 and gnupg21 definitely do conflict and can't be installed at the same time. As stated above, this module can potentially work with any of these. However, in the case where gnupg and gnupg2/21 are installed in parallel, due to its order of search, the module will see and select gnupg first over gnupg2/21. This doesn't seem right. CCing the maintainers of three 3 gnupg ports. Comments please. -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:3> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+---------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: p5.24-module-signature | -------------------------------------+---------------------- Comment (by Ionic): I guess you're not a big fan of variants (and I can understand that, especially related to my suggestion now), but how about variants two variants like `gnupg_gen1` and `gnupg_gen2` that dynamically switch dependencies (`path:bin/gnupg:gnupg` vs. `path:bin/gpg2:gnupg2`) and also patch the source code into submission to hardcode the path to the `gpg` binary or at least remove one branch of the auto-detection? -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:4> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+---------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: accepted Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: p5.24-module-signature | -------------------------------------+---------------------- Comment (by dbevans): Well, I was thinking about this and you're right, I didn't really like it but I don't see an alternative right now. As far as a default variant I would probably pick gnupg2 over gnupg. BTW, do you agree that gnupg and gnupg21 don't really conflict (as in install common paths)? -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:5> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+--------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: p5.24-module-signature | -------------------------------------+--------------------- Changes (by dbevans): * status: accepted => closed * resolution: => fixed Comment: In [changeset:"807c08b9105b0b0907ac8c023339ad04f749dcf7/macports-ports" 807c08b9/macports-ports]: {{{ #!ConfigurableCommitTicketReference repository="macports-ports" revision="807c08b9105b0b0907ac8c023339ad04f749dcf7" p5-module-signature: allow configuration with either gnupg v1 or gnupg v2 Add +gnupg1 variant to specify configuration with gnupg v1 rather than default gnupg v2 even if both are installed. In the default case, patch Makefile.PL to ignore any installed instance of gnupg v1. Fixes https://trac.macports.org/ticket/52795 }}} -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:6> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+--------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: p5.24-module-signature | -------------------------------------+--------------------- Comment (by dbevans): Note that in default case the port now uses a path depspec to allow any installed port that provides ${prefix}/bin/gpg2 to satisfy the dependency, i.e. gnupg2 or gnupg21. gnupg2 will be installed by default if nothing appropriate is available. @ionic: I'll leave it to you to resolve the conflict/non-conflict between gnupg and gnupg21. -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:7> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+--------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: p5.24-module-signature | -------------------------------------+--------------------- Comment (by roederja): GPG 2.1 has a new key format that older versions cannot read. Therefore it is marked as conflicting. -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:8> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+--------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: p5.24-module-signature | -------------------------------------+--------------------- Comment (by dbevans): I understand that. That's why 2.1 is not the default and why it has warning notes that mention this. However, conflicting means that they cannot be installed at the same time because they install one or more common paths. So gnupg2 and gnupg21 conflict but they do not conflict with gnupg. -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:9> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+--------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: p5.24-module-signature | -------------------------------------+--------------------- Comment (by Ionic): Well... theoretically they do not install files with the same path, but they conflict semantically. Do you want to install both so that a spurious call to `gpg2` suddenly converts your keychain to the new format and deletes all your previous private keys? A user would be very confused by suddenly not seeing the keys anymore, just because something called `gpg2` at some point in time (which might well be such a perl script.) Making the ports conflict was the easiest way to counter that situation. -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:10> MacPorts <https://www.macports.org/> Ports system for macOS
#52795: p5.24-module-signature @ 0.810.0 Incompatible with installed gnupg21 -------------------------------------+--------------------- Reporter: rpgoldman | Owner: dbevans Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: p5.24-module-signature | -------------------------------------+--------------------- Comment (by dbevans): OK. I give up. But since you're using the conflict keyword in a somewhat non-standard way, I'd suggest adding some comments to the ports explaining why you're doing it. That way you won't confuse folks like me ;-) I don't believe it has any effect on the changes I've made here. -- Ticket URL: <https://trac.macports.org/ticket/52795#comment:11> MacPorts <https://www.macports.org/> Ports system for macOS
participants (1)
-
MacPorts