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

Bug#1001965: marked as done (Fails to build from source due to outdated symbols file)



Your message dated Mon, 20 Dec 2021 06:03:36 +0000
with message-id <E1mzBlo-000H0M-NK@fasolo.debian.org>
and subject line Bug#1001965: fixed in libdrm 2.4.109-2
has caused the Debian Bug report #1001965,
regarding Fails to build from source due to outdated 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.)


-- 
1001965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001965
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libdrm
Version: 2.4.109-1
Severity: serious
Tags: patch

Hi,
2.4.109-1 fails to build like:

dpkg-gensymbols: warning: debian/libdrm-amdgpu1/DEBIAN/symbols doesn't match completely debian/libdrm-amdgpu1.symbols
--- debian/libdrm-amdgpu1.symbols (libdrm-amdgpu1_2.4.109-1_amd64)
+++ dpkg-gensymbolsRbfBrW	2021-12-18 17:31:37.021023907 +0000
@@ -53,6 +53,7 @@
  amdgpu_cs_wait_fences@Base 2.4.81
  amdgpu_cs_wait_semaphore@Base 2.4.67
  amdgpu_device_deinitialize@Base 2.4.63
+ amdgpu_device_get_fd@Base 2.4.109-1
  amdgpu_device_initialize@Base 2.4.63
  amdgpu_find_bo_by_cpu_mapping@Base 2.4.94
  amdgpu_get_marketing_name@Base 2.4.73
dh_makeshlibs: error: failing due to earlier errors
make[1]: *** [debian/rules:121: override_dh_makeshlibs] Error 25
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:141: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned exit status 2

Full log: https://buildd.debian.org/status/fetch.php?pkg=libdrm&arch=amd64&ver=2.4.109-1&stamp=1639848700&raw=0

Attached patch fixes that for me and I'm happy to NMU if that looks
correct. The symbol got added in
f70e8ae83590d2a1fb1972dc7e875dd6a9355b77 upstream and looks like a valid new
public symbol.

Cheers,
 -- Guido
 

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 0ecc96a5514e030a91be47d62febf7e656170fff Mon Sep 17 00:00:00 2001
Message-Id: <0ecc96a5514e030a91be47d62febf7e656170fff.1639931516.git.agx@sigxcpu.org>
From: =?UTF-8?q?Guido=20G=C3=BCnther?= <agx@sigxcpu.org>
Date: Sun, 19 Dec 2021 17:22:10 +0100
Subject: [PATCH] Update symbols file

---
 debian/libdrm-amdgpu1.symbols | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/libdrm-amdgpu1.symbols b/debian/libdrm-amdgpu1.symbols
index 6ce3d569..d04300e8 100644
--- a/debian/libdrm-amdgpu1.symbols
+++ b/debian/libdrm-amdgpu1.symbols
@@ -53,6 +53,7 @@ libdrm_amdgpu.so.1 libdrm-amdgpu1 #MINVER#
  amdgpu_cs_wait_fences@Base 2.4.81
  amdgpu_cs_wait_semaphore@Base 2.4.67
  amdgpu_device_deinitialize@Base 2.4.63
+ amdgpu_device_get_fd@Base 2.4.109
  amdgpu_device_initialize@Base 2.4.63
  amdgpu_find_bo_by_cpu_mapping@Base 2.4.94
  amdgpu_get_marketing_name@Base 2.4.73
-- 
2.33.0


--- End Message ---
--- Begin Message ---
Source: libdrm
Source-Version: 2.4.109-2
Done: Timo Aaltonen <tjaalton@debian.org>

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

Debian distribution maintenance software
pp.
Timo Aaltonen <tjaalton@debian.org> (supplier of updated libdrm 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: Mon, 20 Dec 2021 07:39:47 +0200
Source: libdrm
Built-For-Profiles: noudeb
Architecture: source
Version: 2.4.109-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Timo Aaltonen <tjaalton@debian.org>
Closes: 1001965
Changes:
 libdrm (2.4.109-2) unstable; urgency=medium
 .
   * amdgpu1.symbols: Updated. (Closes: #1001965)
Checksums-Sha1:
 2c1995a5ffb4b50e1a68682038c314674f923248 3296 libdrm_2.4.109-2.dsc
 ed5a477497b4098f191cb7f4098b3f8dc8710475 57896 libdrm_2.4.109-2.debian.tar.xz
 d458e3cb5dc8848945e07091f3d7b6a686c1aa8e 7092 libdrm_2.4.109-2_source.buildinfo
Checksums-Sha256:
 4a280f2afd077606e464af08b25c4de1be518517d3d22bd2620b3e54ebe0438e 3296 libdrm_2.4.109-2.dsc
 92fb41004ae695745e9d32bf801bd31390211de76d9fce05d8f5953bbda4d668 57896 libdrm_2.4.109-2.debian.tar.xz
 5e8a18f046718a682cd09a822e23aa2fef6dbd00f46bb6ca3d82c02e1df66856 7092 libdrm_2.4.109-2_source.buildinfo
Files:
 fc3874788a2698651bd62d1c2940cbdb 3296 libs optional libdrm_2.4.109-2.dsc
 40262b6fee46af38f91060455c2fb49c 57896 libs optional libdrm_2.4.109-2.debian.tar.xz
 6809bc022536d9b4f35bfe21b3d703dc 7092 libs optional libdrm_2.4.109-2_source.buildinfo

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

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmHAFzkACgkQy3AxZaiJ
hNzykhAAqmgU4rhsLQv8j6B1db5aSa2r0LcBxP4D1bkzco0wcLgBjU5x2MFGceFY
5BOS20eFEugEhycuWJ78Ei1mGwhR9AA9W23C5j2vOLw2WMEdy8Blmd1u1iA5XXla
Oz8or7R3ex6PJHgLp6iDdmqKXdEIyIMgvUorySZweOd5LxGd/IMI92/taUQhCPg4
HFE631x76ussff6jP/F58RWTT311PeL78KL9UzdhuBMX77PRnyTr7M3CgXgh3M9o
IJG+mgluk+RLPSIoT6ZTIYcMJb/Eeh8SmXxY8D7a+0PQiKcIZSwnad8/D9sBQPAW
JwjE7a6yUUZQKxENiXlGA6+3lKtwq54KdO4wcW99G4H/xc+oQ9Iglkd4IHWuxUw/
Ro8GxnGdxLHw3n3JdMmiR5R/SjbOHQwy0GwRql7R9KvpgRfQ594poFh+Zg5Gtw9c
yZvwByiv0Uk+HQpf2Itri7JgFmnYUSQjWnu4N2nsfzR+x2HYSB6OYQSZDibJY5kb
V1ZLpFPuSMIRSe0j27IgwCX0Du1emBjKTzon9XGRWxFEysa6gkomq/g/ePqePP6I
QqrCGIUM0epLqWQ6VdX3GHTJbGErvoQHwgK2SJxW6CW720JHge/1PO9vEN36C79r
pDV5wCzCk/LNRx4rqG6lk436Krh4aiQqFrnSGvZrYW8yRHlPKOw=
=TZ0+
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: