Your message dated Tue, 19 May 2026 11:33:37 +0000
with message-id <[email protected]>
and subject line Bug#301011: fixed in developers-reference 14.9
has caused the Debian Bug report #301011,
regarding more verbose instructions on new upstream package
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.)
--
301011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301011
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: developers-reference
Version: 3.3.5
Severity: wishlist
Please include Brian Nelson recommendations for things to be done on new
upstream package
<http://lists.debian.org/debian-mentors/2004/12/msg00310.html>:
First of all, I'll assume you've skimmed over the source as part of your
initial packaging. I usually go through the following steps:
1. Read the upstream changelog, NEWS, and whatever other documentation
they may have released with the new version.
2. Do a 'diff -urN' between the old and new upstream sources to try to
get a feel for the scope of the changes, where work is actively being
done (and thus where new bugs may appear), and also keep an eye out
for anything suspicious.
3. Port the old Debian packaging to the new version. This basically
involves applying the diff.gz from the old package to the new one and
incrementing the debian/changelog. Tools like uupdate help automate
this for you. Personally I keep all of my packages in a subversion
repository and thus do an svn merge.
4. If the patch/merge did not apply cleanly, inspect the situation to
determine what failed (clues are left in .rej files). Most often the
problem is that a patch you applied to the source was integrated
upstream, and thus the patch is no longer relevant.
5. If any changes were made to the build system (hopefully you'd know
from steps 1 and 2) and update the debian/rules and debian/control
build dependencies if necessary.
6. Build the new package. Personally I always build in a pbuilder
chroot since I use some 3rd party packages on my system and I don't
want those interfering.
7. Verify that the new package builds correctly.
8. Run lintian to catch any obvious policy violations.
9. Run 'debdiff old-package.change new-package.change'. Verify that no
files have been unintentionally misplaced or removed, and no other
inadvertent changes were made.
10. Verify the contents with 'debc new-package.changes'. Ensure no files
are zero-length that should not be.
11. Install the new package. Verify it installs/upgrades correctly.
Verify that it works normally. If the package makes use of
non-trivial pre/post/inst/rm scipts, be sure to test the upgrade
paths of those.
12. Check to see if any bugs have been fixed that are currently open in
the BTS. If they have been, close them in the debian/changelog.
13. Check the sanity of the diff.gz file. Run 'interdiff -z
old-package.diff.gz new-package.diff.gz' and verify any
modifications changes are intentional and no junk files have crept
in.
14. Check the contents of the .changes file to make sure you are
uploading to the correct distribution, the proper bugs closures are
listed in the Closes: field, the Maintainer: and Changed-By: fields
match, the file is GPG-signed, etc.
15. If any changes were made to correct anything in the packaging along
the way, repeat steps 6-13 until satisfied. If your upload needs to
be sponsored, be sure to note any special options required when
building the package (like 'dpkg-buildpackage -sa -v ...') and be
sure to inform your sponsor so he or she builds it correctly.
Regards,
ogi
--- End Message ---
--- Begin Message ---
Source: developers-reference
Source-Version: 14.9
Done: Holger Levsen <[email protected]>
We believe that the bug you reported is fixed in the latest version of
developers-reference, 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.
Holger Levsen <[email protected]> (supplier of updated developers-reference
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: Tue, 19 May 2026 13:23:33 +0200
Source: developers-reference
Architecture: source
Version: 14.9
Distribution: unstable
Urgency: medium
Maintainer: Developers Reference Maintainers <[email protected]>
Changed-By: Holger Levsen <[email protected]>
Closes: 301011 1062983
Changes:
developers-reference (14.9) unstable; urgency=medium
.
[ Serafeim (Serafi) Zanikolas ]
* pkgs: add a section with a checklist for new upstream versions.
Closes: #301011.
* conf.py: set paper size to A4. Closes: #1062983.
.
[ Holger Levsen ]
* Update all .po files for changed strings in the English original.
Checksums-Sha1:
889a09d2e3224b58e8f4d3632a7030e88d7038f2 2522 developers-reference_14.9.dsc
d54810e562622193a7b1d68e32350738c70a093d 582684
developers-reference_14.9.tar.xz
92569cb9fc3d93568db299904681f814b48657b4 8614
developers-reference_14.9_source.buildinfo
Checksums-Sha256:
64da2abef0ef15b636339bb8024485729e5d155ceeafa05b0d73e5b4cd0dcbeb 2522
developers-reference_14.9.dsc
a3c6b01247be737e712410f0cb9b693814bb00cf69f938df283bf75d9d193123 582684
developers-reference_14.9.tar.xz
cf6013748d4dc5b10ebafa3d9f729979e5bee839c3ecec5bdba547a7933d56ce 8614
developers-reference_14.9_source.buildinfo
Files:
978e4dce0381a23c4873aa8a51e6044f 2522 doc optional
developers-reference_14.9.dsc
38f1f16cf41fd4eb1119b955b4a68751 582684 doc optional
developers-reference_14.9.tar.xz
bc1629b0f01260941b730ea6f1cbae78 8614 doc optional
developers-reference_14.9_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmoMSIYACgkQCRq4Vgaa
qhzh9Q/8CIC0xWQ46XIuKx0N0wMggY+MzmkX7OJG334BB6myBR27jK7eYljxjDwn
+WvDKb1Lo1ymX0KmgHzoqxQDqlCWRI8kS3ZNZTKZpNXIqfjRpBHk8xLsaFvUJCU7
+axtGqlkteEX4PxVvy5NJwK0/zCqTd2xKpq2VuaxYB/KsT2FQVApWUJ3GFZiDabI
B1aP3qPQ0Ph5WUEPMyZrpMZW2GauBV4zTKI6WBla58PzTB+ujD9xfXev1QampT/2
YC1f1vU+myDQbsSqVhTj0rfkHOp/TLx0JC2BgGDufohWPv0uE0lx/QGKTmmrcbh6
FqQp1F9OpTIiW6HvAGXTCJ9axJ2BFV27CS6IXaVxn1Dw+e7/Fkrwmh24A6p+uIwO
R6zG8UaV58lElhIgWAYIr/aUGid/MVCsg8+y9KvBijRInPBKA+IZvDF506aWKP7i
P0D7VNrlAmRwJVfWTFL0f7IfLd7Oyv4REbW9C6uTZA2lmL4XVtk9DX9f9/GDKST6
fgpofteuAp+Bl2bF/KdMTj9B/WnTMNMlc2WNMqurPfiDEVPItFH/AnCeDsEWpnWo
HA7AWzYPQrH/jEzNUcp+8suSuQo7pkH/wBI8nXYMHqgZFgEMRqm6q6t9bH4HuGoQ
W/Fyc54KgvPzZjTkR99vKOY3bn/a5gLjmBxX0rIBZPYsaQeihsw=
=YqWq
-----END PGP SIGNATURE-----
pgpjM4mVyf4io.pgp
Description: PGP signature
--- End Message ---
