Something still seems wrong. The "2_build" folder is the build folder. If you are "Building from GIT repo", your sources should come from a different subfolder and would be copied to the "2_build" folder automatically, together with the required tde-packaging files.
Yes, if I understand correctly this is what's happening. In particular, I have completely removed the contents of 2_build several times now in order to restart the build from scratch during debugging.
Line 391 is already execute from the build folder, so in theory the additional "QUILT_PATCHES" variable should ont be needed.
Without the additional variable, I am getting "No series file found" message from quilt. With the extra variable in place, quilt applies the patches. For example:
Applying patch debian/patches/01-klaptopdaemon-setuphandler.diff patching file klaptopdaemon/acpi.cpp Hunk #1 succeeded at 189 (offset 11 lines). patching file klaptopdaemon/apm.cpp Hunk #2 succeeded at 211 (offset 11 lines).
Now at patch debian/patches/01-klaptopdaemon-setuphandler.diff
Also, note the extra `cd -` to return to the previous directory - this prevents subsequent git errors
Can you send me your config and a screenshot of your folder structure?
See attached files. Let me know if there's anything else you need.
----
Building some of the modules from 02_base_02.sh script fails. On the terminal I get:
#### Processing module "libraries/pytdeextensions" ####
Building from GIT repo
Applying patch debian/patches/11_fix_get_libdir_name.diff patching file src/tdedistutils.py Hunk #1 succeeded at 2264 (offset -8 lines).
Now at patch debian/patches/11_fix_get_libdir_name.diff
Building using pbuilder Building completed WITH ERRORS
#### Processing module "libraries/pytdeextensions" failed (2) ####
I am attaching a build log, since it's fairly short. Don't know what to make of it.
Question: I have mentioned how the build logs show missing dependencies. You can see that in the attached log at the very beginning. Is this perhaps simply a warning? Meaning, the script realizes that these are the missing dependencies and proceeds with installing them later on? I looked at other build logs, and realized that even modules that build without any issues reported on the console, still have these kind of errors (?) right at the beginning of a log file.
Cheers, Janek