Package Details: python3-xcgf 2021-2

Git Clone URL: https://aur.archlinux.org/python3-xcgf.git (read-only, click to copy)
Package Base: python3-xcgf
Description: Xyne's common generic functions, for internal use.
Upstream URL: https://xyne.dev/projects/python3-xcgf
Licenses: GPL
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 97
Popularity: 0.89
First Submitted: 2015-12-06 05:39 (UTC)
Last Updated: 2021-12-13 22:17 (UTC)

Latest Comments

Xyne commented on 2021-12-18 18:22 (UTC)

The host is still iteratively working on security rules. Disabling them is unfortunately not an option right now.

If you're building on Arch, you can try using the repo on my site to install the package too.

ozooha commented on 2021-12-18 16:20 (UTC)

That 503 error which @dotted experienced still persists. Any idea on the resolution?

Xyne commented on 2021-12-14 16:14 (UTC)

The host changed some settings. The errors should resolve soon.

dotted commented on 2021-12-14 06:06 (UTC)

Unable to update, using wget i get this:

➜  ~ wget https://xyne.dev/projects/python3-xcgf/src/python3-xcgf-2021.tar.xz
--2021-12-14 07:05:39--  https://xyne.dev/projects/python3-xcgf/src/python3-xcgf-2021.tar.xz
SSL_INIT
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving xyne.dev (xyne.dev)... 172.67.174.199, 104.21.67.125, 2606:4700:3030::ac43:aec7, ...
Connecting to xyne.dev (xyne.dev)|172.67.174.199|:443... connected.
HTTP request sent, awaiting response... 503 Service Temporarily Unavailable
2021-12-14 07:05:39 ERROR 503: Service Temporarily Unavailable.

AchmadFathoni commented on 2021-07-31 07:08 (UTC)

Upstream tarball is downgraded to 2017 https://xyne.archlinux.ca/projects/python3-xcgf/src/

commented on 2020-01-25 12:04 (UTC)

Could you rename it according to the guidelines?

For Python 3 library modules, use python-modulename. Also use the prefix if the package provides a program that is strongly coupled to the Python ecosystem (e.g. pip or tox). For other applications, use only the program name.

alfredo.ardito commented on 2017-05-16 08:01 (UTC) (edited on 2017-05-16 08:20 (UTC) by alfredo.ardito)

Built successfully after setting up the right signatures. gpg --recv-keys --keyserver hkp://pgp.mit.edu 1D1F0DC78F173680

Xyne commented on 2017-05-13 02:29 (UTC)

@alfredo.ardito The signatures are correct. You need to import the key into your user's keyring to verify the signature with makepkg. For details, see e.g. https://aur.archlinux.org/packages/python3-aur/

alfredo.ardito commented on 2017-05-11 08:05 (UTC)

Failed building with the following error: ==> Validating source files with md5sums... python3-xcgf-2017.3.tar.xz ... Passed python3-xcgf-2017.3.tar.xz.sig ... Passed ==> Validating source files with sha512sums... python3-xcgf-2017.3.tar.xz ... Passed python3-xcgf-2017.3.tar.xz.sig ... Passed ==> Verifying source file signatures with gpg... python3-xcgf-2017.3.tar.xz ... FAILED ==> ERROR: One or more PGP signatures could not be verified! ==> ERROR: Makepkg was unable to build python3-xcgf. ==> Restart building python3-xcgf ? [y/N] ==> -------------------------------------

abhisheietk commented on 2016-12-25 01:00 (UTC)

issue resolved trustdb was corrupted

abhisheietk commented on 2016-12-25 00:26 (UTC)

==> Verifying source file signatures with gpg... python3-xcgf-2016.4.26.tar.xz ... FAILED ==> ERROR: One or more PGP signatures could not be verified!

Xyne commented on 2016-11-13 08:35 (UTC)

@Lorax See the comments below. Have you imported my key to your keyring?

Lorax commented on 2016-11-12 06:35 (UTC)

PGP Signatures could not be verified, can you please update them. Thanks.

Xyne commented on 2016-10-12 20:13 (UTC)

@carbolymer I have no control over that as I am not the host. I was not even aware that there was an anti-bot filter. Given that nobody has reported it in the years that the site has been up, it is either very new or most people are not affected. If it becomes an issue then I can ask the host about it, but I do not see how I could counter it in the PKGBUILD. Sorry.

carbolymer commented on 2016-10-09 16:51 (UTC) (edited on 2016-10-09 16:53 (UTC) by carbolymer)

Hi Xyne. When installing your package I am getting the following error: ==> ERROR: One or more files did not pass the validity check! And after investigating python3-xcgf-2016.4.26.tar.xz.sig and python3-xcgf-2016.4.26.tar.xz files, I found that they contain the following content: http://pastebin.com/FWtbwT4V Please make your anti-robot protection on your hosting less proactive or include it in your installation scripts.

Xyne commented on 2016-07-10 20:56 (UTC)

I have been gradually working on a new backend for a while. It is available for testing here[1]. It is not entirely backwards-compatible so please give it a try now and get ready to migrate your configuration files and scripts. Extension developers are most welcome :D. Please keep related discussion in the forum thread. [1] https://bbs.archlinux.org/viewtopic.php?id=214706

Xyne commented on 2016-01-29 19:26 (UTC)

I have replied about the download speed issue on the forum: https://bbs.archlinux.org/viewtopic.php?pid=1599874#p1599874

j1simon commented on 2016-01-29 10:13 (UTC)

@kaeltis thanks, 'gpg --recv-keys' works for me. Although the download speed is extremely slow from the xyne repository.

Xyne commented on 2016-01-14 23:16 (UTC)

@pethead I have just tested the current package. It downloads, verifies and builds without error. Have you tried building the package directly with makepkg? What is the exact error message? Pastebin the full output and post a link here if it doesn't work.

pethead commented on 2016-01-14 10:43 (UTC)

Yes, 1D1F0DC78F173680 is not been verified. :(

ectospasm commented on 2016-01-04 13:28 (UTC)

gpg --recv-key 1D1F0DC78F173680 isn't working for me. I see the key in the keyring, and yet aura says unknown public key. I've added it to both root's, pacman's (pacman-key), and my normal user's public keyring to no avail. Actually, it's an aura problem. Building it the old fashioned way works. I'll post to the aura page.

Kaeltis commented on 2015-12-28 19:51 (UTC)

Try gpg --recv-keys 1D1F0DC78F173680

czipperz commented on 2015-12-23 20:15 (UTC)

Same error as 4ronie4 here.

ZJaume commented on 2015-12-22 14:04 (UTC)

I get an error :( Yaourt cannot verify signing key: unknown public key 1D1F0DC78F173680