Package: libvte-2.91-gtk4-0
Version: 0.75.91-2
Severity: normal
X-Debbugs-Cc: ken...@xdump.org
Dear Maintainer,
* What led up to the situation?
It seems that there is sixel support, but not enabled yet.
https://gitlab.gnome.org/GNOME/vte/-/commits/master?ref_type=heads
In vte-0-76 branch, upstream decided to remove Sixel support
from stable branch.
https://gitlab.gnome.org/GNOME/vte/-/commits/vte-0-76?ref_type=heads
debian/latest branch on salsa.d.o follows as same.
It is reasonable to follow upstream because there is blocker
issue.
Regression: Sixel rendering broken since native GTK4 drawing.
https://gitlab.gnome.org/GNOME/vte/-/issues/2717
For the record about status of supporting Sixel, I send a bug
report.
* What exactly did you do (or not do) that was effective (or
ineffective)?
N/A
* What was the outcome of this action?
Sixel support will be enabled by default with VTE package in the
future release.
* What outcome did you expect instead?
N/A
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE Locale: LANG=ja_JP.utf8, LC_CTYPE=ja_JP.utf8
(charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libvte-2.91-gtk4-0 depends on:
ii libc6 2.37-15
ii libcairo-gobject2 1.18.0-1+b1
ii libcairo2 1.18.0-1+b1
ii libfribidi0 1.0.13-3+b1
ii libgcc-s1 14-20240201-3
ii libglib2.0-0 2.78.4-1
ii libgnutls30 3.8.3-1
ii libgtk-4-1 4.12.5+ds-2
ii libicu72 72.1-4+b1
ii liblz4-1 1.9.4-1+b2
ii libpango-1.0-0 1.51.0+ds-4
ii libpangocairo-1.0-0 1.51.0+ds-4
ii libpcre2-8-0 10.42-4+b1
ii libstdc++6 14-20240201-3
ii libsystemd0 255.3-2
ii libvte-2.91-common 0.75.91-2
libvte-2.91-gtk4-0 recommends no packages.
libvte-2.91-gtk4-0 suggests no packages.
-- no debconf information
