debcraft (0.6.0) [PTS] [DDPO]

COMMITS: VCS has seen 6 commits since the debian/0.6.0 tag

Git: https://salsa.debian.org/debian/debcraft.git
JSON
Enter a full Vcs-* header, supported schemes are: Vcs-Bzr, Vcs-Cvs, Vcs-Darcs, Vcs-Git, Vcs-Hg, Vcs-Mtn, Vcs-Svn.
For Vcs-Git append -b branch to select the branch name; append [subdir] if the debian/ directory is not in the repository root.
The next upload will reset the information from the source package headers.
Branch: main
Path: debian/changelog
Repo size: 667648
Browser: https://salsa.debian.org/debian/debcraft
Last scan: 2025-10-19 23:04:03+00
Next scan: 2025-10-26 12:53:00+00
Open issues: 11
CI pipeline status: success

Debian changelog in Git:

debcraft (0.6.0) unstable; urgency=medium

  [ Otto Kekäläinen ]
  * Rename `debcraft validate` to `debcraft improve` and extend features
    (Closes: #1111477)
  * Support enabling local repo with DEBCRAFT_EXTRA_REPOSITORY
  * If package has no autopkgtests, use autodep8 to run some
  * Fall back to commit id when building a detached HEAD
  * Make upstream tarball (if exists) available for builds
  * Improve notification about cleaning and resetting git repository
  * Add Debian to Ubuntu release mapping: Trixie is like Plucky
  * Strip debug symbols from GCC to keep container image size reasonable
  * Update copyright years and format debian/copyright properly
  * Separate test depends from build depends (Closes: #1116727)
  * Pin Debian experimental to enable packages getting installed from there
  * Add support for sccache and Rust builds caching
  * Replace `dpkg-parsechangelog` with plain shell commands
  * Store all build artefacts in ~/.cache/debcraft
  * When checking for release tags, only consider name space debian|ubuntu/*
  * Strip `-proposed-updates` from container name, similar to `-security`
  * On every build run './debian/rules clean' to ensure sources are clean
  * Run `apt-get update` in background so dropping to `debcraft shell` is faster

  [ TheJayMann ]
  * Ignore quilt exit code 2

  [ Dominik Stadler ]
  * Add section about using debcraft in GitHub Actions

  [ Nicola Chiapolini ]
  * Explicitly use `Containerfile` to fix container builds with Docker

  [ Aquila Macedo ]
  * Implement proper CI with Docker-in-Docker setup for Debcraft development,
    but temporarily skip failing tests in GitLab CI until everything has been
    made fully compatible with DinD CI runs

 -- Otto Kekäläinen <otto@debian.org>  Fri, 10 Oct 2025 22:23:45 -0700

This branch is 6 commits ahead of tag debian/0.6.0

Git log:

commit 3a5c6518d5f780466991af5920442a07d1cff8c8
Author: Otto Kekäläinen <otto@debian.org>
Date:   Thu Oct 16 23:40:50 2025 -0700

    Use existing orig tarball if present in all commands
    
    Previously only `debcraft build` reused an existing orig tarball. Extend
    this functionality to all commands.

commit 5dbaf4808efe506e29546515a7f2780472fb19da
Author: Otto Kekäläinen <otto@debian.org>
Date:   Thu Oct 16 23:40:27 2025 -0700

    Change dput target in `debcraft release` depending on vendor
    
    The dput target `ftp-master` is only for Debian packages. If the
    `debian/changelog` indicates a Ubuntu release, the dput target
    should be `ubuntu`
    
    From a sample `/etc/dput.cf`:
    
        [ftp-master]
        fqdn                        = ftp.upload.debian.org
        incoming            = /pub/UploadQueue/
        login                       = anonymous
        allow_dcut          = 1
        method                      = ftp
    
        [ubuntu]
        fqdn                        = upload.ubuntu.com
        method                      = ftp
        incoming            = /ubuntu
        login                       = anonymous

commit 95da260a37dfc48e8b53d86ec7db31f6cbf00466
Author: Otto Kekäläinen <otto@debian.org>
Date:   Mon Oct 13 21:52:55 2025 +0000

    Add Bash completion for update and logs commands
    
    Improve the command-line experience by providing shell completion
    for the `update` and `logs` commands.
    
    - For `update`, suggest relevant options such as `--build-dirs-path`,
      `--container-command`, `--host-architecture`, `--pull`, `--copy`,
      and `--clean`, along with available targets and HTTPS URLs.
    - For `logs`, suggest `--build-dirs-path`, `--copy`, `--clean`,
      and available targets.
    
    This change also corrects a typo in the completion definition for
    the `--host-architecture` option, ensuring it is correctly
    recognized.
    
    Co-authored-by: aider (gemini/gemini-2.5-pro) <aider@aider.chat>

commit 6f9133a23c4e4e2d4ddf1ff0a096d161db106c7f
Author: Otto Kekäläinen <otto@debian.org>
Date:   Fri Oct 10 22:56:20 2025 +0000

    Implement `debcraft logs` to list package builds (and releases)
    
    Introduce a new `debcraft logs` command that allows users to inspect the
    history of builds and releases for a given package. This functionality
    helps users quickly identify and reference previously generated
    artifacts, aiding in debugging, auditing, or tracking package
    development over time.
    
    Example output:
    
        ± debcraft logs
        Running in path /home/otto/mariadb/mariadb-team/mariadb-server that has Debian package sources for 'mariadb'
        Available logs for completed builds in '~/.cache/debcraft':
        TIMESTAMP            COMMIT    BRANCH                     PATH
        2025-09-25 10:56:35  d2a9813a  feature.salsa.ci.unification  ~/.cache/debcraft/debcraft-build-mariadb-1758821167.d2a9813a3d3+feature.salsa.ci.unification
        2025-09-26 09:57:33  f7d286cd  feature.salsa.ci.unification  ~/.cache/debcraft/debcraft-build-mariadb-1758903214.f7d286cd55c+feature.salsa.ci.unification
        2025-10-09 14:24:58  1a0aef21  debian.latest              ~/.cache/debcraft/debcraft-build-mariadb-1760040484.1a0aef21c4a+debian.latest
        2025-10-10 12:22:02  46c1ce02  ubuntu.25.04.plucky        ~/.cache/debcraft/debcraft-build-mariadb-1760121076.46c1ce02be6+ubuntu.25.04.plucky
        2025-10-10 13:59:41  46c1ce02  next.ubuntu.25.04.plucky   ~/.cache/debcraft/debcraft-release-mariadb-1760129596.46c1ce02be6+next.ubuntu.25.04.plucky
        2025-10-10 21:27:39  82a7ec9e  ubuntu.22.04.jammy         ~/.cache/debcraft/debcraft-build-mariadb-10.6-1760153830.82a7ec9e62a+ubuntu.22.04.jammy
        2025-10-10 22:32:41  151ff2d4  ubuntu.24.04.noble         ~/.cache/debcraft/debcraft-build-mariadb-1760156950.151ff2d4fe6+ubuntu.24.04.noble
        2025-10-11 01:32:52  151ff2d4  ubuntu.24.04.noble         ~/.cache/debcraft/debcraft-build-mariadb-1760168279.151ff2d4fe6+ubuntu.24.04.noble
        2025-10-11 14:28:04  b9793e10  next.ubuntu.25.04.plucky   ~/.cache/debcraft/debcraft-build-mariadb-1760214751.b9793e10cd0+next.ubuntu.25.04.plucky
        2025-10-11 15:36:30  b75a90dd  next.ubuntu.24.04.noble    ~/.cache/debcraft/debcraft-build-mariadb-1760218856.b75a90dd202+next.ubuntu.24.04.noble
        2025-10-11 19:32:49  916f773a  next.ubuntu.22.04.jammy    ~/.cache/debcraft/debcraft-build-mariadb-10.6-1760222367.916f773ae0e+next.ubuntu.22.04.jammy

commit 686f5d2bd0a3b8ae0b529d033e86a547ef62474a
Author: Dominik Stadler <dominik.stadler@gmx.at>
Date:   Sun Oct 12 12:08:13 2025 +0200

    Add initial support for Debian Forky
    
    Adding it to the switch for Debian and Ubuntu
    repositories seems to make it work.

commit 2bb23eaa0ba3f102b50a7b27464de4506bcfe967
Author: Otto Kekäläinen <otto@debian.org>
Date:   Sat Oct 11 15:00:03 2025 -0700

    Enable Sponsor button on project GitHub page