Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1063424: nmu: wlgreet_0.4.1-3
0 views
Skip to first unread message
Arto Jantunen
Feb 8, 2024, 2:00:04 AM2/8/24
to
Package: release.debian.org
Severity: normal
User: release.d...@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: wlg...@packages.debian.org, 106...@bugs.debian.org
Control: affects -1 + src:wlgreet
nmu wlgreet_0.4.1-3 . ANY . unstable . -m "Rebuild against rust-smithay-client-toolkit 0.16.1"
This is needed to fix #1061421 (crash with recent sway versions). This is
caused by the same underlying issue as #1061563 in alacritty, it was already
fixed via binNMU there.
Severity: normal
User: release.d...@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: wlg...@packages.debian.org, 106...@bugs.debian.org
Control: affects -1 + src:wlgreet
nmu wlgreet_0.4.1-3 . ANY . unstable . -m "Rebuild against rust-smithay-client-toolkit 0.16.1"
This is needed to fix #1061421 (crash with recent sway versions). This is
caused by the same underlying issue as #1061563 in alacritty, it was already
fixed via binNMU there.
Debian Bug Tracking System
Feb 8, 2024, 2:00:05 AM2/8/24
to
Processing control commands:
> affects -1 + src:wlgreet
Bug #1063424 [release.debian.org] nmu: wlgreet_0.4.1-3
Added indication that 1063424 affects src:wlgreet
--
1063424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> affects -1 + src:wlgreet
Added indication that 1063424 affects src:wlgreet
--
1063424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Debian Bug Tracking System
Feb 8, 2024, 2:20:04 AM2/8/24
to
Your message dated Thu, 8 Feb 2024 08:10:09 +0100
with message-id <ZcR-UaLQ...@ramacher.at>
and subject line Re: Bug#1063424: nmu: wlgreet_0.4.1-3
has caused the Debian Bug report #1063424,
regarding nmu: wlgreet_0.4.1-3
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.)
with message-id <ZcR-UaLQ...@ramacher.at>
and subject line Re: Bug#1063424: nmu: wlgreet_0.4.1-3
has caused the Debian Bug report #1063424,
regarding nmu: wlgreet_0.4.1-3
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.)
Marc Dequènes
Feb 20, 2024, 5:00:04 AM2/20/24
to
Quack,
On 2024-02-08 15:50, Arto Jantunen wrote:
> This is needed to fix #1061421 (crash with recent sway versions). This
> is
> caused by the same underlying issue as #1061563 in alacritty, it was
> already
> fixed via binNMU there.
Thanks a lot.
I'm in the middle of moving to a new Pond and lacked time to debug more,
so this is really helpful.
Regards.
\_o<
--
Marc Dequènes
On 2024-02-08 15:50, Arto Jantunen wrote:
> This is needed to fix #1061421 (crash with recent sway versions). This
> is
> caused by the same underlying issue as #1061563 in alacritty, it was
> already
> fixed via binNMU there.
I'm in the middle of moving to a new Pond and lacked time to debug more,
so this is really helpful.
Regards.
\_o<
--
Marc Dequènes
Arto Jantunen
Feb 20, 2024, 5:30:04 AM2/20/24
to
wlgreet (while it definitely did for alacritty). I don't know why,
though. More debugging is needed.
--
Arto Jantunen
0 new messages