View Full Version : OpenViX 5.4 - Mut@nt HD2400 plugins?
No plugins in OpenViX 5.4 (the last Python 2.7 version!) - Mut@nt HD2400.
Install Plugins:
There has been an error, please try again later.
If this
issue persists, please check openvix.co.uk or world-of-
satellite.com
opkg:
* opkg_download_backend: Failed to download http://www.openvix.co.uk/feeds/openvix/release/5.4/hd2400/3rdparty/Packages.gz, wget returned 8.
* opkg_download_backend: Failed to download http://www.openvix.co.uk/feeds/openvix/release/5.4/hd2400/all/Packages.gz, wget returned 8.
* opkg_download_backend: Failed to download http://www.openvix.co.uk/feeds/openvix/release/5.4/hd2400/hd2400/Packages.gz, wget returned 8.
* opkg_download_backend: Failed to download http://www.openvix.co.uk/feeds/openvix/release/5.4/hd2400/hd2400_3rdparty/Packages.gz, wget returned 8.
* opkg_download_backend: Failed to download http://www.openvix.co.uk/feeds/openvix/release/5.4/hd2400/mips32el/Packages.gz, wget returned 8.
* opkg_download_backend: Failed to download http://www.openvix.co.uk/feeds/openvix/release/5.4/hd2400/mutant2400/Packages.gz, wget returned 8.
Openvix 5.4 is no longer supported and plugins are not available. Its been like this for a long time. You can upgrade to the 6.2 image
Sorry we just don't have the resources available to maintain feeds for old versions that are years old when it is so easy to upgrade to a newer version.
Sorry we just don't have the resources available to maintain feeds for old versions that are years old when it is so easy to upgrade to a newer version.
Az OpenVIX 6.x is not just "newer" and "better", but Python3 as well.
There are a lot of Python2 add-on, and the Python3 version of them is not expected in the future.
It would be better to continue supporting the last OpenVIX with Python2.
Even on the expense of 6.x:
www.openvix.co.uk/feeds/openvix/release/6.0/hd2400/... available
www.openvix.co.uk/feeds/openvix/release/6.1/hd2400/... available
www.openvix.co.uk/feeds/openvix/release/6.2/hd2400/... available
P.s. I am using 6.2 on one of my boxes, but I would like to "keep" the 5.4 on another because of Python2.
Az OpenVIX 6.x is not just "newer" and "better", but Python3 as well.
There are a lot of Python2 add-on, and the Python3 version of them is not expected in the future.
It would be better to continue supporting the last OpenVIX with Python2.
Even on the expense of 6.x:
www.openvix.co.uk/feeds/openvix/release/6.0/hd2400/... available
www.openvix.co.uk/feeds/openvix/release/6.1/hd2400/... available
www.openvix.co.uk/feeds/openvix/release/6.2/hd2400/... available
P.s. I am using 6.2 on one of my boxes, but I would like to "keep" the 5.4 on another because of Python2.
What python 2 add on‘s??
Tell us which and maybe we can do something
What python 2 add on‘s??
Tell us which and maybe we can do something
Hungarian e2iPlayer. It has also a Python3 version, but this is much poor, than that with Python 2.
Not mentioning the non Hungarian one!
m3uplayer - the Python3 version was requested on LinuxSat-Support as well, but it is not really expected.
I'm sure there are others also, but at the moment these are missing on the 6.2 box.
The "freshly installed" 5.4 is "working, so-so" (it had 5.3 before).
I don't understand it, but I think if I could install samba, nfs, e2iplayer-deps, serviceap, ext3player and ntfs (*), I could "deal with it" .
(*) there was no need since now for 5.3 to recognize an nfts usb drive.
I remembered somehow (from another box), that this is needed. But it did not exist, of course.
Then I thought to "step forward" on this box also. And now then I miss the components mentioned above.
I don't understand it, but I think if I could install samba, nfs, e2iplayer-deps, serviceap, ext3player and ntfs (*), I could "deal with it" .
Unless I have missed something they are all avalable in python 3 images
M3uplayer - don‘t know much about it, but from a brief read would have thought Kiddac‘s Xstreamity would handle or e2m3u2bouquet
Unless I have missed something they are all avalable in python 3 imagesHe means they are not available in 5.4 because I deleted them all.
It really is laughable asking us to maintain feeds for out of date versions because other people are to lazy to update their plugins.
By the way, if you want a 5.4 image and feeds feel free to build it yourself. The branch is still available: https://github.com/OpenViX/enigma2/tree/Dev-old-20211224
It really is laughable asking us to maintain feeds for out of date versions because other people are to lazy to update their plugins.
If somebody has several boxes (e.g. I have three, and I use - just to be safe - OpenATV on the third one), it is a reasonable strategy, that there is an "failsave" one (everything checked, everything works) and there is one you can "step forwards" if you want.
I have already tried OpenVIX 6.0 before, and got back to 5.4 immediately (not just because of Python3!).
It was still possible at that time.
6.2 seems to be okay, and what is not working because of Python3, that is working on OpenATV.
But ViX is "more friendly" for me, then ATV. I would prefer to use ViX Python3 on one box and ViX Python2 on an other one.
And this is not laziness, speaking for myself sure not: It is not me, who writes the plugins and and who does not create their "compatible" (!) P3 version!
On my opinion Python2 is not out of date, no matter how old it is.
So the last ViX with Python2 is not either !
It can happen in the future at any time, that something is mentioned which would worth to try and I would use it also if I like it, but if it is Python2, then it cannot be done In ViX anymore.
Xstreamity
I do not use it much either, but this downloads m3u playlist from stalker portals. As I know, that on the box does not handle m3u playlists.
e2m3u2bouquet - "shooting canons to catch a fly"
It is useful to have a "long-time working" m3u list
But it is still some work with it, which item which #SERVICE (1, 4097, 5002 ?).
The m3uplayer is useful, if you have an htttp: link, then I edit it from PC in an m3u file (it can handle several files!) - e.g. samba would be needed for this also! - and I can watch it on the tv immediatly.
https://www.linuxsat-support.com/thread/129796-m3uplayer-plugin/?postID=583882
If somebody has several boxes (e.g. I have three, and I use - just to be safe - OpenATV on the third one), it is a reasonable strategy, that there is an "failsave" one (everything checked, everything works) and there is one you can "step forwards" if you want.
I have already tried OpenVIX 6.0 before, and got back to 5.4 immediately (not just because of Python3!).
It was still possible at that time.
6.2 seems to be okay, and what is not working because of Python3, that is working on OpenATV.
But ViX is "more friendly" for me, then ATV. I would prefer to use ViX Python3 on one box and ViX Python2 on an other one.
And this is not laziness, speaking for myself sure not: It is not me, who writes the plugins and and who does not create their "compatible" (!) P3 version!
On my opinion Python2 is not out of date, no matter how old it is.
So the last ViX with Python2 is not either !
It can happen in the future at any time, that something is mentioned which would worth to try and I would use it also if I like it, but if it is Python2, then it cannot be done In ViX anymore.
Xstreamity
I do not use it much either, but this downloads m3u playlist from stalker portals. As I know, that on the box does not handle m3u playlists.
e2m3u2bouquet - "shooting canons to catch a fly"
It is useful to have a "long-time working" m3u list
But it is still some work with it, which item which #SERVICE (1, 4097, 5002 ?).
The m3uplayer is useful, if you have an htttp: link, then I edit it from PC in an m3u file (it can handle several files!) - e.g. samba would be needed for this also! - and I can watch it on the tv immediatly.
https://www.linuxsat-support.com/thread/129796-m3uplayer-plugin/?postID=583882
The issue here is that we are forced by the python people to move everything to python 3. Also every new python 3.xx there are changes that remove some features that are no longer supported ..... they tell you ahead of the release .... but!
If something doesn't work on python 3, we are quite happy to have a look at it and if possible provide a resolution, but you need to be exact and in some cases supply the ipk, so we can see the code.
Ref m3u .. post me a file so that I can see what I am handling.
Ref m3u .. post me a file so that I can see what I am handling.
this can also be found at the link above.
this can also be found at the link above.
can you post me(PM) an m3u that needs this IPK to play? Will not post onwards ... just want to see what I can do with something you are using.
have done basic changes for python 3, but bound to be some decode/encode issues, so need test files
1) Python 2 was dropped by the Python developers over 2 years ago including security updates.
2) If OpenATV want to maintain 2 versions that is up to them, but in our opinion that is just prolonging the pain and allowing the lazy plugin authors to pit one distro against another.
3) If you use the current OpenATV image the plugins that are not converted won't work in that image either.
4) Do you think it is fair that people demand us to maintain feeds that are years old at our own expense?
5) Anyone that wants to can build and maintain a copy of 5.4 at their own expense.
OpenATV 6.4 is end of life at the end of December and will no longer be maintained so looks like everyone will have to move over to python 3 eventually.
2) If OpenATV want to maintain 2 versions that is up to them, but in our opinion that is just prolonging the pain and allowing the lazy plugin authors to pit one distro against another.
4) Do you think it is fair that people demand us to maintain feeds that are years old at our own expense?
I have downloaded the 6.0 on 03/05/2022 (the image content is 02/26/2022), then after testing it for cca. one week on 03/16/2022 I went back to the last 5.4 (the image content is 10/12/2021).
That isn't really "years old", is it ?
I did not "demand" anything. ViX displayed, that
There has been an error, please try again later.
If this issue persists, please check openvix.co.uk or world-of-satellite.com
I asked a question. There is a question mark in the topic issue.
If "people" do not like that if the support of a barely one year old distribution is ceased on day to the next (I suppose without any previos warning or temporary period), then it is a rather "unfriendly" step.
And it is downright offensive to call as "lazy plugin authors" people, who create plugins for use and pleasure of other people (I assume for free!), just because they are not following immediately and absolutely the "Python policy".
"...our own expense" vs "...we are forced by the python people to move everything to python 3"
Everyone can decide, what the real reason is.
P.s. There is still an OpenViX Archives link - which is empty of course.
Will it exist sometimes again ?
I have downloaded the 6.0 on 03/05/2022 (the image content is 02/26/2022), then after testing it for cca. one week on 03/16/2022 I went back to the last 5.4 (the image content is 10/12/2021).
That isn't really "years old", is it ?
I did not "demand" anything. ViX displayed, that
There has been an error, please try again later.
If this issue persists, please check openvix.co.uk or world-of-satellite.com
I asked a question. There is a question mark in the topic issue.
If "people" do not like that if the support of a barely one year old distribution is ceased on day to the next (I suppose without any previos warning or temporary period), then it is a rather "unfriendly" step.
And it is downright offensive to call as "lazy plugin authors" people, who create plugins for use and pleasure of other people (I assume for free!), just because they are not following immediately and absolutely the "Python policy".
"...our own expense" vs "...we are forced by the python people to move everything to python 3"
Everyone can decide, what the real reason is.
P.s. There is still an OpenViX Archives link - which is empty of course.
Will it exist sometimes again ?
@malvin1 I have sent you a PM.......
unlike some other images, we are not paid to do this and server costs limit what we can store, especially when the feeds created by the OE-A 5.1 image build are significantly bigger - like everything costs keep rising and software takes up more storage.
The MP3player plugin that I am looking at uses some functionality that is already marked as depreciated by the python 3 bunch and at some stage will have to be replaced - this is nothing that we can control ....... that also applies to the core elements used to build the images, so not just python 3.
"...our own expense" vs "...we are forced by the python people to move everything to python 3"
Everyone can decide, what the real reason is.
P.s. There is still an OpenViX Archives link - which is empty of course.
Will it exist sometimes again ?
You are mixing things up.
From January 1st 2020 Python 2 is dead. No bug fixes whatsoever. Nothing. Zilch.
https://www.python.org/doc/sunset-python-2/
Saving old feeds costs money. We were out of space and changes would cost money. No user or manufacturer pays anything towards our servers. Each machine's is around 2 GB, plus the image files themselves. We maintain more than 60 machines. So that is around 120 GB for each version. And feeds are currently maintained for 6.0, 6.1 and 6.2. Only 5.4 and older feeds were removed.
[root@ns3324542 ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 20026236 2333960 16651944 13% /
devtmpfs 4032384 0 4032384 0% /dev
tmpfs 4032868 0 4032868 0% /dev/shm
tmpfs 4032868 427532 3605336 11% /run
tmpfs 4032868 0 4032868 0% /sys/fs/cgroup
/dev/sda3 1902052484 1542032348 263378448 86% /var
tmpfs 806576 0 806576 0% /run/user/0
[root@ns3324542 ~]#
And like I already said, if you want 5.4 feeds you can build and maintain them yourself. Nothing stopping you.
Saving old feeds costs money. We were out of space and changes would cost money.
And like I already said, if you want 5.4 feeds you can build and maintain them yourself. Nothing stopping you.
It is then 60*120 GB = 7.2TB regarding all "last Pithon2 5.4".
I'm sorry that the ecclesia is poor.
(I have here at home more than 10TB connected to the boxes, only for archiving recordings and torrent films)
Concerning the several time mention "really practical" advice, that "you can build and maintain them yourself":
I have not done such a thing, but I assume that:
1. I needs a Linux - I have it
2. It needs a development environment - I assume it is available somewhere. But not sure, it is exactly that Linux what I have (Ubuntu).
But presuming I can "put it together".
In ATV 6.0 I checked the plugin (it has a feed for this as well!) because of which I killed ViX 5.3:
Package: enigma2-plugin-drivers-ntfs-3g
Version: 1.0-r0
Description: Allow writes to NTFS file systems Allow writes to NTFS file systems.
Section: base
Priority: optional
Maintainer: OE-Core Developers <openembedded-core@lists.openembedded.org>
License: GPLv2+
Architecture: mips32el
OE: enigma2-plugin-drivers-ntfs-3g
Depends: ntfs-3g
Source: None
Filename: enigma2-plugin-drivers-ntfs-3g_1.0-r0_mips32el.ipk
Size: 656
MD5Sum: c1c5be269a9516899eec3566c8d2c2ce
Source: None
Then how should I "do it by yourself"?
It can not be found the link suggested by you in the past (https://github.com/OpenViX/enigma2/tree/Dev-old-20211224) either:
We couldn’t find any code matching 'ntfs-3g'
Build instructions are here https://github.com/OpenViX/enigma2/tree/Developer - you will just have to edit to use the correct branch
Stop expecting others to spend money on server space just for you - you didn't pay anything for openvix
Stop expecting others to spend money on server space just for you - you didn't pay anything for openvix
"just for me"
Maybe you should read other forums as well, a lot of people mourn for Python2.
"you didn't pay anything for openvix"
There are a lot of things in the world you don't pay either, but somehow it "is worth" for those who give it "by free".
ViX is a very nice system (thanks to the developer), but if support is such, one must consider, not only "not to pay for it", but do not use it anymore.
There are a lot of other systems ....
p.s.
Dear ronand (VíX Beta Tester)!
Did you recognize, that BoxBrandingTest.py is missing from ViX 6.2.?
That is the cause, why some Python3 plugin is not installing.
It is a fortune, that they can be "copied" from ATV, and without any extra knowledge can made to Python3 (by including some brackets).
After this everything is o.k.
And just noticed!
You are using ViX 5.4 as well: Zgemma H7S running OpenVIX 5.4
What is the man on about the vid image is excellent and it works great
p.s.
Dear ronand (VíX Beta Tester)!
Did you recognize, that BoxBrandingTest.py is missing from ViX 6.2.?
That is the cause, why some Python3 plugin is not installing.
It is a fortune, that they can be "copied" from ATV, and without any extra knowledge can made to Python3 (by including some brackets).
After this everything is o.k.
And just noticed!
You are using ViX 5.4 as well: Zgemma H7S running OpenVIX 5.4
Deary me. You might have noticed that this is an open source project - you are more than welcome to fix the bugs yourself. No amount of whining is going to get the dev team to build and maintain an old image and feeds for you.
Did you recognize, that BoxBrandingTest.py is missing from ViX 6.2.?
That is the cause, why some Python3 plugin is not installing.
It is a fortune, that they can be "copied" from ATV, and without any extra knowledge can made to Python3 (by including some brackets).
Blah blah, other image works better, blah, blahOpenViX has a box branding inspector built in.
Menu > Information > Boxbranding
"you didn't pay anything for openvix"
There are a lot of things in the world you don't pay either, but somehow it "is worth" for those who give it "by free".If we charged you 1000€ for it you would probably complain less.
ViX is a very nice system (thanks to the developer), but if support is such, one must consider, not only "not to pay for it", but do not use it anymore.
There are a lot of other systems ....If you are not happy with it you are welcome to move on.
We improve things by moving forwards not backwards. If you have something constructive to add that involves moving forward we'll be happy to listen.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.