Your message dated Fri, 23 May 2025 20:34:27 +0000
with message-id <e1uiz63-00dekk...@fasolo.debian.org>
and subject line Bug#1103731: fixed in devicexlib 0.8.6-2
has caused the Debian Bug report #1103731,
regarding libdevicexlib-dev fails to coinstall due to conflicting 
/usr/include/*.mod
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.)


-- 
1103731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdevicexlib-dev
Version: 0.8.5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict

libdevicexlib-dev fails to coinstall despite explicitly declaring that 
capability via Multi-Arch: same. The following files have content that 
varies with each architecture:
 - /usr/include/cublas_core_m.mod
 - /usr/include/cublas_m.mod
 - /usr/include/devxlib.mod
 - /usr/include/devxlib_cublas.mod
 - /usr/include/devxlib_linalg.mod
 - /usr/include/devxlib_rocblas.mod
 - /usr/include/nvtx.mod
 - /usr/include/rocblas_m.mod

One way to solve this would be moving them to
/usr/include/${DEB_HOST_MULTIARCH}. However, due to the trixie freeze 
and since development packages rarely need to be M-A:same, I recommend 
dropping M-A:same at least for trixie and optionally revisiting a better 
solution for forky.

Helmut

--- End Message ---
--- Begin Message ---
Source: devicexlib
Source-Version: 0.8.6-2
Done: Santiago Vila <sanv...@debian.org>

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

Debian distribution maintenance software
pp.
Santiago Vila <sanv...@debian.org> (supplier of updated devicexlib 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: Fri, 23 May 2025 21:55:00 +0200
Source: devicexlib
Architecture: source
Version: 0.8.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team <debichem-de...@lists.alioth.debian.org>
Changed-By: Santiago Vila <sanv...@debian.org>
Closes: 1044973 1103731
Changes:
 devicexlib (0.8.6-2) unstable; urgency=medium
 .
   * Team upload.
   [ Adrian Bunk ]
   * libdevicexlib-dev: Drop Multi-Arch: same. Closes: #1103731.
   [ Santiago Vila ]
   * Fix clean target. Closes: #1044973.
Checksums-Sha1:
 d17fc3a8e2349b0db6d248329983ec4faeb4a446 1676 devicexlib_0.8.6-2.dsc
 3a9ff91f80e2cf6d7b88877cd6f1503e5e6d3f0f 3472 devicexlib_0.8.6-2.debian.tar.xz
 1fae9a17b4b7851f965221693cd53e6b1129fc30 5359 
devicexlib_0.8.6-2_source.buildinfo
Checksums-Sha256:
 6fa7ecc33882b104cf358e4db3a1a240cda500bcbe2aa27ef17826319061a479 1676 
devicexlib_0.8.6-2.dsc
 08e57ec8dee5ae0a4dd8c17980bb005ec072b0731d67e3712ed8b2ca8f5fbcf5 3472 
devicexlib_0.8.6-2.debian.tar.xz
 dbb803f4b0161aba7a3ad301ee5f566644c47fc007b3e3c047806571a3e649d5 5359 
devicexlib_0.8.6-2_source.buildinfo
Files:
 396f304ff98e94b22f6ddc6e416e4c90 1676 science optional devicexlib_0.8.6-2.dsc
 8d5e41f9ed3ffb654c15446eb2a15420 3472 science optional 
devicexlib_0.8.6-2.debian.tar.xz
 77e552f5e620422abd10cc3dbac1a8e0 5359 science optional 
devicexlib_0.8.6-2_source.buildinfo

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

iQEzBAEBCgAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAmgw1bEACgkQQc5/C58b
izIBlgf+MCuAUPma44CfwG42AWNLrR5MO4gr0BKICyp6Eo3u/eThrrPl8iBf8YGB
yU53NFrbdbf43bfKbeVEqOV3fdHIE/Y1FQPNyDdX6hurA9g0Vz5VdJI4zadU7bzo
fqAOypg1sZrKMwpItI8XoCvyMW+0qq9sGn2X5UGjNL4OVJ/i6jqnHB3CWKAPgtDr
0rzPvTEHKBu+vgUmYFsZYgKF9Wak5XqrVXIUEwt+WQDSdGXdERZ5u5OxH/AcZtiI
zEPtKJMw1DbJ9WiAi43yUrQhwJ1IW147lil+S12vgn7zauciCbOBZTKmQSAmmSjs
JmbjlCsw8tfm+668VBdUH3j6n81ASg==
=NcWw
-----END PGP SIGNATURE-----

Attachment: pgpLVWP6BiTIj.pgp
Description: PGP signature


--- End Message ---

Reply via email to