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

Re: Bug#1032623: lintian-brush: vcswatch should not raise error on repos > 1GiB in size



Hi,

On Friday, 10 March 2023 12:47:45 CET Christoph Berg wrote:
> Re: Diederik de Haas
> > 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.
> 
> quantz.debian.org has been running out of disk space several times in
> the past years, and blacklisting the biggest repos helped a lot.
> (There are some that are even > 4 GB.)

Ok, I can understand the limit being put in place.
OTOH, running out of disk space is a problem and 1-4GB is not *that* big IMO 
and that issue should be resolved (asap).

> Specifically on the kernel, vcswatch is of limited use anyway since
> there are several packages using the repo, but only one of them
> ("linux") contains a debian/changelog where the package name matches.
> On "linux", I had the impression that the vcswatch info would be
> helpful in practise, but I forgot the details.
> 
> Were you able to see useful vcswatch info on the kernel packages in
> the past?

I'm a big fan of automated checks, be it Salsa's CI or vcswatch or (pretty 
much) any other tool.
I don't know if vcswatch (specifically) provided useful information in the 
past. Possibly it didn't report an issue before the size limit was imposed. 
That is useful info and it becomes even more useful if it would find an actual 
issue.

I think tracker.d.o is awesome and when looking for ways to contribute to a 
package, I often check the 'action needed' section and work on that.
But when it reports an issue which can not be solved, like in this case, then 
I find that problematic as it then lowers the barier to also ignore other 
issues. In Salsa's CI I tend to disable a test rather then allow failure, so 
when the result is not all green, I should take action.

The best solution would be to fix it at the source (bigger HDD?), but if that's 
not feasible (in the short term), then don't turn the 1GiB self-imposed limit 
into a 'problem' (to be fixed) for someone else.
IOW: filter out this specific issue.

Cheers,
  Diederik

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: