Hi Raphael,
On Sat, Feb 25, 2023 at 03:53:28PM +0100, Raphael Hertzog wrote:
> On Mon, 06 Feb 2023, Jelmer Vernooij wrote:
> > A large number of Debian packages now has upstream metadata, including
> > links to
> > upstream repositories (Repository-Browse) and bugtrackers (B
Package: tracker.debian.org
Severity: wishlist
A large number of Debian packages now has upstream metadata, including links to
upstream repositories (Repository-Browse) and bugtrackers (Bug-Database /
Bug-Submit). Would it be possible to link to those from tracker?
On Sat, Jan 28, 2023 at 04:30:39PM +0100, Raphael Hertzog wrote:
> Hello,
>
> On Fri, 27 Jan 2023, Jelmer Vernooij wrote:
> > I agree, I think anything that reduces the complexity of the ecosystem
> > is great and the lowers the barrier for entry. As pretty anything uses
> > Git now, I think migrat
On Fri, Dec 23, 2022 at 11:10:18AM +0100, Lucas Nussbaum wrote:
> On 12/12/22 at 21:26 +0000, Jelmer Vernooij wrote:
> > Package: qa.debian.org
> > Severity: wishlist
> >
> > It would be great if watch had a json mode, like vcswatch does.
> >
> > E.
Package: qa.debian.org
Severity: wishlist
It would be great if watch had a json mode, like vcswatch does.
E.g. allowing the retrieval of
https://qa.debian.org/cgi-bin/watch?package=foo&json=1 to get the watch status
for package foo.
Package: qa.debian.org
Severity: wishlist
X-Debbugs-Cc: m...@debian.org
It would be great if vcswatch could track who the committers were of the
commits have not yet made it into the archive.
I'm curious about this as a way to track the number of janitor commits that
have not yet been uploaded, a
Package: qa.debian.org
Severity: wishlist
It would be great if vcswatch could call a webhook whenever a packaging
repository changed.
This could be triggered whenever repositories are found to be different
at poll time, but e.g. for salsa this could be triggered by a server side hook
(https://doc
Package: qa.debian.org
Severity: normal
Usertag: udd
The duck table in UDD just has a list of source packages; it would be great if
it could include the actual fields that are invalid.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500
FTR, this is an issue with DDPO.
E.g. the column in https://qa.debian.org/developer.php?login=jelmer
currently shows "failed" for the bzr package, despite the fact that
the last uploaded package passes autopkgtest tests.
signature.asc
Description: Digital signature
Package: qa.debian.org
Severity: normal
ci.debian.net can sometimes be up to a couple of days out of date.
It would be great if the column with ci.debian.net results (fail/pass/-)
showed the version matching the result, or (better yet) indicates
whether the result is for the last upload.
-- Syste
Package: qa.debian.org
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
qa.debian.org currently suggests packaging a new upstream release when
there is a new upstream release that isn't packaged in Unstable. It
would nice if it didn't give this warning when the new upstream release
i
11 matches
Mail list logo
