Your message dated Sat, 07 May 2005 20:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#306768: fixed in beecrypt 4.1.2-1
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 28 Apr 2005 11:47:54 +0000
>From [EMAIL PROTECTED] Thu Apr 28 04:47:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ns.bitdefender.com (mail.bitdefender.com) [217.156.83.1]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DR7Un-0003vD-00; Thu, 28 Apr 2005 04:47:54 -0700
Received: (qmail 12651 invoked by uid 1010); 28 Apr 2005 14:41:15 +0300
Received: from mmaties.dsd.ro (HELO nox.xcyb.org) (10.10.16.18)
by mail.bitdefender.com with SMTP; 28 Apr 2005 14:41:15 +0300
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Mihai Maties <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: beecrypt: Outdated version provided in Debian
X-Mailer: reportbug 3.9
Date: Thu, 28 Apr 2005 14:48:14 +0300
X-Debbugs-Cc: [EMAIL PROTECTED]
X-BitDefender-SpamStamp: 1.1.3 044000040111AB
X-BitDefender-Scanner: Clean, Agent: BitDefender Qmail 1.6.1 on
mail.bitdefender.com
X-BitDefender-Spam: No (1)
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: beecrypt
Severity: normal
The beecrypt version included in Debian (2.2.0-pre1) is 3 years old.
Major development was done during this time and the upstream version is
now 4.1.2. Is there any reason for not upgrading this package ?
The reason I'm requesting this is that a newer version of beecrypt is
required in order to build other packages.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
--
This message was scanned for spam and viruses by BitDefender.
For more information please visit http://linux.bitdefender.com/
---------------------------------------
Received: (at 306768-close) by bugs.debian.org; 8 May 2005 00:38:02 +0000
>From [EMAIL PROTECTED] Sat May 07 17:38:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DUZo2-0000wd-00; Sat, 07 May 2005 17:38:02 -0700
Received: from joerg by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DUZjI-0002gd-00; Sat, 07 May 2005 20:33:08 -0400
From: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: lisa $Revision: 1.30 $
Subject: Bug#306768: fixed in beecrypt 4.1.2-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Joerg Jaspert <[EMAIL PROTECTED]>
Date: Sat, 07 May 2005 20:33:08 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Source: beecrypt
Source-Version: 4.1.2-1
We believe that the bug you reported is fixed in the latest version of
beecrypt, which is due to be installed in the Debian FTP archive:
beecrypt_4.1.2-1.diff.gz
to pool/main/b/beecrypt/beecrypt_4.1.2-1.diff.gz
beecrypt_4.1.2-1.dsc
to pool/main/b/beecrypt/beecrypt_4.1.2-1.dsc
beecrypt_4.1.2.orig.tar.gz
to pool/main/b/beecrypt/beecrypt_4.1.2.orig.tar.gz
libbeecrypt6-dev_4.1.2-1_i386.deb
to pool/main/b/beecrypt/libbeecrypt6-dev_4.1.2-1_i386.deb
libbeecrypt6_4.1.2-1_i386.deb
to pool/main/b/beecrypt/libbeecrypt6_4.1.2-1_i386.deb
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.
Anibal Monsalve Salazar <[EMAIL PROTECTED]> (supplier of updated beecrypt
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: SHA1
Format: 1.7
Date: Sun, 01 May 2005 13:38:31 +1000
Source: beecrypt
Binary: libbeecrypt6-dev libbeecrypt6
Architecture: source i386
Version: 4.1.2-1
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Description:
libbeecrypt6 - open source C library of cryptographic algorithms
libbeecrypt6-dev - header files for beecrypt, a library of cryptographic
algorithms
Closes: 306768
Changes:
beecrypt (4.1.2-1) unstable; urgency=low
.
* New upstream release, closes: #306768.
Sync with ubuntu.
Files:
3f137f548699362727eb7b78eb29f1b9 604 devel optional beecrypt_4.1.2-1.dsc
820d26437843ab0a6a8a5151a73a657c 774280 devel optional
beecrypt_4.1.2.orig.tar.gz
94b96ae5e14dc54fa87a4e6d3d58d3fa 4459 devel optional beecrypt_4.1.2-1.diff.gz
7995e53a3bfa27147bbe46316c75ee16 129002 devel optional
libbeecrypt6-dev_4.1.2-1_i386.deb
3c4c5582be7caad18b2407c91750739a 95604 libs optional
libbeecrypt6_4.1.2-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCdFHPgY5NIXPNpFURAlcEAJ9Qz1iOCvXZ0wDAUuiwzEAHUOKzEgCdFIkT
VrJ6ESigmWJ3aiIF4w1vRkA=
=H9Q8
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
