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

Bug#740202: marked as done (lintian: doesnt detect invalid arch in "Build-Depends: foo, foo [blub]")

Your message dated Mon, 07 Jan 2019 08:34:35 +0100
with message-id <154684647510.9520.11263424630296867264@hoothoot>
and subject line Re: lintian: doesnt detect invalid arch in "Build-Depends: foo, foo [blub]"
has caused the Debian Bug report #740202,
regarding lintian: doesnt detect invalid arch in "Build-Depends: foo, foo [blub]"
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.)


-- 
740202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740202
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.5.22
Severity: normal

Hi,

as suggested by Niels Thykier on IRC I'm reporting the following issue:

Given the line:

	Build-Depends: foo, foo [blub]

lintian will not detect the invalid arch "blub". Though it does find it
if the line says:

	Build-Depends: foo [blub], foo

I found this while trying to create a patch for build profiles. The
following would not produce an error (but should):

	Build-Depends: foo, foo <blubber>

It seems the relevant code in checks/fields.pm is not run.

cheers, josch

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

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lintian depends on:
ii  binutils                       2.24-3
ii  bzip2                          1.0.6-5
ii  diffstat                       1.57-1
ii  file                           1:5.14-2
ii  gettext                        0.18.3.1-2
ii  hardening-includes             2.4
ii  intltool-debian                0.35.0+20060710.1
ii  libapt-pkg-perl                0.1.29+b1
ii  libarchive-zip-perl            1.30-7
ii  libclass-accessor-perl         0.34-1
ii  libclone-perl                  0.35-1
ii  libdpkg-perl                   1.17.7
ii  libemail-valid-perl            1.192-1
ii  libfile-basedir-perl           0.03-1
ii  libipc-run-perl                0.92-1
ii  liblist-moreutils-perl         0.33-1+b2
ii  libparse-debianchangelog-perl  1.2.0-1
ii  libtext-levenshtein-perl       0.06~01-2
ii  libtimedate-perl               2.3000-1
ii  liburi-perl                    1.60-1
ii  man-db                         2.6.5-2
ii  patchutils                     0.3.2-3
ii  perl [libdigest-sha-perl]      5.18.2-2
ii  t1utils                        1.37-2

Versions of packages lintian recommends:
ii  libautodie-perl                 2.21-1
ii  libperlio-gzip-perl             0.18-1+b3
ii  perl-modules [libautodie-perl]  5.18.2-2

Versions of packages lintian suggests:
pn  binutils-multiarch     <none>
ii  dpkg-dev               1.17.7
ii  libhtml-parser-perl    3.71-1+b1
ii  libtext-template-perl  1.46-1
ii  libyaml-perl           0.84-1
ii  xz-utils               5.1.1alpha+20120614-2

--- End Message ---
--- Begin Message --- 
Quoting Chris Lamb (2018-12-28 18:23:25)
> >       Build-Depends: foo, foo [blub]
> > 
> > lintian will not detect the invalid arch "blub"
> 
> I believe this was addressed (via your prompting) in dpkg some time ago:
> 
>   https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=d3d4348c31418fd2a392e148a880dce7db283d20
> 
> For example:
> 
>     dpkg-source: warning: can't parse dependency [invalid]
>     dpkg-source: error: error occurred while parsing Build-Depends
>     dpkg-buildpackage: error: dpkg-source --before-build . subprocess returned exit status 255
>     
> Given the time elapsed since the fix (which is in >= stretch via 1.18.5),
> I don't think it's worth adding such a test to Lintian anymore.

Agreed!

Attachment: signature.asc
Description: signature


--- End Message ---
Reply to: