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 5cfbc5727dba2f4662d24cf4deb7cab7cdd57c14
Author: David Kalnischkies <david@kalnischkies.de>
Date: Wed Jul 10 16:15:30 2019 +0200
Fix typos reported by codespell in code comments
Also in old changelogs, but nothing really user visible
like error messages or alike so barely noteworthy.
Reported-By: codespell
Gbp-Dch: Ignore
commit 2b734a7ec429825c7007c1093883229e069d36c7
Author: David Kalnischkies <david@kalnischkies.de>
Date: Mon Jul 8 15:48:59 2019 +0200
Apply various suggestions by cppcheck
Reported-By: cppcheck
commit cbe90ee516d7f747f981e423f164f99eb767240b
Author: David Kalnischkies <david@kalnischkies.de>
Date: Mon Jun 10 14:30:32 2019 +0200
Show details about the package with bad Provides
The error messages say only which package it was trying to provide, but
not which package & version tried it which can be misleading as to which
package (version) is the offender.
References: #930256
commit 79b1a82983e737e74359bc306d9edb357c5bdd46
Author: David Kalnischkies <david@kalnischkies.de>
Date: Sat Apr 27 16:13:02 2019 +0200
Distribute host-less work based on backlog of the queues
Work like applying patches via rred can be performed by many concurrent
rred processes, but we can't just spawn new ones forever: We limit us to
the number of CPUs which can drive them and reuse existing ones if they
have nothing to do at the moment.
The problem arises if we have reached the limit of queues and all of
them are busy which is more likely to happen on "slow" machines with few
CPUs. In this case we opted for random distribution, but that can result
in many big files (e.g. Contents) being added to one queue while the
others get none or only small files.
Ideally we would ask the methods how much they still have to do, but
they only know that for the current item, not for all items in the
queue, so we use the filesize of the expected result.
commit 8ff87e9cd37a4436eb7e56f814a099cb30845ae1
Merge: 67b51af0f 1c85fff1f
Author: Julian Andres Klode <jak@debian.org>
Date: Mon Jun 24 06:52:30 2019 +0000
Merge branch 'patch-1' into 'master'
Change a pronoun in the readme from `he` to `they`
See merge request apt-team/apt!69
commit 1c85fff1f3a38d355bb06ed3cfe1802854b8773a
Author: Lynn Cyrin <lynncyrin@gmail.com>
Date: Sun Jun 23 22:21:07 2019 +0000
Change a pronoun in the readme from `he` to `they`
Using gender neutral language in your documentation is a inclusion win!
Here's some documents describing more context here:
- https://en.wikipedia.org/wiki/Singular_they#Trend_toward_gender-neutral_language
- https://open.buffer.com/inclusive-language-tech
- https://www.grammarly.com/blog/use-the-singular-they/
https://salsa.debian.org/api/v4/projects/apt-team%2Fapt API request failed: 500 Internal Server Error at /srv/qa.debian.org/data/vcswatch/vcswatch line 387.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/a/apt.png){kind=link}