Hi, What is the status with golang-go.crypto?
I see Andrew uploaded a new version to experimental. What is the plan for putting it in unstable? There are at least two reverse dependencies failing. Are you planning to fix them or shall we just abandon the experimental upload and continue with current version? Gitaly is already broken in debci and has unsatisfiable build dependency, it might be reasonable to ignore it for now. The version of golang-github-azure-azure-sdk-for-go is very old as the debian/watch is misconfigured and unaware of new versions. Why did you do the commits on a new branch debian/experimental? Are you thinking those commits were temporary and might be thrown away instead of being done on the default branch? When are you going to merge in on debian/latest? Are people who want to make improvements to the package expected to target MRs on debian/latest or on debian/experimental? If you upload from the non-default branch, should you change it to the repository default branch? Or in the upload add a `-b debian/experimental` suffix to the debian/control:Vcs-Git line so that vcswatch can keep track of that real state of the package? Status pages: https://tracker.debian.org/pkg/golang-go.crypto https://tracker.debian.org/pkg/gitaly https://tracker.debian.org/pkg/golang-github-azure-azure-sdk-for-go Also I am not able to build neither the current debian/latest nor debian/experimental as it fails on: gbp:info: Creating /debcraft/golang-go.crypto_0.45.0.orig.tar.xz gbp:error: Cannot find pristine tar commit for archive 'golang-go.crypto_0.45.0.orig.tar.xz' Maybe a `gbp push` was forgotten? Or if you intentionally want to stop using pristine-tar,t hen remove it from debian/gbp.conf?
