Your message dated Thu, 30 Sep 2021 07:32:44 -0700 with message-id <CAFHYt55oXaffWZePvWFtRGYphuJfEXU8toSn6guyui4fgO54hQ@mail.gmail.com> and subject line Re: Bug#928809: lintian: suggest adding gitlab-ci file has caused the Debian Bug report #928809, regarding lintian: suggest adding gitlab-ci file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 928809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928809 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: lintian: suggest adding gitlab-ci file
- From: Dmitry Bogatov <KAction@debian.org>
- Date: Sat, 11 May 2019 14:49:02 +0000
- Message-id: <E1hPTJ0-0002aK-Hi@eggs.gnu.org>
Package: lintian Version: 2.13.0 Severity: wishlist Dear Maintainer, please add suggestion that if Vcs-Git points to salsa.debian.org, CI should be used. While CI config can be located anywhere (ci_config_path property of project), both Debian Wiki and salsa(1) manpage mention "debian/.gitlab-ci.yml" path. So, in pseudo-code I propose following: if ($vcs =~ salsa.debian.org && ! -r "debian/.gitlab-ci.yml") { tag-pedantic "consider useing Gitlab CI" }Attachment: pgp4M_q1Inkme.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: 928809-done@bugs.debian.org
- Cc: Chris Lamb <lamby@debian.org>, Mattia Rizzolo <mattia@debian.org>, Dmitry Bogatov <KAction@debian.org>
- Subject: Re: Bug#928809: lintian: suggest adding gitlab-ci file
- From: Felix Lechner <felix.lechner@lease-up.com>
- Date: Thu, 30 Sep 2021 07:32:44 -0700
- Message-id: <CAFHYt55oXaffWZePvWFtRGYphuJfEXU8toSn6guyui4fgO54hQ@mail.gmail.com>
- In-reply-to: <E1hRxYv-0004Ot-RC@eggs.gnu.org>
- References: <20190512120643.GK31497@mapreri.org> <c0cc3a1c-8bfe-48f5-acb0-2e34af408981@www.fastmail.com> <20190513122440.GM31497@mapreri.org> <E1hPTJ0-0002aK-Hi@eggs.gnu.org> <692d8a7b-97ad-459b-99ca-a2fdba18fec0@www.fastmail.com> <E1hRxYv-0004Ot-RC@eggs.gnu.org>
Hi, Not sure if this will reach the reporting party, who has gone emeritus. On Sat, May 18, 2019 at 4:33 AM Dmitry Bogatov <KAction@debian.org> wrote: > > I suggest makeing it impossible to turn of all controversal The tag already exists as a classification tag. [1] Originally implemented as a research tag on behalf of the Salsa CI team, it can be enabled on the command line. To manage a portfolio of packages, you may find it easier to use our website's JSON interface. [2] With that method, it is relatively easy to determine which of your sources is missing a gitlab-ci.yml file, and in which path it should be located. Closing this bug. Kind regards Felix Lechner [1] https://lintian.debian.org/tags/continuous-integration/salsa/specification [2] https://lintian.debian.org/query
--- End Message ---