Your message dated Sat, 20 May 2023 15:19:47 +0100
with message-id <[email protected]>
and subject line Re: Bug#1036179: xss-lock: please consider upgrading to 3.0
source format
has caused the Debian Bug report #1036179,
regarding xss-lock: please consider upgrading to 3.0 source format
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 [email protected]
immediately.)
--
1036179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036179
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: xss-lock
Version: 0.3.0+git20230128.0c562b-1
Please switch xss-lock to the 3.0 (quilt) source format.
--- End Message ---
--- Begin Message ---
Control: tag -1 +wontfix
On Tue, 2023-05-16 at 19:56 +0200, Bastian Germann wrote:
> Please switch xss-lock to the 3.0 (quilt) source format.
Thank you for the suggestion however I maintain xss-lock using the
strategy described in dgit-maint-merge(7) and wish to keep tracking
changes as commits in git not in some further patch queue system. (See
also #1007069)
If you want individual patches then please use
https://salsa.debian.org/debian/xss-lock or dgit clone.
Ian.
--- End Message ---
