Bug 274870

Summary:	repoman's file size check should have warning and error areas
Product:	Portage Development	Reporter:	Diego Elio Pettenò (RETIRED) <flameeyes>
Component:	Repoman	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	normal	CC:	qa
Priority:	High	Keywords:	InVCS
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	210077, 288499

Description Diego Elio Pettenò (RETIRED) gentoo-dev

2009-06-20 23:18:34 UTC

Yes I know I start to get boring on this matter, but since lots of users lament about the "size of the tree", I think this is worth stressing a bit.

I'd say that the file.size check should be splitted in two parts: >10K is a warning, >20K a fatal error. This way we can actually have some sane limits on the system, I'd say.

Thanks,
Diego

Comment 1 Diego Elio Pettenò (RETIRED) gentoo-dev

2009-09-26 08:43:36 UTC

Zac please give priority to this as soon as you have some time; I just found a 41K patch _added to the tree_ (for Python 3 compatibility, no less). We're reaching ludicrous situations.

Comment 2 Torsten Veller (RETIRED) gentoo-dev

2009-09-26 09:38:27 UTC

Three years ago there was a discussion about patches.g.o where patches would also be archived. Maybe we should restart the discussion.

If the ebuild is removed the patch would be lost after two weeks.

Comment 3 Diego Elio Pettenò (RETIRED) gentoo-dev

2009-09-26 09:48:32 UTC

True but we got a cvs module for patches (or git repositories for those disliking cvs).

Comment 4 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2009-10-07 15:35:10 UTC

file.size.fatal check has been added in r14510.

Comment 5 Zac Medico gentoo-dev

2009-10-11 00:42:08 UTC

This is fixed in 2.1.7 and 2.2_rc45.