Your message dated Sat, 29 Mar 2025 06:08:28 -0000 with message-id <20250329060828.4b57a758@debian.org> and subject line Re: Bug#1092179: RFS: boost-ext-ut/2.1.1-1 [ITP] -- C++ single header/module, macro-free unit testing framework has caused the Debian Bug report #1092179, regarding RFS: boost-ext-ut/2.3.0-1 [ITP] -- C++ single header/module, macro-free unit testing framework 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 owner@bugs.debian.org immediately.) -- 1092179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092179 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: RFS: boost-ext-ut/2.1.1-1 [ITP] -- C++ single header/module, macro-free unit testing framework
- From: Raul Tambre <raul@tambre.ee>
- Date: Sun, 05 Jan 2025 20:22:14 +0200
- Message-id: <08187dcf1e67bab02190a6d291af09a76134fb65.camel@tambre.ee>
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "boost-ext-ut": * Package name : boost-ext-ut Version : 2.1.1-1 Upstream contact : Kris Jusiak <kris@jusiak.net> * URL : https://boost-ext.github.io/ut/ * License : BSL-1.0, MIT * Vcs : https://salsa.debian.org/tambre/boost-ext-ut Section : libdevel The source builds the following binary packages: libboost-ext-ut-dev - C++ single header/module, macro-free unit testing framework To access further information about this package, please visit the following URL: https://mentors.debian.net/package/boost-ext-ut/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/b/boost-ext-ut/boost-ext-ut_2.1.1-1.dsc Changes for the initial release: boost-ext-ut (2.1.1-1) unstable; urgency=medium . * Initial release (Closes: #1092173). Regards, Raul Tambre
--- End Message ---
--- Begin Message ---
- To: Raul Tambre <raul@tambre.ee>
- Cc: 1092179-done@bugs.debian.org
- Subject: Re: Bug#1092179: RFS: boost-ext-ut/2.1.1-1 [ITP] -- C++ single header/module, macro-free unit testing framework
- From: Jeroen Ploemen <jcfp@debian.org>
- Date: Sat, 29 Mar 2025 06:08:28 -0000
- Message-id: <20250329060828.4b57a758@debian.org>
- In-reply-to: <[🔎] 5685646697aff11f587daa078a5f8ac384ed5689.camel@tambre.ee>
- References: <08187dcf1e67bab02190a6d291af09a76134fb65.camel@tambre.ee> <08187dcf1e67bab02190a6d291af09a76134fb65.camel@tambre.ee> <[🔎] 20250325143530.5e1e2ea7@debian.org> <[🔎] 5685646697aff11f587daa078a5f8ac384ed5689.camel@tambre.ee>
On Fri, 28 Mar 2025 14:27:20 +0200 Raul Tambre <raul@tambre.ee> wrote: > Boost μt was one such package [2] and it has been my C++ testing > library of choice for years now. It's the simplest of the ones I've > been maintaining by myself locally and as such I picked it as first > one to upstream into Debian. I recently sponsored a package that uses μt for its testsuite (glaze, still sitting in NEW queue today), so it's certainly a welcome addition. > But should I check anything besides the `nocheck` profile in > debian/rules for enabling Valgrind? If it's only available on > certain systems, and that's the reason for `valgrind-if-available` > existing, then it'd sound like enabling it unconditionally might > fail for some ports or such. I didn't find any documentation on > this at a first glance. I think upstream test code handles a scenario with the memcheck enabled but valgrind missing just fine, so this should be good as-is. Uploaded!Attachment: pgplwLJuGdAlS.pgp
Description: OpenPGP digital signature
--- End Message ---