Jump to content


Photo

merge requests for PLi's git


  • Please log in to reply
1748 replies to this topic

Re: merge requests for PLi's git #681 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 30 November 2014 - 23:17

Why handle service name on layout finished here?

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: merge requests for PLi's git #682 herpoi

  • Member
  • 15 posts

+1
Neutral

Posted 1 December 2014 - 10:45

I am not an expert in programming. Maybe this way will be better.

Attached Files



Re: merge requests for PLi's git #683 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 December 2014 - 18:52

Fix for delsys detection issue on machines with kernel<3.3 and latest linux-libc-headers.
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: merge requests for PLi's git #684 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 7 December 2014 - 19:04

Applied :)


* 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: merge requests for PLi's git #685 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 December 2014 - 19:59

Applied :)


Maybe sf.net has cached data, I cannot see changes :(
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: merge requests for PLi's git #686 theparasol

  • Senior Member
  • 4,157 posts

+198
Excellent

Posted 7 December 2014 - 20:33

I get the following when I try to access sourceforge right now:

 


The sourceforge.net website is temporarily in static offline mode.
Only a very limited set of project pages are available until the main website returns to service.

@Camping: ZGemma H.2S, Technisat Multytenne 4-in-1 @Home: Edision Mini 4K, Wave Frontier T55, EMP Centauri EMP DiSEqC 8/1 switch, 4x Inverto Ultra Black single LNB


Re: merge requests for PLi's git #687 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 7 December 2014 - 20:36

fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To ssh://littlesat@git.code.sf.net/p/openpli/enigma2
 ! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to 'ssh://littlesat@git.code.sf.net/p/openpli/en
igma2'

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: merge requests for PLi's git #688 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 December 2014 - 22:40

I think it is up now!
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: merge requests for PLi's git #689 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 8 December 2014 - 11:12

Hello,

 

Yesterday afternoon I was not home. So I could not do what You asked into :

 

http://forums.openpl...a-dm8000/page-2

 

But lucky De Beeker did it.

 

Now to day a did a git reset upgrade and resync.

 

Build for dm8000. Build OK . With libc-headers 3.16. Flash ok start enigma ok. Unfortunately no dvb-s channels. Which means that You're latest patches are not applied to git.

 

I then inserted the patches by enigma2 and modified the enigma2.bb file to applied them increased rev so its rebuild and especially ipk ver is increased so that box is updated. Rebuild for dm8000 build ok. Just updated my box. Update ok. Restarted dm8000.

 

Start ok and it works now ok. All channels dvb-S2 and dvb-S.



Re: merge requests for PLi's git #690 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 8 December 2014 - 11:21

 

Applied :)


Maybe sf.net has cached data, I cannot see changes :(

Reads: screwup by me :( Forgot to push! I have done many pushes yesterday and of course forgot the most important one :( Well now it IS pushed!


* 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: merge requests for PLi's git #691 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 8 December 2014 - 11:22

 

fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To ssh://littlesat@git.code.sf.net/p/openpli/enigma2
 ! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to 'ssh://littlesat@git.code.sf.net/p/openpli/en
igma2'

That may mean that you're out of sync and that you need to pull first.


* 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: merge requests for PLi's git #692 littlesat

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 8 December 2014 - 12:15

I w you forgot this one... SoI tried it and then I get this.... But solved in between,,,.

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: merge requests for PLi's git #693 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 8 December 2014 - 12:19

Yes, that's because you're out of sync ;) Do a pull first. If you have the patches in local branch committed, do this:

 

$ git log origin

note the last commit hash (HEAD)

$ git reset --hard <HEAD commit hash from remote>

$ git pull

 

Then you're in sync again (and the superfluous commits are gone).

 

This can done probably smarter without having to note the remote HEAD commit hash, but I am too lazy to find out ;))


* 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: merge requests for PLi's git #694 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 8 December 2014 - 12:22

Hallo, Just Ter info.

 

Just cleaned out git again (reset repull and resync)

 

Removed enigma2 from build for my two machines (vuduo2 and dm8000).

 

Builde again dm8000 and vuduo2 build ok and this time much faster less rebuilds (almost none) when building for the second machine .

That was the goal I gues wel and it woks very good :)

 

For the dm8000 trough telnet I first did update, then forced reinstall off enigma2 (since previousely i installed r50 with the manual modified git to have athoiks patch applied). Now it's back as the standard git with r49. Then did an upgrade trough remote control.

All ok on dm8000 with standard git now :)

 

Updated vuduo2 . All ok with standard git now.

 

Gues the label condition is over now .

 

Thank's team :) :) :)



Re: merge requests for PLi's git #695 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 8 December 2014 - 12:24

This can done probably smarter without having to note the remote HEAD commit hash, but I am too lazy to find out ;))

 

Did you try?

git reset --hard origin/HEAD

Edited by athoik, 8 December 2014 - 12:25.

Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: merge requests for PLi's git #696 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 8 December 2014 - 12:27

Just a small typ , gues You now that.

 

Best remove with cleanall the packages :

openpli-oe-core/meta-openpli/recipes-openpli/enigma2-softcams/enigma2-plugin-softcams-scam_3.53.bb -f -c cleanall
openpli-oe-core/openembedded-core/meta/recipes-extended/cups/cups_2.0.0.bb -f -c cleanall
openpli-oe-core/openembedded-core/meta/recipes-devtools/python/python-pycurl_7.19.5.bb -f -c cleanall
openpli-oe-core/meta-openpli/recipes-connectivity/samba/samba_3.0.37.bb -f -c cleanall

Before next nightly build for all machines, These where affected by that rebuild due to libc headers change.

 

Then I gues almost shure next nightly build will be 100 % fine for all machines



Re: merge requests for PLi's git #697 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 8 December 2014 - 12:27

@Athoik

 

Yes exactly, something like that, guess exactly how lazy I am :)


* 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: merge requests for PLi's git #698 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 8 December 2014 - 12:33

Fix for delsys detection issue on machines with kernel<3.3 and latest linux-libc-headers.


Lots of code in e2 depends on the dvb api version.
Most of those things cannot be runtime-detected.

An alternative solution might be to stage the dvb headers from the kernel, instead of using the linux-libc-headers.
e2 happens to be closely tied to the dvb-core, and almost every new kernel release changes something in the dvb api.

the delsys enum might be solved now, but there is a lot more. (grep for DVB_API_VERSION)

Re: merge requests for PLi's git #699 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 8 December 2014 - 12:39

Or we can build enigma2 as a (fake) kernel module in order to use correct headers :P


Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: merge requests for PLi's git #700 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 8 December 2014 - 12:41

the only relevant difference in this case is the include path, and the dependency




43 user(s) are reading this topic

0 members, 43 guests, 0 anonymous users