Processed: reopening 884499

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 884499
Bug #884499 {Done: Chris Lamb } [lintian] lintian: Pedantic 
check for packages not using debhelper or CDBS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions lintian/2.5.85.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reopening 898091, closing 884499

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Reopen the correct bug
> reopen 898091
Bug #898091 {Done: Chris Lamb } [lintian] lintian: Alter the 
semantics (etc.) of --pedantic?
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions lintian/2.5.85.
> close 884499
Bug #884499 [lintian] lintian: Pedantic check for packages not using debhelper 
or CDBS
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884499
898091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#894870: lintian could ask maintainers to use dh_auto_*

[Chris Lamb]

Hi Helmut,

> No. I was pondering it on irc and it didn't seem immediately actionable
> to me. You wanted a bug report anyway and you got one.

(Sure, and that was appreciated so we didn't lose the idea and
context.)
 
> Is there really much point in discussing whether tool diversity is good?
> The case seems pretty clear to me.

Hm? I don't quite follow. Or rather, I'm quite sure of the relevance
here?


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#894870: lintian could ask maintainers to use dh_auto_*

[Helmut Grohne]

On Fri, May 04, 2018 at 07:54:46PM +0100, Chris Lamb wrote:
> How did you get on with this? :)

No. I was pondering it on irc and it didn't seem immediately actionable
to me. You wanted a bug report anyway and you got one.

Is there really much point in discussing whether tool diversity is good?
The case seems pretty clear to me.

Helmut

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Chris Lamb]

clone 884499 -1
retitle -1 lintian: Alter the semantics (etc.) of --pedantic?
severity -1 wishlist
tags -1 + moreinfo
thanks

Hi Russ 

> […]

At the very least lets not lose this conversation in a somewhat-
unrelated bug, hence cloning etc. Tagging as "moreinfo" for now.

> lintian --suggestions, maybe?

Well, I was trying to avoid the early bikeshedding on the name, more
trying to capture the different essence. :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: Re: Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 884499 -1
Bug #884499 {Done: Chris Lamb } [lintian] lintian: Pedantic 
check for packages not using debhelper or CDBS
Bug 884499 cloned as bug 898091
> retitle -1 lintian: Alter the semantics (etc.) of --pedantic?
Bug #898091 {Done: Chris Lamb } [lintian] lintian: Pedantic 
check for packages not using debhelper or CDBS
Changed Bug title to 'lintian: Alter the semantics (etc.) of --pedantic?' from 
'lintian: Pedantic check for packages not using debhelper or CDBS'.
> severity -1 wishlist
Bug #898091 {Done: Chris Lamb } [lintian] lintian: Alter the 
semantics (etc.) of --pedantic?
Ignoring request to change severity of Bug 898091 to the same value.
> tags -1 + moreinfo
Bug #898091 {Done: Chris Lamb } [lintian] lintian: Alter the 
semantics (etc.) of --pedantic?
Ignoring request to alter tags of bug #898091 to the same tags previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
884499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884499
898091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Russ Allbery]

Chris Lamb  writes:

> Y'know, I think we could make it even more effective if we renamed --
> pedantic at the same time. This would have the benefits of a)
> highlighting the change of semantics and b) we could perhaps choose a
> name that does not imply it is "just" another level of pickiness…
> Almost to the point of "lintian --give-me-possible-things-to-consider"

Yeah, I was cringing over the break in backward-compatibility in my
original proposal, so I think something like this plus a deprecation
warning on --pedantic while making it do nothing would be friendlier.

lintian --suggestions, maybe?

-- 
Russ Allbery (r...@debian.org)   

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Chris Lamb]

Hi Russ,

> My modest proposal, and this is going to sound nuts so bear with me for a
> moment, would be to make it impossible to get pedantic tags and regular
> tags at the same time.  If you use --pedantic, suppress all other tags.

Ooh, now that's an interesting concept. :) Let me run that over in my
mind for a few days..

Y'know, I think we could make it even more effective if we renamed --
pedantic at the same time. This would have the benefits of a)
highlighting the change of semantics and b) we could perhaps choose a
name that does not imply it is "just" another level of pickiness…
Almost to the point of "lintian --give-me-possible-things-to-consider"


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Scott Kitterman]

On May 7, 2018 1:26:36 AM UTC, Russ Allbery  wrote:
>Chris Lamb  writes:
>
>> However, my experience with being an author of a handful of static
>> analysis tools is that people have a slight tendency to delegate
>> thinking to the computer's output. The addition of an objective
>target
>> (ie. zero output) only encourages our post-lapsarian brains to make
>> poor, err, compromises.
>
>> Do correct me if I'm wrong, but I believe this is the angle Scott was
>> pushing. :)
>
>> How could we make --pedantic more useful/obvious/something? 
>Ironically,
>> if it were less useful in a strict sense — for example, if we moved
>some
>> P: tags to I: — it would get less incorrect usage. :p
>
>My modest proposal, and this is going to sound nuts so bear with me for
>a
>moment, would be to make it impossible to get pedantic tags and regular
>tags at the same time.  If you use --pedantic, suppress all other tags.
>
>This problem stems from the fact that people are using Lintian as if
>pickier is better, and the deeper they go into Lintian's settings while
>keeping the package clear of any output, the better the package is. 
>And
>that's true, up to a point -- moving from error to warning is certainly
>significant, and moving from warning to info is probably significant.
>
>But pedantic was a collection of tags that were mostly designed for a
>far
>different purpose: you run them on a package to ask for a set of things
>that might be out of step with common best practices or that you may
>want
>to consider changing if you've not touched the package in years.  It's
>much more of a one-time thing.  You run it, you look at the tags and
>read
>the descriptions (I would argue that --pedantic is basically useless
>without --info, and perhaps --pedantic should force --info,
>particularly
>if one implements my modest proposal), you decide which ones make sense
>and which ones don't, and then you fix the ones you like and move on
>with
>your life.
>
>Lintian has emitted pedantic warnings about some of my packages for not
>having an upstream changelog for literally years.  This is never going
>to
>be fixed; upstream is not going to make a changelog, and I'm not going
>to
>make an artificial one.  The correct disposition of that tag is for me
>to
>ignore it completely, *but it's still useful* for new packages when I'm
>doing initial packaging and may have forgotten to include the right
>debhelper command to copy over upstream's unconventionally-named
>changelog.
>
>If we *force* people to not treat --pedantic the same as other severity
>levels and *force* it to be a separate pass that you only run in
>specific
>situations, maybe this will finally get through to people, since
>arguing
>with people in debian-mentors that they're using Lintian wrong doesn't
>seem to be working.

I think this is an excellent idea.

Thanks,

Scott K

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Russ Allbery]

Chris Lamb  writes:

> However, my experience with being an author of a handful of static
> analysis tools is that people have a slight tendency to delegate
> thinking to the computer's output. The addition of an objective target
> (ie. zero output) only encourages our post-lapsarian brains to make
> poor, err, compromises.

> Do correct me if I'm wrong, but I believe this is the angle Scott was
> pushing. :)

> How could we make --pedantic more useful/obvious/something?  Ironically,
> if it were less useful in a strict sense — for example, if we moved some
> P: tags to I: — it would get less incorrect usage. :p

My modest proposal, and this is going to sound nuts so bear with me for a
moment, would be to make it impossible to get pedantic tags and regular
tags at the same time.  If you use --pedantic, suppress all other tags.

This problem stems from the fact that people are using Lintian as if
pickier is better, and the deeper they go into Lintian's settings while
keeping the package clear of any output, the better the package is.  And
that's true, up to a point -- moving from error to warning is certainly
significant, and moving from warning to info is probably significant.

But pedantic was a collection of tags that were mostly designed for a far
different purpose: you run them on a package to ask for a set of things
that might be out of step with common best practices or that you may want
to consider changing if you've not touched the package in years.  It's
much more of a one-time thing.  You run it, you look at the tags and read
the descriptions (I would argue that --pedantic is basically useless
without --info, and perhaps --pedantic should force --info, particularly
if one implements my modest proposal), you decide which ones make sense
and which ones don't, and then you fix the ones you like and move on with
your life.

Lintian has emitted pedantic warnings about some of my packages for not
having an upstream changelog for literally years.  This is never going to
be fixed; upstream is not going to make a changelog, and I'm not going to
make an artificial one.  The correct disposition of that tag is for me to
ignore it completely, *but it's still useful* for new packages when I'm
doing initial packaging and may have forgotten to include the right
debhelper command to copy over upstream's unconventionally-named
changelog.

If we *force* people to not treat --pedantic the same as other severity
levels and *force* it to be a separate pass that you only run in specific
situations, maybe this will finally get through to people, since arguing
with people in debian-mentors that they're using Lintian wrong doesn't
seem to be working.

-- 
Russ Allbery (r...@debian.org)   

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Chris Lamb]

Hi Russ & Scott,

> I'm not sure how one could possibly be more clear.  If one's definition of
> lintian-clean includes --pedantic, one's definition of lintian-clean is,
> well, wrong.

There is no doubt that you are absolutely right in a technical sense
and maintainers should not be using --pedantic in this way.

However, my experience with being an author of a handful of static
analysis tools is that people have a slight tendency to delegate
thinking to the computer's output. The addition of an objective
target (ie. zero output) only encourages our post-lapsarian brains to
make poor, err, compromises.

Do correct me if I'm wrong, but I believe this is the angle Scott was
pushing. :)

How could we make --pedantic more useful/obvious/something?
Ironically, if it were less useful in a strict sense — for example,
if we moved some P: tags to I: — it would get less incorrect usage. :p


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Russ Allbery]

Scott Kitterman  writes:

> Back in the debate about the python2 check (thanks for fixing), I made
> the point that not all lintian checks are created equal.  Some represent
> serious package defects that needs to be addressed and some merely
> reflect the lintian maintainer's opinion on what should be tracked and
> it's entirely up to the maintainer to decide if any action is needed.

> This is one of the latter.

Which is why it's pedantic, no?  Speaking as the person who merged
Raphael's patch to introduce pedantic, that's precisely what pedantic
*means*.

> I worry about this class of tag because some people view a lintian
> 'clean' package as an important goal when it's not universally.  One
> needs to look at what lintian is reporting and evaluate it.  Not
> everyone does a great job of that and so unintended consequences arise.

In the lintian man page:

Pedantic tags are Lintian at its most pickiest and include checks for
particular Debian packaging styles and checks that many people
disagree with.  Expect false positives and Lintian tags that you don't
consider useful if you use this option.

I'm not sure how one could possibly be more clear.  If one's definition of
lintian-clean includes --pedantic, one's definition of lintian-clean is,
well, wrong.

-- 
Russ Allbery (r...@debian.org)   

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Scott Kitterman]

On May 7, 2018 12:20:04 AM UTC, Chris Lamb  wrote:
>Hi Scott,
>
>> For what it's worth, this is an example of the kind of check that
>isn't 
>> supported by policy.
>
>I'm not quite following your chain of logic wrt to Lintian and Debian
>Policy. I mean, there are countless checks in Lintian that have no
>basis in Policy? :)
>
>(100% agree that there is no requirement whatsoever to use debhelper
>or CDBS and I have a great deal of sympatahy with you position on
>this tag. Indeed, I can quite possibly see myself removing this tag
>at a later date.)

Back in the debate about the python2 check (thanks for fixing), I made the 
point that not all lintian checks are created equal.  Some represent serious 
package defects that needs to be addressed and some merely reflect the lintian 
maintainer's opinion on what should be tracked and it's entirely up to the 
maintainer to decide if any action is needed.

This is one of the latter.  I worry about this class of tag because some people 
view a lintian 'clean' package as an important goal when it's not universally.  
One needs to look at what lintian is reporting and evaluate it.  Not everyone 
does a great job of that and so unintended consequences arise.

Scott K

Bug#884499: lintian: Pedantic check for packages not using debhelper or CDBS

[Chris Lamb]

Hi Scott,

> For what it's worth, this is an example of the kind of check that isn't 
> supported by policy.

I'm not quite following your chain of logic wrt to Lintian and Debian
Policy. I mean, there are countless checks in Lintian that have no
basis in Policy? :)

(100% agree that there is no requirement whatsoever to use debhelper
or CDBS and I have a great deal of sympatahy with you position on
this tag. Indeed, I can quite possibly see myself removing this tag
at a later date.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#898077: lintian: False positive in missing-build-dependency-for-dh-addon, python package

[Niels Thykier]

Chris Lamb:
> tags 898077 + pending
> thanks
> 
>> Lintian should perhaps check of there is a python package that meets the
>> dependency requirement? Or allow e.g. "*scour"?
> 
> We can't do a wildcard (!) but we can also check for
> python-scour. I've done this in Git, pending upload:
> 
>   
> https://salsa.debian.org/lintian/lintian/commit/fc69686ae2d6aff415762812e805af4e5e9ca627
> 
>   data/debhelper/dh_addons-manual | 1 +
>   debian/changelog| 4 
>   2 files changed, 5 insertions(+)
> 
> 
> Regards,
> 

Hi,

I am not entirely convinced this is a good idea.  As I understand it,
that dependency is a temporary measure to avoid breakage but the plan is
to remove the dependency (i.e. packages will be required to build-depend
directly on "scour" for the add-on).

I have taken the liberty of CC'ing Martin (maintainer of scour) to
clarify the situation.

Thanks,
~Niels

Bug#898077: lintian: False positive in missing-build-dependency-for-dh-addon, python package

[Chris Lamb]

tags 898077 + pending
thanks

> Lintian should perhaps check of there is a python package that meets the
> dependency requirement? Or allow e.g. "*scour"?

We can't do a wildcard (!) but we can also check for
python-scour. I've done this in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/fc69686ae2d6aff415762812e805af4e5e9ca627

  data/debhelper/dh_addons-manual | 1 +
  debian/changelog| 4 
  2 files changed, 5 insertions(+)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: Re: lintian: False positive in missing-build-dependency-for-dh-addon, python package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 898077 + pending
Bug #898077 [lintian] lintian: False positive in 
missing-build-dependency-for-dh-addon, python package
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
898077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#898077: lintian: False positive in missing-build-dependency-for-dh-addon, python package

[Ross Gammon]

Package: lintian
Version: 2.5.55
Severity: normal

Dear Maintainer,

When building laditools, the missing-build-dependency-for-dh-addon lintian
warning is received because scour is not a build dependency when the scour dh
addon is used in debian/rules.

However, python-scour is a build dependency and pulls in the scour package.

Lintian should perhaps check of there is a python package that meets the
dependency requirement? Or allow e.g. "*scour"?

Regards,

Ross



-- System Information:
Debian Release: stretch/sid
  APT prefers artful-updates
  APT policy: (500, 'artful-updates'), (500, 'artful-security'), (500, 
'artful'), (100, 'artful-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-39-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils  2.29.1-4ubuntu1
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1build1
ii  dpkg  1.18.24ubuntu1
ii  file  1:5.32-1
ii  gettext   0.19.8.1-4ubuntu1
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.33
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2build2
ii  libdpkg-perl  1.18.24ubuntu1
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1build3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-8ubuntu1.1
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2build1
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-8ubuntu1.1
ii  t1utils   1.40-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1build3

Versions of packages lintian suggests:
ii  binutils-multiarch 2.29.1-4ubuntu1
ii  dpkg-dev   1.18.24ubuntu1
ii  libhtml-parser-perl3.72-3build1
ii  libtext-template-perl  1.46-1

-- no debconf information