Re: ppc64le strange build errors, needs 1947 inodes on the / filesystem !?

2016-01-27 Thread Sérgio Basto
On Qui, 2016-01-21 at 13:41 +0100, Miroslav Suchý wrote: > Dne 20.1.2016 v 18:50 Sérgio Basto napsal(a): > > I tried 4 days ago and after I decide to wait for "Planned Outage: > > Copr > > upgrade", today still have the same errors.  > > https://copr-be.cloud.fedoraproject.org/results/sergiomb/kde4

failed Unknown error with Mock SCM

2016-01-27 Thread Zaina Afoulki
I tried Mock build from a SCM repository in Copr, and I get "failed Unknown error." https://copr.fedorainfracloud.org/coprs/blpgccgfortran/gcc-gfortran-blp/build/156124/ Using a src.rpm with the same spec file and source code works, running mock locally on my machine works as expected too. I m

Re: Unable to connect with copr-cli

2016-01-27 Thread Patrick Uiterwijk
Hi, 元のメッセージ - > > https://github.com/shazow/urllib3/issues/797 > As of a bit ago, copr.fedoraproject.org will only get IPv4 results from DNS, which should resolve this issue. With kind regards, Patrick Uiterwijk Fedora Infra ___ copr-devel m

Re: Unable to connect with copr-cli

2016-01-27 Thread Miroslav Suchý
Dne 27.1.2016 v 13:31 Pavel Raiskup napsal(a): > Right, I'm not an expert on this topic, but urllib3 should probably > implement Happy Eyeballs for copr client: https://github.com/shazow/urllib3/issues/797 -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsy

Re: Unable to connect with copr-cli

2016-01-27 Thread Miroslav Suchý
Dne 27.1.2016 v 09:55 Pavel Raiskup napsal(a): > This is ipv6 issue. Yes. This is direct result of redirect of copr.fedoraproject.org to copr.fedorainfracloud.org. Because copr.fedoraproject.org is now CNAME for wildcard.fedoraproject.org, which is reverse proxy and HAS IPv6 address. However Cop

Re: Unable to connect with copr-cli

2016-01-27 Thread Pavel Raiskup
On Wednesday 27 of January 2016 11:04:43 Pierre-Yves Chibon wrote: > > This is ipv6 issue. I was told that "Happy Eyeballs" could help here; > > that is: > > https://github.com/python/asyncio/issues/86 > > > > Or switch to PyCURL (this should be more robust solution). > > But this is an asyncio

Re: Unable to connect with copr-cli

2016-01-27 Thread Pierre-Yves Chibon
On Wed, Jan 27, 2016 at 09:55:16AM +0100, Pavel Raiskup wrote: > On Wednesday 27 of January 2016 09:33:05 Pavel Raiskup wrote: > > FYI: Seems like there are some issues on frontend side ATM: > > > > 09:32:04 ~/rh/projects/distgen/rpm$ copr --debug list > > [09:32:12] {/usr/lib/python2.7/site-packa

Re: Unable to connect with copr-cli

2016-01-27 Thread Pavel Raiskup
On Wednesday 27 of January 2016 09:33:05 Pavel Raiskup wrote: > FYI: Seems like there are some issues on frontend side ATM: > > 09:32:04 ~/rh/projects/distgen/rpm$ copr --debug list > [09:32:12] {/usr/lib/python2.7/site-packages/copr_cli/main.py:416} DEBUG - # > Debug log enabled # > [09:32:12]

Unable to connect with copr-cli

2016-01-27 Thread Pavel Raiskup
FYI: Seems like there are some issues on frontend side ATM: 09:32:04 ~/rh/projects/distgen/rpm$ copr --debug list [09:32:12] {/usr/lib/python2.7/site-packages/copr_cli/main.py:416} DEBUG - # Debug log enabled # [09:32:12] {/usr/lib/python2.7/site-packages/copr/client/client.py:172} DEBUG - Fet