Alexey, after trying very hard performing a clean update, I always get
stuck when pacman -Su complains that whatever package is *corrupted
(invalid or corrupted package (PGP signature))*. It then asks if I want to
delete it. Answering yes or no makes no difference. It will always give
this error, no matter what I do. How can we fix this problem?
Here is the exact procedure I followed in order to update the system as
cleanly as possible:
1.
Restored a clean backup of MSYS2 from last week
2.
pacman-Sy
3.
pacman -S msys2-runtime, then autorebase
4. pacman -S bash, then autorebase
5. pacman -S filesystem, then autorebase
6. pacman -S libassuan, then autorebase
7. pacman -S libgpgme twice, because of fork error or something
8. pacman -S --needed filesystem msys2-runtime bash libreadline libiconv
libarchive libgpgme libcurl pacman ncurses libintl, then autorebase
(this updated pacman and some other package)
9. pacman -Sy
10. pacman-db-upgrade
11. pacman-key --init
12. pacman-key --populate msys2
13. pacman-key --refresh-keys
It then gets stuck at:
$ pacman -Su
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (4) dash-0.5.8-1 git-2.1.2-1 help2man-1.46.3-1 scons-2.3.4-1
Total Installed Size: 23.96 MiB
Net Upgrade Size: 0.01 MiB
:: Proceed with installation? [Y/n]
(4/4) checking keys in keyring
[#######################################################################################]
100%
(4/4) checking package integrity
[#######################################################################################]
100%
error: dash: missing required signature
:: File /var/cache/pacman/pkg/dash-0.5.8-1-x86_64.pkg.tar.xz is
corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: git: missing required signature
:: File /var/cache/pacman/pkg/git-2.1.2-1-x86_64.pkg.tar.xz is
corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: help2man: missing required signature
:: File /var/cache/pacman/pkg/help2man-1.46.3-1-x86_64.pkg.tar.xz is
corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: scons: missing required signature
:: File /var/cache/pacman/pkg/scons-2.3.4-1-any.pkg.tar.xz is
corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package (PGP
signature))
Errors occurred, no packages were upgraded.
Here is the output of the keyring commands executed previously:
$ pacman-db-upgrade
$ pacman-key --init
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: Generating pacman keyring master key...
+++++
..+++++
gpg: key 67C64C70 marked as ultimately trusted
gpg: Done
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
$ pacman-key --populate msys2
==> Appending keys from msys2.gpg...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Locally signing trusted keys in keyring...
-> Locally signing key D55E7A6D7CE9BA1587C0ACACF40D263ECA25678A...
-> Locally signing key 123D4D51A1793859C2BE916BBBE514E53E0D0813...
-> Locally signing key B91BCF3303284BF90CC043CA9F418C233E652008...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
gpg: inserting ownertrust of 4
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 3 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 3 signed: 1 trust: 0-, 0q, 0n, 3m, 0f, 0u
gpg: depth: 2 valid: 1 signed: 0 trust: 1-, 0q, 0n, 0m, 0f, 0u
$ pacman-key --refresh-keys
gpg: refreshing 5 keys from hkp://pool.sks-keyservers.net
gpg: requesting key 67C64C70 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 2835216002FD13D88F79172D28AE9FE867C64C70 not found on keyserver
gpg: key CA25678A: "Alexey Pavlov (Alexpux) <[email protected]>"
3 new signatures
gpg: key 3E0D0813: "Ray Donnelly (MSYS2 Developer - master key)
<[email protected]>" 1 new signature
gpg: key 3E652008: "Ignacio Casal Quinteiro <[email protected]>" 2
new signatures
gpg: key A47D45A1: "Alexey Pavlov (Alexpux) <[email protected]>" 1 new signature
gpg: Total number processed: 4
gpg: new signatures: 7
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 3 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 3 signed: 1 trust: 0-, 0q, 0n, 3m, 0f, 0u
gpg: depth: 2 valid: 1 signed: 0 trust: 1-, 0q, 0n, 0m, 0f, 0u
2014-10-02 4:51 GMT-03:00 Alexpux <[email protected]>:
>
> 02 окт. 2014 г., в 2:19, Wayne Stambaugh <[email protected]>
> написал(а):
>
> > I now also have the same problem on my home system as well :(. I'm
> > using msys64 so I don't know if problem exists on msys32. I guess I
> > have to file a bug report.
> >
> Did you run all those commands?
> pacman-db-upgrade
> pacman-key —init
> pacman-key —populate msys2
> pacman-key —refresh-keys
>
> If yes then show me output of them.
>
>
> P.S.: I’m successfully build KiCAD with wxPython+SWIG
> P.P.S.: It would be great if KiCAD have the same files layout on Windows
> as on Linux. Don’t place all files in one folder.
>
> Regards,
> Alexey.
>
> > On 10/1/2014 11:51 AM, Matthieu Vachon wrote:
> >> 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
>
>
>
> ------------------------------------------------------------------------------
> 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
