Bug#1063308: transition: libvterm
On Mon, Mar 04, 2024 at 06:40:46AM -0500, James McCoy wrote:
> On Mon, Feb 05, 2024 at 10:54:12PM -0500, James McCoy wrote:
> > libvterm doesn't have a stable API/ABI yet, so although the SONAME
> > didn't change, this is a breaking update.
> >
> > There are 3 packages which use libvterm:
> > * pangoterm: I've filed #1063196 to RM the package, so it shouldn't
> > block
> > * emacs-libvterm: It supports building against either 0.1 or 0.3, so it
> > just needs a binNMU
> > * neovim: 0.7.2 (in unstable) only supports 0.1, but 0.9.5 (in
> > experimental) supports 0.3.
> >
> > Ben file:
> >
> > title = "libvterm 0.1 -> 0.3";
> > is_affected = .build-depends ~ "libvterm-dev";
> > is_good = .depends ~ /libvterm0 \(>= 0\.[23]/;
> > is_bad = .depends ~ /libvterm0 \(>= 0\.1/;
>
> This was ACKed on IRC, so I've uploaded libvterm and neovim.
Now that cmake is available on arm* again, emacs-libvterm just needs a
binNMU to finish this transition.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Reply to: