[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1087869: marked as done (rocm-hipamd: autopkgtest regression due to new CMake deprecation warning)

Your message dated Thu, 17 Apr 2025 18:50:05 +0000
with message-id <E1u5UJJ-0023u2-Ay@fasolo.debian.org>
and subject line Bug#1087869: fixed in rocm-hipamd 5.7.1-5.1
has caused the Debian Bug report #1087869,
regarding rocm-hipamd: autopkgtest regression due to new CMake deprecation warning
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.)


-- 
1087869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087869
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: rocm-hipamd
Version: 5.7.1-5
Severity: serious
User: cmake@packages.debian.org
Usertags: cmake-3.31

Dear maintainer,

your package has an autopkgtest regression with CMake 3.31. CMake has
deprecated backwards compatibility for versions earlier than 3.10,
which causes cmake_minimum_required() and/or cmake_policy() to emit a
warning on stderr, thereby causing your autopkgtest to fail. The
tests should be unaffected otherwise.

To avoid this warning from cmake_minimum_required() you have two
options:

1. Bump the minimum required version to at least 3.10. For reference,
the CMake version in oldstable is 3.18 and in oldoldstable is 3.13.

2. Add a maximum version with the ... operator. For example, instead
of cmake_minimum_required(VERSION 3.7) use
cmake_minimum_required(VERSION 3.7...3.31).

In either case, please verify that the requested policy profile is
compatible with your package. This is very likely the case you have a
non-trivial autopkgtest which passes after the change.

--- End Message ---
--- Begin Message --- 
Source: rocm-hipamd
Source-Version: 5.7.1-5.1
Done: Paul Gevers <elbrus@debian.org>

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

Debian distribution maintenance software
pp.
Paul Gevers <elbrus@debian.org> (supplier of updated rocm-hipamd 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: Sat, 12 Apr 2025 12:51:52 +0200
Source: rocm-hipamd
Architecture: source
Version: 5.7.1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian ROCm Team <debian-ai@lists.debian.org>
Changed-By: Paul Gevers <elbrus@debian.org>
Closes: 1087869
Changes:
 rocm-hipamd (5.7.1-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * tests: allow deprecation warnings via allow-stderr restriction
     (Closes: #1087869)
Checksums-Sha1:
 74cf33f39e1ea3d73c30c90897ff588f4e6779b8 3213 rocm-hipamd_5.7.1-5.1.dsc
 aaf7efe92a8a062cfd5ff2145905d7d489407eba 24412 rocm-hipamd_5.7.1-5.1.debian.tar.xz
Checksums-Sha256:
 ad3e32ad43bde4d71c58bbe0f7e588efd2412fd990dbde4be9bb868289ad8c06 3213 rocm-hipamd_5.7.1-5.1.dsc
 26d2137f17277df475ebb494b840222cc51d1c2014f65ef929a79e2d0524300e 24412 rocm-hipamd_5.7.1-5.1.debian.tar.xz
Files:
 3cc39a6f4f6c76179c48ceb903f3a8f9 3213 devel optional rocm-hipamd_5.7.1-5.1.dsc
 2af9ce61ba80e57a377f071c16b7e587 24412 devel optional rocm-hipamd_5.7.1-5.1.debian.tar.xz

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

iQEzBAEBCgAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmf6rhcACgkQnFyZ6wW9
dQppkQgAnSDMP7mneskz+QlOzsmfiy6iWkzV2Yf8tGXjwN9VnW0Cr6mXhIH8KcGy
vFGAaCoWNZMGAyAJaIJdqjiM+cIoxrA5pPXCveREYbFFFQC2DOK9on/CEQxNI/In
3w6N/s+OSzNbC5LUvZyEdW7umbhOkxuObW/hMRwjw927xuccns0kGhPIVI+wzveQ
Z5xwVIQRAooiffnQbjEeWDiZmrp0KTkF5Qq1aETofqo2gxyhY1Ah8YZwJW7wCjH4
Jokl02uC1++AVdNDUi9hfeNedvkWG8QpGUW/if/IzuuPwSjE07bSrerZ4ZIqWmBf
DfipwgP2jUO9QdR9e0xnI/WjN+fcUQ==
=+mPB
-----END PGP SIGNATURE-----

Attachment: pgp60AEpDbma0.pgp
Description: PGP signature


--- End Message ---
Reply to: