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)
![]() 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. 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. True but we got a cvs module for patches (or git repositories for those disliking cvs). file.size.fatal check has been added in r14510. This is fixed in 2.1.7 and 2.2_rc45. |