Jump to content


Photo

PLI4.0 does not build anymore due to broken svn fetcher.


  • Please log in to reply
50 replies to this topic

#1 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 23 July 2014 - 16:27

Hello with my to days pli4.0 bitbake update all  http protocol based svn do not fetch anymore due to broken fetcher into bitbake.

 

The base system fetchter is ok. Ubuntu 14.04 subversion svn . It seems that the current bitbake in openpli does not use system fetcher but an uncomplete build in fetcher which can't handle http:protocol svn fetching.

 

Could be solvable(using svn sytem fetcher) with conf adaptation somewhere but do not now wich?

 

Message received.

 

In this case its oscam (but website is ok and base system fetcher ok.)

 

Which works perfect whitout bitbake is

 

 

svn co http://streamboard.tv/svn/oscam/trunk

 

ok latest trunk fetched.

 

In to bitbake file

 

SRCREV = "9077"
PV = "svn${SRCREV}"
PKGV = "${PV}"
SRC_URI = "svn://www.streamboard.tv/svn/oscam;protocol=http;module=trunk"

 

Does not work anymore

 

error issued:

 

WARNING: Failed to fetch URL svn://streamboard.tv/svn/oscam;module=trunk;protocol=http, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 1, output:
svn: E170000: Unrecognized URL scheme for 'http://streamboard.tv/svn/oscam/trunk'

But the website is really ok.

 

The svn: E170000  is an error comming from webdav cause the subversion does not support neon. My base system does , it's the used bitbake coming with the latest openembedded bitbake which fails.

 

I now just showed the way how it is done in base pli4.0 softcams. But to have the latest trunk anyway the bb file must be.

 

SRCREV ?= "${AUTOREV}"  # unless You wan't a fix trunk you can put the trunk you wan't this is not the cause.
PV = "svn${SRCPV}" # this must normaly be used instead off SRCREV 
PKGV = "${PV}"
SRC_URI = "svn://www.streamboard.tv/svn/oscam;protocol=http;module=trunk;scmdata=keep"  # scm data keep to have rev number in web if.

 

But the latest update has a problem with svn fetcher and off course ${AUTOREV} will even put more errors due to this problem.

 

This problem will in time cause the longer the more problems for the whole pli4.0 project. Now for this specific example there will be no problems yet with build server since the fixed 9077 is fetched and in sources. But as soon you change that problems will occur. Also for all other svn packages depending on http:protocol the problems will come in future.

 

It is a problem with latest bitbake update by openpli4.0.

 

 

 

 

 



Re: PLI4.0 does not build anymore due to broken svn fetcher. #2 MiLo

  • PLi® Core member
  • 14,042 posts

+298
Excellent

Posted 23 July 2014 - 19:27

Remove the "protocol=http" directive from the URL.
Real musicians never die - they just decompose

Re: PLI4.0 does not build anymore due to broken svn fetcher. #3 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 23 July 2014 - 19:53

I tried but still it does not work.

 

What work's whitout problem is the standard

 

svn co http://streamboard.tv/svn/oscam/trunk (it's not the website)

 

Whithout protocol=http

SRC_URI = "svn://streamboard.tv/svn/oscam;module=trunk"  also tried

SRC_URI = "svn://www.streamboard.tv/svn/oscam;module=trunk"

 

WARNING: Failed to fetch URL svn://streamboard.tv/svn/oscam;module=trunk;scmdata=keep, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 1, output:
svn: E000111: Unable to connect to a repository at URL 'svn://streamboard.tv/svn/oscam/trunk'
svn: E000111: Can't connect to host 'streamboard.tv': Connection refused
 

With protocol=http

SRC_URI = "svn://streamboard.tv/svn/oscam;module=trunk;protocol=http"

SRC_URI = "svn://www.streamboard.tv/svn/oscam;module=trunk;protocol=http"

 

WARNING: Failed to fetch URL svn://streamboard.tv/svn/oscam;module=trunk;protocol=http, attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 1, output:
svn: E170000: Unrecognized URL scheme for 'http://www.streamboa...svn/oscam/trunk'

 

seems related to bitbake version 1.23.1 instead off 1.23 like before.
 



Re: PLI4.0 does not build anymore due to broken svn fetcher. #4 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 24 July 2014 - 09:01

By using the system svn fetcher problems solved.

 

I just removed all the svn* out off openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin

 

Then it works.

 

The real cause is not found yet what I did is just a hack.



Re: PLI4.0 does not build anymore due to broken svn fetcher. #5 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 24 July 2014 - 13:01

As far info I could retrieve (very few about this) It could be related due to to old subversion not compatible with apache anymore.

 

Still under investigation.

 

anyway removing the svn from out off openpli-oe-core/build/tmp/sysroots/x86_64-linux/usr/bin does work but only good as temporary hack (work-around). It will use the base system svn (if installed)



Re: PLI4.0 does not build anymore due to broken svn fetcher. #6 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 July 2014 - 12:08

Now it is confirmed,

svn is just compiled without neon support which just makes it virtual usseles. It even would be better to exclude it att all. Then system subversion is used. Or disabling the neon version check does work also. Whatever is done with version check it always requires neon 0.29.6 . The patch to add 0.30.0 does not have any effect.

 

However disabling version check by subversion for neon is not the best way. In this integrated openembedded-oe it's not a problem. as native neon 0.30.0 is build and ok.



Re: PLI4.0 does not build anymore due to broken svn fetcher. #7 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 July 2014 - 13:15

Here the solution.

 

It is for openembedded self . No it's not a patch.

 

On a already existing latest build first a couple off cleaning needs to be done. This are.

 

MACHINE=vuduo2 bitbake -b virtual:native:$HOME/openpli40/openpli-oe-core/meta-local/recipes-local/subversion/subversion_1.7.17.bb -f -c cleanall
MACHINE=vuduo2 bitbake -b $HOME/openpli40/openpli-oe-core/meta-local/recipes-local/subversion/subversion_1.7.17.bb -f -c cleanall
MACHINE=vuduo2 bitbake -b virtual:native:$HOME/openpli40/openpli-oe-core/openembedded-core/meta/recipes-support/neon/neon_0.30.0.bb -f -c cleanall
MACHINE=vuduo2 bitbake -b $HOME/openpli40/openpli-oe-core/openembedded-core/meta/recipes-support/neon/neon_0.30.0.bb -f -c cleanall
MACHINE=vuduo2 bitbake -c cleanall openpli-enigma2-image

Modifie the recipes with the includded file over here.

 

I did not set cve patch by subversion , I'm not shure but by version 1.7.17 this should not be needed anymore.

 

The neon version check is disabled by build off subversion.

 

The neon-config build is not inherited anymore by neon build. It is required for the build off subversion.

 

It's evident this is core bussines, should be discussed with openembedded-oe core dev's.

 

 

 

 

 

 

Attached Files



Re: PLI4.0 does not build anymore due to broken svn fetcher. #8 MiLo

  • PLi® Core member
  • 14,042 posts

+298
Excellent

Posted 25 July 2014 - 16:26

Upgrade the openembedded-core, meta-oe and bitbake directories to current master.

If you can still reproduce the problem then, create a patch (for oe-core itself) with a detailed description of the problem and your solution.

Send the patch to
openembedded-core@lists.openembedded.org

You can post the patch here, but it'll take much longer for it to be submitted then.

If upgrading solves the problem, then upgrading is enough, just tell us so...
Real musicians never die - they just decompose

Re: PLI4.0 does not build anymore due to broken svn fetcher. #9 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 July 2014 - 18:12

Ok I have here the final patch for openembedded core versus the latest update You did.

 

Just one small change is needed . That is by neon_0.30.0.bb file.

The inherit binconfig-disabled must be removed since neon-config script is needed in order to compile subversion with neon to have http svn fetch support.

 

Do I have to set more info in a mail I send to them ?

 

 

Attached Files



Re: PLI4.0 does not build anymore due to broken svn fetcher. #10 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 July 2014 - 18:36

I sended the patch file to openembedded-core@lists.openembedded.org



Re: PLI4.0 does not build anymore due to broken svn fetcher. #11 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 July 2014 - 22:24

Hello just checked,

 

The openembedded-core has already subversion_1.8.9

 

done on commit 7 days ago

 

http://cgit.openembe...446e496ad093763

 

In openpli it is still and older openembedded-core.

 

by subversion_1.8.9 neon support and need is dropped but serf is used and that is added to openmbedded-core.

 

Oeps now I saw yes sorry You asked to test with an own downloaded openembedded-core. I first understand that you just had updated the openpli-4.0 with the latest openembedded-master.

 

I'll check with own latest openembedded



Re: PLI4.0 does not build anymore due to broken svn fetcher. #12 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 25 July 2014 - 23:51

but updating to the latest core master of openembedded-core will have again a lot to adapt.

 

Now I do not have time but when I have , I will restart a build from scratch and see.

 

Perhaps just adding subversion_1.8.9 and serf could be more practical.



Re: PLI4.0 does not build anymore due to broken svn fetcher. #13 MiLo

  • PLi® Core member
  • 14,042 posts

+298
Excellent

Posted 26 July 2014 - 09:30

We're just a few weeks behind, so I wouldn't expect much work from upgrading (apart from build time)
Real musicians never die - they just decompose

Re: PLI4.0 does not build anymore due to broken svn fetcher. #14 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 26 July 2014 - 09:48

I have built vuduo2 from scratch a few days ago, no fetchting problems.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: PLI4.0 does not build anymore due to broken svn fetcher. #15 MiLo

  • PLi® Core member
  • 14,042 posts

+298
Excellent

Posted 26 July 2014 - 10:33

If you pull the "master-next" branch, that should compile the version with today's OE state. There were a few minor things that I could see.

My old quad-core Phenom@4GHz is chewing on it now, so I don't know yet what else we might encounter.
Real musicians never die - they just decompose

Re: PLI4.0 does not build anymore due to broken svn fetcher. #16 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 26 July 2014 - 15:43

I have built vuduo2 from scratch a few days ago, no fetchting problems.

Yes first all the svn recipes present have been changed to fixed rev, So a first revision check does not occur. If the specific repo was already present in you're source directory (and you did not used cleanall as this would also removed the obtained sources) The fetcher did not need to try to fetch , result ok. An it builds the package normally since fetching was already done. From the moment you need to fetch (http protocol svn). It did not worked out. And the reamaining packages who are using svn all needs the http protocol.

 

I will now erase everything and build from scratch but with latest openembedded-core masterI already test, the build did not finished complete but the svn was ok with the subversion 1.8.9 which is using serf instead of neon.It was actually not a smart move to remove the neon-config script Since all package who needs neon needs this file to config ok.by build. Think there will be only one package with will need adaptation. it's a bp.append somewhere .

 

That I will now see with a fresh build from scratch. for vuduo2.



Re: PLI4.0 does not build anymore due to broken svn fetcher. #17 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 26 July 2014 - 15:53

Eh yes indeed, I didn't remove the sources directory of course.

* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: PLI4.0 does not build anymore due to broken svn fetcher. #18 MiLo

  • PLi® Core member
  • 14,042 posts

+298
Excellent

Posted 26 July 2014 - 16:21

I cooked up a master-next branch that builds an image just fine. That should fix the SVN fetch problems.
A few minor tweaks were needed which I backported to the master branch because they were mistakes in the recipes to begin with.
Real musicians never die - they just decompose

Re: PLI4.0 does not build anymore due to broken svn fetcher. #19 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 26 July 2014 - 16:52

Eh yes indeed, I didn't remove the sources directory of course.

 Yes off course it's normal :P . I tried to explain what went wrong in a few rules for something I needed 2 days of research work. And (explaining is not my strongest point) :unsure:



Re: PLI4.0 does not build anymore due to broken svn fetcher. #20 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 26 July 2014 - 16:54

I cooked up a master-next branch that builds an image just fine. That should fix the SVN fetch problems.
A few minor tweaks were needed which I backported to the master branch because they were mistakes in the recipes to begin with.

My fresh off scratch build is now bussy (for vuduo2). I just replaced the openembedded-core off pli by the master off Yesterday evening.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users