runit (2.1.2-33) [PTS] [DDPO]

NEW: VCS has unreleased changes: 2.1.2-34 > 2.1.2-33

Git: https://salsa.debian.org/debian/runit.git
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: master
Path: debian/changelog
Browser: https://salsa.debian.org/debian/runit
Last scan: 2019-08-17 13:08:54+00
Next scan: 2019-08-25 07:18:00+00
CI pipeline status: success

Debian changelog in Git:

runit (2.1.2-34) UNRELEASED; urgency=medium

  * Work in progress.

 -- Dmitry Bogatov <KAction@debian.org>  Fri, 16 Aug 2019 05:35:37 +0000

This branch is 1 commit ahead of tag debian/2.1.2-33

Git log:

commit 7327498c26e9c2d2acb8f46ce575b1d8b9c6fbc2
Author: Dmitry Bogatov <KAction@debian.org>
Date:   Fri Aug 16 05:35:37 2019 +0000

    Open new entry in changelog
    
    As explained at[1], piuparts job setup local repository with packages
    just built. If their version is equal to version in archives, job will
    fail with "Sources disagree on hashes of supposely identical version"
    error. So, to keep CI clean, it is necessary to create new changelog
    entry after release.
    
     [1] https://salsa.debian.org/salsa-ci-team/pipeline/issues/46#note_80587