(yay -Su)… :: PGP keys need importing:
-> 3059E09144F56804F0FBF4E126B40624BDBFD9F3, required by: palemoon
==> Import? [Y/n]
:: Importing keys with gpg...
gpg: keyserver receive failed: No name
problem importing keys
Git Clone URL: | https://aur.archlinux.org/palemoon.git (read-only, click to copy) |
---|---|
Package Base: | palemoon |
Description: | Open source web browser based on Firefox focusing on efficiency. |
Upstream URL: | https://www.palemoon.org/ |
Keywords: | browser goanna web |
Licenses: | MPL-2.0 |
Submitter: | artiom |
Maintainer: | WorMzy |
Last Packager: | WorMzy |
Votes: | 141 |
Popularity: | 0.133926 |
First Submitted: | 2014-06-05 10:54 (UTC) |
Last Updated: | 2024-11-05 20:54 (UTC) |
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 38 Next › Last »
(yay -Su)… :: PGP keys need importing:
-> 3059E09144F56804F0FBF4E126B40624BDBFD9F3, required by: palemoon
==> Import? [Y/n]
:: Importing keys with gpg...
gpg: keyserver receive failed: No name
problem importing keys
That commit id is the latest to the master branch, so I'd hazard a guess that the source array (specifically ?signed#commit=79ff7796e5
) isn't being parsed correctly for some reason, effectively meaning you're building palemoon-git rather than the stable version. No idea why that's happening, but I'd guess either yaourt bug (it's ancient and abandoned, don't use it) or you have a reaaaaally old makepkg version kicking about.
yaourt? Did you try just with
git clone https://aur.archlinux.org/palemoon.git
cd palemoon
makepkg
?
@WorMzy i'm getting a different commit
commit bf093ea79550c71889832eada5f6d7067574feec
not sure why though. i'm using a clean "yaourt -G palemoon" into a clean/new directory and PKGBUILD clearly shows _commit=79ff7796e5
Then you're checking out the wrong commit of the Pale-Moon repo somehow. What does git show -q
from inside $srcdir/Pale-Moon show? Should show:
commit 79ff7796e598775f30e00ec251e5c094e31ebe94 (HEAD -> makepkg, tag: 29.0.0_Release, tag: 29.0.0_RC2, origin/release)
Author: Moonchild <moonchild@palemoon.org>
Date: Sat Jan 30 11:15:07 2021 +0000
Update back-end branch pointer to UXP/release with BB fix.
(excuse formatting, using termux on phone)
@WorMzy UXP/dom/html/HTMLMenuItemElement.cpp is correct, but Pale-Moon/platform/dom/html/HTMLMenuItemElement.cpp is incorrect.
@WorMzy I'm getting:
Submodule path 'platform': checked out 'e1daeef18312a0cb17eda6bed7f363d8748ed4a3'
...and that's with a clean directory to start.
What does prepare() say? Should read:
==> Starting prepare()...
Submodule 'platform' (https://repo.palemoon.org/MoonchildProductions/UXP) registered for path 'platform'
Cloning into '/build/palemoon/src/Pale-Moon/platform'...
done.
Submodule path 'platform': checked out '304496d4ab61496a43d9d42cf8deb7811d772fe2'
@micwoj92 are we getting the wrong UXP commit?
@micwoj92 hm. yeah, i see that. and yet for some reason it's not.
should be:
nsGenericHTMLElement*
NS_NewHTMLMenuItemElement(already_AddRefed<mozilla::dom::NodeInfo>&& aNodeInfo,
mozilla::dom::FromParser aFromParser) {
if (mozilla::Preferences::GetBool("dom.menuitem.enabled")) {
return new mozilla::dom::HTMLMenuItemElement(nodeInfo, aFromParser);
} else {
return new mozilla::dom::HTMLUnknownElement(nodeInfo);
}
}
but is still:
nsGenericHTMLElement*
NS_NewHTMLMenuItemElement(already_AddRefed<mozilla::dom::NodeInfo>&& aNodeInfo,
mozilla::dom::FromParser aFromParser) {
RefPtr<mozilla::dom::NodeInfo> nodeInfo(aNodeInfo);
if (mozilla::Preferences::GetBool("dom.menuitem.enabled")) {
return new mozilla::dom::HTMLMenuItemElement(nodeInfo.forget(), aFromParser);
} else {
return new mozilla::dom::HTMLUnknownElement(nodeInfo.forget());
}
}
Pinned Comments
WorMzy commented on 2021-03-02 16:19 (UTC) (edited on 2022-08-03 21:12 (UTC) by WorMzy)
The following key is used to sign release commits:
40481E7B8FCF9CEC
Import it into your keyring however you want.
https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key