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

Bug#1023418: marked as done (libpciaccess: FTBFS on hurd-i386: symbol list update)



Your message dated Tue, 08 Nov 2022 11:04:33 +0000
with message-id <E1osMPB-00D42Y-2v@fasolo.debian.org>
and subject line Bug#1023418: fixed in libpciaccess 0.17-2
has caused the Debian Bug report #1023418,
regarding libpciaccess: FTBFS on hurd-i386: symbol list update
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.)


-- 
1023418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023418
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: libpciaccess
Version: 0.17-1
Severity: important
Tags: patch
User: debian-hurd@lists.debian.org
Usertags: hurd

Hello,

The newer libpciaccess doesn't build on hurd-i386 because the newer
upstream version modified some symbols. The attached patch fixes that. I
checked that indeed no package is using the old
pci_device_x86_map/unmap_legacy/range (they were used only internally by
the library).

Could you apply it?

Thanks,
Samuel

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
Samuel
---
Pour une évaluation indépendante, transparente et rigoureuse !
Je soutiens la Commission d'Évaluation de l'Inria.
--- debian/libpciaccess0.symbols.original	2022-11-03 18:16:21.000000000 +0000
+++ debian/libpciaccess0.symbols	2022-11-03 18:17:26.000000000 +0000
@@ -45,14 +45,10 @@
  pci_device_vgaarb_trylock@Base 0.10.7
  pci_device_vgaarb_unlock@Base 0.10.7
  (arch=hurd-i386)pci_device_x86_close_io@Base 0.16
- (arch=hurd-i386)pci_device_x86_map_legacy@Base 0.16
- (arch=hurd-i386)pci_device_x86_map_range@Base 0.16
  (arch=hurd-i386)pci_device_x86_open_legacy_io@Base 0.16
  (arch=hurd-i386)pci_device_x86_read16@Base 0.16
  (arch=hurd-i386)pci_device_x86_read32@Base 0.16
  (arch=hurd-i386)pci_device_x86_read8@Base 0.16
- (arch=hurd-i386)pci_device_x86_unmap_legacy@Base 0.16
- (arch=hurd-i386)pci_device_x86_unmap_range@Base 0.16
  (arch=hurd-i386)pci_device_x86_write16@Base 0.16
  (arch=hurd-i386)pci_device_x86_write32@Base 0.16
  (arch=hurd-i386)pci_device_x86_write8@Base 0.16
@@ -72,5 +68,6 @@
  pci_system_init@Base 0
  pci_system_init_dev_mem@Base 0.10.2
  (arch=hurd-i386)pci_system_x86_destroy@Base 0.16
+ (arch=hurd-i386)pci_system_x86_map_dev_mem@Base 0.17
  (arch=hurd-i386)x86_disable_io@Base 0.16
  (arch=hurd-i386)x86_enable_io@Base 0.16

--- End Message ---
--- Begin Message ---
Source: libpciaccess
Source-Version: 0.17-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 1023418@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: Tue, 08 Nov 2022 12:39:24 +0200
Source: libpciaccess
Built-For-Profiles: noudeb
Architecture: source
Version: 0.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Timo Aaltonen <tjaalton@debian.org>
Closes: 1023418
Changes:
 libpciaccess (0.17-2) unstable; urgency=medium
 .
   * symbols: Update for Hurd. (Closes: #1023418)
Checksums-Sha1:
 fe30aee15af3cbf105c713623bc1366d7cb981bd 2291 libpciaccess_0.17-2.dsc
 13d651110fa4470103032104b2e6b4369efdeaf5 34513 libpciaccess_0.17-2.diff.gz
 3e67a092cf078de4e57ee70ded67109a33f6a6c1 7491 libpciaccess_0.17-2_source.buildinfo
Checksums-Sha256:
 748486b2c15a9e70a4db39209dffa0129fdc721b9e91a3777936af64cdd545e9 2291 libpciaccess_0.17-2.dsc
 8cbb170711236a2d059a86fa9db72cf53a66548db3d5c3ecebcea2f6ea17e7c9 34513 libpciaccess_0.17-2.diff.gz
 e3f80d4551b0f1eb58b7eb8014a8f512c308c6634540466beb0a18c457533ea3 7491 libpciaccess_0.17-2_source.buildinfo
Files:
 9a9e9e9d7c1370e9ab7ecc17c300b699 2291 devel optional libpciaccess_0.17-2.dsc
 4cefbcdf01fca2f06c82b123da7d3766 34513 devel optional libpciaccess_0.17-2.diff.gz
 ed1d4e1d33a00866922b2935c1dda98d 7491 devel optional libpciaccess_0.17-2_source.buildinfo

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

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmNqMf0ACgkQy3AxZaiJ
hNzSPRAAjQppfRMrbkQq9es7wKNfB/jq9SEaihEt0W/8ag9l8y2HlpPU2Y0N10N0
DKI4E9Wp3ocW7dVaKjRuVXgQnOyogT/WoQK9w3I/pkYIFpcXjJZyJtVC6cPRXwFw
wMBUrsZRNZh3rKhCh73vYUfd/DQWB+TYrTDda3tZFiVNgiiMN/bH32avHKCDmb50
RVjvQOZtFj1dQf3iyKUwJXUEKBx1dgO6/Rdkvi1U5VgjP7qiUFmUkTKPoPT2eiBN
Zx6qCUJgi5vuU4KuCypU4cFMZck5eDXEhy1cYW9UE1sqLJih1r1/IEGIZxlIPtZA
wavsbaBSE2IJBm5ahnofP0x+u+7j/SFWUaKcWJ7utNFrCfYpBsdYiXcEs/Qm9XxV
RemAM/zrP74CPMJ3fOtk7foSIjbCTNrPLX6lGFOzJSFBPP37OvM8v4YDW1WVXIa6
CZPxHKCvtyIWznobVXwOjW4qRmoEuS1KKXxaR6E2qCcKoS69T4zdwbf9WjDvCEUM
tVKz18qJk8G3T/EErRLGT1Agbejo/1U0XbvpCPabC6SRlC03Ms13Z5/kMVOzgaj4
a8L9E6PF9wQbpYh/7QYCXx+Q9k0t5gGlmuiMxVIDVA1/Ycz5MzZOXwjWTeGQr/nn
Tm0fWDd9WXHcflUAFCouVB3sibBhtFBNaptN9VaguqWbHLsoSqU=
=OeFY
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: