Your message dated Thu, 09 Aug 2018 14:38:35 +0000
with message-id <[email protected]>
and subject line Bug#905167: fixed in debmake-doc 1.11-1
has caused the Debian Bug report #905167,
regarding debmake-doc: Handling Upstream Autotools Packaging on Debian
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 [email protected]
immediately.)
--
905167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905167
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debmake-doc
Version: 1.9-1
Tags: patch
Section 5.16.1 recommends running autoreconf when building a package
on Debian GNU/Linux, to improve portability to new systems. That
brings with it considerations about automake. The default
"strictness" level of an automake setup is the "gnu" level, which
requires files AUTHORS, ChangeLog, INSTALL, NEWS, and README along
with the Makefile.am and configure.ac files that autoreconf will
expect. That then brings other implications for using such a package
on Debian.
Elsewhere, the document refers to the GNU Coding Standards, which is
further reason to make mention of the above files, and which get
installed and which do not get installed (COPYING and INSTALL) on
Debian.
I propose that wording like what follows be considered for the end of
Section 8.9 or 8.11. Both of those examples set the automake
strictness level to "foreign", which is good for a simple example but
leaves out some details that could help someone new with Debian
packaging.
I tried to capture the major considerations for packages that follow
GNU standards, and think something along these lines would help:
[begin insert]
The line AM_INIT_AUTOMAKE([foreign]) in configure.ac above tells
automake to use a "foreign" strictness level, which has loose
requirements for what files are in a package. The default strictness
level for automake is "gnu", which expects the following files in the
top-level directory: AUTHORS, INSTALL, NEWS, README, ChangeLog, and
either COPYING (with a copy of a GPL license) or COPYING.LESSER (with
a copy of a LGPL license). If you are building such a package,
Section 5.16.1 [Autotools] of this guide recommends invoking autoreconf
in debian/rules to provide better support for porting to new architectures,
compared to just running "./configure && make". If you intend to run
autoreconf on a package with automake set to a strictness level of "gnu",
automake will complain if the files it expects in the top-level directory
are not present. In this case the INSTALL and COPYING (or COPYING.LESSER)
files must be present in the source directory. However, they are not
installed on Debian systems because Debian uses its own package manager
for installation, and keeps copies of common licenses in
/usr/share/common-licenses.
The other files besides Makefile.am and configure.ac that Autotools
expects in the top-level directory (AUTHORS, NEWS, README, and
ChangeLog) can be installed in /usr/share/doc/<package>. This
can be done by listing those files in debian/doc. If you keep any
Autotools-generated files in the Debian package, make sure that
those files have their copyright and license information captured
in the debian/copyright file. Their copyright notices and license
terms differ slightly, so you will have to check every one. The
GNU Project standard practice is to leave all such files in place
if a "make distclean" leaves them, so asking upstream to remove
them is probably not the correct solution.
Running "autoreconf -ivf" as described in Section 5.16.1 will create
a new INSTALL file even if one existed. That file will have a copyright,
as will the GPL or LGPL in the COPYING or COPYING.LESSER file. Therefore,
list those files in the Files-Exclude field in the first paragraph of
debian/copyright. Also list any files that "autoreconf -ivf" creates
but that remain following a "make distclean" in the Files-Exclude field,
because autoreconf will recreate those files. Some maintainer discretion
is allowed to leave a config.h file that should not change, etc.
Apart from those files, the only other files that must exist with the
"gnu" automake strictness level to run autoreconf in the top-level
directory are Makefile.am and configure.ac.
One of the standard "make" targets that automake creates is "distcheck".
That builds a copy of the package in a staging directory by defining
the DESTDIR variable, then creates a distribution tar file of the package
from the newly-built copy, and finally tries building from that tar file
a second time along with running various checks on the final result (see
the GNU Automake manual for further details). It is advisable if you are
using GNU Autotools to ensure that "make distcheck" succeeds on the upstream
package before attempting to create a debianized version. If the upstream
package fails a "make distcheck" with Autotools, it will probably have
issues on Debian.
[end insert]
Thanks,
Paul Hardy
--- End Message ---
--- Begin Message ---
Source: debmake-doc
Source-Version: 1.11-1
We believe that the bug you reported is fixed in the latest version of
debmake-doc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Osamu Aoki <[email protected]> (supplier of updated debmake-doc package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 09 Aug 2018 22:52:24 +0900
Source: debmake-doc
Binary: debmake-doc
Architecture: source all
Version: 1.11-1
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki <[email protected]>
Changed-By: Osamu Aoki <[email protected]>
Description:
debmake-doc - Guide for Debian Maintainers
Closes: 903804 905167
Changes:
debmake-doc (1.11-1) unstable; urgency=medium
.
* Fix debian/control grammar error. Closes: #903804
* Update contents in line with the Buster environment such as
*-debsym, *.build, and *.buildinfo. Closes: #905167
* Improve README.source and manpage content.
* Now updating po files leave previous msgid contents.
Checksums-Sha1:
20945658adc046a7e643fd7ec25bacf90819cfda 2451 debmake-doc_1.11-1.dsc
05a5eaf77948c7188cf963c13bc3308cdb9828b4 311092 debmake-doc_1.11.orig.tar.xz
23f075f45af4d711f5b9b40868fd1bdd19f4db11 4356 debmake-doc_1.11-1.debian.tar.xz
2e45be164e0752ddbe31d2c72907d972d6a67d1f 4910628 debmake-doc_1.11-1_all.deb
e70f3c9da2c8999aa538fcb1263b8230d249cbd6 17219
debmake-doc_1.11-1_amd64.buildinfo
Checksums-Sha256:
f148e3cbbf00c2bfc80cbc682882f3366952fde744ec591669f9c1baeff10ee9 2451
debmake-doc_1.11-1.dsc
ed4aa7d65cce833aa0f7f56259a2a5ac27bc5428a3f3da32833e92dc37546d41 311092
debmake-doc_1.11.orig.tar.xz
9871bf8e60626f132b8403d9baa36fbf0260329afad55d330c744572056c9c65 4356
debmake-doc_1.11-1.debian.tar.xz
4e73e22000270e56ec0387e1b25b631587e0a29d1d0a6f86864540106c45b8b5 4910628
debmake-doc_1.11-1_all.deb
55b0373b7b45da0fc93963528e540201a1b28b61d0729f95110cfc5500334d59 17219
debmake-doc_1.11-1_amd64.buildinfo
Files:
05eaa2c65d89de917c87e718dc328779 2451 doc optional debmake-doc_1.11-1.dsc
657e30de99016f99602593b7c0ed0f50 311092 doc optional
debmake-doc_1.11.orig.tar.xz
e241aa9a0d1b1143d1cea6942445ace7 4356 doc optional
debmake-doc_1.11-1.debian.tar.xz
162402dab4103aaf6a32d0c96ff643fd 4910628 doc optional
debmake-doc_1.11-1_all.deb
ea397633916c2cdcefd4489814496fce 17219 doc optional
debmake-doc_1.11-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEMTNyTWIHiBV56V1iHhNWiB3Y15EFAltsSUAACgkQHhNWiB3Y
15E1/A/8C5bPxIMEoUy0qDry/5PbD6zi1mgO3uU0guevpVWvicUxZMwr/fbq9Yj0
UMs3F3jRyB8zDkTQGvabz9QaOHXAqV5z71RAvbEIAKfAWMftnajHTs1SSsg7Va81
K21eDfxe4QTIqAOky9kLRW9E23gNYpLpDop/IOsUFNVt80vIylOaya4GvrCAWThR
RzEU5Pau7e+ExYoJiTiIdhA3PSbzbHdwEynKNjEFXBPl/uNbN6pNq2LwRby4KHuq
Q2n9NL6qI1ZKmadFCmn0EV3vAy3qL2bu4ARlJrWtVNTuS63jUPjT+rKJVE7qoCEV
O66JB+HQQQoDy6Afgd4fY6dMx7CCLx5FrtesRWYvZh+9ZZFqBdKaoov7h8hgd15a
LJM1bXYvX9ADX55stTU3BP2NcEncqQgysJ/Zwl2TzTHYHjlU6/4Zz5kPPqHPXDlR
1L4F3uJ8gtWikjsyxDkV4/4fMSwtdBQpxCkqfrGI9k7AySMxdnursgnL2trtUKpc
0yKMjtScSeNhCWvW39j40YlHHpdcM2j+3ArE+6y7WKQVABH7Noi9NPOZxlq0hs7M
XTe3rtGZiGNsynkX5qAbu7nBr3cy5PNx6+OIGfMQhsdae9SqLIwjf/Ol0Pb4kqgD
JqD7tv+91EyFHogXsACb9Ez4NFxaQ4duMoxiSF6Etv3kmyvRtmE=
=9t9X
-----END PGP SIGNATURE-----
--- End Message ---