Package: dpkg-dev
Version: 1.17.6
Severity: wishlist

Hi! While maintaining the KDE/Qt stack I'm sometimes confronted with a problem
that I think we can solve here.

The point is that if a package ships multiple symbols files but dpkg-gensymbols
finds missing symbols in one of them it will not process the others. This means
that we only get the differences from the symbols files that got processed but
not the others, thus throwing away important information.

It would be very good if we could make dpkg-gensymbols to process all files and
failing after the last one if at least one of them contained a problem.

Currently the only thing we can do to take the most of a build is to not fail at
all, but that's not a good solution.

I would really love to provide a patch, but my perl skills are... :-/

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

Kernel: Linux 3.12.6+edid (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dpkg-dev depends on:
ii  base-files    7.2
ii  binutils      2.24-3
ii  bzip2         1.0.6-5
ii  libdpkg-perl  1.17.6
ii  make          3.81-8.3
ii  patch         2.7.1-4
ii  xz-utils      5.1.1alpha+20120614-2

Versions of packages dpkg-dev recommends:
ii  build-essential          11.6
ii  clang-3.3 [c-compiler]   1:3.3-16
ii  fakeroot                 1.20-3
ii  gcc [c-compiler]         4:4.8.2-2
ii  gcc-4.4 [c-compiler]     4.4.7-7
ii  gcc-4.6 [c-compiler]     4.6.4-5
ii  gcc-4.7 [c-compiler]     4.7.3-10
ii  gcc-4.8 [c-compiler]     4.8.2-14
ii  gnupg                    1.4.16-1
ii  gnupg2                   2.0.22-3
ii  gpgv                     1.4.16-1
ii  libalgorithm-merge-perl  0.08-2

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2013.12.13

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to