Your message dated Fri, 28 Jan 2005 05:47:13 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288829: fixed in apt-proxy 1.9.25
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; 5 Jan 2005 21:28:49 +0000
>From [EMAIL PROTECTED] Wed Jan 05 13:28:49 2005
Return-path: <[EMAIL PROTECTED]>
Received: from wavehammer.waldi.eu.org [82.139.196.55] (postfix)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CmIi0-00055L-00; Wed, 05 Jan 2005 13:28:49 -0800
Received: by wavehammer.waldi.eu.org (Postfix, from userid 1000)
        id 727463C025; Wed,  5 Jan 2005 22:28:44 +0100 (CET)
Date: Wed, 5 Jan 2005 22:28:44 +0100
From: Bastian Blank <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: apt-proxy - opens database files as root
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA"
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 


--W/nzBZO5zC0uMSeA
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: apt-proxy
Version: 1.9.24
Severity: grave

I deleted the database as it was out of sync and the new is owned by
root.

Bastian

--=20
I'm a soldier, not a diplomat.  I can only tell the truth.
                -- Kirk, "Errand of Mercy", stardate 3198.9

--W/nzBZO5zC0uMSeA
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)

iEYEARECAAYFAkHcXAwACgkQnw66O/MvCNFBhQCfVMWZD5f/9yTIuhhhSuq9OvdM
5IYAoKAC04SNchNYgBFzrVZyKuZ2WCfH
=HRVz
-----END PGP SIGNATURE-----

--W/nzBZO5zC0uMSeA--

---------------------------------------
Received: (at 288829-close) by bugs.debian.org; 28 Jan 2005 10:53:25 +0000
>From [EMAIL PROTECTED] Fri Jan 28 02:53:24 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 1CuTki-0001It-00; Fri, 28 Jan 2005 02:53:24 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1CuTej-0007OZ-00; Fri, 28 Jan 2005 05:47:13 -0500
From: Chris Halls <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#288829: fixed in apt-proxy 1.9.25
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 28 Jan 2005 05:47:13 -0500
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: apt-proxy
Source-Version: 1.9.25

We believe that the bug you reported is fixed in the latest version of
apt-proxy, which is due to be installed in the Debian FTP archive:

apt-proxy_1.9.25.dsc
  to pool/main/a/apt-proxy/apt-proxy_1.9.25.dsc
apt-proxy_1.9.25.tar.gz
  to pool/main/a/apt-proxy/apt-proxy_1.9.25.tar.gz
apt-proxy_1.9.25_all.deb
  to pool/main/a/apt-proxy/apt-proxy_1.9.25_all.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.
Chris Halls <[EMAIL PROTECTED]> (supplier of updated apt-proxy 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: Fri, 28 Jan 2005 10:26:49 +0000
Source: apt-proxy
Binary: apt-proxy
Architecture: source all
Version: 1.9.25
Distribution: unstable
Urgency: low
Maintainer: Otavio Salvador <[EMAIL PROTECTED]>
Changed-By: Chris Halls <[EMAIL PROTECTED]>
Description: 
 apt-proxy  - Debian archive proxy and partial mirror builder development
Closes: 288829
Changes: 
 apt-proxy (1.9.25) unstable; urgency=low
 .
   * Postpone database creating to first request. Closes: #288829. (Otavio)
   * Reorganise Backends. Now the packages databse is not opened multiple
     times for each alternative URL given.
   * Each [backend] section in apt-proxy.conf creates a new class Backend
   * Each URL in the backend section creates a new class BackendServer
   * New class layout is:
       Backend -> base, packages database, list of BackendServers
       BackendServer -> fetcher, host, port, user etc
   * init script: Change twistd2.3->twistd to help python transitions
   * apt-proxy.conf: Add ubuntu and ubuntu-security archives
Files: 
 2b742cf6c26ee99800b3aaac4957d59f 638 admin extra apt-proxy_1.9.25.dsc
 0f92ea4aba881774b48563c5e8589f58 63361 admin extra apt-proxy_1.9.25.tar.gz
 13b528f253066042eac94d0d5a61bb03 59170 admin extra apt-proxy_1.9.25_all.deb

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

iD8DBQFB+hSgexmdExmX588RAlCNAJ0YM1TXPjMAGqZMHMZSkZAZRqkw+QCgkR2D
IzMt1KT9A5sU++OT3Wifp3I=
=SdFl
-----END PGP SIGNATURE-----


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

Reply via email to