Your message dated Wed, 24 Jul 2024 02:24:21 +0000 with message-id <E1sWRfx-007V2T-PK@fasolo.debian.org> and subject line Bug#973393: fixed in dh-elpa 2.1.3 has caused the Debian Bug report #973393, regarding truncate less of the backtrace during failing ert tests 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.) -- 973393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973393 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: truncate less of the backtrace during failing ert tests
- From: Nicholas D Steeves <nsteeves@gmail.com>
- Date: Thu, 29 Oct 2020 15:42:01 -0400
- Message-id: <160400052106.22776.5182226858080309327.reportbug@DigitalMercury.dynalias.net>
Package: dh-elpa Version: 2.0.4 Severity: normal Hey team, Thomas Koch added a nice workaround for truncated backtraces at: https://wiki.debian.org/Teams/DebianEmacsenTeam/Tips that workaround is d/elpa-test: ert_eval = (setq ert-batch-backtrace-right-margin 500) and I wonder if it should be activated by default, in the spirit of Policy §4.9 "The package build should be as verbose as reasonably possible". Speaking for myself, I would find it helpful, especially for the rare corner cases where only noninteractive --batch ert tests will trigger a failure. Also, I've been asked for untruncated backtraces by various upstreams. The only potential issue I can think of is that the reproducible and DebCI build logs will have then have long lines, but I feel like the benefit outweighs this consideration. A possible, though not ideal, solution to this potential issue might be to word-wrap the backtrace, but that functionality should probably be enabled in upstream Emacs. Let's consider setting `ert-batch-backtrace-right-margin` to a large value in the meantime. Regards, Nicholas
--- End Message ---
--- Begin Message ---
- To: 973393-close@bugs.debian.org
- Subject: Bug#973393: fixed in dh-elpa 2.1.3
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Wed, 24 Jul 2024 02:24:21 +0000
- Message-id: <E1sWRfx-007V2T-PK@fasolo.debian.org>
- Reply-to: Sean Whitton <spwhitton@spwhitton.name>
Source: dh-elpa Source-Version: 2.1.3 Done: Sean Whitton <spwhitton@spwhitton.name> We believe that the bug you reported is fixed in the latest version of dh-elpa, 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 973393@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sean Whitton <spwhitton@spwhitton.name> (supplier of updated dh-elpa 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 24 Jul 2024 11:20:49 +0900 Source: dh-elpa Architecture: source Version: 2.1.3 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team <debian-emacsen@lists.debian.org> Changed-By: Sean Whitton <spwhitton@spwhitton.name> Closes: 973393 1069210 1069326 Changes: dh-elpa (2.1.3) unstable; urgency=low . * Upload to unstable. * Fix some copyright years. * Make autoscripts/prerm-elpa executable. . dh-elpa (2.1.2) experimental; urgency=medium . [ Xiyue Deng ] * Set ert-batch-backtrace-right-margin to nil to allow full backtrace when ERT tests fail (Closes: #973393). * Add support for passing ERT selectors using ert_selectors. * Handle git version with date in dhelpa-sanitise-version. * dh_elpa_test: Don't rename files under test/, tests/ (Closes: #1069326). * Use `pretty' stack frame style in buttercup for full back trace. * Add support for installing nested directories (Closes: #1069210) - Don't recursively add to elpa path, to match package.el - Byte-compile recursively during install - Recursively create the symlinks from elpa-src->elpa. . [ Aymeric Agon-Rambosson ] * Get Package-Requires with lm-header-multiline (some upstream maintainers specify one dependency per line). * Add transient to the list of packages packaged separately as well as provided with Emacs. . dh-elpa (2.1.1) experimental; urgency=medium . * Remove /usr/share/$flavor/site-lisp/elpa (from emacsen-remove) if it is empty . dh-elpa (2.1.0) experimental; urgency=medium . * Call emacsen-remove script directly from generated prerm. For now this requires a custom debhelper autoscript template, that this package installs. * Eliminate dependency on dh-elpa-helper for emacsen-remove. This will require a rebuild to fix emacsen-remove scripts, but seems mandated by policy. * Add a version to debhelper generated snippets. * Make install helper shellcheck clean Checksums-Sha1: 7ad38b9e8a6c423c2965c5c6e553bfbe9b6302f8 1914 dh-elpa_2.1.3.dsc 67470842fc526897f7d0403770200e9274cfec37 27540 dh-elpa_2.1.3.tar.xz Checksums-Sha256: 12f2b82c55a81ed84a8702eec9d83070fac364c3d2a8ea032215b515c18cbf20 1914 dh-elpa_2.1.3.dsc 1a5e8a43f44374f641a76aeec9107bc37ba746d59c5c46950febc276e3f83656 27540 dh-elpa_2.1.3.tar.xz Files: 4c3040a0d40ef66c8d77c88213861cb6 1914 devel optional dh-elpa_2.1.3.dsc f8685b4e2f2c7f61019b79957b72093c 27540 devel optional dh-elpa_2.1.3.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmagZSYACgkQaVt65L8G YkAsaA/7BVW/PyPfF/hIbaPvJlaGWdyVXav2d3WiBiiFnoD3AmoTnau7oZtrNMEg 4+1U7TNJxo3OIJiKc5CM5foHgG+0Dg2nRjf8adlpUQBeUFiNZnjXa3Ce7pfKmhYc Rp/KKZL9sl6cr9tu1rbKai7UHlX0dMhKQZ3QuI5zOVtwbwFtUh3UKwigXDSfnIHJ zX+JTDgrU+7Yv/NAsu/PwaxlRLDqVqZM2zA0QOmTNLm9eKwgKI1PHi1lfiKfu+q3 GVGwobWIYsak+uhIY2BUf55Not5R2jcYpLtbCbHN5G5lxE7dC0XyQDwnVFGcL+u0 fPl2e+B5loSK78i9PXl0GnqKydBskHgSwRR4FytCvboBw0tER8BXNLEHWTV20RJP 0mrx0XRayyvjD07IOAsTNZPirMcKLwDx0f+K2jHWBpn7Q3Cp9sJL8pVpUjZ1ZzI3 J96bncdFpMhr12c/cW7V3Ealhip/sFwSQ8Im+cyu6zxK6TuAL1OKPT2JDUFSrjeO MFDKbvpQEJcmduIZIhwh/DvRNYVMWgvBjgi+T7Zut9QNl9uBXM72rXPKIGL8slYm 2PmWKO5m+g1itjNsNHmVYePY8EUli0UitPNhjuOnOsop24TS+HUjdD3unI6gFe+F 1umiiSAhIs54PnaiXJQb3mW1W0qujzoJEZ2JVUnrIsneeWALn2I= =gqrw -----END PGP SIGNATURE-----Attachment: pgptcbwWPZMew.pgp
Description: PGP signature
--- End Message ---