Sorry to learn that, really think that it would have solved your problem right away :$
I guess you should put a follow-up in the mentioned ticket, maybe Alexey will be able to help you further. Good luck, Matt On Wed, Oct 1, 2014 at 11:30 AM, Wayne Stambaugh <[email protected]> wrote: > Followed the command sequence and the output from pacman-key > --refresh-keys suggests something may be afoul: > > gpg: refreshing 5 keys from hkp://pool.sks-keyservers.net > gpg: requesting key 96DC99A9 from hkp server pool.sks-keyservers.net > gpg: requesting key CA25678A from hkp server pool.sks-keyservers.net > gpg: requesting key 3E0D0813 from hkp server pool.sks-keyservers.net > gpg: requesting key 3E652008 from hkp server pool.sks-keyservers.net > gpg: requesting key A47D45A1 from hkp server pool.sks-keyservers.net > gpgkeys: key 2290CC245D00CB9D8FB0DB7FAD0DC53396DC99A9 not found on keyserver > gpg: key CA25678A: "Alexey Pavlov (Alexpux) <[email protected]>" > not changed > gpg: key 3E0D0813: "Ray Donnelly (MSYS2 Developer - master key) > <[email protected]>" not changed > gpg: key 3E652008: "Ignacio Casal Quinteiro <[email protected]>" not > changed > gpg: key A47D45A1: "Alexey Pavlov (Alexpux) <[email protected]>" not changed > gpg: Total number processed: 4 > gpg: unchanged: 4 > > Now when I run pacman -Syu I get the following error for every package > that is downloaded: > > error: msys2-runtime: missing required signature > :: File > /var/cache/pacman/pkg/msys2-runtime-2.0.16224.6393980-2-x86_64.pkg.tar.xz is > corrupted (invalid or corrupted package (PGP signature)). > Do you want to delete it? [Y/n] n > error: git: missing required signature > > > On 10/1/2014 11:10 AM, Matthieu Vachon wrote: >> Hi Wayne, >> >> Here what Alexey wrote in a ticket >> (http://sourceforge.net/p/msys2/tickets/85/): >> >> Ok, guys. Do next: >> pacman-key --init >> pacman-key --populate msys2 >> pacman-key --refresh-keys >> >> It seems to have worked for people in the ticket. >> >> Regards, >> Matt >> >> On Wed, Oct 1, 2014 at 11:02 AM, Wayne Stambaugh <[email protected]> >> wrote: >>> I just tried to run pacman -Syu and ran into this error: >>> >>> (4/4) checking keys in keyring >>> [######################] 100% >>> downloading required keys... >>> :: Import PGP key 2048D/, "Alexey Pavlov (Alexpux) <[email protected]>", >>> created: 2013-11-11? [Y/n] y >>> error: key "Alexey Pavlov (Alexpux) <[email protected]>" could not be >>> imported >>> error: required key missing from keyring >>> error: failed to commit transaction (unexpected error) >>> Errors occurred, no packages were upgraded. >>> >>> Prior to this error, I got this warning: >>> >>> warning: Public keyring not found; have you run 'pacman-key --init'? >>> >>> so I ran pacman-key --init as suggested. Any ideas how to fix this? >>> Thanks in advance for the help. >>> >>> Wayne >>> >>> ------------------------------------------------------------------------------ >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Msys2-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/msys2-users >> > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Msys2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/msys2-users ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
