Package: golang-github-mattn-go-sqlite3-dev Version: 1.14.24~ds1-1 Hi
I noticed that some packages like 'sigstore-go' doesn't build due to B-D problems on some archs: https://buildd.debian.org/status/package.php?p=sigstore-go One reason for that is golang-github-mattn-go-sqlite3-dev. So I looked at that package and noticed that it only contain identical source code files built for all architectures. All archs I checked (amd64, arm64, armel, armhf) are identical, except for a tiny diff: jas@kaka:~/p$ diffoscope golang-github-mattn-go-sqlite3-dev_1.14.24~ds1-1_amd64.deb golang-github-mattn-go-sqlite3-dev_1.14.24~ds1-1_armel.deb --- golang-github-mattn-go-sqlite3-dev_1.14.24~ds1-1_amd64.deb +++ golang-github-mattn-go-sqlite3-dev_1.14.24~ds1-1_armel.deb ├── control.tar.xz │ ├── control.tar │ │ ├── ./control │ │ │ @@ -1,11 +1,11 @@ │ │ │ Package: golang-github-mattn-go-sqlite3-dev │ │ │ Source: golang-github-mattn-go-sqlite3 │ │ │ Version: 1.14.24~ds1-1 │ │ │ -Architecture: amd64 │ │ │ +Architecture: armel │ │ │ Maintainer: Debian Go Packaging Team <team+pkg...@tracker.debian.org> │ │ │ Installed-Size: 487 │ │ │ Depends: libsqlite3-dev │ │ │ Breaks: textql (<< 2.0.3-5), zabbix-web-service (<< 1:7.0.5) │ │ │ Section: golang │ │ │ Priority: optional │ │ │ Multi-Arch: same jas@kaka:~/p$ Looking at history of this package, I found this change was introduced via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984701 and if I understand the argument correctly, it is that at that time (2021) 'libsqlite3-dev' was not available on several archs. However in 2023 at least one additional arch was fixed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035646 And today it seems 'libsqlite3-dev' builds on all archs: https://buildd.debian.org/status/package.php?p=sqlite3 So can we make 'golang-github-mattn-go-sqlite3-dev' an arch:all package again? This is one of few golang-* packages which are arch:any, and it seems to be causing unnecessary build churn and build dependency issues. My biggest concern in doing this change: bookworm shipped with a arch:all package. How are upgrades handled from bookworm if trixie will ship a arch:any package? Does it just work, or does it fail horribly somehow? Cc'ing Helmut since he wrote the bug report that led to this change, and I suspect you understand these questions better than most. /Simon
signature.asc
Description: PGP signature
