The revbuild below seemed fairly complete, the failures are: apptainer: FTBFS bug report already => not a blocker caddy: not in testing, FTBFS bug report => not a blocker singularity-container: not in testing => not a blocker I also went through the upstream changes between 0.22 and 0.29 and they were rather small and seemed harmless. Thus I have uploaded 0.29.0 to unstable via tag2upload. /Simon Simon Josefsson <simon@josefsson.org> writes: > All, > > inspired by the golang-go.crypto update, I took a look at > https://tracker.debian.org/pkg/golang-golang-x-text too and have made an > experimental upload, started a baseline revbuild of 0.22: > > https://salsa.debian.org/jas/golang-golang-x-text/-/pipelines/947167 > > and started a 0.29 revbuild: > > https://salsa.debian.org/jas/golang-golang-x-text/-/pipelines/947171 > > Is anyone aware of any reason not to upload this to unstable too? Of > course, analyzing revbuild outcome is important, but other than that... > > Btw, I realized golang-go.crypto could be renamed to > golang-golang-x-crypto to comply with our naming guideline... I'm not > sure it is worth going through that hassle for a source package rename. > > /Simon >
Attachment:
signature.asc
Description: PGP signature