WanWizard

as far as it's ok, but i thought if i flash a new image from date 12.08.2019 and now install the three plugins as above mentioned from feed

all these commits are in the new image, but that is not the case - why ?

Because a release image is a stable image, which means everything is pinned on commit hash, which needs manual updating after a component is updated and properly tested in develop.

Often, the component gets updated, if we're lucky it gets properly tested, but a PR to update the commit hash is hardly ever created.

Ok. Here you go: https://github.com/O...2a8fa9d3d0b826a

SDL2 2.0.5 is part of the OE version we ship with OpenPLi 7.1. 

2.0.10 has only been updated in OE 6 days ago (https://github.com/o...raphics/libsdl2), but the recipe is different.

I'd rather port this one, then use a custom recipe, which will always become a pain when we need to upgrade OpenPLi to a newer OE version...

Haha, huge, i presume that there are all packages builded and entire cache.

All images, all packages, complete sstate-cache, rm_work active for release images.
 

I wonder why 7.1 is bigger than RC or develop.

It's the other way around, the second value is "used". I suspect that for debug reasons the RC's where build without rm_work, and with buildhistory active (is used to generate the pinning in reporefs.conf).

Also, we've created a cleanup script that runs after every build, which hasn't run for rc, as that hasn't been build for a while.
 

Can you share infos regarding the hardware behind those buildservers?

Our buildervers are Intel Core i7 7700K machines, 32GB ram, with 2 SATA disks for storage and the OS (part in raid 1), and 2 Samsung EVO 970 1TB SSD disks for the images (hence two build directories per server).

Thanks, I believe I've merged all of them?

I'm all for it. Now if we can open a tin of developers with the right knowledge?

A new GUI? Long overdue...

It is a common illusion that all Enigma based images are compatible, that is not the case, so not every skin out there works on OpenPLi.

Also, we can only include in the feeds what is explicitly licensed with a public license, or if the author has permitted us to do so.

We build Oscam from Git, instead of the antiquated SubVersion,  which Streamboard is using. So you see the git commit hash, instead of the svn version number.

Having said that, what relevance has a number? The version in the feed is the latest stable version, we regularly update it.

The option to unmount a mounted device from the GUI is on the todo list, it is indeed missing functionality at the moment.

In plaats van dat continue gezeik, leg nu eens uit wat 11529 beter maakt voor gebruikers dan 11523?

Sagitarius zeikt alleen maar om te zeiken, die heeft de code niet eens bekeken, laat staan begrepen, maar van jou verwacht ik wel meer. En ik heb de commit list van de 7.1-release branch nog even doorgenomen, maar alles wat ik daar zie fixed een probleem, dus het is me even onduidelijk waarop je alludeerd.

De TS heeft in post #2 al antwoord gehad, het zijn alleen jullie twee die wederom maar door blijven zagen, zonder in te gaan op de gestelde vraag "waarom" die update nu zo nodig moet gebeuren.

Voor mij is het simpel: als je lid wordt van het team, en ook vele uren per week aan het werk hier besteed, dan mag je mee praten (sterker nog, dan mag je het werk zelf doen). En anders heb je hier niks te vertellen. Met stuurlui aan de wal, zoals jullie kunnen we niks. Die kosten alleen maar tijd dat beter besteed kan worden.

Vind je nu ook niet dat jullie weer eens vreselijk aan het zeiken zijn om niks? Zijn jullie nu allemaal zo nummer geil? "Mijn versie is groter dan die van jullie", jezus zeg, wat een kleuter gedrag weer.

Welk deel van "Een stable image is een image waaraan niets veranderd tenzij het absoluut nodig is, zodat de stabiliteit kan worden gegarandeerd" hebben jullie nu niet begrepen?

Gevonden, en gefixt. Update komt mee komende maandag.

Sure, if you istalled it, it's in the feeds.

OpenPLi doesn't use autofs, so this isn't going to work.

You can create the same mount with the mount manager. Possibly, depending on the kernel version on the box, you might have to add

vers=1.0

to the mount options, chances are the Fritz still wants SMBv1.

Danke, merged.