On 29/06/20 at 09:49 +0800, Paul Wise wrote:
> On Sun, 2020-06-28 at 18:17 +0200, Lucas Nussbaum wrote:
>
> > That would be easy. What should that API look like? Would returning all
> > the info for a given source package, as json, be enough?
>
> Probably just the same API as the existing rmadiso
On Sun, 2020-06-28 at 18:17 +0200, Lucas Nussbaum wrote:
> That would be easy. What should that API look like? Would returning all
> the info for a given source package, as json, be enough?
Probably just the same API as the existing rmadison APIs. Since there
is already a udd madison script, prob
Hi Paul,
On 10/11/16 at 13:54 +0800, Paul Wise wrote:
> Package: qa.debian.org
> User: qa.debian@packages.debian.org
> Usertags: udd madison watch
> Severity: wishlist
> Control: affects -1 devscripts
>
> It would be nice if the UDD watch file scanning service had a madison
> frontend that co
Package: qa.debian.org
User: qa.debian@packages.debian.org
Usertags: udd madison watch
Severity: wishlist
Control: affects -1 devscripts
It would be nice if the UDD watch file scanning service had a madison
frontend that could be added to rmadison so that one could get the
upstream version of
4 matches
Mail list logo
