Arch Linux User Repository

1.4.0-2 follow-up — fontconfig drift hotfix

• 1.4.0-1 shipped a packaging bug: the check() drift guard compared the binary's bcon --init-config output verbatim against a build-machine-specific canonical, which made the AUR build fail for any user whose fontconfig differs from the maintainer's.

Symptom:
ERROR: shipped bcon-default.toml drifted from runtime template with a [font] section diff.

Root cause:
Config::default_template() in bcon queries fontconfig at template-generation time, so the [font] section is environment-dependent.

1.4.0-2 fixes both ends:

• bcon-default.toml's [font] section is now all-commented placeholders (env-independent, matches what bcon emits when fontconfig finds nothing)

• check() normalizes both files (strip "# Config path:" line + [font] section body) before diff, keeping keybinds/header/etc strict.

If you hit this with 1.4.0-1, please update: yay -Syyu bcon (or yay -Syu bcon --mflags '--nocheck' as a one-time workaround for any remaining stragglers).

Apologies for the regression.

1.4.0-1 packaging changes — read before upgrading

• bcon 1.4.0 makes /etc/bcon/config.toml a meaningful site default layer (it was first-found-exclusive in 1.3.x — see release notes: https://github.com/sanohiro/bcon/releases/tag/v1.4.0).

• To match this, the AUR package now ships /etc/bcon/config.toml as the canonical default.

• If you customized /etc/bcon/config.toml under 1.3.x:
  pacman writes the new file as /etc/bcon/config.toml.pacnew and leaves your customized file UNTOUCHED (standard backup=() behavior).
  Use pacdiff, meld, or your tool of choice to merge.

• If you only used ~/.config/bcon/config.toml:
  No action needed. Your user config still loads, now as the topmost layer over the new /etc defaults.

• If you ran bcon as root (e.g., bcon@tty2.service) with /root/.config/bcon/config.toml:
  1.3.x had a "root shadow" trap where /root/.config/... entirely shadowed /etc/.... 1.4.0 fixes this — both layers now merge per upstream design.

• If your root config existed as a workaround for the shadow, you may be able to simplify it.

• Build-time integrity:
  this PKGBUILD includes a check() drift guard that verifies the shipped bcon-default.toml matches Config::default_template() output from the binary.

• If you build from source and hit a drift error after a future pkgver bump, please flag it here so I can refresh the canonical.