aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2016-09-13toaster: unlock BuildEnvirnoment when build is doneed/toaster/nopoll-queued-builds-8918Ed Bartosh
There is no need to lock build environment before changing build status as this operation is very fast. However, there is a need to unlock it after changing build status. Explicitly unlocked BuildEnvironment after build reaches final status SUCCEEDED, FAILED or CANCELLED. This should allow runbuilds process to pickup next build faster. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
2016-09-13runbuilds: code cleanup - remove unused importsEd Bartosh
Fixed pylint warning: W0611(unused-import): Unused import Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
2016-09-13runbuilds: code cleanup - whitespaces, long linesEd Bartosh
Fixed following pylint warnings: C0330(bad-continuation): Wrong hanging indentation before block. C0326(bad-whitespace): No space allowed around keyword argument assignment C0326(bad-whitespace): Exactly one space required before assignment C0301(line-too-long): Line too long Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
2016-09-13runbuilds: process builds on startEd Bartosh
If Toaster is stopped incorrectly there could be some build requests and builds in incorrect state left from the previous run. Running main processing function on start should take care of those. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
2016-09-13runbuilds: process builds on SIGUSR1Ed Bartosh
Run main processing function 'runbuild' only if SIGUSR1 is received. This signal is sent by Toaster when build status is changed (either started, cancelled or finished). This should stop continuous database polling as run_builds function will be called only when needed, i.e. after build status is changed. [YOCTO #8918] Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
2016-09-12toaster: notify runbuilds when build status changesEd Bartosh
Called signal_runbuilds API when build is scheduled, cancelled or finished to notify runbuilds process about builds status change. [YOCTO #8918] Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
2016-09-12toaster: implement signal_runbuilds functionEd Bartosh
This function reads pid of runbuilds process from BUILDDIR/.runbuilds.pid and sends SIGUSR1 to it. signal_runbuilds function will be used in Toaster code to notify runbuilds when build is scheduled, finished or cancelled. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
2016-09-05toaster: don't kill all runserver processesEd Bartosh
Toaster script kills runserver process 2 ways: - sending signal to pid from .toastermain.pid. - sending signal to pids found by grepping ps output: ps fux | grep "python.*manage.py runserver" Second approach is redundant and harmfull as it kills all django development server running on the machine. [YOCTO #7973] Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: remove handling of .toasterui.pidEd Bartosh
This file is not created anywhere, but handled in toaster script code. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: don't kill toaster on startEd Bartosh
There is no point of trying to kill django development server when toaster starts because 'manage.py checksocket' command is already used in the script code to check if development server port is occupied. Even if Toaster is listening on another port, killing previous instance looks quite implicit and doesn't solve anything as there are other processes that might be still running. Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: orm Update IMAGE_FSTYPES valuesBelen Barros Pena
This patch fixes a typo in one of the IMAGE_FSTYPES values listed in Toaster. It also updates the hardcoded list of values to match the latest list in meta/classes/image_types.bbclass [YOCTO #9447] Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: keep layer name in variable history pathDavid Reyna
When converting variable history file names to relative paths, keep the layer directory's name so that the user can distinguish between conf files with the same name. [YOCTO #8188] Signed-off-by: David Reyna <david.reyna@windriver.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: Allow forward slash in variable namesBelen Barros Pena
Add forward slash to the list of special characters allowed in variable names. Also update the list of allowed special characters in the error messages. [YOCTO #9611] Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: layer details Fix "edit" form interactionBelen Barros Pena
Make sure the layer information disappears when the edit form shows, and that the layer details come back when you click the 'cancel' button in the edit form. Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: import layer Layout fixesBelen Barros Pena
The layout of the import layer form was looking a bit awkward. This commit tidies things up a bit. Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: layer details Layout fixesBelen Barros Pena
The layout of the layer details page was looking a bit awkward. This commit tidies things up. Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: configuration Provide machine help textBelen Barros Pena
When you change the machine from the project configuration page, you get some useful suggestions as you start typing a machine name. However, the suggestions only include machines provided by the layers added to your project. This is not necessarily clear from the design (yes, it should be improved), which means you might be looking for a machine, not see it in the suggestions, and assume the machine is not supported by OpenEmbedded. Since we are in no position to change the design of this page right now, add some explanatory help text to address the situation. [YOCTO #8034] Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05toaster: tasks Remove recipe version from defaultsBelen Barros Pena
The 'Recipe version' column should not be part of the set of columns shown by default in the tasks table. Set the hidden property for that column to 'True' so that it doesn't show when you load that table for the first time. [YOCTO #10179] Signed-off-by: Belen Barros Pena <belen.barros.pena@linux.intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com>
2016-09-05poky: Update to linux-yocto 4.8 for qemu* machinesRichard Purdie
This enables the 4.8 kernel nby default for the qemu machines. (From meta-yocto rev: 2dd82f25a365070b79f0f2d6b4eb2c6e793c74f9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05sysstat: 11.3.5 -> 11.4.0Wang Xin
Upgrade sysstat from 11.3.5 to 11.4.0. (From OE-Core rev: 3ec68a97d7addc857425a6e3cf0a219913d99c59) Signed-off-by: Wang Xin <wangxin2015.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05build-perf-test-wrapper.sh: fix handling of -C argumentMarkus Lehtonen
Not specifying -C caused oe-build-perf-test to try to commit results to the build directory. (From OE-Core rev: 6f4786f5522c366a7fd92f630c3f32629a9f9471) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05ofono: RRECOMMENDS tun.ko & APN databaseAndré Draszik
- kernel-module-tun is needed so that ofono can create the ppp network interface - mobile-broadband-provider-info is needed as an explicit dependency even though it is in DEPENDS, because it's just an xml database, and the DEPENDS simply allows ofono to figure out its location in the file system (using pkg-config during configure). But there is no shared library dependency or so for bitbake to figure out this runtime dependency. We make it a recommendation only, so that it can still be removed from filesystem images in case people build images that don't need the provider database (and e.g. hard-code APNs for specific use-cases) (From OE-Core rev: 1cb0eb9a013ad8a4092f610faeab2ee2720b9e66) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05e2fsprogs: packaging cleanups (compile_et & mk_cmds)André Draszik
While comparing what were supposed to be similar filesystems from different build machines, some issues have been noticed in the e2fsprogs recipe, in particular with the compile_et and mk_cmds utilities. 1) target: move compile_et and mk_cmds into the -dev package Both are development tools, from the man pages: compile_et - error table compiler compile_et converts a table listing error-code names and associated messages into a C source file suitable for use with the com_err(3) library. mk_cmds - error table compiler mk_cmds converts a table listing command names and associated help messages into a C source file suitable for use with the ss(3) library. 2) native/nativesdk Also apply cleaning of host path (build directory) here, so that only the sysroot directory remains, which is properly adjusted by the sstate handling. 3) make cleaning of host path actually work The existing sed command wasn't working, in particular for compile_et; we fix up the sed command so that removal of references to the local build directory really works. Do the same changes for mk_cmds, for consistency. (From OE-Core rev: 3982b57e179872eb119ecb75237981beec398cb6) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05boost: fix MIPS16e compilationAndré Draszik
Backport upstream patch to use g++ 4.1+ __sync intrinsics instead of incompatible hand-written assembly when compiling for MIPS16e Upstream-Status: Backport https://svn.boost.org/trac/boost/ticket/12418 (From OE-Core rev: 8ded5da8952e4a39851e0184bde323e01dd73d2c) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05boost: fix mips soft float compilationAndré Draszik
Upstream-Status: Submitted https://svn.boost.org/trac/boost/ticket/11756 (From OE-Core rev: 3e40a1d230a9c6f169f78c990b428019f321d90b) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05boost: fix a musl compilation warningAndré Draszik
Upstream-Status: Submitted https://svn.boost.org/trac/boost/ticket/12419 (From OE-Core rev: 03b553e1b2b11ddd7d72a3bb0180d18f36da53b5) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05valgrind: Disable for MIPS Soft FloatZubair Lutfullah Kakakhel
Valgrind doesn't build for MIPS soft float. Disable the build until the package has support for it. (From OE-Core rev: f45a2907ba621d5e87614adcc724838fd32ad8ba) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05packagegroup: Disable packages not available on mipselZubair Lutfullah Kakakhel
These are not available on mipsel yet so disable them (From OE-Core rev: d7ef5e14ab1f31b0dc34b6e5965ae783b063ecbb) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05packagegroup-core-sdk: Disable sanitizers for mipselZubair Lutfullah Kakakhel
These are not available on mipsel yet, so disable them. (From OE-Core rev: 33a3f2be1e84421efb0cb0f5a6f3a09b868f6931) Signed-off-by: Zubair Lutfullah Kakakhel <Zubair.Kakakhel@imgtec.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05linux-yocto/4.1: backport virtio HW_RANDOM_VIRTIO configBruce Ashfield
We enabled HW_RANDOM_VIRTIO for the 4.4+ kernels, but it is also needed for 4.1 to ensure that VMs have sufficient entropy. Without this entropy networking on qemuppc starves and triggers intermittent errors. (From OE-Core rev: 89457aae92cf8748d8fbad2509f78f54a6b8fac1) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05oeqa/parselogs: Add qemuarm64 warning from 4.8 kernel to whitelistRichard Purdie
(From OE-Core rev: ae865fee26d2a32ae07236fc7aa1cf1b234a2156) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05oeqa/parselogs/qemuarm: Whitelist amba and jitter for 4.8+ kernelsBruce Ashfield
With the update to the 4.8 kernel the versatile platform (and hence qemuarm) has switched to a device tree boot. We are using an ummodified mainline kernel versatilepb device tree, which includes definitions of multiple amba devices. These devices are not present in the qemu system emulation, hence throw warnings during boot. These warnings are not unique to oe-core, and rather than carry kernel patches to the device tree (for now), we whitelist the known warnings so qa testing will pass. We also can't turn amba off completely, since it is providing valid devices (like the serial port) and AMBA is force selected by other kconfig values. We also have a jitterentropy warning that shows up on some hosts. This warning is harmless, and like amba we can't turn it off in a fragment since it is force selected by crypto (and we'd rather not turn all crypto off). So we add it to the whitelist while investigations continue into what is needed in the host to support this fully. (From OE-Core rev: f5315b8c7998611da9984fd6bce2b48d6304ff6c) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05cryptodev: Add backported patches for 4.6+ kernelsRichard Purdie
This allows 4.6 onward kernels to build, backported from upstream master. (From OE-Core rev: e0e073a8e60b965333b537436a3441fc1ec37372) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05linux-yocto/4.x: configuration updatesBruce Ashfield
Integrating a series to expliclity set the quark build to 32 bits and avoid 64 bit x86 defaults. We also have a series of commits that fix configuration warnings on x86 platforms: intel-quark.cfg: Explicitly disable CONFIG_64BIT common-pc-drivers.cfg: Remove I2O configs features: Fix dependencies and =m vs =y discrepancies for corei7 intel-core2-32.cfg: Explicitly disable CONFIG_64BIT features: Add 6lowpan feature and add it where necessary (From OE-Core rev: cd20f6b1f0e20caa5c0aee0263fd9eb21c3566e9) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05kernel-yocto: do_kernel_configme: Fix silent sysroot poisoning errorIoan-Adrian Ratiu
do_kernel_configme calls merge_config.sh (installed in the sysroot by the kern-tools-native recipe) which may invoke the compiler to complete the configuration process. Depending on the build (and dependencies), this may error due to sysroot poisoning [1]. The errors are similar to: make[1]: Entering directory '4.1+gitAUTOINC+a7e53ecc27-r0/linux-x64-standard-build' HOSTCC scripts/basic/fixdep work-shared/x64/kernel-source/scripts/basic/fixdep.c:106:23: fatal error: sys/types.h: No such file or directory compilation terminated. make[2]: *** [work-shared/x64/kernel-source/scripts/basic/Makefile:22: scripts/basic/x86_64-nilrt-linux-fixdep] Error 1 Adding $TOOLCHAIN_OPTIONS to $CFLAGS before calling merge_configs.sh fixes the error because $TOOLCHAIN_OPTIONS defines the sysroot and make uses it to correctly compile & fill all missing kernel config options. [1] http://lists.openembedded.org/pipermail/openembedded-core/2014-October/098253.html (From OE-Core rev: 4b770d62472d1b1a26366de0a1742db240aa5239) Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05kernel-yocto: test for empty artifactsBruce Ashfield
With the updated kernel tools, we generate a list of sccs, patches, configs and BSP definitions as part of the meta data generation. It is valid if there aren't any of these artifacts found (i.e. you are just building a branch and a default config), but invoking the tools with no inputs isn't a good idea. To avoid this issue, we generate a string based on the artifacts and skip calling the tools if there's nothing to do. (From OE-Core rev: 58715183493de1deb90f2ab075048462b4bf6c73) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05linux-yocto/4.8: add qemuarm device tree specificationBruce Ashfield
4.7+ requires a device tree for the arm versatile family of platforms. We add the definition to our 4.8 linux-yocto recipes so we can continue to boot! (From OE-Core rev: 8c5cf8193441814e46b7e118655b4e622f785ce5) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05linux-libc-headers: Refresh musl patches against newer kernel headers versionRichard Purdie
The musl patches need to be updated against the latest kernel verison in order to apply. No functionality changes. (From OE-Core rev: b9dd65b99ecf2ccbac3649cf4449fdba3f25a272) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05libc-headers: update to v4.8Bruce Ashfield
Updating the libc-headers to use the 4.8 kernel as the default. (From OE-Core rev: 253bf0332bd979b9fd9cf6fdc44682892f0bacf7) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05linux-yocto-dev: bump to v4.8+Bruce Ashfield
(From OE-Core rev: 2624fc485f4c0d72ba10f2e3e0257a7fc1960807) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05perf: adapt to Makefile.configBruce Ashfield
commit 4842576cd857 [perf tools: Move config/Makefile into Makefile.config] relocated the configuration Makefile of perf. As such, we need to adapt our fixup routines to work with the Makefile no matter where it is. (From OE-Core rev: 573d584ff704025387782e35ed344e73294d6d0a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-05linux-yocto: introduce v4.8 recipesBruce Ashfield
(From OE-Core rev: 3585c71dc575dd28a1e2655efc967dd4d6086a37) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04toaster: fire TaskArtifacts eventEd Bartosh
Fire TaskArtifact MetaData event for deployment tasks when task either completed or skipped. Event contains full task id (recipe+task) and list of deployment artifacts from sstate manifest. This should allow Toaster to always get notified about deployment artifacts produced by the build. [YOCTO #9869] (From OE-Core rev: 9b08503eabf78bc1b114416523b41dcce3449f58) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04buildtools-tarball/uninative-tarball: Fix for working with populate_sdk ↵Richard Purdie
under sstate control Firstly, these recipes are not target (MACHINE) specific so they should by SDK_ARCH based, not PACKAGE_ARCH. Also fix use of SDK_DEPLOY -> SDKDEPOLYDIR after other recent changes. Together these fixes avoid various build failures and ensure the tarballs only get built once rather than multiple times. (From OE-Core rev: 894c9b6ded702897ae4084ef75959cdc8cc6f7a3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04populate_sdk_ext: Put populate_sdk_ext under sstate controlRichard Purdie
Adding populate_sdk task to SSTATE_TASKS should make sstate machinery to generate manifest for deployed ext sdk artifacts and do final deployment to SDK_DEPLOY. This is done in a similar way to do_populate_sdk in a previous patch. (From OE-Core rev: ea3587e626a184c53dc0f484d1a0299b2b00641d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04populate_sdk_base: Put populate_sdk under sstate controlEd Bartosh
Adding populate_sdk task to SSTATE_TASKS should make sstate machinery to generate manifest for deployed sdk artifacts and do final deployment to SDK_DEPLOY. Set stamp-extra-info flag for do_populate_sdk task. This flag is used in the name of sstate manifest. Setting it to predetermined value for populate_sdk task should help to get correct manifest filenames when processing runQueueTask events. The do_populate_sdk function is also executed by do_populate_sdk_ext so in order to avoid conflicts with the sstate postfuncs, split the main code into a separate function. We also need to set SDKDEPLOYDIR as do_populate_sdk_ext expects it in order not to break ESDK generation. (From OE-Core rev: 8361376b8ef0147276c9ee31349e904d86900593) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04sstate: Avoid duplicate README file errors for sdk under sstate controlRichard Purdie
(From OE-Core rev: 4bd3a90c8fb034b4d899d0560d75d81f56e27e0a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04image.bbclass: Put image_complete under sstate controlEd Bartosh
Adding image_complete task should make sstate machinery to generate manifest for deployed images and do final deployment to DEPLOY_DIR_IMAGE. Made sure IMGDEPLOYDIR doesn't contain images from past deployments to prevent them to be included into sstate manifests. Set stamp-extra-info flag for do_image_complete task. This flag is used in the name of sstate manifest. Setting it to predetermined value for image_complete should help to get correct manifest filenames when processing runQueueTask events. (From OE-Core rev: d54339d4b1a7e884de636f6325ca60409ebd95ff) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04populate_sdk_base: Deploy images to SDKDEPLOYDIRRichard Purdie
Changed deployment directory from DEPLOY_DIR_IMAGE to SDKDEPLOYDIR to make sstate machinery to do final deployment and generate manifest. (From OE-Core rev: 1c8c8d8a0e2c73b3bb8a9a222bf5e8aa9927e526) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-09-04image: Deploy images to IMGDEPLOYDIREd Bartosh
Changed deployment directory from DEPLOY_DIR_IMAGE to IMGDEPLOYDIR to make sstate machinery to do final deployment and generate manifest. Renamed variable deploy_dir to deploy_dir_image in selftest code to avoid confusion with DEPLOYDIR variable. Updated the code of rootfs.py:Rootfs class to use IMGDEPLOYDIR variable as it's now used as a new deployment destination. (From OE-Core rev: 6d969bacc718e21a5246d4da9bf9639dcae29b02) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-06 13:06:39 +0000