vcswatch reports that
this package seems to have a new changelog entry (version
0.8.13-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 83f6b0be1e633041fca0690c1fc9b22aa1f189fd
Merge: b96669da cb36bb3b
Author: Manuel A. Fernandez Montecelo <mafm@debian.org>
Date: Mon Jul 6 21:47:56 2020 +0000
Merge branch 'lintian-fixes' into 'debian-sid'
Set upstream metadata fields: Repository, Repository-Browse
See merge request apt-team/aptitude!9
commit cb36bb3ba05b795c5c6ad8919b23270768f06a8a
Author: Debian Janitor <janitor@jelmer.uk>
Date: Wed Jun 3 12:48:03 2020 +0000
Set upstream metadata fields: Repository, Repository-Browse.
Fixes: lintian: upstream-metadata-file-is-missing
See-also: https://lintian.debian.org/tags/upstream-metadata-file-is-missing.html
Fixes: lintian: upstream-metadata-missing-repository
See-also: https://lintian.debian.org/tags/upstream-metadata-missing-repository.html
commit b96669dac61d993d4635b3c507b16fe53aec671e
Author: Axel Beckert <abe@deuxchevaux.org>
Date: Tue May 26 19:56:33 2020 +0200
Disable autopkgtest since we don't have one yet
commit 9f55a02d35dc4e3726f621d3edd5fd3d6a03a4a3
Author: Axel Beckert <abe@deuxchevaux.org>
Date: Tue May 26 13:04:02 2020 +0200
Add a debian/gitlab-ci.yml file to the debian-sid branch
It seems as if gitlab can only copy with a single CI configuration
path per repository, not per branch.
Since the master and the debian-sid branch need different Gitlab CI
configurations and the debian-sid branch must not overwrite files from
the master branch, this is difficult to reach. The only albeit
suboptimal solution would be to add a debian/gitlab-ci.yml file to the
master branch even though it has no debian directory (yet) as the
upstream debian directory is always ignored upon orig.tar import.
So for now, we only have CI in the debian-sid branch.
commit 009c29634beaf88c9b64ff08d6d53d855c452ac9
Author: Axel Beckert <abe@deuxchevaux.org>
Date: Fri May 22 02:44:30 2020 +0200
Prepare for a po4a release where #960892 is fixed
* Drop fix-ftbfs-with-po4a-0.58.patch and hence also
debian/patches/series.
* Build-depend on po4a versions not affected by #960892, i.e. before
0.58 or after 0.59.1.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/a/aptitude.png){kind=link}