Summary: | Make repoman check ChangeLog syntax | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
Component: | Repoman | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | coldwind, fauli |
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
check_changelog.py
check_changelog.py check_changelog.py |
Description
Petteri Räty (RETIRED)
2007-03-23 21:24:53 UTC
Created attachment 114184 [details]
check_changelog.py
Here is the logic for checking ChangeLogs. Can be run like:
find /usr/portage/ -name "ChangeLog" | xargs python changelog.py
It seems the tree is full of broken entries atm:
betelgeuse@pena ~/python $ find /usr/portage/ -name "ChangeLog" | xargs python changelog.py | wc -l
2545
Created attachment 114194 [details]
check_changelog.py
Handle package names with + in them.
Created attachment 114220 [details] check_changelog.py Take package moves into account and check the date syntax for *foo-1.0 (date) lines. http://dev.gentoo.org/~betelgeuse/changelogs_syntax_errors.txt As discussed on irc, I'd like to add 2 new repoman checks for this: 1) Fail if a new ebuild has been added without an appropriate ChangeLog entry. 2) Warn if there are broken ChangeLog entries for previously existing ebuilds. (In reply to comment #4) > 1) Fail if a new ebuild has been added without an appropriate ChangeLog entry. > 2) Warn if there are broken ChangeLog entries for previously existing ebuilds. What is the status? Do we really want to add more stuff into the current repoman incarnation? That beast *really* needs to be rewritten. Obsolete? Devs don't generate changelogs nowadays and repoman won't see them. <ulm> mjo: just close it |