Bug#1063308: marked as done (transition: libvterm)
Your message dated Wed, 24 Apr 2024 05:30:01 -0500
with message-id <z6kb2aunpjkzpdzbqyiuqnpvonm7xdpkxbvjisofzbxu7snua7@6womypwm7536>
and subject line Re: Bug#1063308: transition: libvterm
has caused the Debian Bug report #1063308,
regarding transition: libvterm
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1063308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063308
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: libvterm
- From: James McCoy <jamessan@debian.org>
- Date: Mon, 05 Feb 2024 22:54:12 -0500
- Message-id: <170719165296.3215716.15769069216201930796.reportbug@localhost>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
X-Debbugs-Cc: libvterm@packages.debian.org
Control: affects -1 + src:libvterm
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/;
--- End Message ---
--- Begin Message ---
- To: 1063308-done@bugs.debian.org
- Subject: Re: Bug#1063308: transition: libvterm
- From: James McCoy <jamessan@debian.org>
- Date: Wed, 24 Apr 2024 05:30:01 -0500
- Message-id: <z6kb2aunpjkzpdzbqyiuqnpvonm7xdpkxbvjisofzbxu7snua7@6womypwm7536>
- In-reply-to: <by6r7fqz6qq7szeineoed4og4usd73nf3f4u2hqlujkpd6zapj@32hadt7l4u5z>
- References: <170719165296.3215716.15769069216201930796.reportbug@localhost> <170719165296.3215716.15769069216201930796.reportbug@localhost> <zxrkuiolvs3htjxczyxqgzgprs3v7iurg42u2pvvikizn2dxbm@ckmybwxatznz> <by6r7fqz6qq7szeineoed4og4usd73nf3f4u2hqlujkpd6zapj@32hadt7l4u5z>
On Fri, Mar 15, 2024 at 03:57:06PM -0400, James McCoy wrote:
> Now that cmake is available on arm* again, emacs-libvterm just needs a
> binNMU to finish this transition.
There was a sourceful upload of emacs-libvterm, so that has been
addressed. Closing this bug.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
--- End Message ---
Reply to: