121 replies to this topic

[samsamsam]

It will take some time because I first must compile toolchain and make some fixes for IPTVPlayer.

Please be patient.

 

Regards,

SSS

[WanWizard]

@WanWizard

 

I do not ask you for anything.

Users of your softwares wait long enough.

 

I will prepare binary patch. You will do not need to do anything If you don't like users.

 

No need for a response like this.

 

OpenPLi 4 is being pinned to stable at the moment, which means it will not be updated anymore pending a last and final release, after which the next version will become available (based on develop), which has a newer Python version, and no issues with SSL.

[samsamsam]

 

@WanWizard

 

I do not ask you for anything.

Users of your softwares wait long enough.

 

I will prepare binary patch. You will do not need to do anything If you don't like users.

 

No need for a response like this.

 

OpenPLi 4 is being pinned to stable at the moment, which means it will not be updated anymore pending a last and final release, after which the next version will become available (based on develop), which has a newer Python version, and no issues with SSL.

 

 

This post does not contribute anything. Why do you write the same thing again?

[athoik]

We are working so hard to prepare a new stable version...

The idea is not to make normal users (beta) testers.

All our public work is already used by ALL others, immediately, while fixes from others are never coming back.

Anyway, lets hope that develop version will become available soon from our page.

[samsamsam]

@doubledip

 

I prepared patch for you  

http://iptvplayer.pl...ni_patch.tar.gz

 

Installation:

# backup
cp /usr/lib/python2.7/ssl.py /usr/lib/python2.7/ssl.py_backup
cp /usr/lib/python2.7/lib-dynload/_ssl.so /usr/lib/python2.7/lib-dynload/_ssl.so_backup
cp /usr/lib/python2.7/httplib.py /usr/lib/python2.7/httplib.py_backup
 
# installation
cd /tmp
wget http://iptvplayer.pl/resources/python2.7.3_mipsel_fpu_soft_openssl1.0.2_sni_patch.tar.gz
tar -xvf python2.7.3_mipsel_fpu_soft_openssl1.0.2_sni_patch.tar.gz -C /
rm python2.7.3_mipsel_fpu_soft_openssl1.0.2_sni_patch.tar.gz
sync
reboot
reboot -f

Please be noted that this patch has not been tested. So, please test it and give respond.

 

How to test? After reboot load to console and execute following command:

wget iptvplayer.pl/temp/python_sni_test.py -O - | python2.7 

 

Regards,

SSS

Edited by samsamsam, 20 May 2017 - 21:28.

[samsamsam]

@athoik

 

You exactly know how old this bug is. It has been fixed a long time ago.

It is really no, so hard to make backport several lines of code.

 

But let's be honest, you even not checked how fix looks. Am I correct?

 

Such phrases like you wrote "We are working so hard" do not change anything.

Interesting what you will say in similar situation: "debian developers say, we will fix this bug in next release. You need wait about one year."

What do you think?

Edited by samsamsam, 20 May 2017 - 21:36.

[WanWizard]

What part of "will not be updated anymore pending a last and final release" isn't clear to you?

 

You can't compare it to Debian, it uses a different release mechanism. A mechanism we are going to use as well, as of the next version. For that, a lot of preparation needs to happen, which we are very busy with, and which eats up all our free time.

[samsamsam]

@WanWizard

 

What part of "I do not ask you for anything." isn't clear to you?

[doubledip]

@samsamsam

 

SNI is working

 

Great work!

Edited by doubledip, 20 May 2017 - 21:56.

[samsamsam]

@doubledip

 

No problem

[samsamsam]

If someone is interested I prepared package for:

- mipsel

- hard float

- python 2.7.3

 

Package is available here:

http://iptvplayer.pl/resources/python2.7.3_mipsel_fpu_hard_openssl1.0.2_sni_patch.tar.gz

http://iptvplayer.pl...ni_patch.tar.gz

 

Regards,

SSS

[athoik]

@athoik
 
You exactly know how old this bug is. It has been fixed a long time ago.
It is really no, so hard to make backport several lines of code.
 
But let's be honest, you even not checked how fix looks. Am I correct?
 
Such phrases like you wrote "We are working so hard" do not change anything.
Interesting what you will say in similar situation: "debian developers say, we will fix this bug in next release. You need wait about one year."
What do you think?

It think you should offer a patch on our OE.

You already checked the python bug https://bugs.python.org/issue5639 and got the patch that adds SNI support from there.

So you are at 50% add the patch to python_2.3.7.bbappend, change PV to r5.4 and create a PR and you are 100%.

[samsamsam]

You finally checked how the patch looks? Better late than never.

You know that OpenPLI behaves very ridiculously?

 

@WanWizard say:

 

What part of "will not be updated anymore pending a last and final release" isn't clear to you?

 

You can't compare it to Debian, it uses a different release mechanism. A mechanism we are going to use as well, as of the next version. For that, a lot of preparation needs to happen, which we are very busy with, and which eats up all our free time.

 

Also next time it will be better for you to look closer what patch contain. For example please check httplib.py.

 

And no. I do not plan to add anything to this very strange build system.

I even not use OpenPLI, so at first you should say thank you, because I show you that this patch is very easy to be backported and it is not invasive, so it can be integrated without fear of system stability. 

 

I spent my free time to help users of your image. I did not have to, but I do this.

Did you say thank you? No!

You prefer to teach me what I should. 

You are naughty and ungrateful. Very bad behavior. Consider yourself.

Edited by samsamsam, 21 May 2017 - 08:19.

[ian1095]

Sadly for me this has come too late SSS

 

I became fed up of not being able to connect to many sites and the list was growing at an alarming rate, rendering many scrapers useless. So I moved to ATV several months ago purely because of this issue and the archaic Gstreamer version still in use in PLI 4.0

 

Great work though and I'm sure many users will be very grateful of this.

 

Ian.

Edited by ian1095, 21 May 2017 - 10:03.

[Erik Slagter]

@WanWizard

 

What part of "I do not ask you for anything." isn't clear to you?

The part where you go berserk and you're not trying to understand anything we write. I suggest you cool down and read again.

[samsamsam]

What do OpenPLI team do when this problem was reported first time (a few months ago)?

The problem which affects so many users. 

Did you really analyze the problem? 

 

I do not think so. Because fix for this problem is pretty simple.

I'm sure If you have analyzed this problem you will apply fix a long time a go.

 

This is a problem with OpenPLI team and this is a clue.

Take a newer version of OpenSource component can do anyone (In most cases).

This is much simpler than analyze problem. Am I right?

 

@Erik Slagter

 

You do not had problem with post @WanWizard were he wrote in arrogant manner "What part of  [...]  isn't clear to you?". 

But you have problem when I wrote in the same way.

 

This is funny. 

 

You try to argue with the facts, but that will not change anything. Facts remain facts.

Edited by samsamsam, 21 May 2017 - 10:49.

[Erik Slagter]

I do know Wanwizard a bit and I know that when he writes this, it's not arrogance but failure to understand (as I do as well). Apparently your not addressing his comments/questions. I'd really suggest you work on your temper a bit and don't get angry so easily, it will prove to be much more productive.

[samsamsam]

What does your post bring to the matter? Nothing.  Are you writing about my productivity?

Really? Hehehe

You shot yourself in the foot.

Edited by samsamsam, 21 May 2017 - 10:58.

[WanWizard]

Absolutely no arrogance is intended, I am just stating a fact.

 

As you correctly observed, OpenPLi 4 is ancient. It's OE version, It's Python version, it's Gstreamer version, all old. So we want to move on.

 

So let me explain myself in detail. To be able to move on we need:

1. stablelize de codebase of master 
2. all images to correctly build from master
3. all images to correctly build from develop
4. when that is the case, we need to freeze development on master
5. release a final version of OpenPLi 4 from master
6. move to the next version

We can't do this if master constantly changes, we get stuck between 1 and 2.  So we have been working very hard over the last few months at points 2 and 3 at the moment, and we're now at point 4.

If we now start changing master again, we go back to point 1, and we'l never be able to release something new.

 

I understand that to some people this feels like ages, but there is a big difference between building a single box image, and building for dozens of boxes and multiple architectures. They all interlink, so fixing on thing for box A may break the build for box B, a manufacturer may update it's BSP which breaks the build for another manufacturer, etc.

 

In order to bring order to chaos, we need to approach our development process in a business like fashion, with proper project management and release procedures.  We have gotten too big to remain working like we're busy in our attick room tinkering with the image of a single DM7000....

[samsamsam]

in our attick room tinkering with the image of a single DM7000 ....

 

What? If you want to say that I release image of DM7000 than you are wrong.

 

Another thing there is no problem to work on new stable release and release hot fixes for current stable version.

There is no problem. This is normal procedure. And if you want to say that for example changing one line of code in the current stable version course to start process from step 1. 

This is funny and I think you never works on really big project with quality assurance procedures.

 

Let show me another project working like you describe? I'm curious from were you take such procedure?

 

The main qestion is still open:

What do OpenPLI team do when this problem was reported first time (a few months ago)?

The problem which affects so many users. 

Did you really analyze the problem? 

Edited by samsamsam, 21 May 2017 - 12:41.