Your message dated Tue, 18 Dec 2018 21:04:58 -0800
with message-id
<CAFHYt57EsYmNfz3skt_PucRh=_ga7cjoqgyziwtuxfnsq8v...@mail.gmail.com>
and subject line Report outdated
has caused the Debian Bug report #912454,
regarding gocryptfs: new upstream release
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.)
--
912454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912454
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gocryptfs
Version: 1.4.3-7
Severity: normal
The latest upstream release is 1.6. For cryptographic software like
this I figure it's important to keep up-to-date, especially with the
fsck functions and other features in 1.5. Is it straightforward to
package the new version?
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gocryptfs depends on:
ii libc6 2.27-6
ii libfuse2 2.9.8-2
ii libssl1.1 1.1.1-1
gocryptfs recommends no packages.
gocryptfs suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Gocryptfs 1.6 depended on versions of go-fuse and xattr that were not
available in Debian at the time. I do not think there was a
cryptographic advantage over version 1.4.3. Either way, you can
already find a newer version in the archive.
--- End Message ---
