Re: Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-26 Thread Gilles Filippini
Chris Lamb a écrit le 26/12/2018 à 00:07 : >> Would have been simpler to mention it in the first place. > > Given the context of the mail I had assumed that was implicit. I understand. Usual communication problems when implicitness is involved :) Thanks, _g. signature.asc Description:

Re: Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-25 Thread Chris Lamb
Gilles, > Would have been simpler to mention it in the first place. Given the context of the mail I had assumed that was implicit. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- -- debian-science-maintainers mailing list

Re: Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-25 Thread Gilles Filippini
Graham Inggs a écrit le 25/12/2018 à 19:46 : > Hi Chris > > On Tue, 25 Dec 2018 at 20:36, Chris Lamb wrote: >> Hey, it's your package! :) No, I was merely seeing an override for >> what could be a Lintian bug. Quickly looking into this, these two >> tags were removed in Lintian 2.5.5 (Feb 2012)

Re: Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-25 Thread Graham Inggs
Hi Chris On Tue, 25 Dec 2018 at 20:36, Chris Lamb wrote: > Hey, it's your package! :) No, I was merely seeing an override for > what could be a Lintian bug. Quickly looking into this, these two > tags were removed in Lintian 2.5.5 (Feb 2012) so can probably just be > dropped. Ah! I didn't

Re: Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-25 Thread Chris Lamb
Hi Graham, > I'm unable to get Lintian to show this message locally, so I'd also > like to know which option is needed to display it. Hey, it's your package! :) No, I was merely seeing an override for what could be a Lintian bug. Quickly looking into this, these two tags were removed in Lintian

Re: Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-25 Thread Graham Inggs
Hi On Tue, 25 Dec 2018 at 01:08, Chris Lamb wrote: > > Which lintian option does cause this message? > > Option? Don't you mean tag? :) ie. "uploader-address-missing" etc. ^ I'm unable to get Lintian to show this message locally, so I'd also like to know which option is needed to display it.

Re: Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-24 Thread Chris Lamb
Gilles Filippini wrote: > > 1 # Lintian thinks uploader Adam Powell's name violates policy > > 2 med-fichier source: uploader-address-missing "Adam C. Powell > > 3 med-fichier source: uploader-not-full-name IV" > > > > Can you file a bug against Lintian please? > > Which lintian option does

Re: Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-24 Thread Gilles Filippini
Hi, Chris Lamb a écrit le 24/12/2018 à 18:40 : > 1 # Lintian thinks uploader Adam Powell's name violates policy > 2 med-fichier source: uploader-address-missing "Adam C. Powell > 3 med-fichier source: uploader-not-full-name IV" > > Can you file a bug against Lintian please? Which lintian option

Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-24 Thread Chris Lamb
Missing copyright for debian/*? -- Chris Lamb Mon, 24 Dec 2018 17:40:33 + -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Comments regarding med-fichier_4.0.0+repack-3~exp1_amd64.changes

2018-12-24 Thread Chris Lamb
1 # Lintian thinks uploader Adam Powell's name violates policy 2 med-fichier source: uploader-address-missing "Adam C. Powell 3 med-fichier source: uploader-not-full-name IV" Can you file a bug against Lintian please? -- Chris Lamb Mon, 24 Dec 2018 17:40:01 + --