[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#904573: marked as done (qa.debian.org: lintian.d.o reports spurious errors)

Your message dated Wed, 13 Feb 2019 15:14:33 +0100
with message-id <20190213141433.whcaaxqn6nwyb4ev@bogus>
and subject line Re: qa.debian.org: lintian.d.o reports spurious errors
has caused the Debian Bug report #904573,
regarding qa.debian.org: lintian.d.o reports spurious errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
904573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904573
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: important

Dear QA team,

lintian.debian.org reports a source-is-missing error against a package I
co-maintain, nyx [0]. However, Lintian does not report the issue on my
development machine, and the file in question does not exist in the source
tarball.

Would it be possible for someone to check out why lintian.d.o reports
spurious errors?  This severely limits its usefulness.  :(

For information, here are some information about my lintian version and
how I checked the error was indeed spurious :

> $ apt-cache policy lintian
> lintian:
>   Installed: 2.5.93
>   Candidate: 2.5.93
>   Version table:
>  *** 2.5.93 990
>         990 http://localhost:3142/debian buster/main amd64 Packages
>         500 http://localhost:3142/debian sid/main amd64 Packages
>         100 /var/lib/dpkg/status
> 
> $ lintian -iI --show-overrides /opt/deb/buildarea/nyx_2.0.4-5.dsc 
> I: nyx source: testsuite-autopkgtest-missing
> N: 
> N:    This package does not declare a test suite. Having a test suite helps
> N:    with automated QA in response to changes in the archive. For example, if
> N:    your package has a test suite, it is possible to re-execute that test
> N:    suite when any of the package dependencies has a new version and check
> N:    whether that update caused problems for your package.
> N:    
> N:    To declare a test suite, please add a debian/tests/control file to your
> N:    package.
> N:    
> N:    For more information on how to add functional tests to your package,
> N:    browse to https://ci.debian.net/doc/.
> N:    
> N:    Severity: wishlist, Certainty: certain
> N:    
> N:    Check: testsuite, Type: source
> N: 
> 
> $ tar -tf /opt/deb/buildarea/nyx_2.0.4.orig.tar.gz | grep -F min.js
> [No result]


Best,

  nicoo

[0]: https://lintian.debian.org/maintainer/dererk@debian.org.html#nyx

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Hi Chris,

On Wed, Jul 25, 2018 at 10:45:32AM +0100, Chris Lamb wrote:
> Thanks for filing this. Whilst qa.debian.org might be "technically"
> correct, it's easier to track them under src:lintian.. or at least this
> is where we go looking for them. :)

OK, now I know  :)


> Anyway, I cannot reproduce this issue:
>
>   $ apt-get source nyx                         
>   [...]

I ended up narrowing it down to having had a different orig tarball than what
was in the archive, because of a tooling messup between dererk@ and I
(I had setup uscan/mk-origtargz things to excise the binary files, but it
 seems it wasn't working in dererk's workflow and he shot first.)

So, qa.d.o was right after all  :)


Best,

  nicoo

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: