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

Bug#956357: marked as done (lintian: fpos: package-has-a-duplicate-build-relation)

Your message dated Sun, 14 Jun 2020 18:39:32 -0700
with message-id <CAFHYt55gWLHYH8mjWDeyPgO-SJgj2MvH+WVr0myqNxUPYOtWjw@mail.gmail.com>
and subject line Re: Bug#956357: lintian: fpos: package-has-a-duplicate-build-relation
has caused the Debian Bug report #956357,
regarding lintian: fpos: package-has-a-duplicate-build-relation
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.)


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

% head -n 30 debian/control
Source: libxml2
Priority: optional
Section: libs
Maintainer: Debian XML/SGML Group <debian-xml-sgml-pkgs@lists.alioth.debian.org>
Uploaders:
 Aron Xu <aron@debian.org>,
 YunQiang Su <wzssyqa@gmail.com>,
Build-Depends:
 debhelper-compat (= 12),
Build-Depends-Indep:
 pkg-config,
Build-Depends-Arch:
 dh-python <!nopython>,
 libicu-dev,
 liblzma-dev,
 libpython-all-dbg <!nopython>,
 libpython-all-dev <!nopython>,
 libpython3-all-dbg <!nopython>,
 libpython3-all-dev <!nopython>,
 pkg-config,
 python-all-dbg:any <!nopython>,
 python-all-dev:any (>= 2.7.5-5~) <!nopython>,
 python3-all-dbg:any <!nopython>,
 python3-all-dev:any (>= 3.5) <!nopython>,
 rename,
 zlib1g-dev | libz-dev,
Standards-Version: 4.5.0
Rules-Requires-Root: no
Homepage: http://xmlsoft.org
Vcs-Git: https://salsa.debian.org/xml-sgml-team/libxml2.git
%

that yields:

W: libxml2 source: package-has-a-duplicate-build-relation pkg-config, pkg-config
N:
N:    The package declares the given build relations on the same package in
N:    either Build-Depends or Build-Depends-Indep, but the build relations
N:    imply each other and are therefore redundant.
N:
N:    Severity: warning
N:
N:    Check: fields/package-relations
N:


that's not true: pkg-configs is in both B-D-I and B-D-A, but one doesn't
imply the other.

(note that this version of libxml2 is not uploaded anywhere yet.)

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
More about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Hi Mattia,

On Fri, Apr 10, 2020 at 1:27 AM Mattia Rizzolo <mattia@debian.org> wrote:
>
> (note that this version of libxml2 is not uploaded anywhere yet.)

The version you wrote about may have been uploaded on the day you
filed this report. libxml2 version 2.9.10+dfsg-5 appeared in the
archive on April 10. It showed the following (partial) package
relations in d/control:

Build-Depends-Indep:
 pkg-config,
Build-Depends-Arch:
 pkg-config,

> W: libxml2 source: package-has-a-duplicate-build-relation pkg-config, pkg-config

The tag did not appear when I used Lintian's development version:

% ./frontend/lintian
/mirror/debian/pool/main/libx/libxml2/libxml2_2.9.10+dfsg-5.dsc
I: libxml2 source: debian-watch-uses-insecure-uri
ftp://xmlsoft.org/libxml2/libxml2-(\d[\d\.]+)@ARCHIVE_EXT@
P: libxml2 source: package-uses-old-debhelper-compat-version 12
N: python3-all-dev is in B-D-A, the failure to call py3support in the
other target doesn't bother me, nor bothers the build.
O: libxml2 source:
debian-rules-uses-supported-python-versions-without-python-all-build-depends
py3versions -s (line 14)

The bug is no longer reproducible. Closing.

Please reopen if your bug was closed in error.

Kind regards
Felix Lechner

--- End Message ---
Reply to: