Hello,

Updating etcd to 3.6.x, with Praveen. Four packages, all sbuild green in
an unstable chroot, no lintian W or E:

  golang-go.etcd-raft                3.6.0+ds-1   unstable      NEW
  golang-github-google-btree         1.1.3-1      unstable
  golang-github-jonboulle-clockwork  1:0.5.0-2    experimental
  etcd                               3.6.14-1     experimental

Asks:
- I've requested go-team access on Salsa (azeezalishah); please approve.
- go-team/packages/golang-go.etcd-raft doesn't exist and I can't create
  it. Please create it, or the access above covers it.
- Not a DD, so all four need a sponsor.

Notes:
- raft is new (ITP #1141877). Split out of the etcd tree upstream before
  3.6, so etcd now build-depends on it. Pinned to 3.6.0; 3.7 needs a
  newer Go than sid has. Repacked +ds to drop tla/ (partly CC-BY-4.0,
  unused by the Go code). Goes first, it'll sit in NEW.
- btree 1.0.1 -> 1.1.3: etcd 3.6 needs the generic BTreeG API from 1.1.0.
- clockwork: sid has 0.5.0+really+0.1.0-1, Andreas' Oct 2025 revert. Both
  reasons for it are gone - the x-tools stringer bug is fixed (sid has
  1:0.46.0+ds-1), and etcd 3.6 uses the struct-based FakeClock that real
  0.5.0 provides. Epoch needed because +really+0.1.0 sorts above 0.5.0.
  Targets experimental so it lands with etcd 3.6 and doesn't break the
  3.5 in sid. Andreas, would like your ack on this one.
- etcd 3.6.14 rather than 3.6.12: 3.6.14 fixes a watch authz bypass
  (read on one key returned watch responses for every key onwards) plus
  three smaller ones. Rebase was free, all 24 patches applied clean.
  0 test failures, 87 test packages OK.
- 18 of the previous 26 patches survive; the 8 dropped and 6 new ones are
  itemised per patch in d/changelog.

Two things I left alone, say the word if you disagree:
- etcd keeps XS-Go-Import-Path: go.etcd.io/etcd while go.mod now says
  go.etcd.io/etcd/v3. Lintian notes it. Changing it would move the
  installed source path for every rdep, so not in this upload.
- 0005 (big-endian test fix) is still Forwarded: no. It looks
  upstreamable but it isn't mine to forward.

Branches on my fork:
  azeezalishah/etcd                               feature/3.6.14-update
  azeezalishah/golang-github-google-btree         import/1.1.3-1
  azeezalishah/golang-github-jonboulle-clockwork  import/0.5.0-2

Salsa CI passes on clockwork. etcd fails there because the build-deps
aren't in the archive yet - it can only go green last.

Upload order: raft, btree to unstable; then clockwork, etcd to
experimental together.

/azeez

Reply via email to