vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 87348b912c4bb5e22919a2ad838ef73ec564ae04
Author: Jeremy Sowden <azazel@debian.org>
Date: Sun Dec 15 16:03:27 2024 +0000
d/gbp.conf: disable `pristine-tar` and `upstream-signatures` by default
`Pristine-tar` is used by gbp-pull, so disable it by default and enable it
explicitly in import-orig.
Signed-off-by: Jeremy Sowden <azazel@debian.org>
commit 391fd3f39c5a44b6d5cea6b4a60a37d6de385222
Author: Jeremy Sowden <azazel@debian.org>
Date: Sun Dec 15 16:03:27 2024 +0000
d/gbp.conf: buildpackage: disable `pristine-tar` and `upstream-signatures`
Commit d9e39113b41a ("d/gbp.conf: remove postunpack hook and use upstream
tar-balls as-is") removed them, because there is no need to repack the upstream
tar-balls. However, they need to be retained to build 5.2.8. Once 5.2.9 is
imported, they can be removed again.
Signed-off-by: Jeremy Sowden <azazel@debian.org>
commit 3c434ef21b3a89bd97aa99bf2bd2945223dbfcb9
Author: Jeremy Sowden <azazel@debian.org>
Date: Sun Dec 15 15:39:17 2024 +0000
d/README.source: minor textual & formatting improvements
Signed-off-by: Jeremy Sowden <azazel@debian.org>
commit d9e39113b41ac1a2e80d488297233048773f27b9
Author: Jeremy Sowden <azazel@debian.org>
Date: Thu Nov 21 11:15:03 2024 +0000
d/gbp.conf: remove postunpack hook and use upstream tar-balls as-is
gbp-import-orig does the right thing by default, so there is no need to repack
the tar-balls and the upstream ones can be used directly.
Signed-off-by: Jeremy Sowden <azazel@debian.org>
commit c3c323384ae6063057995939c4143608d806cbdd
Author: Jeremy Sowden <azazel@debian.org>
Date: Tue Jul 23 23:01:23 2024 +0100
d/changelog: fix typo
Signed-off-by: Jeremy Sowden <azazel@debian.org>