Your message dated Sat, 30 Nov 2024 10:25:45 +0100 with message-id <[email protected]> and subject line Re: Bug#1088731: vcswatch confusion: e2fsprogs does not exceeds 500 MiB has caused the Debian Bug report #1088731, regarding vcswatch confusion: e2fsprogs does not exceeds 500 MiB 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.) -- 1088731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088731 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: qa.debian.org Severity: normal Per https://qa.debian.org/cgi-bin/vcswatch?package=e2fsprogs The e2fsprogs repository is blocked because: Repository size 537583616 exceeds 500 MiB, blocking it However, this is very clearly not the case: % git clone https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git -b debian/master Cloning into 'e2fsprogs'... remote: Enumerating objects: 59697, done. % du -sh e2fsprogs 77M e2fsprogs % du -sh e2fsprogs/.git 45M e2fsprogs/.git This is very clearly *not* greater than 500 MiB, and I can't think of any time when this might have been the case. Can someone debug why this is the case, and/or just unblock e2fsprogs? Many thanks! - Ted
--- End Message ---
--- Begin Message ---Re: Theodore Y. Ts'o > The e2fsprogs repository is blocked because: > > Repository size 537583616 exceeds 500 MiB, blocking it > > However, this is very clearly not the case: > > % git clone https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git -b > debian/master > Cloning into 'e2fsprogs'... > remote: Enumerating objects: 59697, done. > % du -sh e2fsprogs > 77M e2fsprogs > % du -sh e2fsprogs/.git > 45M e2fsprogs/.git Hi Ted, the repo is indeed 43MB after re-cloning it, it will be scanned normally now. > Can someone debug why this is the case, and/or just unblock e2fsprogs? I don't know the git protocol, but I suspect that some fetching methods aren't very smart and re-fetch large chunks of the repo, adding up to a final size that is much larger than a fresh clone. Christoph
--- End Message ---
