Re: Bug#1007002: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Andreas Tille
Hi Axel, Am Wed, Jun 29, 2022 at 06:01:33PM +0200 schrieb Axel Beckert: > Andreas: Sorry if I was a bit too opposing because of assuming that > every DD uses Unstable by default. No need to be sorry, really not. I simply missed the point of that change. > (Actually I think the Dev Ref says >

Re: Bug#1007002: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Axel Beckert
Hi again, Axel Beckert wrote: > Andreas Tille wrote: > > I'll start editing lintian-overrides then. > > Maybe wait a bit with that. Given Lucas' comment, I feel a bit more > urged to provide such a migration script. > > I will look into this for the next upload. No promises as of now, > though.

Re: Bug#1007002: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Axel Beckert
Hi Lucas, Lucas Nussbaum wrote: > Just a note that since the last version of lintian to migrate to testing > was 2.111 (which was also the last one to be backported to stable), some > of us might not have updated since 2.111 and might be hit by changes > that happened since then. Oh, right!

Re: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Lucas Nussbaum
On 29/06/22 at 15:49 +0200, Axel Beckert wrote: > Correct, except that it happened for quite a while (7 months at least) > and was (and maybe still is — see below) a continuous transition. It > is present since at least 2.114.0 from November 2021. According to the > git history, the implementation

Re: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Andreas Tille
Hi Samuel and Axel, Am Wed, Jun 29, 2022 at 04:10:49PM +0200 schrieb Samuel Thibault: > Axel Beckert, le mer. 29 juin 2022 15:49:11 +0200, a ecrit: > > > I consider these [] not helpful […] no visible advantage. OK, thanks for making the advantages visible to me then. I'll start editing

Re: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Samuel Thibault
Hello, Axel Beckert, le mer. 29 juin 2022 15:49:11 +0200, a ecrit: > > I consider these [] not helpful […] no visible advantage. > > The advantage is to clearly mark what is a file with potentially a > line number in the output of lintian so that further processors like > the lintian website can

Re: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Axel Beckert
Hi Andreas, Andreas Tille wrote: > I realised that lintian (at least) starting with version 2.115.1 (may be > earlier) wraps file names into [] which breaks existing > lintian-overrides. Correct, except that it happened for quite a while (7 months at least) and was (and maybe still is — see

Re: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Andrey Rahmatullin
On Wed, Jun 29, 2022 at 02:49:35PM +0200, Andreas Tille wrote: > Hi, > > I realised that lintian (at least) starting with version 2.115.1 (may be > earlier) wraps file names into [] which breaks existing > lintian-overrides. Random example: > > >

Re: Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Roberto C . Sánchez
On Wed, Jun 29, 2022 at 02:49:35PM +0200, Andreas Tille wrote: > Hi, > > I realised that lintian (at least) starting with version 2.115.1 (may be > earlier) wraps file names into [] which breaks existing > lintian-overrides. Random example: > > >

Lintian breaks existing lintian-overrides due to added []

2022-06-29 Thread Andreas Tille
Hi, I realised that lintian (at least) starting with version 2.115.1 (may be earlier) wraps file names into [] which breaks existing lintian-overrides. Random example: https://salsa.debian.org/med-team/biomaj3-user/-/blob/master/debian/lintian-overrides now becomes invalid by lintian