Bug#840062: marked as done (tracker.debian.org: show historical data of no-longer existing source packages)
Your message dated Sun, 3 Dec 2017 12:13:45 +0100
with message-id <20171203111345.GA5998@home.ouaza.com>
and subject line Re: Bug#840062: tracker.debian.org and packages.qa.debian.org show different packages
has caused the Debian Bug report #840062,
regarding tracker.debian.org: show historical data of no-longer existing source packages
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.)
--
840062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840062
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: tracker.debian.org and packages.qa.debian.org show different packages
- From: Adrian Bunk <bunk@stusta.de>
- Date: Fri, 07 Oct 2016 23:39:43 +0300
- Message-id: <147587278323.3934.5535078997760091484.reportbug@localhost>
Package: tracker.debian.org
Severity: normal
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=nxproxy
links to
https://packages.qa.debian.org/n/nxproxy.html
links to "tracker.debian.org/pkg/nxproxy", which is
https://tracker.debian.org/pkg/nx-libs-lite
How do I make tracker.debian.org show the src:nxproxy page?
And the links from packages.qa.debian.org should be adjusted
accordingly.
--- End Message ---
--- Begin Message ---
- To: Paul Wise <pabs@debian.org>, 840062-done@bugs.debian.org
- Subject: Re: Bug#840062: tracker.debian.org and packages.qa.debian.org show different packages
- From: Raphael Hertzog <hertzog@debian.org>
- Date: Sun, 3 Dec 2017 12:13:45 +0100
- Message-id: <20171203111345.GA5998@home.ouaza.com>
- In-reply-to: <20161010145120.wx7mmx77d7sze5tt@home.ouaza.com>
- References: <147587278323.3934.5535078997760091484.reportbug@localhost> <20161010115440.pjqnvpd5zxn3w4ln@home.ouaza.com> <20161010120206.urbmpbu3s3s6p2pc@bunk.spdns.de> <20161010121506.x7tfukmo2ilixqdp@home.ouaza.com> <20161010130151.iahvkltmrbfm5ipm@bunk.spdns.de> <20161010131431.y62p6o5b2bd6lq37@home.ouaza.com> <CAKTje6Eiedpz67Jzq8Ge+kk55A_NqO=mabuje3j0EsE9kNRvUQ@mail.gmail.com> <20161010145120.wx7mmx77d7sze5tt@home.ouaza.com>
On Mon, 10 Oct 2016, Raphael Hertzog wrote:
> It might even be not too hard to implement. For example by checking the
> number of associated news before deciding that we want to consider a
> binary lookup...
We did this at some point in the past. You can see for example linux-2.6
on tracker.debian.org. You can access it with the "src:" prefix (in case
it's hidden by a new binary package) or without it otherwise.
https://tracker.debian.org/pkg/linux-2.6
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/
--- End Message ---
Reply to: