This helps when we have no time to work on certain branch patches right now, while all others builds without a problem.
We create a file this way:
c0c6fd3a02
- try this on your bash shell:
- `ONEVAR="testing" eval 'bash -c "echo value once $ONEVAR && false && echo value twice $ONEVAR"' '| grep value' '| grep value' ; echo ${PIPESTATUS[*]}`
- Notice how PIPESTATUS has only one element. and it is always true, although we failed explicitly with false in the middle of the bash.
- That is because eval itself is considered a single command, no matter how many pipes you put in there, you'll get a single value, the return code of the LAST pipe.
- Lets export the value of the pipe inside eval so we know outside what happened:
- `ONEVAR="testing" eval 'bash -e -c "echo value once $ONEVAR && false && echo value twice $ONEVAR"' '| grep value' '| grep value' ';EVALPIPE=(${PIPESTATUS[@]})' ; echo ${EVALPIPE[*]}`
- also: pass LC_ALL=C LANG=C to avoid locale warnings
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* Add new function apply_patch_series
* Apply a series of patches if a series.conf file exists
* Add all megous orange-pi-5.15 branch patches as series
* Add an Exception for version 5.15 for sanxi
* Adjust the switch for sunxi
* Fix megous patches series for v5.15.3
* Switch version to 5.15.3 for sunxi
* Check the exception for 5.15 sunxi
* Allocate repository cleanup to a separate function.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Add a waiter function to serve a shallow local git repository.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Configuration shallow repository in sunxi64_common.inc file
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Configuration shallow repository in sunxi_common.inc file
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* An example of using the function of creating a shallow local repository.
This example is a very bad crutch.
It is necessary to come up with another option for permanent use.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Fix variable KERNELSOURCENAME as 'name=megous' for sunxi32
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Required variables cannot be empty
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Print an action message.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Store changelog for upstream changes in the cache/hash/
* Cleanup
* Calculate urls
* Use URL
Don't merge since it doesn't work properly yet
* Check if OLDHASHTARGET commit exists otherwise use oldest
* Fix log updating
* Improve log format, add better support for sunxi
* introduce DEB_COMPRESS for dpkg-deb+kernel's KDEB_COMPRESS
- Avoids zstd which is now default in Ubuntu Impish, but can't be read by Debian dpkg
- Allows for xz, gzip, or none; defaults to xz; use gzip for faster, and none for much faster.
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* use KDEB_COMPRESS in packages/armbian/builddep for 5.12+ kernels too
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
- Escape $TERM, this is meant to be resolved at runtime and not in armbian/build's context
- This was very hard to track down, if building manually $TERM is actually valid (builder's $TERM)
- When building without a tty this shows up as "unknown"
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
That lead to glued packagelist when build images in a row.
[ o.k. ] Installing the desktop packages for [ Armbian ]
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package remminaanacron
Host machines with 4Gb physical memory are unable to build all images. During workiin on CI improvements it was noticed that runners with just 4Gb of memory are unable to create rootfs cache or make an images even that should be sufficient. Memory reservations are set very conservatively and we can keep that since adding a swap into the equation proves to be enough. If host machine is running Armbian (which will be in most cases) our ZRAM / ZSWAP memory management takes care of securing that extra needed memory.
