On Fri, Aug 02, 2024 at 05:09:49PM +0200, Lucas Nussbaum wrote:
> UDD has an importer for https://janitor.debian.net/.
> Unfortunately, the service has been down for some time now.
>
> In the meantime the importer has been removed from UDD's configuration
> in commit a13247444876aed518bba5058423ba
On Wed, Jan 10, 2024 at 07:58:31PM -0500, Yogeswaran Umasankar wrote:
> I want to join the QA team and get access to orphaned packages in
> salsa git. I want to contribute by fixing them. Would you provide me
> access to my salsa ID: yogu
Orphaned packages on salsa live under the debian/ group, so
On Wed, Apr 12, 2023 at 07:35:30PM +0200, Diederik de Haas wrote:
> On Wednesday, 12 April 2023 18:45:31 CEST Jelmer Vernooij wrote:
> > I think the git repositories should just be created directly under
> > debian/. There's no reason not to, it makes it easier to find them
>
On Thu, Apr 06, 2023 at 11:02:26PM +0200, Diederik de Haas wrote:
> Hi,
>
> On Friday, 27 January 2023 20:14:43 CEST Jelmer Vernooij wrote:
> > I've been looking at how to do a mass conversion. There's about 375 packages
> > still listed as being on alioth (~100 i
retitle 1032623 vcswatch: should not raise error on repos > 1GiB in size
thanks
My understanding is that the restriction on 1Gb in size for repositories was
recently introduced and is intentional (due to disk constraints on the host
where vcswatch runs?).
Hi Diederik!
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 migrating more things from SVN to Git would be great.
On Fri, Jan 27, 2023 at 07:56:37PM +0100, Diederik de Haas wrote:
> I w
On Wed, Nov 02, 2022 at 08:50:14AM +0100, Lucas Nussbaum wrote:
> Hi,
>
> https://trends.debian.net/
Nice!
Since you ask for suggestions on the web site, it would also be great to
include a graph with the number of outstanding multi-arch hints there.
Jelmer
Thanks!
It would indeed be great if we could also extract the authors into a proper
JSON structure so downstream consumers like the janitor don't have to implement
that themselves for each VCS type.
On 8 August 2022 17:14:44 CEST, Christoph Berg wrote:
>Re: To Jelmer Vernooij
>> Does that work
On Tue, Apr 06, 2021 at 08:49:01AM +0200, Lucas Nussbaum wrote:
> Hi,
>
> On 05/04/21 at 15:14 +0100, Jelmer Vernooij wrote:
> > The python3-buildlog-consultant package now has a "analyse-sbuild-log"
> > command that can parse and analyse sbuild logs and in most
ot;section": "Build", "lineno": 857, "kind":
"missing-python-module", "details": {"module": "setuptools", "python_version":
3, "minimum_version": null}}
This is what powers the line selection for the frag
On Mon, Mar 08, 2021 at 09:17:15PM +0100, Davide Prina wrote:
> I will try to propose a new check to improve Debian Quality :-)
>
> I'm using repology (https://repology.org) to report packages with home page
> not work anymore and where I found a possible new home page.
> But a lot of what I'm doi
- instead of
getting these tools to just do the right thing without making a
human edit a file.
"allow-reformatting" is irrelevant if tools that edit control
files can perfectly preserve existing formatting. Perhaps it's
possible to autodetect what release to maintain backwards
compatibility with as well?
Cheers,
Jelmer
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
signature.asc
Description: PGP signature
On Thu, Dec 17, 2020 at 06:39:28PM +0100, Christoph Berg wrote:
> Re: Jelmer Vernooij
> > My bad, the word "changed" in my original bug was ambiguous. I'm
> > interested in notifications when there are new commits to the
> > packaging repository - rather than
On Thu, Dec 17, 2020 at 05:40:31PM +0100, Christoph Berg wrote:
> Re: Jelmer Vernooij
> > It would be great if vcswatch could call a webhook whenever a packaging
> > repository changed.
> currently repository information is extracted from the Sources files
> in unstable and experimental, i.e. vcswa
notifications would be less real-time.
--
Jelmer Vernooij
PGP Key: https://www.jelmer.uk/D729A457.asc
On Sun, Aug 16, 2020 at 02:17:13PM +0200, Mattia Rizzolo wrote:
> On Sat, Aug 15, 2020 at 01:04:35AM +, Paul Wise wrote:
> > I wonder if storing metadata (including Homepage, debian/watch,
> > debian/upstream/*) about the upstream project in the Debian source
> > package is the wrong approach.
Hi Charles, Andreas,
DEP-12 appears to have been stalled for a while in the draft phase; I'd be keen
to see if it can be moved forward - and would really appreciate any suggestions
on how to help do so.
Adoption
It looks like there are already close to 5000 debian/upstream/metadata file
On Thu, Mar 05, 2020 at 09:40:33PM +0100, gregor herrmann wrote:
> On Thu, 05 Mar 2020 10:28:03 +, Iain Lane wrote:
> > Since the discussions on the bug I've learned a
> > bit more about the upstream metadata spec
> > https://wiki.debian.org/UpstreamMetadata
> > I think a slight gap there is
Hi Andreas,
On Tue, Dec 03, 2019 at 08:10:46AM +0100, Andreas Tille wrote:
> On Tue, Dec 03, 2019 at 02:27:58AM +0000, Jelmer Vernooij wrote:
> > The debian/upstream/metadata file spec
> > (https://wiki.debian.org/UpstreamMetadata) currently supports
> > a "Repository&quo
Package: qa.debian.org
Severity: wishlist
For tools that rely on vcswatch to know what vcs repository to process,
it would be great if vcswatch could store:
* the latest revision (e.g. commit SHA for Git, revision number for
SVN, etc)
* When that revision was created
-- System Information:
amba.git
Branch: 4.7
* Allow specifying the branch in the Repository header somehow. This
would be more consistent with what happens for e.g. the packaging
metadata headers in debian/control. E.g.:
Repository: https://git.samba.org/samba.git -b 4.7
Jelmer
--
Jelmer Vernooij
PGP Key: https://ww
Hi Charles,
https://wiki.debian.org/UpstreamMetadata mentions that
there is a draft collector system for debian/upstream/metadata at
http://upstream-metadata.debian.net/. However, that page just contains
a stock web page ("It works!").
Do you happen to know who runs the upstream-metadata site?
C
22 matches
Mail list logo
