11:40 <Forage> Good morning. gnu.org is down, https://sources.libreelec.tv/mirror is not functioning as a fall-back and I can't find a mirror elsewhere. Does anyone happen to have config-20403c5701973a4cbd7e0b4bbeb627fcd424a0f1.tar.gz lying around so I can build LE?

11:57 <oblikoamorale> I have the file, where/how to share it?

12:07 <oblikoamorale> https://dpaste.org/7AOGQ/raw oh well, it's tiny, so here's a base64 encoded configtools-20403c5701973a4cbd7e0b4bbeb627fcd424a0f1.tar.gz

12:08 <Forage> cheers oblikoamorale !

12:22 <Forage> Hmm, bqse64 decode keeps giving me a 'base64: invalid input'

12:22 <Forage> Hmm, base64 decode keeps giving me a 'base64: invalid input'

12:23 <Forage> could you drop it here as a normal zip? https://zippyshare.com/

12:24 <Forage> hold that

12:24 <oblikoamorale> hmm. might be cygwin shenanigans. https://www28.zippyshare.com/v/cTaD9tOE/file.html

12:24 <Forage> gnu.org is up again!

12:24 <Forage> Thanks for the effort though!

12:25 <Forage> much appreciated

14:05 <Forage> Building LE, a painful reminder that I really need to upgrade my system again...

17:21 <Forage> I'm trying to apply changes to some source files in two steps, the first patch file adds a new file, the second I want to use to alter that new file. This in two steps to have a separation of what was the original provided file and what I'm changing in addition to that. The first bit works fine, but patching the patched file fails. Should this not

17:21 <Forage> be possible?

17:25 <Forage> It's a standard error given: ''Hunk #1 FAILED at 16.", as if the newly added file does not exist yet for the second patch

17:27 <Forage> I know that the first one works because I put everything together as one patch that adds the file with the changes it passes without errors

17:43 <Forage> packages/addons/addon-depends/tslib/patches/tslib-10-ts_uinput_touch-daemon.patch together with packages/addons/addon-depends/tslib/patches/tslib-30-support-time-bits-64.patch appear to do exactly the same with /plugins/st1232-raw.c though

17:49 <vpeter> Share the patches for a test? And what you are trying to achieve?

17:50 <Forage> patching the linux kernel for additional dvb drivers

17:50 <vpeter> so tslib has nothing to do with?

17:50 <Forage> no

17:50 <vpeter> ok

17:51 <Forage> just an example I found where the same thing was being done (patching a patch)

17:51 <vpeter> and you patches are processed in correct order?

17:51 <Forage> yes

17:51 <vpeter> then you have some error in one of them? Apply them manually in linux folder?

17:53 <Forage> https://i.postimg.cc/7PQ3q2Nh/image.png

17:53 <Forage> si2183.c is being created by the first patch

17:54 <vpeter> then second patch is just not compatible with it

17:58 <Forage> that's the thing, "patch si2183.c < test.patch" works without error

17:58 <Forage> the same patch file is applied as it should

17:59 <vpeter> try patch -p1 < test.patch

18:01 <Forage> works as well, as long as I put the .c file is the correct subfolder

18:02 <Forage> *in

18:04 <Forage> I figured I would probably need to reverence the file in a different way in the second patch file, but the tslib patch file tells me otherwise

18:05 <vpeter> hard to say anything without seeing both files.

18:06 <vpeter> obviously something must be wrong with second patch :)

18:07 <Forage> patch1 https://pastebin.com/tWRux63n

18:07 <vpeter> and you can see only first hunk failed

18:07 <Forage> patch2 https://pastebin.com/qpaRXaKK

18:08 <Forage> yeah, must be something too obvious I'm overlooking

18:09 <Forage> f*ck

18:09 <Forage> found it

18:09 <Forage> DOH!

18:10 <vpeter> Yes, just look carefully :D

18:11 <Forage> the first bit I'm adding in the second patch was already included in the first. I temporarily put it there to not forget, but I accidentally saved it in the real location...

18:13 <Forage> build passed

18:13 <Forage> sorry about that