Your message dated Sat, 21 Sep 2024 09:13:54 +0200
with message-id <[email protected]>
and subject line Re: dynamite: 2012 changed repo to GH
has caused the Debian Bug report #1080217,
regarding dynamite: 2012 changed repo to GH
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.)
--
1080217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080217
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: dynamite
Version: 0.1.1-2
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
In 2012 dynamite has been moved to:
https://github.com/twogood/dynamite
With last activity dec-2020 cant tell there are significant changes. (I'm not a
coder)
(I'm not a coder)
-- System Information:
Debian Release: 12.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-23-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Control: severity -1 wishlist
Control: retitle -1 "dynamite: upstream VCS possibly moved to github."
On Sat, 31 Aug 2024 20:41:22 +0200 Ben Tris <[email protected]>
wrote:
> Source: dynamite
> Version: 0.1.1-2
> Severity: normal
> X-Debbugs-Cc: [email protected]
>
> Dear Maintainer,
>
> In 2012 dynamite has been moved to:
>
> https://github.com/twogood/dynamite
>
> With last activity dec-2020 cant tell there are significant changes.
If you don't have an actual problem with the package, please do not file
such bugs, as this only creates noise and extra work. I say this, as th
bugs you've filed in the past few weeks make the overall impression that
you file the bugs for the sake of filing bugs. *Please do not do that.*
You've been told that before, by the way.
Looking at the changes upstream at the github, upstream only added a
REAMDE and a configuration file for a codescanner. Even if you a not
a coder, you should have researched this before filing this bug.
Closing this bug as non actionable. For this package I wouldn't even
know, expect maybe putting this into d/s/metadata, what this information
would change on package.
(I'm not a
> coder)
>
> (I'm not a coder)
>
>
> -- System Information:
> Debian Release: 12.6
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 6.1.0-23-amd64 (SMP w/4 CPU threads; PREEMPT)
> Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8),
LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
>
--- End Message ---
