Here I am trying to build a new template…and it keeps dying trying to get the latest bookworm stuff–which seems to just happen automatically–I’m not in a salt state where I’m trying to get them; it just insists on trying to get them…and sometimes for hours at a time, it can’t be done.
Is there some way to bypass this and just install the package I am asking for without it?
It is failing to fetch a bunch of Debian Bookworm “InRelease” things claiming it cannot allocate memory. I’ve doubled the memory available in the template. I’m still getting the same thing.
This is blocking me pretty badly. I just want to install Keepass.
Poking around on the internet this is apparently some sort of glitch with apt-cacher-ng.
Generally I can just wait a while–perhaps as long as a couple of hours–and it clears up on its own. But this has been ALL DAY, and I also couldn’t check for updates via the update gui on account of it.
Ditching the cacher allowed my template build to succeed.
If the cacher is this flaky, I probably should stop using it.
Can you provide a reference?
I find apt-cacher-ng flawless, and havent seen the issue you’ve
recorded. How is your caching qube configured for memory use? How did
you install it?
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
Unfortunately, I can’t find the same thing I found a couple of days ago. It had a link to a gripes page (which I didn’t visit) and a claim that it could sometimes do this if too many people were trying to access a repository. Also claimed it got worse under Debian 12.
One thing I did try was a complete rebuild of the cacher (it’s an appvm of course, but could have ended up in some sort of overloaded state). That made no difference…so if even a tabula rasa cacher had the issue, I doubt it’s memory.
I do notice these problems only on my laptop. (Oh, and sometimes the cacher has to be killed; it will hang as it shuts down, but again, only on my laptop (a librem 13)).
Settings between the two systems should be identical thanks to salt.
Whenever I come across people complaining about apt-cacher-ng, I see
others immediately jumping in to say it’s rock solid with no problems.
Just like me in this thread.
This one is a head scratcher for me, because as far as I can recall, I only see these issues on my laptop…on which cacher should be configured identically to my desktop–I do everything with a combination of salt and scripts, and I sync those files (manually) between the two systems.