Re: [yocto] Fetcher failure on mpfr 4.0.1

2018-10-31 Thread Burton, Ross
The usual process is the autobuilder populates the source mirror as it runs. I pinged Richard earlier about this, basically it's fallout from the autobuilder migration and should be looked at next week. Ross On Tue, 30 Oct 2018 at 15:52, Gunnar Andersson wrote: > > I'm right now seeing a

[yocto] Fetcher failure on mpfr 4.0.1

2018-10-30 Thread Gunnar Andersson
I'm right now seeing a fetcher failure on mpfr-4.0.1.tar.xz As far as mirrors I believe we rely on this through the inclusion of poky.conf? http://downloads.yoctoproject.org/mirror/sources/ but we also add our own (PRE)MIRRORS in the conf files. Regardless of the project, it's not enough to

Re: [yocto] Fetcher failure for URL

2017-12-26 Thread Zoran Stojsavljevic
> Inside the bb file, there are following descriptions for this URL: > > SRC_URI = "git://github.com/GENIVI/dlt-daemon.git;protocol=https" > SRCREV = "e9a486a08fff6d3cc7133a350cec3ee10f463207" Interesting problem, for the sake of expertise/exercise I wanted to reproduce it in poky/referent YOCTO

[yocto] Fetcher failure for URL

2017-12-25 Thread Hou, Yong
Hello all, When i build the project based on yocto 2.0.2 using bitbake tool, i encountered one fetch error : "Failed to fetch URL git://github.com/GENIVI/dlt-daemon.git;protocol=https, attempting MIRRORS if available" Inside the bb file, there are following descriptions for this URL:

Re: [yocto] fetcher failure

2016-09-27 Thread Anicic Damir (PSI)
hed folder from Ubuntu) From: Zhenhua Luo [zhenhua@nxp.com] Sent: Tuesday, September 27, 2016 11:44 To: Anicic Damir (PSI); Chris Z. Cc: yocto@yoctoproject.org Subject: RE: [yocto] fetcher failure I have submitted a patch for the fetch issue, can you please

Re: [yocto] fetcher failure

2016-09-27 Thread Anicic Damir (PSI)
This is anoying. My primary build host, ScientificLinux 6.4, it stil fails (error log in previous mail). But on my secondary build host,Ubuntu 16.04, it now succeeded. -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] fetcher failure

2016-09-27 Thread Anicic Damir (PSI)
If I understood properly, all I have to do is to change the line: -SRC_URI = "git://git.freescale.com/ppc/sdk/linux.git;branch=sdk-v2.0.x \ with +SRC_URI = "git://git.freescale.com/ppc/sdk/linux.git;nobranch=1 \ If that is so, it did not help. Attached the new log file. Damir

Re: [yocto] fetcher failure

2016-09-27 Thread Zhenhua Luo
, September 27, 2016 5:34 PM To: Chris Z. <winotu.em...@gmail.com> Cc: yocto@yoctoproject.org Subject: Re: [yocto] fetcher failure Why should I check, the meta-fsl-ppc/recipes-kernel/linux/linux-qoriq_4.1.bb has SRC_URI = "git://git.freescale.com/ppc/sdk/linux.git;branch=sdk-v2.0

Re: [yocto] fetcher failure

2016-09-27 Thread Anicic Damir (PSI)
Why should I check, the meta-fsl-ppc/recipes-kernel/linux/linux-qoriq_4.1.bb has SRC_URI = "git://git.freescale.com/ppc/sdk/linux.git;branch=sdk-v2.0.x \ SRCREV = "bd51baffc04ecc73f933aee1c3a37c8b44b889a7" If that is wrong freescale should correct it. And besides, the downloaded file gets

Re: [yocto] fetcher failure

2016-09-27 Thread Chris Z.
Hi, Have you checked repository for hash bd51baffc04ecc73f933aee1c3a37c8b44b889a7 in branch sdk-v2.0.x ? On Tue, Sep 27, 2016 at 9:50 AM, Anicic Damir (PSI) wrote: > Hi again, > > it seems no one has interests in my problem. > > I have the same problem with Ubuntu host

Re: [yocto] fetcher failure

2016-09-27 Thread Anicic Damir (PSI)
Hi again, it seems no one has interests in my problem. I have the same problem with Ubuntu host build, too. What I see is that file gets downloaded several times, and then discarded for some reason. One of the last downloads (or the last one), does some git -c core.fsyncobjectfiles=0 fetch

[yocto] fetcher failure

2016-09-26 Thread Anicic Damir (PSI)
Hi, Yocto 2.1 Trying to switch from yocto default linux-yocto to freescale linux-qoriq but getting fetcher failure: $ bitbake core-image-psi-gfa-cmd NOTE: Unable to use interactive mode for this terminal, using fallback WARNING: Host distribution "Scientific-6.4" has not been validated with

Re: [yocto] Fetcher failure

2016-09-14 Thread Daniel.
You're welcome :) 2016-09-14 11:50 GMT-03:00 Burton, Ross : > > On 14 September 2016 at 15:48, Anicic Damir (PSI) > wrote: >> >> it turns out that something HAS changed in my system/libraries (but not >> Python itself), >> influencing python urllib2 to

Re: [yocto] Fetcher failure

2016-09-14 Thread Burton, Ross
On 14 September 2016 at 15:48, Anicic Damir (PSI) wrote: > it turns out that something HAS changed in my system/libraries (but not > Python itself), > influencing python urllib2 to fail, although wget, chrome, firefox, ... > worked > > Fortunately we have another python

Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
Thanx all for a help, I have tested with: python -c 'import urllib2; print urllib2.urlopen. The problem was only with https protocol, http worked. The certificate was not accepted (SSL, as used by bitbake wget.py), but with TLS it worked. it turns out that something HAS changed in my

Re: [yocto] Fetcher failure

2016-09-14 Thread Daniel.
try: python -c 'import urllib; print urllib.urlopen("http://www.example.com;).read()' I'm running out of ideias :). I already had received "Connection reset by peer" because dupplicate IPs on network. Regards, 2016-09-14 9:58 GMT-03:00 Anicic Damir (PSI) : > Ups, typo. > >

Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
Ups, typo. It also works wget https://www.example.com/ --2016-09-14 14:58:03-- https://www.example.com/ Resolving www.example.com... 93.184.216.34, 2606:2800:220:1:248:1893:25c8:1946 Connecting to www.example.com|93.184.216.34|:443... connected. HTTP request sent, awaiting response... 200 OK

Re: [yocto] Fetcher failure

2016-09-14 Thread Burton, Ross
On 14 September 2016 at 13:42, Anicic Damir (PSI) wrote: > wget https://www.exampe.com/ > --2016-09-14 14:42:39-- https://www.exampe.com/ > Resolving www.exampe.com... 69.172.201.153 > Connecting to www.exampe.com|69.172.201.153|:443... connected. > Unable to establish SSL

Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
This works: wget http://www.exampe.com/ --2016-09-14 14:42:23-- http://www.exampe.com/ Resolving www.exampe.com... 69.172.201.153 Connecting to www.exampe.com|69.172.201.153|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: “index.html.1”

Re: [yocto] Fetcher failure

2016-09-14 Thread Daniel.
Can you connect to "www.example.com" from command line?! Something like `telnet www.example.com 80' !?!? 2016-09-14 9:27 GMT-03:00 Anicic Damir (PSI) : > Sorry, the error message is: > >DEBUG: checkstatus() urlopen failed: Connection reset by peer> > > > -- >

Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
Sorry, the error message is: DEBUG: checkstatus() urlopen failed: -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
No, I have direct internet connection, no proxy needed (and was not needed before). Temporarily I use CONNECTIVITY_CHECK_URIS="" in local.conf That way it works again, but I would like to have better solution. After investigating little bit more, I see an error: Fetcher failure for URL:

Re: [yocto] Fetcher failure

2016-09-14 Thread Burton, Ross
On 14 September 2016 at 08:52, Anicic Damir (PSI) wrote: > Fetcher failure for URL: 'https://www.example.com/'. URL > https://www.example.com/ doesn't work. Please ensure your network is > configured correctly. > This is the "is networking correctly configured" test,

[yocto] Fetcher failure

2016-09-14 Thread Anicic Damir (PSI)
Hi, Yocto 2.1: I had working setup, and wanted to rebuild. I am quite sure that I did not change anything, and suddenly it does not work any more: Fetcher failure for URL: 'https://www.example.com/'. URL https://www.example.com/ doesn't work. Please ensure your network is configured

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

2016-04-26 Thread Zhenhua Luo
o-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Bruce Ashfield > Sent: Tuesday, April 26, 2016 10:11 AM > To: Jaggi, Manish <manish.ja...@caviumnetworks.com>; Burton, Ross > <ross.bur...@intel.com> > Cc: yocto@yoctoproject.org > Subject:

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

2016-04-26 Thread Jaggi, Manish
works.com>; Burton, Ross > <ross.bur...@intel.com> > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Fetcher failure: Unable to find revision > 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from > upstrea

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

2016-04-25 Thread Bruce Ashfield
On 2016-04-25 9:05 PM, Jaggi, Manish wrote: From: Bruce Ashfield [bruce.ashfi...@windriver.com] Sent: Monday, April 25, 2016 11:04 PM To: Jaggi, Manish; Burton, Ross Cc: yocto@yoctoproject.org Subject: Re: [yocto] Fetcher failure: Unable to find revision

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

2016-04-25 Thread Jaggi, Manish
From: Bruce Ashfield [bruce.ashfi...@windriver.com] Sent: Monday, April 25, 2016 11:04 PM To: Jaggi, Manish; Burton, Ross Cc: yocto@yoctoproject.org Subject: Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

2016-04-25 Thread Bruce Ashfield
On 2016-04-25 12:10 PM, Jaggi, Manish wrote: *From:* Burton, Ross <ross.bur...@intel.com> *Sent:* Monday, April 25, 2016 8:12 PM *To:* Jaggi, Manish *Cc:* yocto@yoctoproject.org *Subject:* Re: [yocto] Fetcher f

Re: [yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

2016-04-25 Thread Burton, Ross
On 25 April 2016 at 14:30, Jaggi, Manish wrote: > It seems the revid / tag is not on any branch > git branch --contains 2134d97aa3a7ce38bb51f933f2e20cafde371085 > returns nothing. > > How to fix this issue ? > You probably want to use git branch -r --contains

[yocto] Fetcher failure: Unable to find revision 2134d97aa3a7ce38bb51f933f2e20cafde371085 in branch master even from upstream

2016-04-25 Thread Jaggi, Manish
In my bb file I added the below line, SRCREV = "2134d97aa3a7ce38bb51f933f2e20cafde371085" SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev" The revision id is of v4.4.3 tag. Below errors are generated upon kernel fetching ERROR: linux-4.4 do_fetch: Fetcher failure: Unable to find

[yocto] Fetcher failure for git repository using tag name in SRCREV

2014-07-07 Thread Richard Leitner
Hi folks, I've ran into a problem using tag names in SRCREV for git repositories after migrating from 1.4 to 1.6.1 daisy. Before (1.4) the following worked fine: SRCREV = v${PV} SRC_URI = git://github.com/rleitner/psplash.git;protocol=https When using 1.6.1 the following error

[yocto] Fetcher failure for mercurial repos: 'unknown revision' due to -r SRCREV in both clone and update?

2012-12-03 Thread Jon Szymaniak
I've been running into Fetcher failures for my recipes using mercurial recently. They only seem to crop up the first time a package that comes from a hg repo is fetched. I believe the issue stems from the combination of the arguments used by the hg fetcher and the fact that I specified a tag

[yocto] Fetcher failure for URL: 'http://download.oracle.com/berkeley-db/db-5.3.15.tar.gz

2012-06-17 Thread Robert P. J. Day
gr ... after four beers, that's all you're getting out of me. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: