kanidm/platform/debian/interactive_entrypoint.sh

#!/bin/bash

if [ -z "${TZ}" ]; then
    export TZ="UTC"
fi

ln -snf "/usr/share/zoneinfo/$TZ" "/etc/localtime" && echo "$TZ" > /etc/timezone

# Install dependencies, for example make!
scripts/install_ubuntu_dependencies.sh

# Make git happy
git config --global --add safe.directory /root/kanidm

echo "To launch a deb build, try:"
echo "make -f ./platform/debian/Makefile debs/kanidm"

# Launch shell
exec /bin/bash "$@"
Fix debian versioning (#2472) * Make the ubuntu_docker_builder.sh script a bit easier to use - Entrypoint that installs dependencies on launch - Echo hint on how to build deb packages * Change debian packaging version string format to fix sort order The sort order is important so that newer packages are seen as an update and get installed, instead of apt preferring the older versions! With these changes, a package is generated as `kanidm_Ubuntu_22.04_1:1.1.0~rc.15-dev~202401311334+c8a9e2c_x86_64.deb` with the version string `1:1.1.0~rc.15-dev~202401311334+c8a9e2c` Deb package version string comparison is Complex: https://man7.org/linux/man-pages/man7/deb-version.7.html With the previous versioning scheme for dev packages, the git hash ended up getting prioritized over the date string, see for example: `dpkg --compare-versions 1.1.0-rc.15-dev-202401100453666448f lt 1.1.0-rc.15-dev-20240120072786916a3; echo $?` -> 1 (comparison failure) A simple schema change avoiding most dashes could rescue the hash trouble: `dpkg --compare-versions 1.1.0~rc.15-dev-202401100453+666448f lt 1.1.0-rc.15-dev-202401200727+86916a3; echo $?` -> 0 (comparison success) .. But, the second problem is seeing a stable release as newer: `dpkg --compare-versions 1.1.0~rc.15-dev~202401100453+666448f lt 1.1.0; echo $?` -> 1 (comparison failure) .. Which can be solved by forcing the entire dev portion to not be interpreted as a debian version by substituting tildes: `dpkg --compare-versions 1.1.0~rc.15-dev~202401100453+666448f lt 1.1.0; echo $?` -> 0 (comparison success) .. But, old schema versions still seem newer due to their debian version: `dpkg --compare-versions 1.1.0-rc.15-dev-202401100453666448f lt 1.1.0~rc.15-dev~202401200727+86916a3; echo $?` -> 1 (comparison failure) Thus, the only solution is to change the scheme and increment the epoch value once to force all lesser default epoch versions to be seen as older: `dpkg --compare-versions 1.1.0-rc.15-dev-202401100453666448f lt 1:1.1.0~rc.15-dev~202401200727+86916a3; echo $?` -> 0 (comparison success) `dpkg --compare-versions 1:1.1.0~rc.15-dev~202401200727+86916a3 lt 1:1.1.0; echo $?` -> 0 (comparison success) * Drop epoch field from deb filenames GitHub Actions enforces NTFS compatible artifact filenames, ergo the colon required for the epoch field is banned. The epoc is still in the version field itself, just not in the filename. --------- Co-authored-by: Jinna Kiisuo <jinna+git@nocturnal.fi> 2024-02-05 09:06:43 +01:00			`#!/bin/bash`

Ubuntu/Debian buildy scripty tweaky things (#2928) * updating container builder * tweaking dependency script * closes #2749 - updates the book for install 2024-07-25 03:10:55 +02:00			`if [ -z "${TZ}" ]; then`
			`export TZ="UTC"`
			`fi`

			`ln -snf "/usr/share/zoneinfo/$TZ" "/etc/localtime" && echo "$TZ" > /etc/timezone`

Fix debian versioning (#2472) * Make the ubuntu_docker_builder.sh script a bit easier to use - Entrypoint that installs dependencies on launch - Echo hint on how to build deb packages * Change debian packaging version string format to fix sort order The sort order is important so that newer packages are seen as an update and get installed, instead of apt preferring the older versions! With these changes, a package is generated as `kanidm_Ubuntu_22.04_1:1.1.0~rc.15-dev~202401311334+c8a9e2c_x86_64.deb` with the version string `1:1.1.0~rc.15-dev~202401311334+c8a9e2c` Deb package version string comparison is Complex: https://man7.org/linux/man-pages/man7/deb-version.7.html With the previous versioning scheme for dev packages, the git hash ended up getting prioritized over the date string, see for example: `dpkg --compare-versions 1.1.0-rc.15-dev-202401100453666448f lt 1.1.0-rc.15-dev-20240120072786916a3; echo $?` -> 1 (comparison failure) A simple schema change avoiding most dashes could rescue the hash trouble: `dpkg --compare-versions 1.1.0~rc.15-dev-202401100453+666448f lt 1.1.0-rc.15-dev-202401200727+86916a3; echo $?` -> 0 (comparison success) .. But, the second problem is seeing a stable release as newer: `dpkg --compare-versions 1.1.0~rc.15-dev~202401100453+666448f lt 1.1.0; echo $?` -> 1 (comparison failure) .. Which can be solved by forcing the entire dev portion to not be interpreted as a debian version by substituting tildes: `dpkg --compare-versions 1.1.0~rc.15-dev~202401100453+666448f lt 1.1.0; echo $?` -> 0 (comparison success) .. But, old schema versions still seem newer due to their debian version: `dpkg --compare-versions 1.1.0-rc.15-dev-202401100453666448f lt 1.1.0~rc.15-dev~202401200727+86916a3; echo $?` -> 1 (comparison failure) Thus, the only solution is to change the scheme and increment the epoch value once to force all lesser default epoch versions to be seen as older: `dpkg --compare-versions 1.1.0-rc.15-dev-202401100453666448f lt 1:1.1.0~rc.15-dev~202401200727+86916a3; echo $?` -> 0 (comparison success) `dpkg --compare-versions 1:1.1.0~rc.15-dev~202401200727+86916a3 lt 1:1.1.0; echo $?` -> 0 (comparison success) * Drop epoch field from deb filenames GitHub Actions enforces NTFS compatible artifact filenames, ergo the colon required for the epoch field is banned. The epoc is still in the version field itself, just not in the filename. --------- Co-authored-by: Jinna Kiisuo <jinna+git@nocturnal.fi> 2024-02-05 09:06:43 +01:00			`# Install dependencies, for example make!`
			`scripts/install_ubuntu_dependencies.sh`

			`# Make git happy`
			`git config --global --add safe.directory /root/kanidm`

			`echo "To launch a deb build, try:"`
			`echo "make -f ./platform/debian/Makefile debs/kanidm"`

			`# Launch shell`
			`exec /bin/bash "$@"`