Your message dated Sun, 23 Dec 2018 07:34:14 +0000 with message-id <[email protected]> and subject line Bug#916092: fixed in nullmailer 1:2.2-2 has caused the Debian Bug report #916092, regarding nullmailer: architecture specific test failures 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.) -- 916092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916092 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: nullmailer Version: 1:2.2-1 Severity: serious Tags: upstream Justification: ftbfs nullmailer 2.2 should not transition to testing until we figure out what is going on with the test Testing auth permanent failure with smtp which seems to fail or hang on various architectures (but not amd64). It seems possible replicate the hang on plummer (ppc64el porterbox). This is a bit puzzling because on the pps64el buildd it actually failed relatively quickly, rather than hanging until killed. The test is using some tcp sockets on localhost according to netstat, the connection is ESTABLISHED, but that's all I know at this point. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nullmailer depends on: ii debconf [debconf-2.0] 1.5.69 ii libc6 2.27-8 ii libgnutls30 3.5.19-1+b1 ii libstdc++6 8.2.0-9 ii lsb-base 10.2018112800 nullmailer recommends no packages. nullmailer suggests no packages. -- debconf information excluded
--- End Message ---
--- Begin Message ---Source: nullmailer Source-Version: 1:2.2-2 We believe that the bug you reported is fixed in the latest version of nullmailer, 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. David Bremner <[email protected]> (supplier of updated nullmailer 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: SHA256 Format: 1.8 Date: Sun, 23 Dec 2018 15:57:13 +0900 Source: nullmailer Binary: nullmailer Architecture: source Version: 1:2.2-2 Distribution: unstable Urgency: medium Maintainer: David Bremner <[email protected]> Changed-By: David Bremner <[email protected]> Description: nullmailer - simple relay-only mail transport agent Closes: 916092 Changes: nullmailer (1:2.2-2) unstable; urgency=medium . * Do not delete smtp-response from server process in tests (Closes: #916092) (hopefully). Checksums-Sha1: e4fa1ab27e59799f4b94d32a28704e8e7bb55dda 1785 nullmailer_2.2-2.dsc 99c6c46b50ab7da7e26566366b88362c220dddb2 27716 nullmailer_2.2-2.debian.tar.xz Checksums-Sha256: 3ba6acb140924e95df4aab41f59e96e656814e695c2827d0051d8c429a50cbd5 1785 nullmailer_2.2-2.dsc 4ba091750e69663adce7adb6e757564b1d5df0f5982f2d8fce2194288b8339a1 27716 nullmailer_2.2-2.debian.tar.xz Files: b3de33938d4b6af609a3b37579768357 1785 mail optional nullmailer_2.2-2.dsc 6d8d93b4a315a01d01f1564381306513 27716 mail optional nullmailer_2.2-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlwfNcMACgkQ8gKXHaSn niw34Av/Z8xJdWrAN3B1gwzvhtnUAh7NzbjV3QTHOeEqkhLMsgclm3lqBl5aHFjM lCBYe3h52cemj9gwR83tvblxBPPa/Mv02ADcjnLTOeVggT6w1muzGb8sDV8vIbuo +yJV2HzyEADNPeTunT4oE92aBNFTM2K2aq6br7ZNuA/y4MJA1Vuf4EWT1GWn/dun dndTLFZ8/B0u+ZeDWucWX301FJCNd8b73O7yLoa429fyJxTz4mjvfN+xxx+vQfra Hnyw3Mv74cCJVcsx6r4wbgh3LDcOPM4jP0iK8vPrxHhYGcz4pbDAZ6o8huDinzCu WLu0VZ0TcDEXDlyJe8ZQyv6yxW3+3DLgnAe/K7S+xdkLZSC32wYJWMQAooSNo+Sq JAHjTFMWbce39ZWFwDBoxUsBF5deSzbeWM6WUuUYZEji0/2cOqA9vKxUc4g/2cgD h7S9BssVokYKrYealkcgSUBUkdxBKo5AAkaxRX+8Df7cIMxGEFCR7joOLYd7nHTQ 8XLQEalJ =+f8O -----END PGP SIGNATURE-----
--- End Message ---
