Bug#1055245: marked as done (RFS: tint2/17.0.1-1.1 [NMU] [RC] -- lightweight taskbar)
Your message dated Fri, 3 Nov 2023 14:28:59 +0100
with message-id <0dcb480a-7033-49b9-a237-b857eade29d7@debian.org>
and subject line Re: tint2 coredumps on startup
has caused the Debian Bug report #1055245,
regarding RFS: tint2/17.0.1-1.1 [NMU] [RC] -- lightweight taskbar
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.)
--
1055245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055245
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "tint2":
* Package name : tint2
Version : 17.0.1-1.1
Upstream contact : [fill in name and email of upstream]
* URL : https://gitlab.com/o9000/tint2/
* License : GPL-2, GPL-2+
* Vcs : https://salsa.debian.org/debian/tint2
Section : x11
The source builds the following binary packages:
tint2 - lightweight taskbar
To access further information about this package, please visit the following URL:
https://mentors.debian.net/package/tint2/
Alternatively, you can download the package with 'dget' using this command:
dget -x https://mentors.debian.net/debian/pool/main/t/tint2/tint2_17.0.1-1.1.dsc
Changes since the last upload:
tint2 (17.0.1-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add patch for fix crash with glib 2.76. (Closes: #1054261) (LP: #2015052)
Regards,
--
Mateusz Łukasik
--- End Message ---
--- Begin Message ---
- To: 1054261@bugs.debian.org, 1055245-done@bugs.debian.org
- Subject: Re: tint2 coredumps on startup
- From: Bastian Germann <bage@debian.org>
- Date: Fri, 3 Nov 2023 14:28:59 +0100
- Message-id: <0dcb480a-7033-49b9-a237-b857eade29d7@debian.org>
- In-reply-to: <169776374005.28010.3706344003337708957.reportbug@rider.home.pv>
- References: <169776374005.28010.3706344003337708957.reportbug@rider.home.pv> <169776374005.28010.3706344003337708957.reportbug@rider.home.pv>
I am uploading a NMU to fix this, which also includes the latest git commits.
The change that I am sponsoring is also available in git.
--- End Message ---
Reply to: