Your message dated Wed, 06 Mar 2024 14:13:20 +0000
with message-id <65e87a00c054a_2433439607...@godard.mail>
and subject line Bug#1032623 fixed in qa.debian.org
has caused the Debian Bug report #1032623,
regarding vcswatch: should not raise error on repos > 1GiB in size
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 ow...@bugs.debian.org
immediately.)
--
1032623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian-brush
Version: 0.147
Severity: normal
X-Debbugs-Cc: debian-qa@lists.debian.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I'm not sure this is the right package, but filed it against
lintian-brush as it contains vcswatch.py.
On https://tracker.debian.org/pkg/linux there is a high-priority action
needed item because vcswatch "Failed to analyze the VCS repository".
The reason: "Repository size 1135554560 exceeds 1 GiB, blocking it"
So I queried `udd` to see what it had to tell:
udd=> select vcs, url, status, error from vcswatch where source = 'linux';
vcs | url | status |
error
-
-----+------------------------------------------------+--------+-------------------------------------------------------
Git | https://salsa.debian.org/kernel-team/linux.git | ERROR | Repository
size 1135554560 exceeds 1 GiB, blocking it
(1 row)
The thing is that the Debian kernel repository is big and that's NOT an
error; it's just big. There is no need to take action to fix it.
AFAIC, the error is in the tool that put the error in udd.
I don't know the reason for this (self-imposed?) limit is, but IMO that
limit should be removed or contain some allow-list with src:linux in it,
so that it will still be scanned.
Alternatively (or in addition to), `vcswatch` should not propagate the
error when it's due to the limit of 1 GiB in repo size.
Cheers,
Diederik
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lintian-brush depends on:
ii devscripts 2.23.2
ii python3 3.11.2-1
ii python3-asyncpg 0.27.0-1+b2
ii python3-breezy 3.3.2-2+b1
ii python3-debian 0.1.49
ii python3-debmutate 0.65
ii python3-distro-info 1.5
ii python3-dulwich 0.21.2-1+b1
ii python3-iniparse 0.5-1
ii python3-iso8601 1.0.2-1
ii python3-levenshtein 0.12.2-2+b4
ii python3-pyinotify 0.9.6-2
ii python3-ruamel.yaml 0.17.21-1
ii python3-semver 2.10.2-3
ii python3-tomlkit 0.11.6-1
ii python3-tqdm 4.64.1-1
ii python3-upstream-ontologist 0.1.35-1
Versions of packages lintian-brush recommends:
ii debhelper 13.11.4
ii decopy 0.2.4.8-0.1
ii dos2unix 7.4.3-1
ii gpg 2.2.40-1
ii lintian 2.116.3
ii ognibuild 0.0.18+git20230208.1.9b890a2-1
ii python3-bs4 4.11.2-2
ii python3-debianbts 4.0.1
ii python3-docutils 0.19+dfsg-6
ii python3-lxml 4.9.2-1+b1
ii python3-markdown 3.4.1-2
Versions of packages lintian-brush suggests:
ii brz-debian 2.8.76
ii git-buildpackage 0.9.30
pn gnome-pkg-tools <none>
ii po-debconf 1.0.21+nmu1
ii postgresql-common 247
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCZAsTEwAKCRDXblvOeH7b
buACAP9LooUG2xFr3Eg2SwUHLijgXzGIOEktqJUXcCdem+E0PwD/Q3tOIar0KoUf
ott/cpmwos9YVvahGpCanHDSfcBpjgU=
=FaJq
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hello,
Bug #1032623 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/d404abd20e11b8bbad551b5991eaf0a0a8220fc2
------------------------------------------------------------------------
vcswatch: Use --filter blob:none
Required blobs (changelog, control, upstream metadata) are fetched by
git on demand. Thanks to Gábor Németh for the suggestion!
Closes: #1032623
------------------------------------------------------------------------
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1032623
--- End Message ---
