Your message dated Wed, 18 Feb 2026 13:13:28 +0000
with message-id <[email protected]>
and subject line Bug#1107620 fixed in qa.debian.org
has caused the Debian Bug report #1107620,
regarding vcswatch: e2fsprogs: repository blocked even though it is nowhere
near 500MiB
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1107620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107620
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qa.debian.org
Severity: normal
Dear Maintainer,
Hi,
I was recently looking at the tracker page for e2fsprogs, and I
noticed that there was the VFS watch error: "Failed to analyze the VCS
repository. Please troubleshoot and fix the issue."
Looking at this this page [1] the complaint seems to be: "Repository
size 531054592 exceeds 500 MiB, blocking it". However, looking at the
e2fsprogs git repo, the bare repo (just the git packs) is only 43
megs, and the checked out working tree is 41 megs. I'm not sure why
the repo on VCS watch is over 500 MiB, but could it be that it's in
deperate need of having a "git gc" being run on it?
[1] https://qa.debian.org/cgi-bin/vcswatch?package=e2fsprogs
Note, this isn't the first time this has come up. The last time I
reported it to the debian-qa mailing list on July 25, 2024. Perhaps
there needs to be an automated "git gc" run on the git clones of the
repos which are used by vcswatch?
Thanks,
- Ted
--- End Message ---
--- Begin Message ---
Hello,
Bug #1107620 in qa.debian.org reported by you has been fixed in the Git
repository.
You can see the commit message below and you can check the diff of the fix at:
https://salsa.debian.org/qa/qa/-/commit/f38bb8d61a132cd65eebc35e5e37ab71d5914239
------------------------------------------------------------------------
vcswatch: Force a «git gc» after fetch to avoid hitting repo quotas
The current code requests a depth of 50 commits, and requests auto
garbage collection after 200 loose objects are in the repository.
The problem is that on each fetch we might get a pack with all the
relevant object, which will be duplicated with the packs for the
previous fetches, where there will be no loose objects. These will
keep stacking and then we will hit the repository quota, and further
fetching will be completely disabled.
Instead, request that we do not want more than 4 non-keep packs,
before triggering an auto garbage collection.
Closes: #1107620
Ref: #1072498
------------------------------------------------------------------------
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1107620
--- End Message ---
