Federico Grau <donfede@casagrau.org> writes: > Some questions/issues include (advise if these are better addressed OOB): > > a) golang-github-hashicorp-go-version in Debian is 1.6.0 . > pat 0.19.1 released 2025-09-13 lists a dependency on 1.7.0 (but compiles ok > with 1.6.0). > Since then, a new hashicorp-go-version 1.8.0 was released 2025-11-28. > > I'm not clear how to best proceed. Should I explore updating > hashicorp-go-version to 1.7.0, or the latest 1.8.0, or is there a better > path? If things build, then I would start by getting 'pat' into unstable first, and test if it works. Having version diffs is unavoidable in the Go/Debian ecosystem, what matters is if things works. If you have time, please prepare hashicorp-go-version 1.8.0 and do reverse builds of it and upload to unstable if it it works with all reverse build dependencies. But doing this is not a show-stopper for 'pat'. > Per vendor-n8jja-pat-vara.patch Why not package that properly? Vendoring is a maintainance pain. > Debian package golang-github-imdario-mergo has v1.0.1 which was released > 2024-08-17 and packaged 2024-11-09. > > Upstream released v1.0.2 on 2025-05-07. Same here, if you have time, do a package update, check reverse builds, and upload if okay. /Simon
Attachment:
signature.asc
Description: PGP signature