Your message dated Sun, 23 Mar 2025 14:46:29 +0000
with message-id <[email protected]>
and subject line Bug#1100847: fixed in gvfs 1.57.2-2
has caused the Debian Bug report #1100847,
regarding /run/user/1000/gvfs is not populated with current build of gvfs
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 [email protected]
immediately.)
--
1100847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100847
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gvfs
Version: 1.57.2-1+b1
Hi
I hope this report is correct.
I use borg to backup my debian sid system over sftp and after the gvfs
packages were updated to 1.57.2-1+b1 borg was unable to access the
remote repository.
Upon inspection, the /run/user/1000/gvfs directory which borg uses for
the location was empty while the remote repository was open and
accessible in Nautilus.
Reverting the gvfs packages to 1.57.2-1 populated the directory again
and restored functionality.
--- End Message ---
--- Begin Message ---
Source: gvfs
Source-Version: 1.57.2-2
Done: Simon McVittie <[email protected]>
We believe that the bug you reported is fixed in the latest version of
gvfs, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie <[email protected]> (supplier of updated gvfs 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 23 Mar 2025 13:42:23 +0000
Source: gvfs
Architecture: source
Version: 1.57.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
<[email protected]>
Changed-By: Simon McVittie <[email protected]>
Closes: 1100847 1101025
Changes:
gvfs (1.57.2-2) unstable; urgency=medium
.
* Team upload
* d/p/fuse-use-fuse_-un-set_feature_flag-instead-of-setting-man.patch:
Add proposed patch for interoperability with FUSE 3.17.
Direct access to `fuse_conn_info.want` is deprecated, and currently
doesn't work (although that might be a libfuse bug). Use the
non-deprecated accessors instead. (Closes: #1100847, #1101025)
* d/p/Remove-version-from-polkit-gobject-dependency.patch:
Drop patch, no longer necessary.
Debian and Ubuntu are both tracking recent upstream versions of
polkit again, so having a stricter dependency is not a concern.
* d/patches: Improve patch metadata
* Standards-Version: 4.7.2 (no changes required)
Checksums-Sha1:
669171d673f20dffd47aade0e9cf5ba7d2d2612d 3643 gvfs_1.57.2-2.dsc
2d263bad1449fc7c5df8173350ab3a175d1113a9 27504 gvfs_1.57.2-2.debian.tar.xz
7aa80782f380f7ee6810f32a40206759651481c0 15351 gvfs_1.57.2-2_source.buildinfo
Checksums-Sha256:
a225fe11333a2052ed27c1ba4649a921f60f08f331e853973d3fcc8c081d96bf 3643
gvfs_1.57.2-2.dsc
358eeeeef3f67f60aa866ab7ef60b4ffbb3befdd53dcbdfe3eae87e0722382f7 27504
gvfs_1.57.2-2.debian.tar.xz
5552844614cd3d9b4c66a7a45fc48127e1db1ee9085945950ffde2ffd48e1371 15351
gvfs_1.57.2-2_source.buildinfo
Files:
86d1a2dbdf4621eb188ac38ffe18c7dd 3643 gnome optional gvfs_1.57.2-2.dsc
8259421be7260616a7cb1fc7440f898c 27504 gnome optional
gvfs_1.57.2-2.debian.tar.xz
c23d1006bd6550663aa4df357cfddfc7 15351 gnome optional
gvfs_1.57.2-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEegc60a5pT6Jb/2LlI1wJnT6zMHYFAmfgGPYACgkQI1wJnT6z
MHaq0g//b/QAmLEhmLBAenZmxxrEPmzct3b3AqP/bJ5B/EZb8qx8TmQrIWde5P7D
xCcFCbUVXQSB/5aPrCDuG1cPKNRDOnBEJ/kcZts8sddvMfYF7EN+Whsi/CNqbxjh
CoEBtFpxYUSkkneOdOeurwBwBdu9S+N/oNHyy0LIrrzBcccJ6JMbDQdez1HK5kek
xjWB68mg1bs61KPXyhFUiyhq8o7IufmfvFJV+TUsU/qCqJ5b2RLjAAabJfXd0IUV
VSHtEVmsCaFBjPDchkF8lXVXBKXEd0i799SOUcEiQgTKTNFQFMx3OpBBYpvov9MR
mqVUhd0y/UoODJH+Q2zD366JCEQ8Ic9oSJgPr+/MFo0p6VrqGZpYmobbTYNqulZt
vnFhzXaWPF0aofhm26B5F2GwywTyJoRaMkKgFhhi1PhZnLzRU5r1IV666LfgNW7/
F+VOiBj54Y3ir2dlztej4AkUQAgjGEtbLOEM2sJixCCBLVE/iJXU7yP1cC4+98dn
sYF+RirvTvtMZOcAMDiaoOgeUhDEVg8s2DCoMEI9j+NAAReyDxbUbYZ0iNqAXH4b
jxwndYTCkESqBnrJfOirJPt2a0FpBtYhd+jr4CNUpzGWjvEgrZi/LplPMnstxfsH
Uequbl4gOieIzEhS0Xtmj8K2ivXu8bh3PIoQczQLB4NhXWhc5bk=
=MXNr
-----END PGP SIGNATURE-----
pgpe0JNj2j1Mf.pgp
Description: PGP signature
--- End Message ---
