Package: sbuild Version: 0.66.0-2 Severity: normal sbuild by default assigns the user building the package as the Maintainer listed in the changes files. That is, sbuild ignores the Maintainer: field in debian/control.
This means a natural use of sbuild to build a team-maintained package results in the team (the Maintainer listed in debian/control) being ignored. This does not strike me as optimal. sbuild does provide the -m --maintainer flag to work around this problem. But wouldn't it be more natural for sbuild to use the field in debian/control by default? For a more nuanced logic, you could perhaps use the debian/control Maintainer field only if the user performing the build is listed in the Uploaders field. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sbuild depends on: ii adduser 3.113+nmu3 ii apt-utils 1.0.10.2 ii libsbuild-perl 0.66.0-2 ii perl 5.20.2-6 Versions of packages sbuild recommends: ii debootstrap 1.0.72 ii fakeroot 1.20.2-1 Versions of packages sbuild suggests: ii deborphan 1.7.28.8-0.2 ii wget 1.16.3-3 -- no debconf information
