What steps will reproduce the problem?
1. Trying to download the latest version. (Actually, any late version.)
2. Getting redirected to sourceforge.
3. Getting blocked by the "You live in the EU. Accept our cookies!!!" thing.
4. Failing to find a way around it. Accepting it. Same question again.
Accepting it. Same question again. Accepting ...
5. Reading up on how the problem's experienced by people in the EU.
6. Realizing I'm sharing the situation with a wast majority of EU citizens.
7. Failing to report the problem at sourceforge 'cause I can't reach the site,
'cause I'm blocked out by "the cookie thingy".
8. Renouncing to try out the promising Webiopi software cause I can't get my
hands on it.
9. realizing that anything sourceforge requires not to live in the EU.
10. Looking in other directions. Walking off...
Hmm... Unless... Is there any other distribution channel for Webiopi than "Go
to sourceforge and don't live in the EU" ???
...
WebIOPi version used?
=> Well, none. Can't reach it.
Python version used?
=> Does it really matter now?
Distro used? (WebIOPi has only been tested on Raspbian Wheezy)
=> Intention was: Raspbian Wheezy. And I said "was".
Raspberry Pi board revision? (1 or 2)
=> Several.
For Javascript side bugs, Browser?
=> Not applicable.
Please provide any additional information below.
=> Just to say I realize it's not the Webiopi team's fault sourceforge locked
the EU out. Still can't reach them to complain. Just wanted to give you guys a
heads up.
Original issue reported on code.google.com by gustav.s...@gmail.com on 14 Feb 2015 at 10:30
Original issue reported on code.google.com by
gustav.s...@gmail.comon 14 Feb 2015 at 10:30