Your message dated Tue, 11 Apr 2006 04:51:35 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#361792: yafc: Newer upstream version, fixes some
potentially serious bugs
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: yafc
Version: 1.1-4
Severity: normal
Hi,
There is a new version of yafc upstream. Some of the changes seem to
address some potentially serious problems (including password problems?):
* Applied patch by Norihiko Murase for ls -t (timestamp) fix
* Double fclose() segfault fix
* autoconf herror include fix
* Modified code to use strtoul / strtoull
* Changed getpass hook to use new code (fixes ctrl+c password local echo bug)
* Updated TODO
* Confirmed remaining bugs as fixed or non-issues
* Added KNOWN_ISSUES file
Cheers,
Steve
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.4
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages yafc depends on:
ii libc6 2.3.6-5 GNU C Library: Shared libraries an
ii libncurses5 5.5-1 Shared libraries for terminal hand
ii libreadline5 5.1-7 GNU readline and history libraries
yafc recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Steve writes:
> There is a new version of yafc upstream. Some of the changes seem to
> address some potentially serious problems (including password problems?):
Thanks for this. I was hoping there might be some further activity from
upstream, as the 1.1.1 tarball was messed up, but I guess not; I will
bug them about it again...
--
things change.
[EMAIL PROTECTED]
--- End Message ---
