Bug#997009: marked as done (libpciaccess: FTBFS on hurd-i386)
Your message dated Wed, 12 Jan 2022 13:48:36 +0000
with message-id <E1n7dzQ-000FVh-Eo@fasolo.debian.org>
and subject line Bug#997009: fixed in libpciaccess 0.16-2
has caused the Debian Bug report #997009,
regarding libpciaccess: FTBFS on hurd-i386
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.)
--
997009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997009
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libpciaccess
Version: 0.16-1
Severity: important
Tags: patch
User: debian-hurd@lists.debian.org
Usertags: hurd
Hi,
Currently libpciaccess FTBFS on GNU/Hurd due to missing symbols in the
libpciaccess0.symbols file. The attached patch,
debian_libpciaccess0.symbols.hurd-i386.diff, defines the symbols
specifically for Hurd.
Thanks!
--- /dev/null 2021-10-22 11:54:06.000000000 +0200
+++ b/debian/libpciaccess0.symbols.hurd-i386 2021-10-22 11:54:40.000000000 +0200
@@ -0,0 +1,73 @@
+libpciaccess.so.0 libpciaccess0 #MINVER#
+ pci_device_cfg_read@Base 0
+ pci_device_cfg_read_u16@Base 0
+ pci_device_cfg_read_u32@Base 0
+ pci_device_cfg_read_u8@Base 0
+ pci_device_cfg_write@Base 0
+ pci_device_cfg_write_bits@Base 0
+ pci_device_cfg_write_u16@Base 0
+ pci_device_cfg_write_u32@Base 0
+ pci_device_cfg_write_u8@Base 0
+ pci_device_close_io@Base 0.11.0
+ pci_device_enable@Base 0.10.2
+ pci_device_find_by_slot@Base 0
+ pci_device_get_agp_info@Base 0
+ pci_device_get_bridge_buses@Base 0
+ pci_device_get_bridge_info@Base 0
+ pci_device_get_device_name@Base 0
+ pci_device_get_parent_bridge@Base 0.11.0
+ pci_device_get_pcmcia_bridge_info@Base 0
+ pci_device_get_subdevice_name@Base 0
+ pci_device_get_subvendor_name@Base 0
+ pci_device_get_vendor_name@Base 0
+ pci_device_has_kernel_driver@Base 0.10.7
+ pci_device_is_boot_vga@Base 0.10.7
+ pci_device_map_legacy@Base 0.12.902
+ pci_device_map_memory_range@Base 0
+ pci_device_map_range@Base 0.8.0+git20071002
+ pci_device_map_region@Base 0
+ pci_device_next@Base 0
+ pci_device_open_io@Base 0.11.0
+ pci_device_probe@Base 0
+ pci_device_read_rom@Base 0
+ pci_device_unmap_legacy@Base 0.12.902
+ pci_device_unmap_memory_range@Base 0
+ pci_device_unmap_range@Base 0.8.0+git20071002
+ pci_device_unmap_region@Base 0
+ pci_device_vgaarb_decodes@Base 0.10.7
+ pci_device_vgaarb_fini@Base 0.10.7
+ pci_device_vgaarb_get_info@Base 0.10.7
+ pci_device_vgaarb_init@Base 0.10.7
+ pci_device_vgaarb_lock@Base 0.10.7
+ pci_device_vgaarb_set_target@Base 0.10.7
+ pci_device_vgaarb_trylock@Base 0.10.7
+ pci_device_vgaarb_unlock@Base 0.10.7
+ pci_device_x86_close_io@Base 0.16-1
+ pci_device_x86_map_legacy@Base 0.16-1
+ pci_device_x86_map_range@Base 0.16-1
+ pci_device_x86_open_legacy_io@Base 0.16-1
+ pci_device_x86_read16@Base 0.16-1
+ pci_device_x86_read32@Base 0.16-1
+ pci_device_x86_read8@Base 0.16-1
+ pci_device_x86_unmap_legacy@Base 0.16-1
+ pci_device_x86_unmap_range@Base 0.16-1
+ pci_device_x86_write16@Base 0.16-1
+ pci_device_x86_write32@Base 0.16-1
+ pci_device_x86_write8@Base 0.16-1
+ pci_get_strings@Base 0
+ pci_id_match_iterator_create@Base 0
+ pci_io_read16@Base 0.11.0
+ pci_io_read32@Base 0.11.0
+ pci_io_read8@Base 0.11.0
+ pci_io_write16@Base 0.11.0
+ pci_io_write32@Base 0.11.0
+ pci_io_write8@Base 0.11.0
+ pci_iterator_destroy@Base 0
+ pci_legacy_open_io@Base 0.11.0
+ pci_slot_match_iterator_create@Base 0
+ pci_system_cleanup@Base 0
+ pci_system_init@Base 0
+ pci_system_init_dev_mem@Base 0.10.2
+ pci_system_x86_destroy@Base 0.16-1
+ x86_disable_io@Base 0.16-1
+ x86_enable_io@Base 0.16-1
--- End Message ---
--- Begin Message ---
Source: libpciaccess
Source-Version: 0.16-2
Done: Timo Aaltonen <tjaalton@debian.org>
We believe that the bug you reported is fixed in the latest version of
libpciaccess, 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 997009@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 libpciaccess 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: Wed, 12 Jan 2022 15:24:41 +0200
Source: libpciaccess
Built-For-Profiles: noudeb
Architecture: source
Version: 0.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Timo Aaltonen <tjaalton@debian.org>
Closes: 997009
Changes:
libpciaccess (0.16-2) unstable; urgency=medium
.
* libpciaccess0.symbols.hurd-i386: Add a symbols file for Hurd.
(Closes: #997009)
Checksums-Sha1:
51246ea7d9ba2a64e17ac6be3da47c8d304186de 2291 libpciaccess_0.16-2.dsc
33fdc10cae10eb3ed397cd9f8a340bec6438eca1 28636 libpciaccess_0.16-2.diff.gz
7fd94a2a63f3ddb2682c9d78d3f6674877c1205b 6480 libpciaccess_0.16-2_source.buildinfo
Checksums-Sha256:
99f9422eae2c250f3abb87f3e3c4372faadd640e72d77ca2cd8a292b09f825c5 2291 libpciaccess_0.16-2.dsc
c796e2576969964165aaef61a018fb131cce590c572240c41a798ed4ef4f5031 28636 libpciaccess_0.16-2.diff.gz
cf364f006cc2d253c8f00df0031c312563b6b5653474cddd7ffaa1c731a8ea6d 6480 libpciaccess_0.16-2_source.buildinfo
Files:
3d0e78569fbc0d971a0f1efffaed1b45 2291 devel optional libpciaccess_0.16-2.dsc
fad87a5ac4a77fdceb6c4c5ccd212671 28636 devel optional libpciaccess_0.16-2.diff.gz
eba58f45ed1feed01b508214eb007891 6480 devel optional libpciaccess_0.16-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmHe1xgACgkQy3AxZaiJ
hNy2EQ/+Pzrn0ISMMaWcTlbmUSUWd3hs3fIzpJGircbfKi9i1CzMNGz7d0zxt1Q3
Ow8RS5tNPlvFIWHnyOwKX0hTCS5qEIBBorOMs3Gg3/y5WFugOZV+wazw4R6v2gKY
5mUcGv0mcl40h9Q3Y1V3zNrYuAbt6DaRXCrDs2MbVgSRVWcG2pXnDzAhEIVZGmsg
n1Qf9Wa/2QM0U5X7OugRrbOaSzmijKVa+GrjUEKGcSSDEsIjTSemew4XYUl5tj+i
KjTi3eiG1a8xKQ+NpqlMZN3rbgDzc+scL0Y4MozsXZm+PPwGoQN5uXM7+kIvtrL7
aPBruQt+FUcWbH5AM9EW0V9wrg35UTJ2nIfIlm1hbF2THtqDpOyWSSeRcskcK7iy
2Ha9fCnOeYX8wvotm7a8VUu37twjEykWOQrLuqsEeQe5TyfOFvKctfbF0KY9Pm8n
oee2ug+5gy6TsKnXXzHZFAMG0xCNx9ps6R05ij+PFL7DU7BWmENCB9dHwt51RIZm
vtLJRmpdvq2YXTCTHpuETrPTC+UaLAdj2J4UmqaPtexxe00vhgoR75O9KyVcVxEa
jqlM/sdrwriVlsmD0CIBOecpftumdOX2kKsFb/ftPkq9EhPzpGjMYvGjspb3+02m
/6s72jXE0ibC5w8+VhMNwed45cvDBZHZc1fPu7bk1EkvVb8ZFNs=
=A+oj
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: