Hi,
On Wed, 14 Apr 2021, Lucas Nussbaum wrote:
> I think that in Debian, we would aim for a better separation between:
>
> A/ QA tools development, focused on getting the good tools to analyze
> packages (output: tools, as Debian packages)
>
> B/ infrastructure that mass-process the archive usin
Hi,
On Wed, Apr 14, 2021 at 1:49 AM Lucas Nussbaum wrote:
>
> C/ infrastructure that gathers the current status from all instances of
> (B) and exposes it per-package, per-maintainer, per-team, etc.
For some data, such as Lintian packaging hints, there may be a
powerful combination of AMQP and P
Hi Lucas,
TL;DR please find one idea to solve your issue below
> provide the current
> status of the archive against the current version of lintian as
> something parsable
Just for lintian.d.n (which is about to be transferred to
lintian.d.o), that is exactly what we provide. It just won't be on
(Adding debian-qa@ to Cc to broaden the discussion a bit)
Hi,
On the issue of lintian.d.n/lintian.d.o/UDD/tracker.d.o, I wonder if the
separation of concerns is the right one.
I think that in Debian, we would aim for a better separation between:
A/ QA tools development, focused on getting the g
On 13/04/21 at 11:49 -0700, Felix Lechner wrote:
> Hi,
>
> On Tue, Apr 13, 2021 at 11:27 AM Lucas Nussbaum wrote:
> >
> > From the UDD point of view, I would very much prefer to get a full dump
> > something I can import every few hours, than having to deal with a
> > stream of updates or with qu
Hi,
On Tue, Apr 13, 2021 at 11:27 AM Lucas Nussbaum wrote:
>
> From the UDD point of view, I would very much prefer to get a full dump
> something I can import every few hours, than having to deal with a
> stream of updates or with querying a per-package API.
Since few users ever need *all* data
On 13/04/21 at 18:45 +0200, Mattia Rizzolo wrote:
> [ Adding lucas@ to CC since he is the main person behind UDD after all ]
>
> On Sun, Apr 11, 2021 at 12:45:14PM -0700, Felix Lechner wrote:
> > On Sat, May 9, 2020 at 5:33 PM Mattia Rizzolo wrote:
> > > have lintian decide on a nice machine-pars
On Tue, Apr 13, 2021 at 11:03:12AM -0700, Felix Lechner wrote:
> On Tue, Apr 13, 2021 at 9:46 AM Mattia Rizzolo wrote:
> > full import of everything
>
> I do not believe that is practicable. There are other ideas below.
>
> > * Figure out a way for UDD to know it needs to check the status of a
>
Hi,
On Tue, Apr 13, 2021 at 9:46 AM Mattia Rizzolo wrote:
>
> I'd have probably used a different bug, but guess we'll cope.
I thought you might get upset the other way around. This bug already
blocks a UDD counterpart (#960156). The solutions I offered to date
were stop gaps.
> full import of e
[ Adding lucas@ to CC since he is the main person behind UDD after all ]
On Sun, Apr 11, 2021 at 12:45:14PM -0700, Felix Lechner wrote:
> On Sat, May 9, 2020 at 5:33 PM Mattia Rizzolo wrote:
> > have lintian decide on a nice machine-parsable (text!) format
> > then udd will adapt its importer.
>
10 matches
Mail list logo
