Your message dated Wed, 23 Sep 2020 19:35:24 +0000
with message-id <e1klay0-000j5w...@fasolo.debian.org>
and subject line Bug#970334: fixed in wslay 1.1.1-2
has caused the Debian Bug report #970334,
regarding wslay: autopkgtest needs update for new version of cmake: warning on 
stderr
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 ow...@bugs.debian.org
immediately.)


-- 
970334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wslay
Version: 1.1.1-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, cm...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:cmake

Dear maintainer(s),

With a recent upload of cmake the autopkgtest of wslay fails in testing
when that autopkgtest is run with the binary packages of cmake from
unstable. It passes when run with only packages from testing. In tabular
form:

                       pass            fail
cmake                  from testing    3.18.2-1
wslay                  from testing    1.1.1-1
all others             from testing    from testing

I copied some of the output at the bottom of this report. The output
contains a warning that's written to stderr. By default that fails a
test. If you can't fix the underlying cause, you can have the output to
stderr ignored by adding an allow-stderr restriction to the test
specification.

Currently this regression is blocking the migration of cmake to testing
[1]. Of course, cmake shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in cmake was
intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from cmake should really add a
versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=cmake
        
https://ci.debian.net/data/autopkgtest/testing/amd64/w/wslay/7008132/log.gz

autopkgtest [18:08:26]: test build1:  - - - - - - - - - - results - - -
- - - - - - -
build1               FAIL stderr: CMake Warning (dev) at
/usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273
(message):
autopkgtest [18:08:26]: test build1:  - - - - - - - - - - stderr - - - -
- - - - - -
CMake Warning (dev) at
/usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273
(message):
  The package name passed to `find_package_handle_standard_args` (NETTLE)
  does not match the name of the calling package (Nettle).  This can lead to
  problems in calling code that expects `find_package` result variables
  (e.g., `_FOUND`) to follow a certain pattern.
Call Stack (most recent call first):
  FindNettle.cmake:15 (find_package_handle_standard_args)
  CMakeLists.txt:10 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: wslay
Source-Version: 1.1.1-2
Done: Anton Gladky <gl...@debian.org>

We believe that the bug you reported is fixed in the latest version of
wslay, 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 970...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky <gl...@debian.org> (supplier of updated wslay 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 23 Sep 2020 21:22:49 +0200
Source: wslay
Architecture: source
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Anton Gladky <gl...@debian.org>
Changed-By: Anton Gladky <gl...@debian.org>
Closes: 970334
Changes:
 wslay (1.1.1-2) unstable; urgency=medium
 .
   [ Chris Hofstaedtler ]
   * [9429e45] Avoid CMake casing warnings (Closes: #970334)
 .
   [ Anton Gladky ]
   * [6f1c0ef] Refresh patches
Checksums-Sha1:
 23d3abec58f4d257fc778f0b06f419b089464dcd 2082 wslay_1.1.1-2.dsc
 cf95605f99795a9ec915c4e8b532f8549843c205 5296 wslay_1.1.1-2.debian.tar.xz
 2cdc7adee7ac644131545bf601bcc89bbd568a25 6722 wslay_1.1.1-2_source.buildinfo
Checksums-Sha256:
 7670dcb101b9beca229eb8ed863613ce996baacbd0adf954218df3557092bf48 2082 
wslay_1.1.1-2.dsc
 2ab9f253c9f9891f5d2af3485062ceef5585e9221d1db0d0f60f4bbfd9499ff5 5296 
wslay_1.1.1-2.debian.tar.xz
 a4dd64e5a7534e5f8f9a60799065836269339d2d409a2cf1c3afef694a9f5a16 6722 
wslay_1.1.1-2_source.buildinfo
Files:
 25306e799d1db878075e57b306c43b3f 2082 libs optional wslay_1.1.1-2.dsc
 be30392c1c1b500f00fe1416f1159b3a 5296 libs optional wslay_1.1.1-2.debian.tar.xz
 83a9a328d346c9f2c8f2c47f552f3599 6722 libs optional 
wslay_1.1.1-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl9roJwACgkQ0+Fzg8+n
/wbiMw//WTx3HkusVQdD8Do1AIBjnP9DR++nRFxHjMSEVk5S7vrcxRH+5ZL5Aqqb
kwLR/xknKuL++CAyU0AZgDmbhzJYJNhQo8kMRPzdGkdtb52qLVx1TN6EFXEZrWOY
QckwDzdD+bKbd02Z3Q0abKU+C4dJe2GzOdrjEpXl1CjOBO6C7NGV4Vdh7StVSU3k
a32TwtwAUruMYH3m4wnm2Pg5A/sUrEZJVEaAfxHvQz11qRdZSQdSZTF60Fp1DE8F
CQPvIioc8lFv6AwkVDrBhzOH3sVsw1ZwL5yQDIE0ZnBPX7IutKf275jgE61lSrmK
yCsM6LR9o1zPU0zNHn5cmyO6TUMOuJl1ceDAmrAKmw4d9ysrg8yEuNI9ZJOYrVy6
sLdIhtmqLWgJIUZgGn06lKO//auUtP6cPIt25uMSes9ocz4UsWQGqQFVNI+zzfKl
bmdm5949sK0BNmj/XmNarrjMsRphLogjRlpMBYic0xwrneojrBSL58OHMdsiaQMI
UY1V2FAggz+DV33NB93Jo9LGljb4OvRgzXhYwtUZyf/3OaVMxA2vilcb9/oBoIFK
lfbYeA5/IbaO+yH5R+x8YbwVPLItV23vuY23mh4ugYwlZeW9cnYxlmTjrSbtB+IW
dA65QxKArwkjAGrjGhY6DJd0CddN+CqMbsVtYaFnh3nIakMRZ0w=
=SNZL
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to