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

Bug#953934: marked as done (obexpushd: Switch from deprecated <attr/xattr.h> to <sys/xattr.h>)

Your message dated Fri, 18 Oct 2024 06:34:43 +0000
with message-id <E1t1gZP-00575t-TA@fasolo.debian.org>
and subject line Bug#953934: fixed in obexpushd 0.11.2-5
has caused the Debian Bug report #953934,
regarding obexpushd: 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.)


-- 
953934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953934
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: obexpushd
Source-Version: 0.11.2-1.1
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: obexpushd
Source-Version: 0.11.2-5
Done: Petter Reinholdtsen <pere@debian.org>

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

Debian distribution maintenance software
pp.
Petter Reinholdtsen <pere@debian.org> (supplier of updated obexpushd 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: Fri, 18 Oct 2024 08:18:59 +0200
Source: obexpushd
Architecture: source
Version: 0.11.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Petter Reinholdtsen <pere@debian.org>
Closes: 953934
Changes:
 obexpushd (0.11.2-5) unstable; urgency=medium
 .
   * QA upload.
 .
   * Added 1000-glibc-sys-xattr.patch to switch to <sys/xattr.h>
     (Closes: #953934).
Checksums-Sha1:
 bc111261f65e43babeb406c5be3eaaa5880cef23 1857 obexpushd_0.11.2-5.dsc
 f9047b41dcc8e2b5fb6a40bd075446ad2358f9ae 5484 obexpushd_0.11.2-5.debian.tar.xz
 005a7eff2f491d0bb7fdb754317c5f0056cc8539 7429 obexpushd_0.11.2-5_source.buildinfo
Checksums-Sha256:
 45098147f09784aa3e1327019f5758ac1479df3f03d4f8a19d645e3f59cdafeb 1857 obexpushd_0.11.2-5.dsc
 e6a68861efdb370a508c1a77a412e50ecd71d2c13e98ba7042ac4410e384d0bd 5484 obexpushd_0.11.2-5.debian.tar.xz
 0ccbd31b2dc57a180955a8ce31bca3df1c96861bf5ae0d59ae5c8951114d81fd 7429 obexpushd_0.11.2-5_source.buildinfo
Files:
 6e3481a257e78b9931baf85f53c5147c 1857 comm optional obexpushd_0.11.2-5.dsc
 e5286b46dfab04851607fb983b5f9215 5484 comm optional obexpushd_0.11.2-5.debian.tar.xz
 846e314b7d5311c4f5f40a76d8ff1a9e 7429 comm optional obexpushd_0.11.2-5_source.buildinfo

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

iQIzBAEBCAAdFiEERqLf4owIeylOb9kkgSgKoIe6+w4FAmcR/oYACgkQgSgKoIe6
+w4Xdg//Zlb1tJq6VEdFMUly8uwsKPZwWK0HilZUqZ3bVeNRMfmNFVe5VCoZfme0
3ms72tW75cSVjIoxA7qF7y2reRQoKWAuREgzSyfNWFuz3QQWSOpWfDOjKjj/sBO1
5o6HaYbPsBrSVBtmJO7mo7gyKgqFKLhy+D7YQSyfZkCIjhzkwl56hwtRXY7VBrmG
O/rVaaAynALiJ+dfUAhJgqZsstRLecEnLAigrcpB/MnnG0xHZM/sAeJUViGMGeiX
Grhmbx9dvbpQQFUkIYeUL590u+GnDuwl/Ly0n396sSsHDM992JWPBVhf49/YZIvD
5SVHfZRsGphKKy1SEAPINefoi7a+vZFk1hBRw5Z0hSnWeER+BmkGO6ynhp0QWjg9
Xh02mrd4aMdGJnAf0mK/lpSKjYvZt5HLAh7DGV4AHijkBu7/5Ya+08dYNrjaeWR1
C539ZQlHz2U1ed8CeqHvx9S331ghTuZVr2RThgDVq4ZlZjj+1TG3e6R3Z0LzXP4t
FigdvVo7uRY6oRTmvC5ruZHz+/QVJSBbqeSaLXx68G1dw1RDqqCoRtZWK4nMzfIK
4Y7KEvwkJbEMOPJNKJj5UOgFGb7K+apkQZ2uYCccwQO54Sty/PMcHH4vuZrqbaKr
IO9cEvax0jFwROo0WknNJTn3usPYK/ek/b+p0AA8INeVmLcIyCA=
=+Z0I
-----END PGP SIGNATURE-----

Attachment: pgpsCMCvGGfjt.pgp
Description: PGP signature


--- End Message ---
Reply to: