Bill Allombert wrote:
> Indeed, but I am concerned that providing data for a small subset of
> the archive is a increasing the risk a deanonymization.
>
> Currently unstable+testing is about 15% of the archive but it is
> often much less. Furthermore if we publish data for unstable+testing,
> the
On Tue, Oct 14, 2014 at 02:57:50PM -0400, Joey Hess wrote:
> Bill Allombert wrote:
> > I am a bit confused by your report. I would expect what you request to be
> > adequately provided by the popcon.debian.org website and the
> > popularity-contest version field. We even provide separate data for
Bill Allombert wrote:
> I am a bit confused by your report. I would expect what you request to be
> adequately provided by the popcon.debian.org website and the
> popularity-contest version field. We even provide separate data for stable.
But not separate data for unstable+testing.
Also, there
On Mon, Oct 13, 2014 at 11:09:07PM -0400, Joey Hess wrote:
> Package: popularity-contest
> Version: 1.61
> Severity: normal
>
> I use popcon data a lot for eg, tasksel, and often one is only
> interested in data for unstable, or stable. But there's no good way to
> separate those in the results. I
[Joey Hess]
> So, could the release information please be included in the report?
> Specifically just the name of the current release from
> /etc/debian_version.
According to the changelog, this was added in versoin 1.8 and replaced
by the popcon version in version 1.19 because the content was not
Package: popularity-contest
Version: 1.61
Severity: normal
I use popcon data a lot for eg, tasksel, and often one is only
interested in data for unstable, or stable. But there's no good way to
separate those in the results. Instead, various workarounds have to be
used, like trying to tease out inf
6 matches
Mail list logo
