public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bradford Boyle <[email protected]>
To: [email protected]
Subject: vip-manager and vip-manager2 FTBFS
Date: Sun, 11 Aug 2024 23:34:14 -0700
Message-ID: <CAOMoQbRG3=vJNUm8W2fONx17FCiDUjQHOqOBaaOG2tic0xuk9Q@mail.gmail.com> (raw)

Hi All,

The package golang-etcd-server-dev was updated from 3.4.30 to to 3.5.15
at the end of July. This version of etcd introduced a couple of changes
to import paths that caused vip-manager and vip-manager2 to FTBFS in sid
[1, 2]. I've prepared patches for both packages to update the import
paths [3, 4]. With these patches, both packages build on sid and
autopkgtests pass.

However, bookworm has etcd 3.4.23 and noble has 3.4.30 so the patches
break the build on older distributions. I don't believe this is an issue
for vip-manager since this pakcage provides vip-manager 1.x which hasn't
had a new release since 2022. vip-manager2 has had a release as recently
as three weeks ago. If we want to build updated packages of vip-manager2
for both bookworm and trixie on pgdg, we would need to apply different
patches for etcd 3.4 and 3.5.

I suppose we could also just disable vip-manager2 for any distribution
besides sid and trixie but I don't have a sense of how popular this
package is and if that is a viable solution for this particular package.

Before updating these packages, I wanted to see if there was any input
on how to handle these packages on older distributions.

Thanks,
-- Bradford

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078322
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078323
[3]: https://salsa.debian.org/postgresql/vip-manager/-/commit/ac57eaba565013c462da95276db4824af3069beb
[4]: https://salsa.debian.org/postgresql/vip-manager2/-/commit/244ba273f40125861603403064171e2736a2978d

view thread (4+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected]
  Subject: Re: vip-manager and vip-manager2 FTBFS
  In-Reply-To: <CAOMoQbRG3=vJNUm8W2fONx17FCiDUjQHOqOBaaOG2tic0xuk9Q@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox