vcswatch reports that
this package seems to have a new changelog entry (version
1.2.10-2, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit a4e8811c85ee5fe1218e1a7f2ddaa7175fff23c3
Author: Peter Pentchev <roam@debian.org>
Date: Thu Oct 10 17:20:19 2019 +0300
Update the changelog file.
commit 52bbafb84f46d062bcb005b16cbda3529ffc93aa
Author: Peter Pentchev <roam@debian.org>
Date: Mon Oct 7 18:15:23 2019 +0300
Declare compliance with Policy 4.4.1 with no changes.
commit 94ca263efc6984ecaa3f18125910c78a47988262
Author: Peter Pentchev <roam@debian.org>
Date: Mon Oct 7 18:15:10 2019 +0300
Mark the adequate test as superficial.
commit 4b0122e5c2b2f82d8e9084d1a4e992e644a933cc
Author: Peter Pentchev <roam@debian.org>
Date: Tue Mar 5 10:56:01 2019 +0200
Update the changelog file.
commit 11ca2d6937c63f4f57eae8502b6bc0fe45be2b1b
Author: Peter Pentchev <roam@debian.org>
Date: Tue Mar 5 10:55:33 2019 +0200
Add a simple git-buildpackage config file.
commit 15439087d78b9d2c1eec9f990c2ea7de88c138db
Author: Peter Pentchev <roam@debian.org>
Date: Tue Mar 5 10:53:25 2019 +0200
Use the test-name autopkgtest feature.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/m/mdk-doc.png){kind=link}