Dear Go maintainers:
I've detected a bunch of Go packages which do not build from source
because they use tzdata without a build-dependency.
This will not happen if tzdata is installed by default, but such package
is not really build-essential, so this is technically a FTBFS bug in a
release architecture.
For the packages in stable which do not fail in testing/unstable, I
could maybe report them this way:
Version: version-in-stable
Fixed: version-in-testing
That way the bugs will not interfere with development in testing.
For the packages which fail both in stable and unstable, I'm in doubt.
Please advise about the best way to have all the affected packages fixed
in stable (packages in stable must build in stable). (If I have to
become part of the team and do uploads myself, so be it).
[ As a sample, I'm attaching a list of packages which fail in bookworm,
but I've not checked that all of them are maintained by this group ].
Thanks.
arduino-builder
golang-github-araddon-dateparse
golang-github-go-co-op-gocron
golang-github-go-git-go-git
golang-github-go-playground-locales
golang-github-jedib0t-go-pretty
golang-github-libgit2-git2go
golang-github-mattn-go-sqlite3
golang-github-mitch000001-go-hbci
golang-github-mohae-deepcopy
golang-github-rickb777-date
golang-github-spf13-cast
golang-github-tealeg-xlsx
golang-github-teambition-rrule-go
golang-go.uber-atomic
hugo
miller
_______________________________________________
Pkg-go-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers
