Your message dated Mon, 2 Aug 2004 14:54:40 +0200
with message-id <[EMAIL PROTECTED]>
and subject line synchronization between dehs and developer.php
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; 27 Jul 2004 10:39:42 +0000
>From [EMAIL PROTECTED] Tue Jul 27 03:39:42 2004
Return-path: <[EMAIL PROTECTED]>
Received: from master.debian.org [146.82.138.7] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BpPN0-0000Sn-00; Tue, 27 Jul 2004 03:39:42 -0700
Received: from dsl-082-082-224-080.arcor-ip.net (pezone.net) [82.82.224.80] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BpPMz-0007Q5-00; Tue, 27 Jul 2004 05:39:41 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Peter Eisentraut <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: developer.php: watch error details missing
X-Mailer: reportbug 2.63
Date: Tue, 27 Jul 2004 12:39:40 +0200
X-Debbugs-Cc: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-9.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
        OUR_MTA_MSGID,X_DEBBUGS_CC autolearn=ham 
        version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: qa.debian.org
Severity: normal

Example: Go to

    http://qa.debian.org/[EMAIL PROTECTED]

For the package "pinentry", the column "watch/upstream unstable" shows an
error.  A click on "Details" leads to

    http://dehs.alioth.debian.org/maintainer.php?name=pinentry

which shows nothing about pinentry, but instead a search page.  If there
are no details available, please remove the link, but I'd really be
interested what the error is.  (uscan works locally.)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-1-586tsc
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]

---------------------------------------
Received: (at 261645-done) by bugs.debian.org; 2 Aug 2004 12:54:46 +0000
>From [EMAIL PROTECTED] Mon Aug 02 05:54:46 2004
Return-path: <[EMAIL PROTECTED]>
Received: from atoulouse-201-2-1-120.w193-251.abo.wanadoo.fr (genibel.org) 
[193.251.11.120] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BrcKy-0005IF-00; Mon, 02 Aug 2004 05:54:45 -0700
Received: by genibel.org
        via sendmail from stdin
        id <[EMAIL PROTECTED]> (Debian Smail3.2.0.115)
        Mon, 2 Aug 2004 14:54:41 +0200 (CEST) 
From: Igor Genibel <[EMAIL PROTECTED]>
Organization: Debian GNU/Linux
To: [EMAIL PROTECTED]
Subject: synchronization between dehs and developer.php
Date: Mon, 2 Aug 2004 14:54:40 +0200
User-Agent: KMail/1.6.2
MIME-Version: 1.0
Content-Type: multipart/signed;
  protocol="application/pgp-signature";
  micalg=pgp-sha1;
  boundary="Boundary-02=_RmjDBCHetUoKrpA";
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (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_2004_03_25
X-Spam-Level: 


--Boundary-02=_RmjDBCHetUoKrpA
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

As Stefano said, it was certainly due to a synchronization problem=20
between the two system. Since now this bug did not reappers, so let's=20
close it :)
Do not hesitate to reopen it if not

Thanks
=2D-=20
Igor Genibel=20
http://www.answare.fr/                             [EMAIL PROTECTED]
http://www.tuxfamily.org/                            [EMAIL PROTECTED]
http://people.debian.org/~igenibel/                 [EMAIL PROTECTED]
GPG: 1024D/1648F6C8

--Boundary-02=_RmjDBCHetUoKrpA
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQBBDjmR+xgdMBZI9sgRAk0uAJ0XUvf4Nl5evJ5YlvPTPFju7k2A6QCdEH6Y
EzrQlV+9KW2pbhcnq4yQNRM=
=/dcZ
-----END PGP SIGNATURE-----

--Boundary-02=_RmjDBCHetUoKrpA--

Reply via email to