#1144739 RFS: doctest/2.5.3-1 -- Light and feature-rich C++ testing framework

#1144739#5
Date:
2026-08-18 12:55:41 UTC
From:
To:
Dear mentors,

I am looking for a sponsor for my package "doctest":

* Package name : doctest
Version : 2.5.3-1
Upstream contact : https://github.com/doctest/doctest/issues
* URL : https://github.com/doctest/doctest
* License : CC-BY-4.0, Expat
* Vcs : https://salsa.debian.org/debian/doctest
Section : devel

The source builds the following binary packages:

doctest-dev - Light and feature-rich C++ testing framework

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/doctest/

Alternatively, you can download the package with 'dget' using this command:

dget -x
https://mentors.debian.net/debian/pool/main/d/doctest/doctest_2.5.3-1.dsc

Changes since the last upload:

doctest (2.5.3-1) unstable; urgency=medium
.
* New upstream version 2.5.3.
* Update 2002_pkgconfig_arch_ind.patch for latest changes.

Regards,

Syed Shahrukh Hussain.

#1144739#10
Date:
2026-08-20 01:30:51 UTC
From:
To:
Hi Syed,

Please address this Lintian output on your next upload:

Running lintian...
N:
P: doctest-dev: example-unusual-interpreter /usr/bin/python [usr/share/doc/doctest-dev/examples/range_based_execution.py]
N:
N:   This package contains an example script for an interpreter that is not
N:   shipped in the package and is not known to Lintian. It is possible that
N:   there is a typo or the interpreter is not executable.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: scripts
N:
N:
P: doctest source: package-uses-old-debhelper-compat-version 13
N:
N:   This package uses a debhelper compatibility level that is no longer
N:   recommended. Please consider using the recommended level.
N:
N:   For most packages, the best way to set the compatibility level is to
N:   specify debhelper-compat (= X) as a Build-Depends in debian/control. You
N:   can also use the debian/compat file or export DH_COMPAT in debian/rules.
N:
N:   If no level is selected debhelper defaults to level 1, which is
N:   deprecated.
N:
N:   Please refer to the debhelper(7) manual page for details.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debhelper
N:
N:
P: doctest source: redundant-priority-optional-field [debian/control:4]
N:
N:   This package currently sets the Priority field in the debian/control file
N:   to "optional".
N:
N:   As of dpkg version 1.22.13, this field is set to "optional" by default. As
N:   such, in this case the Priority field is redundant and should be removed.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/control/field/priority
N:
N:
P: doctest source: redundant-rules-requires-root-no-field [debian/control:13]
N:
N:   This package currently sets the Rules-Requires-Root field in the
N:   debian/control file to "no".
N:
N:   As of dpkg version 1.22.13, this field is set to "no" by default. As such,
N:   in this case the Rules-Requires-Root field is redundant and should be
N:   removed.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/control/field/rules-requires-root
N:
N:
X: doctest source: debian-watch-does-not-check-openpgp-signature [debian/watch]
N:
N:   This watch file does not specify a means to verify the upstream tarball
N:   using a cryptographic signature.
N:
N:   If upstream distributions provides such signatures, please use the
N:   pgpsigurlmangle options in this watch file's opts= to generate the URL of
N:   an upstream OpenPGP signature. This signature is automatically downloaded
N:   and verified against a keyring stored in debian/upstream/signing-key.asc
N:
N:   Of course, not all upstreams provide such signatures but you could request
N:   them as a way of verifying that no third party has modified the code after
N:   its release (projects such as phpmyadmin, unrealircd, and proftpd have
N:   suffered from this kind of attack).
N:
N:   Please refer to the uscan(1) manual page for details.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/watch
N:   Renamed from: debian-watch-does-not-check-gpg-signature
N:   debian-watch-may-check-gpg-signature
N:   This tag is experimental.
N:
N:
X: doctest source: very-long-line-length-in-source-file 522 > 512 [doc/markdown/assertions.md:124]
N:
N:   The source file includes a line length that is well beyond the normally
N:   human made code line length.
N:
N:   This very long line length does not allow Lintian to do correctly some
N:   source file checks.
N:
N:   This line could also be the result of some text injected by a computer
N:   program, and thus could lead to FTBFS bugs.
N:
N:   Last but not least, long line in source code could be used to obfuscate
N:   the source code and to hide stuff like backdoors or security problems.
N:
N:   It could be due to jslint source comments or other build tool comments.
N:
N:   You may report this issue upstream.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: files/contents/line-length
N:   Renamed from: insane-line-length-in-source-file
N:   This tag is experimental.
N:
N:   Screen: autotools/long-lines
N:     Advocates: "Russ Allbery" <rra@debian.org>
N:     Reason:
N:             Upstream sources using autoconf have traditionally been
N:             distributed with generated ./configure scripts as well as
N:             other third-party m4 macro files such as libtool.
N:
N:             When paired with automake, there may also be some intermediate
N:             Makefile.in files.
N:
N:             A lot of sources potentially contain such files, but they are
N:             not actionable by either the Debian distributor or by the
N:             upstream maintainer.
N:
N:             As a side note, modern Debian build protocols will re-create
N:             many of those files via dh_autoreconf. They are present merely
N:             to aid in bootstrapping systems where the GNU suite may not yet
N:             be available.
N:
N:             Read more in Bug#996740.
N:
N:
X: doctest source: very-long-line-length-in-source-file 554 > 512 [CONTRIBUTING.md:95]
N:
X: doctest source: very-long-line-length-in-source-file 573 > 512 [debian/patches/2001_privacy_breach.patch:24]
N:
X: doctest source: very-long-line-length-in-source-file 675 > 512 [doc/markdown/configuration.md:71]
N:
X: doctest source: very-long-line-length-in-source-file 712 > 512 [doc/markdown/tutorial.md:87]
N:
X: doctest source: very-long-line-length-in-source-file 757 > 512 [scripts/data/article2.txt:115]
N:
X: doctest source: very-long-line-length-in-source-file 784 > 512 [README.md:71]
N:
X: doctest source: very-long-line-length-in-source-file 825 > 512 [doc/markdown/stringification.md:90]
N:
X: doctest source: very-long-line-length-in-source-file 890 > 512 [doc/markdown/faq.md:93]

I: Lintian run successful (worst tag: pedantic)

Otherwise, enjoy:

$ dput ftp-master ../doctest_2.5.3-1_source.changes
Uploading doctest using ftp to ftp-master (host: ftp.upload.debian.org; directory: /pub/UploadQueue/)
running allowed-distribution: check whether a local profile permits uploads to the target distribution
running protected-distribution: warn before uploading to distributions where a special policy applies
running checksum: verify checksums before uploading
running suite-mismatch: check the target distribution for common errors
running gpg: check GnuPG signatures before the upload
Uploading doctest_2.5.3-1.dsc
Uploading doctest_2.5.3.orig.tar.gz
Uploading doctest_2.5.3-1.debian.tar.xz
Uploading doctest_2.5.3-1_source.buildinfo
Uploading doctest_2.5.3-1_source.changes

I also gave you DM rights for next time, since this is your third upload to this package and you maintain it:

$ dcut -k 5C7ABEA20F8630459CC8C8B5E27F2CF8458C2FA4 ftp-master dm --uid 9637124373C13019BE114BCCEB62B1057DE7A8B1 --allow doctest
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
Picking DM Syed Shahrukh Hussain <syed.shahrukh@ossrevival.org> with fingerprint 9637124373C13019BE114BCCEB62B1057DE7A8B1
Uploading tsimonq2-1787189378.dak-commands to ftp-master

Best regards,
Simon Quigley
tsimonq2@debian.org

#1144739#11
Date:
2026-08-20 11:07:59 UTC
From:
To:

Thank you for providing DM rights :-).

Sure, I will try to fix these in next release.


Kind Regards,

Syed Shahrukh Hussain.