The repo no longer exists: https://github.com/oscam-emu/oscam-patched
But the patch only is still up: https://github.com/oscam-emu/oscam-emu
Does anyone know why it was taken down?
I was building from it.
There are 27 replies in this Thread which was already clicked 8,984 times. The last Post () by Chris230291.
The repo no longer exists: https://github.com/oscam-emu/oscam-patched
But the patch only is still up: https://github.com/oscam-emu/oscam-emu
Does anyone know why it was taken down?
I was building from it.
is this not the same thing
https://github.com/oscam-emu/oscam-patched-old
is this not the same thing
https://github.com/oscam-emu/oscam-patched-old
That's the old version, though.
Just wondering if the patched version, that is still referenced in the patch only repo, was taken down or was removed for another reason.
I was successfully building from it a few days ago, and now it's gone.
Neither the oscam developers have anything to say about it, but I could see it coming after reading strong discussions between developers, you can still compile some people provide oscam-emu.patch.
Neither the oscam developers have anything to say about it, but I could see it coming after reading strong discussions between developers, you can still compile some people provide oscam-emu.patch.
So it's just people being childish?
The patch it still up, just not the pre-patched version.
EDIT: I found an email address for the dev. If he replies, I'll post back.
look for others on github
Display MoreNeither the oscam developers have anything to say about it, but I could see it coming after reading strong discussions between developers, you can still compile some people provide oscam-emu.patch.
So it's just people being childish?
The patch it still up, just not the pre-patched version.
EDIT: I found an email address for the dev. If he replies, I'll post back.
well building the docker version is not so different now, it's actually cleaner imho.
RUN \
echo "**** compile oscam ****" && \
mkdir -p /tmp/oscam && \
git clone https://git.streamboard.tv/common/oscam.git /tmp/oscam && \
cd /tmp/oscam && \
git apply /tmp/patches/oscam-emu.patch && \
./config.sh
or also dont statically include the patch in the Dockerfile but rather curl it from oscam-emu repo.
ah, also, to keep the Dockerfile cleaner, take a look at the patched libdvbcsa repo so you dont have to actually include anything.
I use simplebuild, to have the latest emu version this way is to wait for someone to upload the patch, copy it to the path and apply the repopatch command, it's easy, but it's not as fast as it was before.
Thats not with emu support.
Display MoreDisplay MoreNeither the oscam developers have anything to say about it, but I could see it coming after reading strong discussions between developers, you can still compile some people provide oscam-emu.patch.
So it's just people being childish?
The patch it still up, just not the pre-patched version.
EDIT: I found an email address for the dev. If he replies, I'll post back.
well building the docker version is not so different now, it's actually cleaner imho.
CodeRUN \ echo "**** compile oscam ****" && \ mkdir -p /tmp/oscam && \ git clone https://git.streamboard.tv/common/oscam.git /tmp/oscam && \ cd /tmp/oscam && \ git apply /tmp/patches/oscam-emu.patch && \ ./config.shor also dont statically include the patch in the Dockerfile but rather curl it from oscam-emu repo.
ah, also, to keep the Dockerfile cleaner, take a look at the patched libdvbcsa repo so you dont have to actually include anything.
Thanks. I know I can just patch it manually, but I thought it would be safer to use the pre-patched version since the patch could need changing to support the latest version of oscam.
Why patch libdvbcsa? Is that for e2 users?
Why patch libdvbcsa? Is that for e2 users?
Think so, memory is not what is once was....remind me what you TVheadend guys patch for icam ?
Why patch libdvbcsa? Is that for e2 users?
Think so, memory is not what is once was....remind me what you TVheadend guys patch for icam ?
We patch libdvbcsa for TVH.
I assume we need the patched libdvbcsa for stream relay to work with iCam?
As far as I know, it's only e2 users that use stream relay?
We patch libdvbcsa for TVH.
I assume we need the patched libdvbcsa for stream relay to work with iCam?
As far as I know, it's only e2 users that use stream relay?
You dont really need any of the stream relay stuff that has now been added to oscam, (as you say TVhedend has patched it elsewhere anyways)
There is options to build without when using simple build.....something else i have been meaning to test but not got round to it.
Neither the oscam developers have anything to say about it, but I could see it coming after reading strong discussions between developers, you can still compile some people provide oscam-emu.patch.
As you may or may not know, I was the only maintainer and developer of the oscam emu repo in github . That was true for a decade now, but as time didn't allowed I was proposed to add some more people to help.
These were the same people that took over oscam. Mainly wxbet and ohmza. Unfortunately, this has been a total disaster as apart from committing questionable quality code to oscam, they totally removed the emu related parts (despite my objections) that resulted in making oscam-emu code more difficult to maintain. I didn't like this, but as my free time was limited I decided to let it go.
I also decided to let wxbet have full control of the emu repo in github and essentially run it alone. Things were okish between us.
On the contrary, I had some arguments In the past with ohmza regarding some code he was about to commit in oscam, tried to explain, but didn't want to understand. Problem was he was posting again and again making fun of me in streamboard forum. That's why I decided to leave oscam (I was a dev there as well) some months ago and asked them to completely delete my account so he would stop mentioning me. This wasn't enough for him, and he kept mentioning me and making fun of me in streamboad even without me being a member there. I decided to ask wxbet to put a leash on him, but as the future revealed this wasn't the case.
This was how things were for some months now, until the other day I got a personal attack from ohmza in github without any reasoning. See pictures attached. So, this is why I decided to removed all these guys from the repo and bring it down as well. I asked github to take action and they deleted his account and the offending posts, so get prepared for a different nickname for him there in the future.
THIS ACTION IS TO TELL PEOPLE THAT OSCAM-EMU MANAGEMENT BY NAUTILUS7 HAS ENDED.
There are plenty of places to get the code. Whoever wants can make a new repo and do whatever he likes with it. Just do not mention me at any way. I do not want to have any relation or responsibility with oscam(-emu) anymore. Sorry for the trouble this brings to users and especially e2 image makers, but you have to look elsewhere for the root cause of this.
Regards, nautilus7 out.
Sorry for the trouble this brings to users and especially e2 image makers, but you have to look elsewhere for the root cause of this.
Sorry to hear how things have now turned sour, there is a lot of that going around lately.
I will take this opportunity to thank you for the past decade, (and beyond that) maintaining the EMU patch and all of the development we the end user's have benefitted from, both with EMU and oscam core. Should time allow.... and if you ever find the desire to continue a separate branch at some point, please let us know. ![]()
I have followed your publications here and in github, I am also sorry that you are leaving this project, and I think I will not be the only one, maybe there is still something to do for example in powervu, however I will always thank you for all the help for us less knowledgeable in software development, you have helped us to enjoy TV for so long.
Thanks for clearing things up.
I guess we can use the patch while it's still being maintained.
If not, we can just switch to NCam.
I just wish Ncam used the same defaults as OSCam and the links in the web ui to the wiki still existed!
Maybe someone close to fairbird can give a polite nudge :)
Display MoreGli sviluppatori di oscam non hanno nulla da dire al riguardo, ma potrei vederlo arrivare dopo aver letto le accese discussioni tra gli sviluppatori; alcune persone forniscono ancora oscam-emu.patch.
Come forse saprete, ero l'unico manutentore e sviluppatore del repo emu oscam in github. Ciò è stato vero per un decennio ormai, ma poiché il tempo non lo ha permesso, mi è stato proposto di aggiungere altre persone per dare una mano.
Erano le stesse persone che avevano preso il controllo di oscam. Principalmente wxbet e ohmza. Sfortunatamente, questo è stato un disastro totale perché, oltre a inviare codice di qualità discutibile a oscam, hanno rimosso completamente le parti relative a emu (nonostante le mie obiezioni) il che ha reso il codice oscam-emu più difficile da mantenere. Non mi piaceva, ma poiché il mio tempo libero era limitato, ho deciso di lasciarlo andare.
Ho anche deciso di lasciare che wxbet avesse il pieno controllo del repo emu in github e di gestirlo essenzialmente da solo. Le cose andavano abbastanza bene tra noi.
Al contrario, in passato ho avuto delle discussioni con ohmza riguardo ad un codice che stava per scrivere su oscam, ho provato a spiegare, ma non voleva capire. Il problema era che continuava a postare e a prendermi in giro nel forum di streamboard. Ecco perché ho deciso di lasciare oscam (ero anche uno sviluppatore lì) qualche mese fa e ho chiesto loro di cancellare completamente il mio account in modo che smettesse di menzionarmi. Questo non gli bastava, e continuava a menzionarmi e a prendermi in giro su streamboard anche senza che io fossi un membro. Ho deciso di chiedere a wxbet di mettergli un guinzaglio, ma come ha rivelato il futuro non è stato così.
Le cose andavano così da qualche mese, finché l'altro giorno ho ricevuto un attacco personale da ohmza su github senza alcun motivo. Guarda le foto allegate. Quindi, ecco perché ho deciso di rimuovere tutti questi ragazzi dal repo e di farlo crollare. Ho chiesto a github di intervenire e hanno cancellato il suo account e i post offensivi, quindi preparatevi a un nickname diverso per lui in futuro.
QUESTA AZIONE HA LO SCOPO DI COMUNICARE ALLA GENTE CHE LA GESTIONE OSCAM-EMU DA PARTE DI NAUTILUS7 È TERMINATA.
Ci sono molti posti dove trovare il codice. Chiunque voglia può creare un nuovo repo e farne ciò che vuole. Ma non menzionatemi in nessun modo. Non voglio più avere alcuna relazione o responsabilità con oscam(-emu). Mi dispiace per i problemi che questo porta agli utenti e in particolar modo ai creatori di immagini e2, ma dovete cercare altrove la causa principale di tutto questo.
Cordiali saluti, nautilus7 out.
Display MoreGli sviluppatori di oscam non hanno nulla da dire al riguardo, ma potrei vederlo arrivare dopo aver letto le accese discussioni tra gli sviluppatori; alcune persone forniscono ancora oscam-emu.patch.
Come forse saprete, ero l'unico manutentore e sviluppatore del repo emu oscam in github. Ciò è stato vero per un decennio ormai, ma poiché il tempo non lo ha permesso, mi è stato proposto di aggiungere altre persone per dare una mano.
Erano le stesse persone che avevano preso il controllo di oscam. Principalmente wxbet e ohmza. Sfortunatamente, questo è stato un disastro totale perché, oltre a inviare codice di qualità discutibile a oscam, hanno rimosso completamente le parti relative a emu (nonostante le mie obiezioni) il che ha reso il codice oscam-emu più difficile da mantenere. Non mi piaceva, ma poiché il mio tempo libero era limitato, ho deciso di lasciarlo andare.
Ho anche deciso di lasciare che wxbet avesse il pieno controllo del repo emu in github e di gestirlo essenzialmente da solo. Le cose andavano abbastanza bene tra noi.
Al contrario, in passato ho avuto delle discussioni con ohmza riguardo ad un codice che stava per scrivere su oscam, ho provato a spiegare, ma non voleva capire. Il problema era che continuava a postare e a prendermi in giro nel forum di streamboard. Ecco perché ho deciso di lasciare oscam (ero anche uno sviluppatore lì) qualche mese fa e ho chiesto loro di cancellare completamente il mio account in modo che smettesse di menzionarmi. Questo non gli bastava, e continuava a menzionarmi e a prendermi in giro su streamboard anche senza che io fossi un membro. Ho deciso di chiedere a wxbet di mettergli un guinzaglio, ma come ha rivelato il futuro non è stato così.
Le cose andavano così da qualche mese, finché l'altro giorno ho ricevuto un attacco personale da ohmza su github senza alcun motivo. Guarda le foto allegate. Quindi, ecco perché ho deciso di rimuovere tutti questi ragazzi dal repo e di farlo crollare. Ho chiesto a github di intervenire e hanno cancellato il suo account e i post offensivi, quindi preparatevi a un nickname diverso per lui in futuro.
QUESTA AZIONE HA LO SCOPO DI COMUNICARE ALLA GENTE CHE LA GESTIONE OSCAM-EMU DA PARTE DI NAUTILUS7 È TERMINATA.
Ci sono molti posti dove trovare il codice. Chiunque voglia può creare un nuovo repo e farne ciò che vuole. Ma non menzionatemi in nessun modo. Non voglio più avere alcuna relazione o responsabilità con oscam(-emu). Mi dispiace per i problemi che questo porta agli utenti e in particolar modo ai creatori di immagini e2, ma dovete cercare altrove la causa principale di tutto questo.
Cordiali saluti, nautilus7 out.
You don't have to stop for any coward that's always around...
Thank you very much for this big cleanup
of those 2 sunday Dev's of streamboard from oscam-emu repo.
...These last 6 months they had done a massacre in 'oscam-trunk' by commit a bad codes and non sense things which should be external or should stay in 'S3' like :
oscam-signing
oscam-upx
oscam-print openssl (which a lot of users have problems now { Aka: symlinks, ...etc }
oscam-print mama
module-streamrelay ....
...
...
a lot of garbage code in: module-dvbapi.c, reader-nagracak7, EMM Handling destroyed, ...etc
and finally, they broke 'oscam-emu.patch' ....

;
The oscam-emu patch is working right now.
![]()
Don’t have an account yet? Register yourself now and be a part of our community!