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

Bug#934384: marked as done (libvma: FTBFS: some symbols or patterns disappeared)



Your message dated Sun, 21 Feb 2021 11:00:09 +0000
with message-id <E1lDmTB-000D2X-Os@fasolo.debian.org>
and subject line Bug#934384: fixed in libvma 9.2.2-1
has caused the Debian Bug report #934384,
regarding libvma: FTBFS: some symbols or patterns disappeared
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.)


-- 
934384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934384
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libvma
Version: 8.8.1.really.8.7.7-1
Severity: serious
Tags: ftbfs

This package fails to build on current sid/amd64.

>From my build log:

  dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below
  dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
  dpkg-gensymbols: warning: debian/libvma8/DEBIAN/symbols doesn't match completely debian/libvma8.symbols
  --- debian/libvma8.symbols (libvma8_8.8.1.really.8.7.7-1_amd64)
  +++ dpkg-gensymbolsBhlY4G       2019-08-10 14:41:41.948238949 +0000
  @@ -542,7 +542,7 @@
    _ZN12sockinfo_tcp2rxE9rx_call_tP5ioveclPiP8sockaddrPjP6msghdr@Base 8.8.1.really.8.7.7
    _ZN12sockinfo_tcp2txE9tx_call_tPK5iovecliPK8sockaddrj@Base 8.8.1.really.8.7.7
    _ZN12sockinfo_tcp30create_flow_tuple_key_from_pcbER10flow_tupleP7tcp_pcb@Base 8.8.1.really.8.7.7
  - _ZN12sockinfo_tcp30return_reuse_buffers_postponedEv@Base 8.8.1.really.8.7.7
  +#MISSING: 8.8.1.really.8.7.7-1# _ZN12sockinfo_tcp30return_reuse_buffers_postponedEv@Base 8.8.1.really.8.7.7
    _ZN12sockinfo_tcp4bindEPK8sockaddrj@Base 8.8.1.really.8.7.7
    _ZN12sockinfo_tcp5fcntlEim@Base 8.8.1.really.8.7.7
    _ZN12sockinfo_tcp5ioctlEmm@Base 8.8.1.really.8.7.7
  [...]
  dh_makeshlibs: failing due to earlier errors
  make: *** [debian/rules:15: binary] Error 255
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

-- 
Niko Tyni   ntyni@debian.org

--- End Message ---
--- Begin Message ---
Source: libvma
Source-Version: 9.2.2-1
Done: Tzafrir Cohen <tzafrir@debian.org>

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

Debian distribution maintenance software
pp.
Tzafrir Cohen <tzafrir@debian.org> (supplier of updated libvma 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: SHA256

Format: 1.8
Date: Tue, 02 Feb 2021 14:50:57 +0200
Binary: libvma libvma9 libvma9-dbgsym libvma-dbgsym libvma-dev libvma-utils libvma-utils-dbgsym
Source: libvma
Architecture: amd64 source
Version: 9.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team <debian-hpc@lists.debian.org>
Changed-By: Tzafrir Cohen <tzafrir@debian.org>
Closes: 934384
Description: 
 libvma9    - LD_PRELOAD-able library that boosts performance - shared library
 libvma-dev - Development files for the libvma library
 libvma     - LD_PRELOAD-able library that boosts performance
 libvma-utils - Examples and tools for the libvma library
Changes:
 libvma (9.2.2-1) unstable; urgency=medium
 .
   * New upstream release:
     - init_allow_nonroot_status.patch, init_fix_root_test.patch,
       init_force_reload.patch, init_local_fs.patch, systemd_dir.patch
       dropped: merged upstream
     - Upstream init script dropped (uses systemd unit).
   * Rename libvma8 to libvma9 (Closes: #934384)
   * Removed arch i386: no longer supported by Upstream
   * Compat level 13
   * Standards-Version: 4.5.1
   * Remove leftover init.d symlinks on purge
   * systemd_doc.patch: Documentation for systemd unit
Checksums-Sha1: 
 fa55ccc45633bba19e2009a5c3fc2def20f9d1a1 66448 libvma-dbgsym_9.2.2-1_amd64.deb
 d6fcae086f53aebc097858f328288ed9c7dd6a31 52280 libvma-dev_9.2.2-1_amd64.deb
 46566a558f8951b717e57462edbc3e539b3d029c 113264 libvma-utils-dbgsym_9.2.2-1_amd64.deb
 a1ebd9d1c63ac1c78ef8905871d8409f2ffb7840 65864 libvma-utils_9.2.2-1_amd64.deb
 36d8e866778a776bd79cbca55261506820b08c19 3462200 libvma9-dbgsym_9.2.2-1_amd64.deb
 b1342edebdb5c46c88222fe586c30c58fcb4cb55 552260 libvma9_9.2.2-1_amd64.deb
 43c7245a8a6526ba73da788698df2bdd84e32789 8407 libvma_9.2.2-1_amd64.buildinfo
 a1b2ac02e4f0f54f0d516c74ed93800123a6a064 88812 libvma_9.2.2-1_amd64.deb
 0b9effb277cab323a47ee184d4ffa54fa4ffb32d 2156 libvma_9.2.2-1.dsc
 12a465dee38c4a7e9593382cdc0cb34d8a2dda29 1076931 libvma_9.2.2.orig.tar.gz
 8b42b18478c15a3e16b588e98b1340d1ddaec028 26552 libvma_9.2.2-1.debian.tar.xz
Checksums-Sha256: 
 a54f191c0f75fd3a22a4b4d822321c54c595812cb76ddd1d262326c6ec979f13 66448 libvma-dbgsym_9.2.2-1_amd64.deb
 a1244e1c0c622c1241d56f02357337d0c8da8e378ec074d81a397942aed3b644 52280 libvma-dev_9.2.2-1_amd64.deb
 f72b41a6d7098d855acb26a542cd3930d84f5b872a9326c55d0190d06be9a726 113264 libvma-utils-dbgsym_9.2.2-1_amd64.deb
 851837b4de213c71297a6c56c76babd6b4b0be6c430ab6219b4412a1e307d780 65864 libvma-utils_9.2.2-1_amd64.deb
 3920d8f25f3994befec34eef66523d3147fd69658c9794e0dc0fa7c6394238c5 3462200 libvma9-dbgsym_9.2.2-1_amd64.deb
 b07644b3f4bce26d475b150a6b2779b3b06217f0c3b02c33293d7e5f7edbb0fb 552260 libvma9_9.2.2-1_amd64.deb
 8c4bd26669df54ea4f2136ad7817f28be2347eb90e6af5e08121398a28d8fa0a 8407 libvma_9.2.2-1_amd64.buildinfo
 77cc490c208668c4f6cf40a2c2f92e22cc5df360ef1cf400d8244c3427dd48ac 88812 libvma_9.2.2-1_amd64.deb
 57fe160012c1091b4e05155b41a0d521153b63498498ab6d378e3108ee029f92 2156 libvma_9.2.2-1.dsc
 f86b94de843982ddf7c47264605ad1fb27ee27e761d66cffab0b5a61ad471aa7 1076931 libvma_9.2.2.orig.tar.gz
 3db88e27f7d6450fca74097d882d79aca5ec501574c96beb968fde381eb1beac 26552 libvma_9.2.2-1.debian.tar.xz
Files: 
 8d18f71ed70ee1d2cf14811359931997 66448 debug optional libvma-dbgsym_9.2.2-1_amd64.deb
 573d28ee4a45b59e97fa378b049d696d 52280 libdevel optional libvma-dev_9.2.2-1_amd64.deb
 b10332c9b564c7872e7269309579453a 113264 debug optional libvma-utils-dbgsym_9.2.2-1_amd64.deb
 98968f40b2cc0680127393e41ce97270 65864 utils optional libvma-utils_9.2.2-1_amd64.deb
 598d27db1000476abc953a239af5114f 3462200 debug optional libvma9-dbgsym_9.2.2-1_amd64.deb
 0bdc6a54329c99d9ff9425412ac87ede 552260 libs optional libvma9_9.2.2-1_amd64.deb
 4cd4262fd442fccdc2ce5964988255b9 8407 net optional libvma_9.2.2-1_amd64.buildinfo
 2a456e05edf71e8d2fc4ae395d9558d2 88812 net optional libvma_9.2.2-1_amd64.deb
 eb82d661ed46795cc48e8e1d1c860726 2156 net optional libvma_9.2.2-1.dsc
 9010672a2bed0c1a51922c05862b9665 1076931 net optional libvma_9.2.2.orig.tar.gz
 a2158acfa11951655693b3da203c831c 26552 net optional libvma_9.2.2-1.debian.tar.xz

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

iQGzBAEBCAAdFiEEjhGGa0mM+W3ykQJyjv1MLwMloM4FAmAZeL8ACgkQjv1MLwMl
oM7krgwAixmj/sQXAywaOphQxHzcYdIRufbcfaCw8GBV9HzYU9EJjyWHqJin4Wd6
ejoZoU+G/KYv34AS5HBDFhl8pA+QJFTDY4vUZS2FC5/DelA7lDSy11WAWzi16PnJ
C/1o7KPIkMFWrEr+UKLdA3uZhOyGlAzDIUD9gFgaxv08Kwz101fMSpGuliTnTKOn
BTUM7bR9WGa0mJD2NRWt5r8d6/WJmC/xN1aHvpIf1z7g68XRhZ96Qz03qSv4++A+
CvWnvcInys3vU1tjbT4Tys1FS2qmhRIRtic4QOrODtrB59rBzaoszmGdfjDx7xTQ
Lq5NMFa1hEduskAMhpKdDLbSYUxPMdYT2ag9at9/7FtTT/MjBWsk9nWOOTnSVbYr
VT+xs1ccwZ/cSKX2WDeJOTlNQW1EaMkW4EDHRX0OLWjGa8Ow0koP0jYmNq7so8/Z
WpUT9rOIqcr2cquMGLCqZ2OA94H1bAl4rf0WgGylbbqUySfAZgefUttcenNmM2xw
9GMddgZZ
=Fotl
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: