[ViX_Misc] Built openvix myself, now want to replicate feeds - issues...

[AnfieldRoar]

As the Xpeed LX2 is no longer supported I built openvix myself and flashed fine.

Now I want to manage updates to my box so I changed the opkg feeds in /etc/opkg to point to my own website and uploaded the ipk's and packages to my site in /feeds/openvix/release/5.0/inihde/3rdparty etc

Seems to work great for plugins, as I can now install new ones

When I do a 'software update' it gets the packages.gz files file (from /etc/opkg files) fine and says there are X packages to update.

But when I install the updates, the opkg log file says that it's downloading the ipk, then removing the corrupt ipk. But the ipk's do indeed download fine (tested separately and webserver mimetype is good) and the ipk's are correct ones from the build so any ideas what is wrong here anyone?

Just want to extend the life of my LX2

TIA

 

[AnfieldRoar]

Ah scrub that, my mistake, the ipk's with a plus sign were failing to download so added some web.config lines and now all is good

 

[twol]

Quicker to run a new build ... shouldn't take long as not many changes, and reflash after a settings backup.....
If you change the feeds url in the OpenVix conf file in the meta-oe (in the OE-A) you don't have to change the etc/opkg and you can do the above without issues.

 

[Huevos]

I changed the opkg feeds in /etc/opkg to point to my own website and uploaded the ipk's and packages to my site in /feeds/openvix/release/5.0/inihde/3rdparty etc

You're making this difficult for yourself. Change the feeds URI in openvix.conf. Then just link to the ipk directory. No need to move files around. To create the links you need something like the following (modify to suit your directory structure).

mkdir -p /var/webserver-directory/feeds/openvix/release/5.0/inihde

ln -s /home/user-directory/5.0/builds/openvix/release/inihde/tmp/deploy/ipk/* /var/webserver-directory/feeds/openvix/release/5.0/inihde

 

[AnfieldRoar]

Many thanks for the input, I've made the change and will test asap.

I have some edits for AutoTimer.py that I want to include in the build so I've modified the only AutoTimer.py file I have at:

/home/oealliancebuilder/oealliance/build-enviroment/builds/openvix/release/inihde/tmp/sysroots/inihde/usr/lib/enigma2/python/Plugins/Extensions/AutoTimer.py

and will build the image again using:

MACHINE=xpeedlx DISTRO=openvix make image

I tried this before and no changes were included in the image or autotimer ipk. Any ideas how I can do this? Thought make image would rebuild using changes...

Cheers

 

[Huevos]

If you want to force a recipe to update you need to bump the PR in that recipe.

What changes have you made to autotimer? Maybe it is something that OE-A would consider adding to the code base.

 

[AnfieldRoar]

If you want to force a recipe to update you need to bump the PR in that recipe.

What changes have you made to autotimer? Maybe it is something that OE-A would consider adding to the code base.

Sorry new to openvix dev here - what does 'bump the PR in that recipe' mean?

I've updated autotimer.py to record IPTV bouquets - simple hack - I've sent the code to the git maintainer of autotimer.

Original discussion here: http://www.techkings.org/threads/how-to-record-iptv.123223/page-3

Cheers

 

[birdman]

I have some edits for AutoTimer.py that I want to include in the build so I've modified the only AutoTimer.py file I have at:

/home/oealliancebuilder/oealliance/build-enviroment/builds/openvix/release/inihde/tmp/sysroots/inihde/usr/lib/enigma2/python/Plugins/Extensions/AutoTimer.py

and will build the image again using:

MACHINE=xpeedlx DISTRO=openvix make image

That's unlikely to produce anything useful.

All you've done is edit the file that gets put into the image, but given that the build is highly likely to find a new version of enigma2-plugins (which is what contains the AutoTimer code) it will build a new one and overwrite what you have done. Even if it does no rebuild it will not produce an ipk which includes that file.

What you have to do is to make your own git clone of the enigma2-plugins code, edit that and change the build config to use it.
It's probably simpler just to copy the AutoTimer.py onto your box, if that's the only change, although you will have to track changes to the "real" one (which you'd need to do anyway if you cloned the git).

 

[birdman]

Original discussion here: http://www.techkings.org/threads/how-to-record-iptv.123223/page-3

Cheers

Unfortunately it seems that the end of the error message at the end of that thread has been chopped. It looks like it's about to report a missing attribute, but there's no indication of which (it should be in the debug log file...).
At a guess it might be about the popup-timeout value, which was only added at the last release so if you're running with your own edited copy of an older version and not tracking updates, might be an issue.

 

[AnfieldRoar]

Ah yes, I am running openvix 5.0.17 and so the autotimer.py I posted isn't for older versions! I'll message the other user. Thanks for your help.

 

[AnfieldRoar]

Quite different to how I currently use git. I usually pull code, make changes, build and release. Then I can pull code again, get the latest code merged into my changes and build/release again. By what you're saying that isn't how this 'make image' works?

I was expecting to find autotimer.py in my build-environment path somewhere, make changes and rebuild. If that's not how it works then I'll stick to full image builds direct from git and copy my own .py files manually. Shame...

 

[abu baniaz]

Bump PR = increase the PR version.

AutoTimer repository is here if you want to submit a pull request so all OE-A images benefit

https://github.com/oe-alliance/enigma2-plugins/tree/2.3/autotimer

Alternatively, if you fork the file to your own tree, you can alter the bitbake file to point to your own instead of the official one. I can't advise further as I do not know how to achieve this, but it is possible.

 

[abu baniaz]

What changes have you made to autotimer? Maybe it is something that OE-A would consider adding to the code base.

After re-adding comments to log lines again, his changes are in the attached file.

 

[birdman]

Quite different to how I currently use git. I usually pull code, make changes, build and release.

Would work fine(-ish) for a single git repository, but this is a bitbake OS build environment with a large number of software downloads (not all git) from multiple locations.

So bitbake downloads the sources then saves them all into its own repository and only downloads them again if there is a change.

To get your own mods into the bitbake build you need to point the bitbake build at your own copy of the download repository tat you wish to alter.

I was expecting to find autotimer.py in my build-environment path somewhere, make changes and rebuild. If that's not how it works then I'll stick to full image builds direct from git and copy my own .py files manually. Shame...

As I said, that will be the much simpler way for a *.py file, which you just have to drop into place on the box.