redumper-gui (1.0.5-1) UNRELEASED; urgency=medium

  * Automated sync to upstream redumper-gui release v1.0.5.

 -- gmipf <gmipf64@gmail.com>  Sat, 01 Aug 2026 03:55:39 +0000

redumper-gui (1.0.4-1) UNRELEASED; urgency=medium

  * Automated sync to upstream redumper-gui release v1.0.4.

 -- gmipf <gmipf64@gmail.com>  Tue, 28 Jul 2026 00:13:33 +0000

redumper-gui (1.0.3-1) UNRELEASED; urgency=medium

  * Automated sync to upstream redumper-gui release v1.0.3.

 -- gmipf <gmipf64@gmail.com>  Fri, 24 Jul 2026 09:12:52 +0000

redumper-gui (1.0.2-1) UNRELEASED; urgency=medium

  * Update to upstream 1.0.2; Source0 moves to a release asset on the packaging repo.
  * Drop 0001-default-dump-folder-must-be-writable.patch: upstream implemented the
    same fix itself in 1.0.2, so it no longer applies and is no longer needed.

 -- gmipf <gmipf64@gmail.com>  Sun, 19 Jul 2026 15:45:27 +0000

redumper-gui (1.0.1-4) UNRELEASED; urgency=medium

  * Add aarch64 (arm64) support: Architecture is now amd64 arm64. Built from
    source, so nothing is bundled per-arch -- it simply compiles natively on the
    arm64 builders. Ships UNTESTED on arm64 -- no hardware drive-access proof.

 -- gmipf <gmipf64@gmail.com>  Sat, 18 Jul 2026 02:20:00 +0000

redumper-gui (1.0.1-3) UNRELEASED; urgency=medium

  * Put the fallback dump folder in the user's HOME (~/Dumps), not in
    ~/Downloads. Home is the Linux convention for a tool like this, and it is
    what our own mpf package already does (DefaultOutputPath = $HOME/ISO) -- two
    disc dumpers from one repository should not disagree about where a dump
    goes. Downloads is the folder a browser empties; nobody looks for disc
    images there. Upstream's macOS branch keeps the download folder it has
    always used, untouched.

 -- gmipf <gmipf64@gmail.com>  Mon, 13 Jul 2026 21:30:00 +0200

redumper-gui (1.0.1-2) UNRELEASED; urgency=medium

  * Patch the default dump folder so a packaged install can actually dump
    (debian/patches/0001-default-dump-folder-must-be-writable.patch). It pointed
    at a Dumps subfolder beside the executable -- /usr/lib/redumper-gui/Dumps
    here, owned by root: measured on a clean install, the user cannot create it
    (mkdir: Permission denied). Worse, dump.rs discards the error from
    create_dir_all(), so pressing DUMP did not stop with "permission denied";
    the dump ran on and failed later for a reason that never named the cause.
    The patch keeps that folder wherever it IS writable (upstream's portable
    build) and otherwise falls back to the user's download folder -- which is
    what upstream's own macOS branch has always done, the .app bundle being the
    very same predicament. Offered upstream.

 -- gmipf <gmipf64@gmail.com>  Mon, 13 Jul 2026 20:00:00 +0200

redumper-gui (1.0.1-1) UNRELEASED; urgency=medium

  * Initial package of Redumper GUI v1.0.1 (Rust / egui), a desktop frontend
    for redumper, suggested by its author in the VGPC preservation community.
  * Built from source rather than repackaging the upstream release binary:
    that binary is compiled on Ubuntu 24.04 and requires GLIBC_2.39, which
    would rule out jammy (2.35) entirely. A source build links against whatever
    glibc the series ships, so every series is covered.
  * Built with the versioned rustc-1.91 / cargo-1.91 toolchain from
    <series>-updates on jammy and noble, whose default rustc is 1.75 and too old
    for edition 2024. resolute's own rustc (1.93) is new enough and the
    alternative in Build-Depends falls back to it.
  * Crates are vendored into the orig tarball and the build runs --offline: the
    Launchpad build farm has no network.
  * Ships no copy of redumper. Upstream bundles a pinned b729 next to the GUI
    executable and runs its sibling by that name; a package cannot add a second
    /usr/bin/redumper, so the pinned build is packaged separately as redumper729
    and symlinked into the GUI's private directory.

 -- gmipf <gmipf64@gmail.com>  Sun, 12 Jul 2026 16:00:00 +0200
