Your message dated Sun, 10 Jan 2021 19:39:58 +0100 with message-id <8ab0a6abe46a28d489d0db769cffc163545b9335.ca...@debian.org> and subject line Re: Bug#972075: RFS: klystrack/0.20171212-5 [RC] -- Chiptune tracker has caused the Debian Bug report #972075, regarding RFS: klystrack/1.7.3+git20171212+ds-5 [RC] -- Chiptune tracker 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.) -- 972075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "klystrack": * Package name : klystrack Version : 0.20171212-5 Upstream Author : Tero Lindeman (kometbomb) <kometb...@gmail.com> Ilija Melentijevic * URL : https://github.com/kometbomb/klystrack * License : BSD-3-clause, MIT * Vcs : n/a Section : sound It builds those binary packages: klystrack - Chiptune tracker To access further information about this package, please visit the following URL: https://mentors.debian.net/package/klystrack/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/klystrack/klystrack_0.20171212-5.dsc Changes since the last upload: klystrack (0.20171212-5) unstable; urgency=medium . * Add -fcommon to upstream CFLAGS. (Closes: #957407) * Bump standards version to 4.5.0. * Bump debhelper version to 13, drop d/compat. Regards, -- Gürkan Myczko
--- End Message ---
--- Begin Message ---On Mon, 14 Dec 2020 07:29:16 +0100 =?UTF-8?Q?G=c3=bcrkan_Myczko?= <gur...@phys.ethz.ch> wrote: > On 25/11/2020 15:27, Tobias Frost wrote: > > > > My confusion was created because: > > It seems that the bug was not autoclosed, as the version in the bug title > > did not match > > the version to be sponsored. > > True. > > > This bug should be closed, shouldn't it? An a new one filed for -6? > > Not sure, I would like to reuse it by renaming it with a new upload > updating the version (still some time until freeze), would that be bad? Bug filing is cheap. Also, it tracker.d.o tells "there is something to sponsor" and it took me some brain cycles (better spent somewhere else) to realize that the tracker is wrong. There, to avoid time being wasted, its better to close. (And you always can reopen, if you want; it is equally cheap as filing a new one.) I'm closing this now to get caught by this a third time… -- tobi
--- End Message ---
