On 16128 March 1977, Felix Lechner wrote:
With the kind help of the good folks at DSA [1] Lintian's experimental
web application—still labeled "beta"—is now the official web presence.
[2] Please bear with us as we optimize the deployment and implement
additional features for you.
Thanks to you
Hi Norbert,
On Sun, Jan 17, 2021 at 5:02 AM Norbert Preining wrote:
>
> As part of this rework and the ongoing development, you said you have plans
> to set up a test version of the Lintian web application on non-Debian
> infrastructure. How is that going, Felix?
With the kind help of the good f
Hi Felix
thanks for the message and the web site. I have immediately tried it out
with a few packages of mine, as well as all of my packages. Indeed, that
took quite some time ;-)
Looks nice, but I am not sure how useful it will be for me, as I said, I
usually run lintian before uploading, so the
Le vendredi 02 avril 2021 à 19:31:30-0700, Felix Lechner a écrit :
> Dear Norbert,
>
> On Sun, Jan 17, 2021 at 5:02 AM Norbert Preining
> wrote:
> >
> > you said you have plans to set up a test version of the Lintian web
> > application on non-Debian infrastructure. How is that going, Felix?
>
Dear Norbert,
On Sun, Jan 17, 2021 at 5:02 AM Norbert Preining wrote:
>
> you said you have plans to set up a test version of the Lintian web
> application on non-Debian infrastructure. How is that going, Felix?
A beta version of Lintian's new service is now live at
lintian.debian.*net*. [1] The
Hi Dominique,
On Mon, Mar 22, 2021 at 05:19:10PM +0100, Dominique Dumont wrote:
>
> Once libconfig-model-dpkg-perl/experimental is installed on your system,
> 'cme
> check dpkg' checks the contents of all lintian-overrides files and warn about
> unknown tags.
>
> The command 'cme fix dpkg' r
On Wednesday, 27 January 2021 14:26:41 CET Andreas Tille wrote:
> > I can add support to lintian-overrides in cme. I can also add a more or
> > less automatic update of renamed tags.
> >
> > Is this something Debian people would like to see ?
>
> YES. (Since cme rocks - thanks again for working o
On Wed, 27 Jan 2021 14:20:06 +0100, Dominique Dumont wrote:
> On Thursday, 21 January 2021 23:18:07 CET Felix Lechner wrote:
> > While we often change tag names (or combine tags etc.), the majority
> > of the renames people talk about seems to stem from two bug reports by
> > third parties asking
On Wed, Jan 27, 2021 at 02:20:06PM +0100, Dominique Dumont wrote:
> On Thursday, 21 January 2021 23:18:07 CET Felix Lechner wrote:
> > While we often change tag names (or combine tags etc.), the majority
> > of the renames people talk about seems to stem from two bug reports by
> > third parties as
On Thursday, 21 January 2021 23:18:07 CET Felix Lechner wrote:
> While we often change tag names (or combine tags etc.), the majority
> of the renames people talk about seems to stem from two bug reports by
> third parties asking that we make tag names more consistent (bug
> numbers are available,
Hi Felix,
thanks for your email, and no worry about sending it late, we are all
volunteers.
> Due to the number of messages already posted in this thread, I will
> respond—with the best of ability—to each message separately.
Thanks, I will only go into answer those items that I find here.
> Tha
Le 21 janvier 2021 23:51:55 GMT+01:00, Felix Lechner
a écrit :
>Hi Pierre-Elliott,
>
>On Mon, Jan 18, 2021 at 5:00 AM Pierre-Elliott Bécue wrote:
>>
>> As I said on that time, I'd be glad to provide help and
>> support should Felix feel the need for some.
>
>I do not recall our most recent excha
Hi Antonio,
On Tue, Jan 19, 2021 at 4:43 AM Antonio Terceiro wrote:
>
> My hope is that this, and other use cases, could be enabled by
> collaborating on existing infrastructure, instead of creating yet
> another one.
I totally agree with you. I would like to spend some time looking at
your code
Hi Raphaël,
On Tue, Jan 19, 2021 at 3:27 AM Raphael Hertzog wrote:
>
> From my (relatively remote) point of view, ci.debian.net seems really
> very basic in terms of features related to scheduling of jobs.
Inspired by an early peek into your own ideas of a codenamed piece of
vaporware I wrote wh
Hi Pierre-Elliott,
On Mon, Jan 18, 2021 at 5:00 AM Pierre-Elliott Bécue wrote:
>
> As I said on that time, I'd be glad to provide help and
> support should Felix feel the need for some.
I do not recall our most recent exchanges as quite so positive, but I
would be happy to read you into some of
Hi Lucas,
On Mon, Jan 18, 2021 at 2:31 AM Lucas Nussbaum wrote:
>
> I agree that a service that provides an overview of the status regarding
> lintian for the whole archive would be useful (for example, to identify
> packages that need some area of work inside a team).
This functionality is not
Hi Norbert,
First of all, please accept my apologies for responding late. I
subscribe to d-d but filter lists for later perusal. Thanks to Lucas
Nussbaum for pointing me here!
Due to the number of messages already posted in this thread, I will
respond—with the best of ability—to each message sepa
Hi,
On Tue, 19 Jan 2021, Antonio Terceiro wrote:
> > Can you expand on the kind of features that ci.debian.net offers and what
> > kind of mistakes we would likely avoid by reusing it?
>
> To name a few:
>
> - distributed processing
> - data retention policies
> - web interface
Thanks for your
On Tue, Jan 19, 2021 at 12:27:31PM +0100, Raphael Hertzog wrote:
> Hi,
>
> On Mon, 18 Jan 2021, Antonio Terceiro wrote:
> > FWIW, The ci.debian.net infrastructure is mostly independent from
> > autopkgtest, so we could have different types of jobs there. This could
> > be used for lintian, but als
Hi,
On Mon, 18 Jan 2021, Antonio Terceiro wrote:
> FWIW, The ci.debian.net infrastructure is mostly independent from
> autopkgtest, so we could have different types of jobs there. This could
> be used for lintian, but also for on-demand rebuilds, and other types of
> checks that needs to be done t
interest/motivation to redesign lintian.d.o as a
> > standalone service, maybe a simpler architecture to explore would be to
> > build it on top of UDD (with lintian runners feeding a table in UDD
> > directly). That would make it possible to simplify most of the web stuff
> &g
able in UDD
> directly). That would make it possible to simplify most of the web stuff
> (and of course would still allow exporting to other services that need
> the data). I would be quite motivated to work on that.
Hey all,
Last time me and Felix discussed about lintian, his motivation
Hi,
On 17/01/21 at 22:00 +0900, Norbert Preining wrote:
> On the infrastructure side, you mentioned on #debian-qa that in your
> opinion, lintian is best run in a CI pipeline instead of on the
> lintian.d.o service. While this is certainly true, do you plan to keep
> the functionality on your rewo
Dear Felix, Chris,
(please Cc, I am not subscribed to d-d)
Here are a few questions regarding Lintian past and upcoming changes,
both as tool as well as infrastructure.
In the past year, many changes in lintian tag names occurred, along with some
tag removals. While it seems quite normal for lin
On Mon, 10 Jan 2011 at 21:30:57 +0200, Evgeniy Dolgih wrote:
> lintian shows me 2 warnings:
> changelog-should-mention-nmu and
> source-nmu-has-incorrect-version-number.
Have a look at the output of "lintian-info --tags changelog-should-mention-nmu"
and "lintian-info --tags source-nmu-has-incorrec
On Mon, 10 Jan 2011 21:30:57 +0200
Evgeniy Dolgih wrote:
> Hello.
> I going to adopt of orphaned package. I'm doing like described in this
> instruction: http://www.debian.org/devel/wnpp/index.en.html. I'm
> almost done with packaging but lintian shows me 2 warnings:
> changelog-should-mention-n
Hello.
I going to adopt of orphaned package. I'm doing like described in this
instruction: http://www.debian.org/devel/wnpp/index.en.html. I'm almost
done with packaging but lintian shows me 2 warnings:
changelog-should-mention-nmu and
source-nmu-has-incorrect-version-number. I'm double check debi
27 matches
Mail list logo
