Your message dated Tue, 6 Feb 2024 09:05:50 +0100
with message-id <zchoxktxxxaub...@ramacher.at>
and subject line Re: Bug#1061565: nmu: rust-alacritty_0.12.2-2
has caused the Debian Bug report #1061565,
regarding nmu: rust-alacritty_0.12.2-2
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 ow...@bugs.debian.org
immediately.)
--
1061565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: rust-alacri...@packages.debian.org
Control: affects -1 + src:rust-alacritty
nmu rust-alacritty_0.12.2-2 . ANY . unstable . -m "Rebuild against
rust-smithay-client-toolkit 0.16.1"
This is needed to fix #1061563 (crash with recent sway versions).
--- End Message ---
--- Begin Message ---
On 2024-02-05 22:21:09 -0500, James McCoy wrote:
> On Fri, Jan 26, 2024 at 10:16:50AM -0500, James McCoy wrote:
> > nmu rust-alacritty_0.12.2-2 . ANY . unstable . -m "Rebuild against
> > rust-smithay-client-toolkit 0.16.1"
> >
> > This is needed to fix #1061563 (crash with recent sway versions).
>
> Ping? It'd be nice to get this fixed, since other things are blocking
> an update of alacritty.
Scheduled.
Cheers
--
Sebastian Ramacher
--- End Message ---
