Hi,

please remove golang-github-go-git-go-git-fixtures-v5 from testing, it
has already been removed from sid.

Regards,
Daniel

Hi Daniel,


No need to file bugs like this, it will happen automatically when all
reverse (build) dependencies are fixed and migrate. Currently I see this
in [1]:
trying: -golang-github-go-git-go-git-fixtures-v5
skipped: -golang-github-go-git-go-git-fixtures-v5 (28, 0, 25)
     got: 44+0: a-18:a-6:a-2:i-17:l-1:p-0:r-0:s-0
     * amd64: git-pages-faux-build-depends,
golang-github-go-git-go-git-v6-dev,
golang-github-go-git-go-git-v6-faux-build-depends

Which means that src:git-pages, golang-github-go-git-go-git-v6-dev and
src:golang-github-go-git-go-git-v6 in testing need updates before
src:golang-github-go-git-go-git-fixtures-v5 can be removed.
src:git-pages seems fixed in unstable, but is blocked by
src:golang-github-go-git-go-git-v6. src:golang-github-go-git-go-git-v6
is blocked because it regresses the autopkgtest of src:git-pages (the
version in testing). As there apparently is no *versioned* relation
between the packages, our migration software can't see that
src:git-pages needs to be tested for the
src:golang-github-go-git-go-git-v6 migration with the git-pages version
from unstable. Is a versioned breaks from
bin:golang-github-go-git-go-git-v6-dev to bin:git-pages in order as it
breaks at least the test?

Paul

[1] https://release.debian.org/britney/update_output.txt