Hi,
today I've seen the first time this new lintian warning:
mailing-list-obsolete-in-debian-infrastructure Debian Med Packaging Team
I wonder whether we could this set from severity Warning to Pedandic.
The point is that this address works not only as maintainer but rather
as key in severa
package: lintian
version: 2.67.0
x-debbugs-cc: Debian Med Project List , Debian
Developers , Debian Lintian Maintainers
, reproducible-bui...@lists.alioth.debian.org
On Fri, Apr 24, 2020 at 09:56:24AM +0200, Andreas Tille wrote:
> today I've seen the first time this new lintian warning:
>
>
Andreas,
> I wonder whether we could this set from severity Warning to Pedandic.
This was already done in:
https://salsa.debian.org/lintian/lintian/commit/fd8ee67d96c713698f4c5e08eea0b0dafe02bdf4
> […] So if you insist that this should be at severity warning I'll
> probably rather add a lint
tags 958666 + pending
thanks
Holger Levsen wrote:
> definitly, yes, filing this bug now.
As mentioned elsewhere, this was already fixed yesterday in fd8ee67d.
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
On Fri, Apr 24, 2020 at 10:22:22AM +0100, Chris Lamb wrote:
> > definitly, yes, filing this bug now.
> As mentioned elsewhere, this was already fixed yesterday in fd8ee67d.
ah, cool! & thanks for the quick fix!
--
cheers,
Holger
-
On Fri, 24 Apr 2020 10:22:22 +0100, Chris Lamb wrote:
> Holger Levsen wrote:
> > definitly, yes, filing this bug now.
> As mentioned elsewhere, this was already fixed yesterday in fd8ee67d.
Thank you, a lowered severity is of course better.
But to be honest, it doesn't change a lot if I'm seein
On Fri, Apr 24, 2020 at 11:46:47AM +0200, gregor herrmann wrote:
> On Fri, 24 Apr 2020 10:22:22 +0100, Chris Lamb wrote:
> Thank you, a lowered severity is of course better.
>
>
> But to be honest, it doesn't change a lot if I'm seeing
>
> "W: $package source: mailing-list-obsolete-in-debian-inf
Hi Chris.
On Fri, Apr 24, 2020 at 09:55:52AM +0100, Chris Lamb wrote:
> Andreas,
>
> > I wonder whether we could this set from severity Warning to Pedandic.
>
> This was already done in:
>
>
> https://salsa.debian.org/lintian/lintian/commit/fd8ee67d96c713698f4c5e08eea0b0dafe02bdf4
Not reall
Hi Andreas,
On Fri, Apr 24, 2020 at 5:57 AM Andreas Tille wrote:
>
> I've written lots of mails to upstreams just to learn
> that I'm mostly ignored.
You are facing the dilemma of #907727, except a change would also
negatively impact your users.
Lintian may in the future automatically reduce th
Hi,
I have packaged the new upstream version of jebl2 and made various changes.
Now the packaging is in Salsa [1], could someone please check and upload it
when time permits?
The changes are
* New upstream version 0.1+git20190308
* Deleting now useless patch source_8.patch
* Bumping Standar
[replacing lintian-ma...@debian.org → 958...@bugs.debian.org]
Andreas Tille wrote:
> > This was already done in:
[…]
> Not really (as Gregor pointed out since Info is also on the radar).
I've just marked the tag as "experimental". This has the same
practical effect of it being removed.
> To giv
Hi,
On Fri, Apr 24, 2020 at 10:24 AM Chris Lamb wrote:
>
> in order to spare this boilerplate within the Med team.
Wouldn't it be better to lower the severity for scripts shipped by
upstream (vs the maintainer)?
Kind regards
Felix Lechner
> > https://github.com/nf-core/nanoseq/blob/master/bin/scrape_software_versions.py
> > guppy
> Missing in Debian. Is it this project
>https://staff.aist.go.jp/yutaka.ueno/guppy/ ?
Hi, Andreas,
No, it seems that guppy is a base caller provided by Oxford Nanopore
technologies.
```
$ pwd
/home
Hi Pierre,
thanks a lot for your work. I usually would leave the commit ID inside
the version number (so 0.1+git20190308.a98448e) since this would silence
the new upstream available check - but I guess you thought about this
and left it as is when uploaded.
Work on Java packages is extremely wel
Hi Andreas,
Le 24/04/2020 à 22:34, Andreas Tille a écrit :
> Hi Pierre,
>
> thanks a lot for your work. I usually would leave the commit ID inside
> the version number (so 0.1+git20190308.a98448e) since this would silence
> the new upstream available check - but I guess you thought about this
>
Hi Pierre,
On Fri, Apr 24, 2020 at 11:17:40PM +0200, Pierre Gruet wrote:
>
> Thanks for the review and the upload. I must admit I had not thought about
> the new upstream message that would remain... I only considered keeping the
> meaningful, ``understandable'' part of the version number. I will
> Andreas Tille wrote:
>
> > I admit I *personally* *really* hate this since I think I perfectly
> > subscribe all those good reasons to not add language extensions.
Le Fri, Apr 24, 2020 at 06:13:45PM +0100, Chris Lamb a écrit :
>
> I share your dislike. Please file a separate wishlist bug for
Hi Charles,
On Sat, Apr 25, 2020 at 07:40:59AM +0900, Charles Plessy wrote:
>
> The goal of this policy was to make it easier to rewrite a program from
> one language to another language while keeping a compatible interface.
> We now have more than 15 years of experience on that matter with
> sci
Package: lintian
Version: 2.67.0
Severity: wishlist
Hi,
as suggested by Chris Lamb I hereby asking for either ignoring or
setting severity to either experimental or pedantic for certain teams
for the issue
script-with-language-extension
This should happen for the teams
Debian Med Packag
19 matches
Mail list logo
