Package: dh-make Version: 2.202001 Severity: normal When dh_make creates a debian subdir, it initialises the release archive in debian/changelog straightaway as unstable.
In typical workflow the initial debianisation would be committed, then typically a few more commits would be made until the package is finally ready for upload. A git tag would be set against this last commit, that one that corresponds to the actual upload. It's common to mark the release archive in debian/changelog as UNRELEASED while work is in progress. On the final commit, the one that would be tagged and uploaded, it would be updated to unstable (or experimental, etc). This is the workflow that debchange (dch) supports, with 'dch -r' automatically updating UNRELEASED to unstable. It would be helpful if dh_make initialised the release archive in debian/changelog to UNRELEASED rather than unstable. This would have having to change it over manually when making the initial debianisation. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dh-make depends on: ii debhelper 13.1 ii dpkg-dev 1.19.7 ii make 4.3-3 ii python3 3.8.2-3 dh-make recommends no packages. Versions of packages dh-make suggests: ii build-essential 12.8 -- no debconf information
