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

Bug#953938: marked as done (zfs-fuse: Switch from deprecated <attr/xattr.h> to <sys/xattr.h>)



Your message dated Thu, 05 Sep 2024 14:54:09 +0000
with message-id <E1smDs9-007jlz-NZ@fasolo.debian.org>
and subject line Bug#953938: fixed in zfs-fuse 0.7.0-29
has caused the Debian Bug report #953938,
regarding zfs-fuse: Switch from deprecated <attr/xattr.h> to <sys/xattr.h>
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.)


-- 
953938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953938
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: zfs-fuse
Source-Version: 0.7.0-20
Severity: important
User: attr@packages.debian.org
Usertags: libattr-drop-attr-xattr-header

Hi!

This package uses the deprecated <attr/xattr.h> header (from libattr)
instead of the one provided now by glibc <sys/xattr.h>.

The former header has been removed in upstream libattr, but got
reintroduced in Debian to avoid breakage just before the Debian buster
freeze. But I'd like to be able to remove it in Debian too, so that
the interface can be synced with upstream.

It looks like this is the only header used by this package from libattr,
so you should be able to drop the dependency on libattr entirely, as
glibc should be providing all that is needed now.

Thanks,
Guillem

--- End Message ---
--- Begin Message ---
Source: zfs-fuse
Source-Version: 0.7.0-29
Done: Hilko Bengen <bengen@debian.org>

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

Debian distribution maintenance software
pp.
Hilko Bengen <bengen@debian.org> (supplier of updated zfs-fuse 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: Thu, 05 Sep 2024 15:19:32 +0200
Source: zfs-fuse
Architecture: source
Version: 0.7.0-29
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Hilko Bengen <bengen@debian.org>
Closes: 953938
Changes:
 zfs-fuse (0.7.0-29) unstable; urgency=medium
 .
   * QA upload.
   * Add patch to use sys/xattr.h instead of xattr/xattr.h (Closes: #953938)
Checksums-Sha1:
 288d705c9a940d0d5002e0e5f66a17406de2b5a2 2025 zfs-fuse_0.7.0-29.dsc
 8c31c7a2ffde4f3c1c517ca5838e898e0997ab09 30924 zfs-fuse_0.7.0-29.debian.tar.xz
 7e375190d8089e7484e3d7811359b99bee10afa9 7915 zfs-fuse_0.7.0-29_source.buildinfo
Checksums-Sha256:
 a09e06510fb7e562c5142d5bb8a82f3906c1105a28cc5a525135011be14b7ffd 2025 zfs-fuse_0.7.0-29.dsc
 f3d2d91123f030839fb962be0b3ca8fe9c525d206c124b1d1d20158a86f584c8 30924 zfs-fuse_0.7.0-29.debian.tar.xz
 19e680672103cc1c5e28563edaae52ae00eec2666ef5d831bf73e0a458b3b5f3 7915 zfs-fuse_0.7.0-29_source.buildinfo
Files:
 cd030d5b564df846a62d6da5b8b5a6c2 2025 otherosfs optional zfs-fuse_0.7.0-29.dsc
 92c395c86074e1223911be9c5d2b6aaa 30924 otherosfs optional zfs-fuse_0.7.0-29.debian.tar.xz
 356a10b45dcd7940a4e6b0b640992a46 7915 otherosfs optional zfs-fuse_0.7.0-29_source.buildinfo

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

iQIzBAEBCAAdFiEErnMQVUQqHZbPTUx4dbcQY1whOn4FAmbZuNUACgkQdbcQY1wh
On7yWQ/+K5ias/gDWPe8WH/s/NIxoTFiinuy6KaYLP/eU8IjqsbCuVgr1D1Fjk8s
FqcQOS1JqRDDHn2kp7XXw+d2hWlQ3HnBO7hs5j0mhfYdHz6IiSZnCSjdXqif7SR3
7IH/SUni9bafibVaEY3yRWEdTfHKY3Qjjx4yscpC+RiAkqQJjfRNyCwy1wgF9Trv
c62NeDz6q6J1kNrgj2MMMXRz0QaS3/aBKwsOdtLXxRnBb5hO5a/+5O1GXCpDZAV8
ghgg+Y9ILUshf1L+rutxfElPJZgYdcx6esuoAYk16jkx6bnaSkWfmJparoa3fp0+
ZvA+Cs027cp8TRb0LFT0nOJR6vWoeA5Un40qDk4bgopzZXGSz1MfmYIHB22r3chE
tgvXMD/1a7g/Km6vIllO3x0Teik1UInD2xyIsE7gL1LU882r+u7OkAJIVgjYt1et
z50P+fR08yQTVR3o7LkYn0qsgozSVkeyptfNEJutFt/KVX9kktQKazNxvCYCVHg3
BdEMrgKF3qOrJlFnCy+I5aJJlCS49Ieka6D6Uqh+u1PYlBpZZDuHx2U7Z4GPEDo6
CMJrPLDCR3Na3BZaMnJdouMQ45jAxrsRUouqtowIyj8Z0tQeOfbb17LDPLBHVMbl
NU6o5/Fopk+KDwvhmWPgHy62EZbKghAYBeR6Cet8lHMlAIyPdb4=
=EJ4d
-----END PGP SIGNATURE-----

Attachment: pgpXCpiupA5Np.pgp
Description: PGP signature


--- End Message ---

Reply to: