I'm do not agree with this e2 patch because it impress a fake safety when auth is on...
merge requests for PLi's git
Started by Persian Prince, 16 Apr 2013 12:12
1748 replies to this topic
Re: merge requests for PLi's git #921
-
- PLi® Core member
- 56,297 posts
+691
Excellent
Posted 23 November 2016 - 19:01
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: merge requests for PLi's git #922
-
- PLi® Core member
- 68,676 posts
+1,740
Excellent
Posted 23 November 2016 - 20:58
I suggest that for the time being, we should pin the OWIF for OpenPLi 4 on a stable commit hash. The longer we allow "unstable" code into OpenPLi 4, the longer it takes before we can move on to OpenPLi 5.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: merge requests for PLi's git #923
-
- PLi® Core member
- 56,297 posts
+691
Excellent
Posted 24 November 2016 - 08:54
WanWizard... I think this is a good plan... Pin the OWIF to a few days ago for OpenPLi4... and avoid to put more energy to keep OpenPLi4 running on new steps forward.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: merge requests for PLi's git #924
-
- PLi® Core member
- 68,676 posts
+1,740
Excellent
Posted 24 November 2016 - 12:10
Since nobody bothered to react in time, the question is now if we can still pin it, as it will mean a downgrade, which is difficult in opkg.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: merge requests for PLi's git #925
-
- PLi® Core member
- 56,297 posts
+691
Excellent
Posted 24 November 2016 - 13:33
I'm afraid we're to late... we can upgrade... but not downgrade...
Athoik posted an Ipk for the missing package. When the 3rd party feed kan 'hold' it this might be a way to go....
or we are very simple and not complicated... add the package in the same way oe-a did.... why should we keep openpli4 that clean?
Edited by littlesat, 24 November 2016 - 13:36.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: merge requests for PLi's git #926
-
- PLi® Core member
- 2,269 posts
+118
Excellent
Posted 24 November 2016 - 14:35
...
or we are very simple and not complicated... add the package in the same way oe-a did.... why should we keep openpli4 that clean?
I have no idea why we shouldn't simply add this python-ipaddress to the feed and call it a day...
it's a standard python package, included in openembedded, and it has nothing to do with openpli cleanliness, polluting, nor anything like this
True sarcasm doesn't need green font...
Re: merge requests for PLi's git #927
-
- Senior Member
- 1,030 posts
+65
Good
Posted 24 November 2016 - 16:50
Exactly.
And nothing is cleaner than just adding the plain standard package to the feed.
In contrast, I consider all those bbappend and versions kept down in other layers the pollution.
In a perfect world, the openpli or oe-a layers would contain nothing but enigma2 and plugins.
And nothing is cleaner than just adding the plain standard package to the feed.
In contrast, I consider all those bbappend and versions kept down in other layers the pollution.
In a perfect world, the openpli or oe-a layers would contain nothing but enigma2 and plugins.
1st box: Vu+ Ultimo 4k 4xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390
Re: merge requests for PLi's git #928
-
- PLi® Core member
- 68,676 posts
+1,740
Excellent
Posted 24 November 2016 - 17:05
@blzr can you prepare a PR for it (or ask Athoik for it)? I agree it is much cleaner that adding a 'native' ipk to a third party feed.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: merge requests for PLi's git #929
-
- Senior Member
- 1,030 posts
+65
Good
Posted 24 November 2016 - 17:20
1st box: Vu+ Ultimo 4k 4xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390
Re: merge requests for PLi's git #930
-
- PLi® Core member
- 68,676 posts
+1,740
Excellent
Posted 24 November 2016 - 17:22
Merged. My gratitude borders on ridiculous... 
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: merge requests for PLi's git #931
-
- Senior Member
- 1,030 posts
+65
Good
Posted 24 November 2016 - 17:26
I just wonder why you need a pull request for that 
Is it so that you have someone to blame if it doesn't work?
Is it so that you have someone to blame if it doesn't work?
1st box: Vu+ Ultimo 4k 4xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390
Re: merge requests for PLi's git #932
-
- PLi® Core member
- 10,039 posts
+339
Excellent
Posted 24 November 2016 - 17:40
Done: https://github.com/O...nigma2/pull/537
Info: Optipng is doing a great job for optimizing png files but it seems libpng >=1.6.x cares about iCCP chunk so we could easily remove all meta data from all png files for future warnings.
Also we would have smaller png files after this.
Revert more "optimized" png files.
why?
GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K
Re: merge requests for PLi's git #933
-
- PLi® Core member
- 2,344 posts
+120
Excellent
Posted 24 November 2016 - 22:30
I just wonder why you need a pull request for that
Is it so that you have someone to blame if it doesn't work?
No, but before to change something someone needs to check if it would work, rather than blindly offer changes.
For example in this case this commit breaks master branch building, because the master branch used the meta-openembedded srev, in which is not yet added python-ipaddress.
Re: merge requests for PLi's git #934
-
- PLi® Core member
- 68,676 posts
+1,740
Excellent
Posted 24 November 2016 - 22:31
I just wonder why you need a pull request for that
No, it's because I'm clueless when it comes to OE and bitbake. So I won't even know where to start. And there was nobody in the team available with time to address it.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: merge requests for PLi's git #935
-
- Senior Member
- 1,531 posts
+118
Excellent
Posted 24 November 2016 - 22:36
I've added python-ipaddress and the required class from master-next to PLi4 and it works fine.
Re: merge requests for PLi's git #936
-
- Senior Member
- 1,030 posts
+65
Good
Posted 24 November 2016 - 23:17
I've told multiple times that I have no OpenPLi build-environment and can not check anything there.No, but before to change something someone needs to check if it would work, rather than blindly offer changes.
For example in this case this commit breaks master branch building, because the master branch used the meta-openembedded srev, in which is not yet added python-ipaddress.
But PLi keeps asking for PRs for whatever one suggests
But:
JFK, how outdated is the PLi build env?
It's already a shame that it was VTi who had it on their feed first and not oe-a ... but that the PLi build env couldn't even build it ... OMG ...
1st box: Vu+ Ultimo 4k 4xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390
2nd box: Gigablue Quad 4k 2xDVB-S2 FBC / 2xDVB-C / 1.8 TB HDD / OpenATV 6.2
testing boxes: Vu+ Duo² + AX Quadbox HD2400 + 2x Vu+ Solo² + Octagon SF4008
Sats & Pay-TV: Astra 19.2°E + Hotbird 13°E with Redlight / SCT HD / SES Astra HD- / Sky V14 / 4th empire propaganda TV
Card-Server: Raspberry Pi + IPv6-capable oscam
Router: Linksys WRT1900ACS w/ LEDE + Fritz!Box 7390
Re: merge requests for PLi's git #937
-
- PLi® Core member
- 68,676 posts
+1,740
Excellent
Posted 24 November 2016 - 23:19
The current OpenPLi 4 environment is ANCIENT. We should have been on 5 or 6 by now, but due to lots of reasons that hasn't happened yet. We're trying very hard to pick up the pace though, and get OpenPLi 5 out.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: merge requests for PLi's git #938
-
- Senior Member
- 1,982 posts
+247
Excellent
Posted 27 November 2016 - 12:27
Again for "E2OpenPlugins" :
https://github.com/E...ienradar/pull/1
"Delete png meta data for libpng >=1.6.x iCCP chunk warning"
Good luck
Open Vision sources: https://github.com/OpenVisionE2
Re: merge requests for PLi's git #939
-
- Senior Member
- 7,766 posts
+184
Excellent
Posted 27 November 2016 - 13:14
Be aware that we had to revert a lot of those 'enhancements' in the OE-A environment, as the result was not that good 
Re: merge requests for PLi's git #940
-
- Senior Member
- 1,982 posts
+247
Excellent
Posted 27 November 2016 - 13:18
Deleting meta data and optimizing are 2 different things and about optimizing I said this before :
Optimizing png files will reduce the image size.
Also we need to conisder two things about HD skins :
1- Do we want less image size ?
2- Do we want 32-bit pngs ?
The answer to the first question is optimizing.
About other things like plugins ... we can optimize without consider anything.
I did this in my fork and I'm using it, You can ignore it if you don't want to reduce the image size when you can
It's a contribution anyway.
Open Vision sources: https://github.com/OpenVisionE2
1 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
-
Bing (1)
