Philipp Kern (2022-10-16):
> Unfortunately it doesn't look like there was progress on #887649 this
> cycle either. So I fear that we'll end up needing to tag both #887649
> and #885563 bookworm-ignore. :(
I'm keeping an open mind but given the remaining time, and the otherwise
important workload
On Sun, Sep 30, 2018 at 09:03:47AM -0400, Jeremy Bicha wrote:
> On Sun, Sep 30, 2018 at 2:57 AM Niels Thykier wrote:
> > AFAICT, the cdebconf-gtk-terminal bug (#887649) has not been updated in
> > the past 8 months. Is it still realistic to remove vte before the
> > transition freeze
Control: severity -1 important
Control: retitle -1 vte: Do not release with bullseye
The only thing using the old vte in Debian is cdebconf-terminal. But
since that's a critical package that hasn't been converted yet, let's
defer vte's removal until Bullseye.
Thanks,
Jeremy Bicha
On Sun, Sep 30, 2018 at 2:57 AM Niels Thykier wrote:
> AFAICT, the cdebconf-gtk-terminal bug (#887649) has not been updated in
> the past 8 months. Is it still realistic to remove vte before the
> transition freeze (2019-01-12)?
I agree that I don't see anyone working on that bug now. I think
On Thu, 28 Dec 2017 00:05:02 -0500 Jeremy Bicha wrote:
> Source: vte
> Severity: serious
> Tags: sid buster
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs vte
>
> The old vte 0.28 series has not had a release since GNOME3's release in 2011.
>
> Please port your app to
Source: vte
Severity: serious
Tags: sid buster
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs vte
The old vte 0.28 series has not had a release since GNOME3's release in 2011.
Please port your app to the vte2.91 source. That also means porting
your app to gtk3. gtk3 was
6 matches
Mail list logo
