Bug#222639: apt: Cache-Limit influences Release processing, without notice on failure
On Wed, Dec 03, 2003 at 10:36:39AM -0700, Jason Gunthorpe wrote:
>
> On Mon, 1 Dec 2003, Yann Dirson wrote:
>
> > If the Cache-Limit is raised from 10M to 100M, and the cache rebuilt,
> > then:
>
> I really doubt this is the source of your problem, there are error
> messages when the limit is hit.
When it is hit while processing packages, yes, I've hit it in the
past. Looks like something is not caught when processing the Release
file.
> IIRC apt does not reload the release file unless the package file is also
> changed. So if you are messing around with it you probably ran into this
> problem instead.
I've ran into it several times while investigating, and take good care
of this with the final reproduction from which I cut'n'pasted the
lines in the report.
I started from the "fixed" state at 100M, where "apt-cache policy"
showed 995, went down to 10M, where it showed 500, then back to 100M,
where it showed 995 again. I'm quite confident that rules out the
problem (which I think should be considered more than "wishlist", as
the current issue somewhat shows) of the Release file not being
sufficient to trigger cache regeneration.
Regards,
--
Yann Dirson <ydirson@altern.org> | Why make M$-Bill richer & richer ?
Debian-related: <dirson@debian.org> | Support Debian GNU/Linux:
Pro: <yann.dirson@fr.alcove.com> | Freedom, Power, Stability, Gratuity
http://ydirson.free.fr/ | Check <http://www.debian.org/>
Reply to: