Your message dated Tue, 15 Aug 2023 12:04:37 +0000
with message-id <e1qvsmr-008ksi...@fasolo.debian.org>
and subject line Bug#1034009: fixed in gocryptfs 2.4.0-1
has caused the Debian Bug report #1034009,
regarding gocryptfs: Missing fuse in package dependency
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 ow...@bugs.debian.org
immediately.)


-- 
1034009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gocryptfs
Version: 1.8.0-1+b6
Severity: normal
X-Debbugs-Cc: debian-bugrep...@frost-it.de

Dear Maintainer,

please add the fuse package as an dependency for gocryptfs.

See https://github.com/rfjakob/gocryptfs the section Installation.

"The fuse package from your distribution must be installed for mounting to 
work."

Mounting is an essential component in gocryptfs. So setting fuse as an 
installation dependency it makes the use of gocryptfs more comportable after an
installation. Otherwise you must install it manual, that is the current way.

Thanks,
Christian


-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-20-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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

Versions of packages gocryptfs depends on:
ii  libc6      2.31-13+deb11u5
ii  libfuse2   2.9.9-5
ii  libssl1.1  1.1.1n-0+deb11u4

gocryptfs recommends no packages.

gocryptfs suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: gocryptfs
Source-Version: 2.4.0-1
Done: Unit 193 <unit...@debian.org>

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

Debian distribution maintenance software
pp.
Unit 193 <unit...@debian.org> (supplier of updated gocryptfs 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 11 Aug 2023 18:06:13 -0400
Source: gocryptfs
Architecture: source
Version: 2.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<pkg-go-maintain...@lists.alioth.debian.org>
Changed-By: Unit 193 <unit...@debian.org>
Closes: 1034009
Changes:
 gocryptfs (2.4.0-1) unstable; urgency=medium
 .
   [ Unit 193 ]
   * Team upload.
   * New upstream release.
     - Refresh patch.
   * d/p/003-revert-jacobsa-fork.patch:
     - Revert the switch to a jacobsa/crypto fork, not in Debian.
   * d/control:
     - Update (Build-)Depends.
       + B-D: golang-github-moby-sys-dev, golang-golang-x-term-dev.
       + R: fuse3 (Closes: #1034009), S: fido2-tools.
       - B-D: golang-golang-x-sync-dev, fuse, D: libfuse2
     - Add ${misc:Static-Built-Using} to Built-Using.
   * d/rules:
     - Remove some debug calls.
     - Add tests/root_test to disabled tests list.
   * Update Standards-Version to 4.6.2.
 .
   [ Damian Szuberski ]
   * Corrected "watch" file.
Checksums-Sha1:
 133a59719722f9eedfdad3a82a4fbdcf5b19ac14 2588 gocryptfs_2.4.0-1.dsc
 f969a80b4cfcf5ca869d723f3f4487322ef45b01 1134296 gocryptfs_2.4.0.orig.tar.xz
 8c4742b80e3032c85e08580101d210ad8f23cc25 10372 gocryptfs_2.4.0-1.debian.tar.xz
 90d39e695ddd2cb8a7547318e4f51d4d920c2401 7672 gocryptfs_2.4.0-1_amd64.buildinfo
Checksums-Sha256:
 c02d2e9f29796ab1a6fc357a7490450e61dd4e29568d05ac655ac54e091cbf64 2588 
gocryptfs_2.4.0-1.dsc
 7cd65c3fd5f02d822432458e82e4c13223a6e959cb6568ffe5313e88c0a81dbe 1134296 
gocryptfs_2.4.0.orig.tar.xz
 721581a9e96af3b0dee36966fc82729ae44635a92736296e6c70ed48758d9d81 10372 
gocryptfs_2.4.0-1.debian.tar.xz
 47c18d8a27ed06d0c04b5585008024be5f72f97cdc4554e7cf012d090825795f 7672 
gocryptfs_2.4.0-1_amd64.buildinfo
Files:
 0a8d7d9decbac394e628ab51a8832544 2588 devel optional gocryptfs_2.4.0-1.dsc
 c58c300e84ac0667c0ec52b79e3a5ce0 1134296 devel optional 
gocryptfs_2.4.0.orig.tar.xz
 03c3abfa64b22f4132169e452560e94b 10372 devel optional 
gocryptfs_2.4.0-1.debian.tar.xz
 5002a78d868bd9b77dd3bb5e02960fc5 7672 devel optional 
gocryptfs_2.4.0-1_amd64.buildinfo

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

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmTbYlYACgkQUra72VOW
jRs5FQ//Vq98A74yTHgppQuZ/ZciRhMNHg97v155RcY0t5MRpVZsNzmAkWiX4nzD
76pRht2iZ8qSNydtlSVtYK6a04bn/IeGDk8lHLDIsIFZpHTsK5k2WllXI16URJty
CvMCjpgLcN4szCZB+NQHfxDzHiHKWIHf4QSjzl9kgfyzxlxKNxL1uwJHLnvhdgm4
fRG+ohmev/jv6KgWK13GyLwrviQGHPNzIu161tqg3TYRzq1H22p2x1KjnRyXz8gR
gK2pHhUrq+7O/xuP75krfkNx00xMzChTt8+pnVfwpK1kBl/Hbpw6TnRJZsm7/pBd
IjwzbwgueNimDyjUl008SA4fadV/f1PTqyY6wiCiDpk2Bk2tY90yK03wTrU6KK7O
hJ3zMZEMsZ2UM+JNTgAGY6nGpdcUyYCJS9fnITPTwhbyYP9KTjWp5nV983Lf10/0
2K/QvspvCDPFkirDYRCe5Q5ARQrABWswb+I75nqsk+NzA0hpZR1m6AohvrdPhNh+
yQ/7tkWo0ymFS0a7OQVaTWG6wCpLKbCq6M/jURPZfnfdqo/xlEdAp9O60tY7NLsj
NnZgeRtnuxzfUq0rK2oNRjPu6tH5fGDIAsdYaGiKW8I9AiwlxxVzqel+mn+M+avG
qtrzKBeoh5ocZCPHFbhkxH1V1AAFkvUeEHoGzxks4E0KINrhJzs=
=yFJG
-----END PGP SIGNATURE-----

--- End Message ---
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to