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

Bug#1014318: marked as done (rocm-smi-lib: ftbfs on riscv64(error: some symbols or patterns disappeared in the symbols file))

Your message dated Tue, 05 Jul 2022 06:34:09 +0000
with message-id <E1o8c8P-0008MW-J5@fasolo.debian.org>
and subject line Bug#1014318: fixed in rocm-smi-lib 5.2.0-2
has caused the Debian Bug report #1014318,
regarding rocm-smi-lib: ftbfs on riscv64(error: some symbols or patterns disappeared in the symbols file)
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.)


-- 
1014318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014318
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: rocm-smi-lib
Version: 5.2.0-1
Severity: normal
Tags: ftbfs, patch
User: debian-riscv@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-riscv@lists.debian.org

Dear rocm-smi-lib Maintainer,

The rocm-smi-lib package has a ftbfs issue due to :

```
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
dpkg-gensymbols: warning: debian/librocm-smi64-1/DEBIAN/symbols doesn't match completely debian/librocm-smi64-1.symbols
--- debian/librocm-smi64-1.symbols (librocm-smi64-1_5.2.0-1_riscv64)
+++ dpkg-gensymbolsIBeNBq	2022-07-04 00:53:31.834782542 +0000
@@ -809,32 +809,50 @@
  (arch=any-i386 armel armhf mipsel hppa m68k powerpc sh4)_ZN9__gnu_cxx13new_allocatorISt13_Rb_tree_nodeISt4pairIKySt10shared_ptrISt6vectorIySaIyEEEEEEC2Ev@Base 5.1.0
  (arch=any-i386 armel armhf mipsel hppa m68k powerpc sh4)_ZN9__gnu_cxx13new_allocatorISt13_Rb_tree_nodeISt4pairIKySt10shared_ptrISt6vectorIySaIyEEEEEED1Ev@Base 5.1.0
  (arch=any-i386 armel armhf mipsel hppa m68k powerpc sh4)_ZN9__gnu_cxx13new_allocatorISt13_Rb_tree_nodeISt4pairIKySt10shared_ptrISt6vectorIySaIyEEEEEED2Ev@Base 5.1.0
+ _ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEEESaIS7_ELNS_12_Lock_policyE1EEE10deallocateEPSA_m@Base 5.2.0-1
+ _ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEEESaIS7_ELNS_12_Lock_policyE1EEE8allocateEmPKv@Base 5.2.0-1
+ _ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEEESaIS7_ELNS_12_Lock_policyE1EEEC1Ev@Base 5.2.0-1
+ _ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEEESaIS7_ELNS_12_Lock_policyE1EEEC2Ev@Base 5.2.0-1
+ _ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEEESaIS7_ELNS_12_Lock_policyE1EEED1Ev@Base 5.2.0-1
+ _ZN9__gnu_cxx13new_allocatorISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEEESaIS7_ELNS_12_Lock_policyE1EEED2Ev@Base 5.2.0-1
...
```
The full buildd log is here:

https://buildd.debian.org/status/fetch.php?pkg=rocm-smi-lib&arch=riscv64&ver=5.2.0-1&stamp=1656896064&raw=0

The symbols file attached is to fix the issue and I can build the package
successfully on my locally real riscv64 hardware(Unmatched board).
But it still give warning about some new symbols appeared in the 
symbols file. Although I have tried several times to update the symbol 
file from the riscv64 build log. So do we wait to new upload and get new
others arch buildd log to clear those warnings[0]?

Please let me know if there are any issues.

Bo

[0]: https://www.eyrie.org/~eagle/journal/2012-01/008.html
-- 
Best Regards,

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: rocm-smi-lib
Source-Version: 5.2.0-2
Done: Étienne Mollier <emollier@debian.org>

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

Debian distribution maintenance software
pp.
Étienne Mollier <emollier@debian.org> (supplier of updated rocm-smi-lib 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: Tue, 05 Jul 2022 07:57:32 +0200
Source: rocm-smi-lib
Architecture: source
Version: 5.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: ROCm Team <debian-ai@lists.debian.org>
Changed-By: Étienne Mollier <emollier@debian.org>
Closes: 1014318
Changes:
 rocm-smi-lib (5.2.0-2) unstable; urgency=medium
 .
   * d/*.symbols: adjust for armel and riscv64. (Closes: #1014318)
Checksums-Sha1:
 c0c9808f8a544608e7af795cd91ade9641598f7a 2470 rocm-smi-lib_5.2.0-2.dsc
 c223dc7fe0840fb30d4da4a841de3d5570d3cd89 86768 rocm-smi-lib_5.2.0-2.debian.tar.xz
Checksums-Sha256:
 e40ea243ae3bc4c3bb236c57c7324cb3a1c305f68cd42ce7494a43a508f5361c 2470 rocm-smi-lib_5.2.0-2.dsc
 33b974be396445f49e00b90a360985a5f79a0e2312a387a4ed5e1bddb5501d98 86768 rocm-smi-lib_5.2.0-2.debian.tar.xz
Files:
 cdbefee2d3fc180792af632b41d95a44 2470 devel optional rocm-smi-lib_5.2.0-2.dsc
 70b54d9c855a5d33d7716adac7f32ee3 86768 devel optional rocm-smi-lib_5.2.0-2.debian.tar.xz

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

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmLD18UUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdp8hw/9HKSkVvL4Sx0TpOxHaP4IlvK0K1Km
gsOE2fZMWIOeCdYhJ9RDODlDVAGgWkDiynDSnyJEAnB31m1tNRBBykixLIWsPcKN
tZsdpd2+FwCVOGC01vCN6qA1uaHxSVJ7Q+VQCFzLv8Ao4LKS3fAcqR1Ix5SuqL9a
xoTtScSKCFmeV/ufFWpuO/ozEe74Te46mDPcFQZSkoSwGnmKoI0xLZWehjAxtkIK
hO6dvuHER6SXMjTcetQLhPmB/WZoVnMZTKntWNyqszcuA4/v00WD5qWZmyKXNNOT
hp5leu65/10iUdEo+wPAK5un/lVrZrrz0BBuY4G7t3H17lRMFhe5tYjp/Bg7iva/
B+AHv9efJXroJocQM0hHiNyTmSjGbKekL2L+rI68V0NBTwgytBIzi/1Jr8sWF+Wc
N4VCiib/E+uggwe/nx3gRMYdHyWFXbXIzlMzuONW+/3kEnGiGtOIRkm3Fdv+nK/X
i5Gj9hMXkUWP1e/Ax+V/AQ7wc5Zuef0KCXNV6oddzZ0buSsxhYfsr/0SC2gCfqRh
XLSj/Ax6ogf4ZriQ+xAWhWD/G9Wtct6j9XsvDtJI50U9wyvAjswZP+HOsH3T3Mzm
sFafd1CGkUv/s8FP8QzTeBoDHHEFJG1CbmKbBuf3amdE9VIjqa3eNncUn2utSUy+
mzIDF4ZmyO4WUKM=
=yiqU
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: