Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 795693 - app-crypt/gnupg-2.2.28 failed compiling
Summary: app-crypt/gnupg-2.2.28 failed compiling
Status: RESOLVED DUPLICATE of bug 795669
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-13 03:30 UTC by Errelin
Modified: 2021-06-13 04:11 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
verbose USE for app-crypt/gnupg (emerge app-cryptgnupg.txt,542 bytes, text/plain)
2021-06-13 03:30 UTC, Errelin 		Details
emerge --info for gnupg (emerge --info app-sctpy.gnupg.txt,5.52 KB, text/plain)
2021-06-13 03:31 UTC, Errelin 		Details
build.log (gnupg-2.2.28-build.log.txt,193.19 KB, text/plain)
2021-06-13 03:32 UTC, Errelin 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Errelin 2021-06-13 03:30:29 UTC 
Created attachment 715638 [details]
verbose USE for app-crypt/gnupg

Hello,

However I tried to emerge app-crypt/gnupg-2.2.28, it just failed with the same error. I'm currently on app-crypt/gnupg-2.2.27. One or some of the following pkgs may have pulled in gnupg on my machine:

gohan ~ # equery depends app-crypt/gnupg
 * These packages depend on app-crypt/gnupg:
app-crypt/gpgme-1.15.1 (>=app-crypt/gnupg-2)
app-crypt/openpgp-keys-gentoo-release-20200704 (test ? app-crypt/gnupg)
app-portage/gemato-16.2 (gpg ? >=app-crypt/gnupg-2.2.20-r1)
                        (test ? >=app-crypt/gnupg-2.2.20-r1)
dev-lang/python-3.9.5_p2 (verify-sig ? app-crypt/gnupg)
dev-lang/python-3.10.0_beta2 (verify-sig ? app-crypt/gnupg)
dev-lang/rust-1.52.1 (verify-sig ? app-crypt/gnupg)
dev-lang/rust-bin-1.52.1 (verify-sig ? app-crypt/gnupg)
dev-libs/libxml2-2.9.12-r3 (verify-sig ? app-crypt/gnupg)
dev-libs/libxslt-1.1.34-r1 (verify-sig ? app-crypt/gnupg)
dev-vcs/git-2.32.0 (gpg ? app-crypt/gnupg)
                   (test ? app-crypt/gnupg)
net-dns/libidn-1.37 (verify-sig ? app-crypt/gnupg)
net-dns/libidn2-2.3.1 (verify-sig ? app-crypt/gnupg)
sys-apps/portage-3.0.19 (rsync-verify ? >=app-crypt/gnupg-2.2.4-r2[ssl(-)])

I'm on the "~amd64" tesing branch of Gentoo. Though I can go by with 2.2.27 for now, but I do prefer to keep my whole system as latest as possible: if there is a chance for any any app to upgrade, I prefer to move on.

I've attached my emerge --info as well as other required logs. Could you look into this at your convenience? Many thanks :)
Comment 1 Errelin 2021-06-13 03:31:43 UTC 
Created attachment 715641 [details]
emerge --info for gnupg

the `emerge --info '=app-crypt/gnupg-2.2.28::gentoo'` as required
Comment 2 Errelin 2021-06-13 03:32:29 UTC 
Created attachment 715644 [details]
build.log
Comment 3 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2021-06-13 03:33:37 UTC 
>Timestamp of repository gentoo: Sat, 12 Jun 2021 22:15:01 +0000

Could you emerge --sync?

*** This bug has been marked as a duplicate of bug 795669 ***
Comment 4 Errelin 2021-06-13 04:11:32 UTC 
(In reply to Sam James from comment #3)
> >Timestamp of repository gentoo: Sat, 12 Jun 2021 22:15:01 +0000
> 
> Could you emerge --sync?
> 
> *** This bug has been marked as a duplicate of bug 795669 ***

Sorry for not mentioning that. I always upgrade after running emerge --sync. I've glanced through the bug 795669. It looks very like the one I met. I'll study it to see if that works. 

If any inconvenience, my apologies.