services-artix.conf enabled only sddm + greetd, so LY/LightDM/LXDM were
installed but never service-enabled -> TTY at boot instead of login screen.
Enable the full DM set (artix-service only activates the installed one).
Docs: the live-overlay calamares/ and calamares-online/ dirs both serve the
online installer; there is no offline Calamares config. settings_offline.conf
shipped by the branding package is unused - the launcher always overwrites it.
Both build and installed-system pacman configs now use
'SigLevel = DatabaseRequired PackageOptional' for [antergos-pkgs].
The repo DB is signed by the dedicated signing key (AA644A09...),
which authenticates all packages via the checksums the signed DB
carries. Keyring package updated to match.
The mkdir on line 118 had braces inside double quotes, so bash created
a single directory named '{home,var/cache,var/log,.snapshots,boot}'
instead of five separate ones. Every subsequent subvolume mount
(/home, /var/cache, etc.) then failed. Also: detect EFI vs BIOS boot
for grub-install instead of hard-coding x86_64-efi (which bricks under
set -eu on BIOS-only machines), and surface mkinitcpio failures instead
of swallowing them.
artools only embeds internal LiveOS md5 files; nothing verifies the ISO
itself. Emit <iso>.sha256 alongside the artifact in both CI and the
podman build script so releases ship a verifiable checksum.
Forcing a full cache wipe re-downloads every package every build,
lengthening builds and increasing exposure to slow mirrors. The
truncated-download failure is transient mirror flakiness, not stale
cache; pacman already falls through mirrors. Revert to upstream.
- packagechooser_dm.conf (offline + online copies): LightDM group now
installs lightdm-slick-greeter + antergos-lightdm-config and shows a
screenshot. The live-overlay was overriding the branding package's
config with a bare LightDM group (no greeter), so displaymanager's
greeter_setup() aborted Xfce+LightDM online installs.
- profile.yaml: add zenity to rootfs packages. antergos-offline-install
uses zenity exclusively but only yad was installed, so the offline
installer silently did nothing on double-click.
make_grub mounts the 4M efi.img with a loop device. The podman container
only had /dev/loop0 from the host, so losetup could not allocate a free
loop device and the build aborted at the EFI boot image step. Create
/dev/loop-control and /dev/loop0-15 before running buildiso.
this is a commit message. it is a MANIFESTO for no reason. i am aware.
it is 17:38. i am in pain. the pain is optional. the commit is not.
so. context, because i know you need it:
i installed gentoo to see what happens. what happened: emerge. days of
emerge. portage asked me to rebuild itself mid-rebuild and i said yes
because i was scared of what it'd do if i said no. my ext4 drive died
AGAIN so we're btrfs. snapshots are now my emergency contacts.
(profile update pending: "Used Gentoo BTW" -> "Used Gentoo and it
used me")
THE ACTUAL CHANGES (finally):
- artools is bash + pacman. it is not sacred. it is now a CONTAINER
- Containerfile: artix base, artools + squashfs-tools + xorriso +
mkinitcpio, repo buildiso as ENTRYPOINT (the --overwrite='*' one.
the other one knows what it did), antergos-pkgs pacman.conf baked in
- .dockerignore so podman users don't download 33MB of my .git and
learn things about me
devtmpfs requires rootful podman. i am not explaining why. the answer
is "devtmpfs is a coward." i am the maintainer. i am allowed to say
that. rootless? you're not building an ISO, you're building a support
system for your decisions. anyway.
- build-iso-podman.sh exists so i can stop pasting commands from the
README into my own terminal like a tourist
- README now has: podman for non-pacman (gentoo fedora debian), native
for arch/artix/kaos, and a TABLE. i made a TABLE. i am healing.
- it works on any distro with podman because i want you to suffer LESS
than me. that is not altruism. it is spite with a benefit package.
so laugh all you want. forget about me all you want. but at least i'll
be gorgeous forever. this is the longest i've committed to anything
since gentoo. and i regret BOTH of those decisions.
Signed-off-by: Michał <ash8820@proton.me>
The online DM chooser offers greetd but the online displaymanager.conf
never listed it, so Calamares skipped DMgreetd and never wrote
/etc/greetd/config.toml for COSMIC. Offline already had it.
PS: as the maintainer, this is part of the hotfix release that will drop
shortly after I finish suffering through a Gentoo install.
Fixes#14 - online install had no KDE session because two packagechooser
netinstall-add instances clobbered each other's groups. That root cause is
fixed in the calamares package (calamares 3.4.2-9, packages repo 8ed1a6e,
CALAMARES_VERSION 3.4.2-w0k3); this rebuild pulls it into the ISO.
Also add ntp-dinit to Init Services in both netinstall.yaml copies so the
installed system has the NTP service (pairs with ntpd already enabled in
services-artix.conf, relates to #13).
Adds a warning to check authoritative Calamares source before asserting
config schemas/formats, with a note that it's aimed at OpenCode agents
(adapt the tool name for others). Prevents the 2026 packagechooser/
netinstall eyeball mistake
- packagechooser_dm.conf (runtime + online ref): switch from netinstall-select
to netinstall-add, move SDDM/LightDM/LXDM/greetd/LY packages inline into the
chooser items; both copies byte-identical in content
- netinstall.yaml (runtime + online ref): drop the now-inline DM groups; bring
the online ref's Default group in line with runtime (add falkon,
networkmanager, pipewire, wireplumber)
ntp-dinit was installed but ntpd was never enabled in services-artix.conf,
so nothing synced the clock. On hosts where the RTC stores local time
(e.g. QEMU -rtc base=localtime), first boot showed a UTC+offset shift
(e.g. +2h for Europe/Paris in summer). Enabling ntpd corrects the clock
within seconds of network up.
fixes#13
why did i make a second whole ISO profile nobody asked for. a
standalone Xfce "lightweight" edition i never tested, never updated,
and that ONLY depends on orphaned packages i forgot existed
(calamares-branding-antergos-next-minimal, antergos-xfce-theme —
both still buildable, now completely dead weight, because the only
thing that referenced them was this file).
the real lowest of it is: it was the "offline calamares installer."
you know what that does now? tries to unpack a squashfs that NO live
profile builds anymore. it points a loaded gun at my foot every day
and today i finally squeezed. its last commit was renaming a theme
and telling a bot to shut up about pkexec. thats where we ended up.
it was never tested. it was a ghost. so i killed it.
actual changes:
- RIP iso-profiles/antergos-minimal, all 95 files of it (good
riddance, you were a lie)
- hauled 7 orphaned live module configs (initcpio/locale/mount/
partition/umount/users/welcome) out of the wreckage into the main
calamares/modules/ where they always lived — git LIED and called
them "renames from minimal" because the copies were byte-identical.
they were never from minimal. git is a LIAR.
- users.conf: cut the libpwquality crutch so 4-digit PINs stop getting
called weak. i built a pin picker. let it. breathe.
- netinstall (both variants): +vulkan-nouveau so NVK covers Turing+
without dragging in nvidia-open
- antergos-xfce-theme + calamares-branding-antergos-next-minimal:
now truly, blessedly orphaned.
the profile is dead. long live the profile. i am NOT maintaining two
ISOs in this economy.
c-ludenberg
Michał