On 24/01/2025 19:02, Brian Inglis via Cygwin wrote:
On 2025-01-24 10:00, ASSI via Cygwin wrote:
ASSI via Cygwin writes:
Turns out that the (fresh) installation of Cygwin on this machine which
has exactly the same package selection was hosed up by a different
package installation order: Some time ago the GnuPG2 package was
changed to replace /usr/bin/gpg (and gpg2 is now a symlink to that), but
of course the old gpg package installs it's own executable in exactly
the same place. Guess which package was installed last… :-)
Further, the reason it attempts to install both versions is that wget
(and wget2) pull in libgpgme11, which in turn wants gnupg. Given that
gnupg v1 is dead as a dodo on Cygwin that doesn't look right…
gpgme is ORPHANED with no maintainer - CCing and RT apps
I had the impression to have properly declared
NAME="gnupg2"
VERSION=2.4.7
RELEASE=1
OBSOLETES="gnupg"
and so setup.ini has
@ gnupg2
sdesc: "GNU tool for secure communication and data storage"
...
obsoletes: gnupg
so what went wrong ?
Marco
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
