Your message dated Thu, 27 Jun 2024 12:20:55 +0000
with message-id <e1smo7t-00gssf...@fasolo.debian.org>
and subject line Bug#1073050: fixed in rdma-core 52.0-2
has caused the Debian Bug report #1073050,
regarding rdma-core: Fails to build on several architectures: dh_install 
missing files
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.)


-- 
1073050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rdma-core
Version: 52.0-1
Severity: serious
Tags: ftbfs

rdma-core is failing to build on multiple architectures including the
release architectures armel and armhf.

Build logs
------------
https://buildd.debian.org/status/package.php?p=rdma-core

Build log excerpt
----------------------
dh_install: warning: ibverbs-providers missing files: usr/lib/*/libhns.so.*
dh_install: warning: libibverbs-dev missing files:
usr/include/infiniband/hnsdv.h
dh_install: warning: libibverbs-dev missing files: usr/lib/*/libhns.a
dh_install: warning: libibverbs-dev missing files: usr/lib/*/libhns.so
dh_install: warning: libibverbs-dev missing files: usr/lib/*/pkgconfig/libhns.pc
dh_install: warning: libibverbs-dev missing files: usr/share/man/man3/hnsdv_*.3
dh_install: warning: libibverbs-dev missing files: usr/share/man/man7/hnsdv.7

Thank you,
Jeremy Bícha

--- End Message ---
--- Begin Message ---
Source: rdma-core
Source-Version: 52.0-2
Done: Benjamin Drung <bdr...@ubuntu.com>

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

Debian distribution maintenance software
pp.
Benjamin Drung <bdr...@ubuntu.com> (supplier of updated rdma-core 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: Thu, 27 Jun 2024 13:49:34 +0200
Source: rdma-core
Built-For-Profiles: noudeb
Architecture: source
Version: 52.0-2
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung <bdr...@ubuntu.com>
Changed-By: Benjamin Drung <bdr...@ubuntu.com>
Closes: 1073050
Changes:
 rdma-core (52.0-2) unstable; urgency=medium
 .
   * Exclude hns provider on archs without coherent DMA (Closes: #1073050)
Checksums-Sha1:
 a5df48097b801cd665c67f703d7b918800797a79 3201 rdma-core_52.0-2.dsc
 20e8d5408226bff8e1e83052a4fa29238be77660 24268 rdma-core_52.0-2.debian.tar.xz
 e02373f683d6d79c531b8ef973a3137cf5d57f85 9266 rdma-core_52.0-2_source.buildinfo
Checksums-Sha256:
 50f8f58712bbfbd5be42a4edfa4c4f3a1aa274eebf56e513a1d8a7e8fc8c3902 3201 
rdma-core_52.0-2.dsc
 6e06ac02aab7586a841bc9e1fc4c2d0bf38f5e0f15cdefca50f5a95129f6280d 24268 
rdma-core_52.0-2.debian.tar.xz
 f7c8615237c6c12641b92a0f372b43bda53e650a8b733c6617f3fb362a2d9665 9266 
rdma-core_52.0-2_source.buildinfo
Files:
 ec87ce38e9ca246e87ffbb04c064f693 3201 net optional rdma-core_52.0-2.dsc
 cfccbf7c71acaa5df87040fca569cb38 24268 net optional 
rdma-core_52.0-2.debian.tar.xz
 0166a108c0146484c31618125d66d88d 9266 net optional 
rdma-core_52.0-2_source.buildinfo

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

iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmZ9VX4ACgkQFZ61xO/I
d0xNgw//Z6U4xdsQeYr2LPe6w/SsV83u9KnLr/0B9PgVYqwuMw+fYVQ2veeqGS0O
x887pccWQeuxlE6BnqyOnzHBCNKbMSfc08zbwOA4B3fJhPO+zo9cQZzGjEGtDduW
jvA82zr44jt6u5FLgDJzFdWwxqqWXS/rbIK/b3fPO3hCqlxAus9+pYqkyEk946jA
XQhuBIGs1BPPGiva4AT0kU4qfjaJmYHTx8EaMaU/MApe/QVHNr/7IQuq911c/z5O
8Vk/3IcDC5cYbExp9o36zZdXQzXvYNgaevBnIvwusuS6C5Jd4dtB7XCXmHrJYukU
zMWX5VFH2QaxIa7jCDosXxlwDmxuTSv2kk51tpQre3LOjtP9vvoYHnyfO6OQGf8R
hatDwu53g8Yr241d/Pvdhz2/Xob41mcsZW5O5wrG0G+e9BGaO7Wz05kJCQkBfoTn
ftfnNlFqsLm4+dRRXtR0TtKoKbx0OgfQUxfN0HHLJsOFn0jlATdEnwNGl8w0ttUY
i7nJb/FjcNFkQj+gF22GNeIa16zg6dK1sRYiwkDOIg2MbzxYQyHABF6m0HHDLLH2
HrUPzf39FkzQVHohKl0wQeb9vj59xh1mN8reUe2F1MJgPKDsTTuSlwfTVB8EiCUO
gMy7D9tHvZ8a1zfYDBCqyR0RJ1uzmazKEh4douNLlsJZf5avG80=
=vrj5
-----END PGP SIGNATURE-----

Attachment: pgpIaUXLypYSP.pgp
Description: PGP signature


--- End Message ---

Reply via email to