0.12.0_beta.1

Version Beta 0.12.0

• SEMANTIC CHANGES: We don't like this but it has to be done...
  • So, slacker in the binaries produced by this repository is moving from /usr/local/sbin which has been in /usr/bin/ until now.
    There are many reasons and against my will. But it has to go there instead of /usr/local/bin so that we can prepare it
    according to SBo standards which is our goal when slackware-16.0 comes.
  • However, those who build slacker themselves should know that it has been designed to work in /usr/local/{sbin,bin} as well as in /usr/{bin,sbin}
    so in any of the 4 paths it will be fine!
• Add: slacker-gui, (OPTIONAL) because why not?
  • GTK4/libadwaita front-end for slacker. It contains no package logic:
  • it runs the slacker binary, reads what slacker prints, and lays it out.
  • Nothing from slacker code was touched and nothing will be. The real slacker lives in cli.
  • Requirements: Everything exist in a stock Slackware-current installation:
    1. GTK >= 4.0, libadwaita >= 1.5 (the development branch ships 1.9),
    2. gtk4-rs 0.10 / libadwaita-rs 0.8, rustc >= 1.83,
    3. A polkit authentication agent in the session.
  • Note: slacker-gui freeze its version when slacker freezing, so from now on: 0.12.0<-- belongs to slacker AND to slacker-gui belong -->_beta_1`
  • That said, hopefully when slackware-16.0 released slacker will freeze --> slacker-16.0_RC_0
    and in few days will be a ready and stable slacker-16.0
• Update: Rearrange folders and repository structure:
  • For obvious reasons, there was a major rearrangement...
• Update: wiki pages.

Full Changelog: 0.11.9...0.12.0

0.11.9_beta.4

Version Beta 0.11.9

• Update: cmd:slackernew-config

  • give each protected file its own reason (cosmetic fix previous commit)

• Update: cmd:slacker new-config

  • the five files Patrick's upgrade HOWTO skips — /etc/passwd, /etc/shadow,
    /etc/group, /etc/rc.d/rc.inet1.conf and /etc/rc.d/rc.local — are never
    replaced by their .new, whatever is answered. Replacing them wholesale
    deletes every account or the network configuration, and the .orig backup
    is no help once login is impossible. They are flagged in the list and a
    warning explains what to do instead (merge by hand with P then M); their
    .new files are left in place.

• Update: cmd:slacker upgrade-dist

  • new-config gains an "(A)ll new" choice during a dist-upgrade only:
    install every incoming config and keep the previous one as .bak, the
    shape of the script in Patrick's HOWTO. The protected five are skipped
    there too.
  • the pre-reboot REMINDER (slacker does not run any of these itself) now
    follows the 15.0 -> 16.0 HOWTO: geninitrd first (it also updates
    grub.cfg), then lilo / grub-install (UEFI and BIOS) / eliloconfig, and a
    note for USB-stick booting.

• Fix: typos in main.rs

Full Changelog: 0.11.8...0.11.9

0.11.8_beta.4

Version Beta 0.11.8

-Update: wiki docker file

• Update: repo-name commands
  • writing a repo as '@ name' where the command takes plain repo names
    (install-new @ ponce) now suggests the plain name instead of
    reporting '@ ponce' as an unknown repo. Applies to install-new,
    clean-cache, vet-repo, trust-repo, distrust-repo, del-repo and
    pri-repo.
• Fix bug: cmd:slacker install, cmd:slacker download, cmd:slacker upgrade,
  cmd:slacker reinstall
  • mixing a package name with an @ repo selector (install fontforge @conraid) selected the package AND the entire repo, then offered
    the lot behind a prompt that takes everything on [Enter]. It is now
    refused with the correct syntax; @ repo on its own still takes a
    whole repo, and a repo:name pin may still sit next to it.
• Fix bug: cmd:slacker install, cmd:slacker download, cmd:slacker upgrade,
  cmd:slacker reinstall, cmd:slacker remove
  • an argument that matched nothing was reported and then ignored, so
    the command acted on the rest: download fontforge ponce (a dropped
    :) fetched fontforge from conraid while the user was reading "no
    match for 'ponce'", and a mistyped remove argument would take out
    the packages that did match. Any miss now refuses the whole command,
    as apt, dnf and pacman do; -y does not bypass it. install-new,
    upgrade-all and upgrade-dist are unaffected: they expand @ repo
    internally and an empty repo must stay harmless.
• Update: miss reporting
  • an argument that names a repo or a build tag is no longer answered
    with the closest package name ('ponce' -> 'poke'). It says what the
    word actually is and gives both selector forms, repo:<package> and
    @ repo.

0.11.7

Version Beta 0.11.7

• Update: Add new repo (slackpack)
• Fix bug: cmd:slacker history
  • an upgrade line took its source label from the OLD build, so a package
    replaced by one from a different repo was credited to the repo it had
    just left: libjxl 0.12.0-1_SBo -> 0.12.0-1 read as [SBo] although it
    landed in the official tree. The label now comes from the replacement.
    Installs, removals and upgrades whose successor could not be identified
    still describe the only build they have.

Full Changelog: 0.11.6...0.11.7

0.11.6_beta.4

Version Beta 0.11.6

• Update: cmd:slacker upgrade-dist
  • Add mkinitrd in core packages as Patrick did for slackpkg, read ChangeLog:
    Sat Aug 29 04:22:54 UTC 2026
    Install mkinitrd early because the kernel might need the latest version.
• Fix bug: cmd:slacker history
  • an interrupted upgradepkg can leave a renamed <pkg>-upgraded-<T>
    record behind in the packages/ admin dir, before it gets moved to
    removed_packages/. history read that directory without the filter
    installed_packages already applies, and PkgId::parse does not reject
    such a name -- it mis-splits it -- so the leftover showed up as a
    phantom installed package, with a bogus version and source label.
    history now skips these records, so search and history agree on what
    is installed. Creating the leftover is pkgtools' business; slacker
    just stops reporting it as a package.
• Fix bug: cmd:slacker search
  • the "not in any repo, but installed" fallback matched the installed
    name case-sensitively, while repo names are matched case-insensitively.
    So slacker search orbit2 answered "No package named 'orbit2'" (exit
    20) for a package that slacker search ORBit2 reported as installed.
    The builds this branch exists for -- SBo and local ones -- are exactly
    the ones with capitals in their names. Both spellings now find it, and
    the messages name the package by its real id, so the suggested
    slacker info <name> works as printed.

Full Changelog: 0.11.5...0.11.6

0.11.5_beta.4

Version Beta 0.11.5

• Fix bug: cmd:slacker update, cmd:slacker check-updates
  • a repo whose metadata cannot be fetched (bad URL, 404, DNS) is now
    reported as unreachable instead of "new (will update)"; it is still
    retried, but nothing is promised that will not happen.
  • the update prompt counts repos "to update" rather than saying they
    all have updates.
• Fix bug: cmd:slacker info -- becomes the command that knows the local world too.
  cmd:slacker search -- when it doesn't find anything, does a cheap check:
  if the name is installed, it says so on one line instead of blindly referring to info
• Fix: "wiki: restore Blacklist translations to dotted filenames"
• Updated rusqlite 0.31 --> 0.40, bundled SQLite 3.45.0 --> 3.53.2.
  No functional or API changes. Keeps the SQLite dependency on a
  maintained release line so future security fixes can be picked up
  without source changes.
• Update repo lists

Full Changelog: 0.11.4...0.11.5

0.11.4_beta.4

Version Beta 0.11.4

Update: cmd:slacker search
- the (also: ...) list now names each repo's own candidate in full,
e.g. (also: testing kernel-generic-7.1.7), so a repo carrying a
different version is visible without running slacker info.
Update: cmd:slacker status
- Tag prio: every installed package's source must be ranked or frozen!
anyway slacker will protect unranked tags and their installed packages
BUT slacker status will report that this is wrong and user must fix it.

Full Changelog: 0.11.3...0.11.4

0.11.3_beta.4

Version Beta 0.11.3

Fix bug: slacker search command

• search: label an installed build by its own source, never by the winner
  search_display fell back to the priority winner when no candidate
  matched the installed build tag, so a package installed from a source
  that is not a configured repo (_SBo, _local) was printed as if it came
  from whichever repo happened to outrank it — and with that repo's
  version, which diverges as soon as the versions differ. It now returns
  None for that case and cmd_search labels the line from the installed
  build tag, with the installed name and version. kept_detail shares the
  new installed_source_label helper so both name a source identically.
  Update: wiki (for docker & podman)
  Add: contrib/check-yes-noninteractive.sh
  Update: Templates folder for docker images.

Full Changelog: 0.11.2...0.11.3

0.11.2_beta.4

Version Beta 0.11.2

Update: clippy: apply 26 machine-applicable fixes, all tests pass
Add: container folder for testing sbopkg-ci (docker image version)
Add: Vendor folder, start palying with static offline builds...

Full Changelog: 0.11.1...0.11.2

0.11.1_beta.4

Version Beta 0.11.1

Fix: Bug: slacker update --yes or slacker --yes update now respect the flag --yes no more questions.
Add: Templates in /etc/slacker/templates/ these needed when slacker runs in container systems.
Add: minimal/container sackeware64-currnet images (slacker included in image) can be found:
- https://hub.docker.com/r/rizitis/slackware-slacker
- https://github.com/rizitis/slackware64-current-ci

Full Changelog: 0.11.0...0.11.1