[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#166047: marked as done (apt.conf(8) should document the default for APT::Cache-Limit)



Your message dated Wed, 23 Oct 2002 11:04:25 -0600 (MDT)
with message-id <[🔎] Pine.LNX.3.96.1021023110155.24661B-100000@wakko.debian.net>
and subject line Bug#166047: apt.conf(8) should document the default for APT::Cache-Limit
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; 23 Oct 2002 14:46:49 +0000
>From ydirson@fr.alcove.com Wed Oct 23 09:46:48 2002
Return-path: <ydirson@fr.alcove.com>
Received: from ns1.alcove-solutions.com (smtp-out.fr.alcove.com) [212.155.209.139] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 184MmW-0001fF-00; Wed, 23 Oct 2002 09:46:48 -0500
Received: from vitel.alcove-fr ([10.16.10.8])
	by smtp-out.fr.alcove.com with esmtp (Exim 3.12 #1 (Debian))
	id 184MlI-0008Oo-00; Wed, 23 Oct 2002 16:45:32 +0200
Received: from ydirson by vitel.alcove-fr with local (Exim 3.35 #1 (Debian))
	id 184MmR-0002QY-00; Wed, 23 Oct 2002 16:46:43 +0200
Date: Wed, 23 Oct 2002 16:46:43 +0200
From: Yann Dirson <dirson@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: apt.conf(8) should document the default for APT::Cache-Limit
Message-ID: <[🔎] 20021023144642.GA9253@vitel.alcove-fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.3.25i
X-Reportbug-Version: 1.50
Sender: Yann Dirson <ydirson@fr.alcove.com>
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-7.2 required=5.0
	tests=SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01,USER_AGENT,
	      USER_AGENT_MUTT
	version=2.41
X-Spam-Level: 

Package: apt
Version: 0.5.4
Severity: normal

When needed (ie. too many sources listed), a trial-and-error is
required to find a suitable value for APT::Cache-Limit, because:

1/ there is no default value listed in apt.conf(8)
2/ apt-config does not list one either

For the record, with the current default value, I cannot have at the
same time potato, woody, sid (main, contrib,non-free,non-US), plus a
deb-src for woody and sid, plus a (small) local repository of
backported packages.


Also, it may be worthwile to mention that it is only used when
"apt-cache gencaches" needs to rebuild the caches.  This would reduce
potential confusion, because if one rereuns, say, "apt-get update",
even with a ridiculously low value, there is an apparent success,
which is only due to the fact the parameter is not used (or at least
it's my understanding).

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux vitel 2.4.19-station #1 Tue Aug 6 11:36:58 CEST 2002 i686
Locale: LANG=french, LC_CTYPE=french

Versions of packages apt depends on:
ii  libc6                         2.2.5-6    GNU C Library: Shared libraries an
ii  libstdc++2.10-glibc2.2        1:2.95.4-7 The GNU stdc++ library

-- 
Yann Dirson <Yann.Dirson@fr.alcove.com>                 http://www.alcove.com/
Technical support manager                Responsable de l'assistance technique
Senior Free-Software Consultant          Consultant senior en Logiciels Libres
Debian developer (dirson@debian.org)                        Développeur Debian

---------------------------------------
Received: (at 166047-done) by bugs.debian.org; 23 Oct 2002 17:06:23 +0000
>From jgg@debian.org Wed Oct 23 12:06:23 2002
Return-path: <jgg@debian.org>
Received: from shawidc-mo1.cg.shawcable.net (pd6mo1so.prod.shaw.ca) [24.71.223.10] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 184Oxb-0005S9-00; Wed, 23 Oct 2002 12:06:23 -0500
Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-ser.prod.shaw.ca [10.0.141.178])
 by l-daemon (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 12 2002))
 with ESMTP id <0H4G00E2X23EH6@l-daemon> for 166047-done@bugs.debian.org; Wed,
 23 Oct 2002 11:04:26 -0600 (MDT)
Received: from pn2ml7so.prod.shaw.ca
 (pn2ml7so-qfe0.prod.shaw.ca [10.0.121.151]) by l-daemon
 (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 12 2002))
 with ESMTP id <0H4G00DFH23DBL@l-daemon> for 166047-done@bugs.debian.org; Wed,
 23 Oct 2002 11:04:26 -0600 (MDT)
Received: from wakko.debian.net ([24.86.210.128])
 by l-daemon (iPlanet Messaging Server 5.1 HotFix 0.8 (built May 12 2002))
 with ESMTP id <0H4G00EIM23D0P@l-daemon> for 166047-done@bugs.debian.org; Wed,
 23 Oct 2002 11:04:25 -0600 (MDT)
Received: from localhost	([127.0.0.1] helo=wakko.debian.net ident=jgg)
	by wakko.debian.net with smtp (Exim 3.35 #1 (Debian))
	id 184Ovh-0006RH-00; Wed, 23 Oct 2002 11:04:25 -0600
Date: Wed, 23 Oct 2002 11:04:25 -0600 (MDT)
From: Jason Gunthorpe <jgg@debian.org>
Subject: Re: Bug#166047: apt.conf(8) should document the default for
 APT::Cache-Limit
In-reply-to: <[🔎] 20021023144642.GA9253@vitel.alcove-fr>
X-Sender: jgg@wakko.debian.net
To: Yann Dirson <dirson@debian.org>, 166047-done@bugs.debian.org
Cc: APT Development Team <deity@lists.debian.org>, apt@packages.qa.debian.org
Message-id: <[🔎] Pine.LNX.3.96.1021023110155.24661B-100000@wakko.debian.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Delivered-To: 166047-done@bugs.debian.org
X-Spam-Status: No, hits=-8.1 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      SPAM_PHRASE_00_01,USER_AGENT_PINE
	version=2.41
X-Spam-Level: 


On Wed, 23 Oct 2002, Yann Dirson wrote:

> 1/ there is no default value listed in apt.conf(8)
> 2/ apt-config does not list one either

All the default values for all the parameters are in
/usr/share/doc/apt/examples/configure-index.

I notice the cache-limit one is actually wrong at the moment, it's
actually 6 meg.
 
> even with a ridiculously low value, there is an apparent success,
> which is only due to the fact the parameter is not used (or at least
> it's my understanding).

It's only used when it is actually going to generate caches, whihc is done
by update if the list files have changed.

Jason



Reply to: