Your message dated Fri, 31 Jul 2015 18:42:16 +0200
with message-id <[email protected]>
and subject line Re: Close bug?
has caused the Debian Bug report #693399,
regarding New upstream version available with KeePass 2 format support
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.)
--
693399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693399
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: keepassx
Version: 0.4.3-2
Severity: wishlist
Tags: patch
Hi,
since I needed support for the KeePass 2 file format, I went ahead and
package the 2.0 alpha3 release.
This version still lacks many of the features of 0.4.x but it should be
good enough for experimental.
I thought this might be useful to you, so I've uploaded my work to [1].
Michael
[1] http://people.debian.org/~biebl/keepassx/
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages keepassx depends on:
ii libc6 2.13-36
ii libgcrypt11 1.5.0-3
ii libqt4-dbus 4:4.8.2+dfsg-2
ii libqtcore4 4:4.8.2+dfsg-2
ii libqtgui4 4:4.8.2+dfsg-2
ii libstdc++6 4.7.2-4
ii zlib1g 1:1.2.7.dfsg-13
keepassx recommends no packages.
keepassx suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.0~alpha6-1
On Fri, 31 Jul 2015 16:43:18 +0200 Diederik de Haas <[email protected]>
wrote:
> Since KeePassX 2.0~beta1-1 is in experimental, it looks like this bug can be
> closed.
Yes, indeed.
Thanks,
Felix
--- End Message ---
