Bug#904694: marked as done (tracker.debian.org: don't complain about outdated S-V for packages only in <= stable)
Your message dated Mon, 20 Aug 2018 21:51:57 +0000
with message-id <5b7b37fd77cc4_38e2b1bb614b0d4677c8@godard.mail>
and subject line Bug #904694 in tracker.debian.org fixed
has caused the Debian Bug report #904694,
regarding tracker.debian.org: don't complain about outdated S-V for packages only in <= stable
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.)
--
904694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904694
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: tracker.debian.org: don't complain about outdated S-V for packages only in <= stable
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Thu, 26 Jul 2018 21:07:13 +0100
- Message-id: <1532635633.3030.230.camel@adam-barratt.org.uk>
Package: tracker.debian.org
Hi,
https://tracker.debian.org/pkg/postgresql-9.6 reports both that the
package is "not in any development repository", and that "[t]he package
is severely out of date with respect to the Debian Policy".
It seems silly (and apparently confusing to at least some users) to
complain about the outdated S-V for a package that only exists in
(old)stable, where the package won't be tracking updates to Policy.
Regards,
Adam
--- End Message ---
--- Begin Message ---
Hello,
Bug #904694 in tracker.debian.org reported by you has been fixed in the Git repository.
You can see the commit message below, and you can check the diff of the fix at:
https://salsa.debian.org/qa/distro-tracker/commit/73eafc168ede50bc0e53c4cd36a23e8ad8ee8764
------------------------------------------------------------------------
stdver_warnings: properly handle removal from default repository
The way I initially implemented items_extend_queryset() means that
we processed all repositories instead of only the default one. The
task was taking way too long and we failed to drop some items that
should have been dropped.
Closes: #904694
------------------------------------------------------------------------
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/904694
--- End Message ---
Reply to: