Package: golang-github-hashicorp-consul-dev Severity: normal Control: affects -1 golang-github-shirou-gopsutil
Dear Maintainer, The upload of golang-github-shirou-gopsutil/3.21.10-1 introduced the following breaking changes: https://github.com/shirou/gopsutil/blob/master/README.md#v3-migration https://github.com/shirou/gopsutil/blob/master/_tools/v3migration/v3Changes.md Upstream writes "from v3.20.10, gopsutil becomes v3 which breaks backwards compatibility". Our gopsutil package dependencies do yet enforce the compatibility break. Affected packages are as follows: consul golang-github-satta-ifplugo ncbi-entrez-direct nomad nomad-driver-lxc nomad-driver-podman packer slinkwatch syncthing Please verify that your package is ready for gopsutil v3. If the version in sid/unstable is v3-ready, then please set "fixed -1 sourcepkgname/version" for this bug. If not, the latest upstream release may already support it, in which case, please import it! If the latest release is not ready, please contact that upstream without delay, because some may be reticent to keep pace with changing libraries. It may be worth mentioning to them that the v2 series is EOL: https://github.com/shirou/gopsutil/blob/master/README.md#v3-migration * Contains the upstream statement v2 is gone. https://pkg.go.dev/github.com/shirou/gopsutil/v3#readme-v3-migration * Also available here. https://github.com/shirou/gopsutil/blob/v2 * (404 error) Three weeks from now (18 July) I will increase severity to important as a gentle reminder. Around 17 September I will upload to experimental. The 15 October I will increase severity to RC. To justify downgrading severity at that time, please add the forwarded tag the bug, with a URL that shows that upstream is working towards solving this issue before 2023. Either the first week of December, or the first week of January 2023 (at the latest), the compatibility break will be enforced with an upload of gopsutil to unstable. I hope that everyone affected feels that these deadline are fair, and prefers to have a roadmap rather than vague "at some point" guesturing followed by stresssful surprises at the worst times. Best wishes, Nicholas -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages golang-github-hashicorp-consul-dev depends on: pn golang-github-armon-go-metrics-dev <none> pn golang-github-armon-go-radix-dev <none> pn golang-github-hashicorp-go-bexpr-dev <none> pn golang-github-hashicorp-go-cleanhttp-dev <none> pn golang-github-hashicorp-go-hclog-dev <none> pn golang-github-hashicorp-go-memdb-dev <none> pn golang-github-hashicorp-go-msgpack-dev <none> pn golang-github-hashicorp-go-rootcerts-dev <none> pn golang-github-hashicorp-go-uuid-dev <none> ii golang-github-hashicorp-golang-lru-dev 0.5.4-2 pn golang-github-hashicorp-hcl-dev <none> pn golang-github-hashicorp-hil-dev <none> pn golang-github-hashicorp-memberlist-dev <none> pn golang-github-hashicorp-raft-boltdb-dev <none> pn golang-github-hashicorp-raft-dev <none> pn golang-github-hashicorp-serf-dev <none> pn golang-github-hashicorp-yamux-dev <none> pn golang-github-inconshreveable-muxado-dev <none> pn golang-github-miekg-dns-dev <none> pn golang-github-mitchellh-cli-dev <none> pn golang-github-mitchellh-copystructure-dev <none> pn golang-github-pascaldekloe-goe-dev <none> ii golang-golang-x-sys-dev 0.0~git20210124.22da62e-1 golang-github-hashicorp-consul-dev recommends no packages. golang-github-hashicorp-consul-dev suggests no packages.
