Hi! 309 nine packages sounds like quite a lot, why does ratt think that many are needed?
It only has a few reverse deps: aerc: golang-github-protonmail-go-crypto-dev apptainer: golang-github-protonmail-go-crypto-dev aptly: golang-github-protonmail-go-crypto-dev gittuf: golang-github-protonmail-go-crypto-dev go-sendxmpp: golang-github-protonmail-go-crypto-dev golang-github-apptainer-sif: golang-github-protonmail-go-crypto-dev golang-github-crc-org-crc: golang-github-protonmail-go-crypto-dev golang-github-emersion-go-pgpmail: golang-github-protonmail-go-crypto-dev golang-github-go-git-go-git: golang-github-protonmail-go-crypto-dev golang-github-henrybear327-go-proton-api: golang-github-protonmail-go-crypto-dev golang-github-protonmail-go-srp: golang-github-protonmail-go-crypto-dev golang-github-protonmail-gopenpgp: golang-github-protonmail-go-crypto-dev (1.3.0~ >=) golang-github-protonmail-gopenpgp-v3: golang-github-protonmail-go-crypto-dev (1.3.0~ >=) golang-github-sylabs-sif: golang-github-protonmail-go-crypto-dev (1.1.2~ >=) gosop: golang-github-protonmail-go-crypto-dev (1.1.0~ >=) rclone: golang-github-protonmail-go-crypto-dev singularity-container: golang-github-protonmail-go-crypto-dev To ensure the package is well tested _before_ upload, I think we should use CI to build it and run Lintian, autopkgtest etc. I wish this was general practice in the Go team already, I have been suggesting it for 1.5 years already. I submitted https://salsa.debian.org/go-team/packages/golang-github-protonmail-go-crypto/-/merge_requests/1 to start using Salsa CI in this package. Once you have Salsa CI, you can easily also run the reverse deps build, which I did now in https://salsa.debian.org/go-team/packages/golang-github-protonmail-go-crypto/-/pipelines/1034104
