Your message dated Fri, 18 Mar 2005 23:47:07 -0800
with message-id <[EMAIL PROTECTED]>
and subject line yacas: #276782 is still present in sarge
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; 12 Feb 2005 21:21:53 +0000
>From [EMAIL PROTECTED] Sat Feb 12 13:21:53 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mailout.stusta.mhn.de [141.84.69.5] 
        by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
        id 1D04i9-0007ym-00; Sat, 12 Feb 2005 13:21:53 -0800
Received: (qmail 11946 invoked from network); 12 Feb 2005 21:21:21 -0000
Received: from r063144.stusta.swh.mhn.de (10.150.63.144)
  by mailout.stusta.mhn.de with SMTP; 12 Feb 2005 21:21:21 -0000
Received: by r063144.stusta.swh.mhn.de (Postfix, from userid 1000)
        id 15E4BBBF90; Sat, 12 Feb 2005 22:21:18 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Adrian Bunk <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: yacas: #276782 is still present in sarge
X-Mailer: reportbug 3.2
Date: Sat, 12 Feb 2005 22:21:18 +0100
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: yacas
Version: 1.0.55-6
Severity: grave
Tags: sarge



This is a reminder that the archived bug #276782 (yacas: Doesn't run)
is still present in sarge.

---------------------------------------
Received: (at 294993-done) by bugs.debian.org; 19 Mar 2005 07:47:10 +0000
>From [EMAIL PROTECTED] Fri Mar 18 23:47:10 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (localhost.localdomain) 
[66.93.39.86] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DCYfu-0001UZ-00; Fri, 18 Mar 2005 23:47:10 -0800
Received: by localhost.localdomain (Postfix, from userid 1000)
        id 10B18171D21; Fri, 18 Mar 2005 23:47:07 -0800 (PST)
Date: Fri, 18 Mar 2005 23:47:07 -0800
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: yacas: #276782 is still present in sarge
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="QNDPHrPUIc00TOLW"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 


--QNDPHrPUIc00TOLW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

yacas 1.0.57-2 has transitioned to sarge, therefore I believe this bug
should be closed now.

Thanks,
--=20
Steve Langasek
postmodern programmer

--QNDPHrPUIc00TOLW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCO9jwKN6ufymYLloRAgx9AKDT9PLiuSjZb8HTU/VC1ZY7zHqNUgCgxBOX
R345iEmWKLkKPSqhe42Pp00=
=1BH5
-----END PGP SIGNATURE-----

--QNDPHrPUIc00TOLW--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to