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

Bug#1118031: Unable to detect when local and remote metadata no longer matches



Control: severity -1 normal

(lowered severity since it sounds like this issue may be unique to my
system for some reason)

On Tue, 14 Oct 2025 10:44:02 +0200 =?UTF-8?Q?St=C3=A9phane_Glondu?=
<glondu@debian.org> wrote:
> Hi,
> 
> Le 14/10/2025 à 01:35, Aaron Rainbolt a écrit :
> > [...] approx
> > does not seem to store any metadata that would allow it to determine
> > when some part of metadata has gone out of date however. [...]
> 
> Approx uses filesystem metadata (mtime and ctime) for that... Maybe
> the issues you face is related to your filesystem: what is it?

ext4, mounted with relatime enabled (which is what the Trixie
netinstaller gave me by default).

> > The "interval" feature in approx.conf appears to be designed to
> > prevent this exact scenario, and according to /etc/approx.conf it
> > defaults to 60 minutes. [...]
> 
> This should address your issue.
> 
> I do use approx myself on my regular laptop (with btrfs,relatime),
> and I do not observe what you describe: there might be a slight delay
> (60 minutes, I guess) before getting updates, but I always get them
> eventually.
> 
> Have you tried setting interval to a smaller value (like 0)?

I have not, since 60 minutes of buffer isn't a problem for me. However,
I will try setting it to something smaller and see what happens. (I
might not be back with results all that quickly, but I should be able
to report back how things work after a couple weeks or so.

> 
> Cheers,
> 
> -- 
> Stéphane
> 
> 
> 

Attachment: pgpgX6KkYDu2n.pgp
Description: OpenPGP digital signature


Reply to: