| Summary: | =dev-python/git-review-1.28.0 version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
| Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d015de13542befecd26f59ace246020d75ffeab commit 4d015de13542befecd26f59ace246020d75ffeab Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2020-01-17 16:04:59 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2020-01-17 16:05:27 +0000 dev-python/git-review: 1.28.0 bump more pythons as well Fixes: https://bugs.gentoo.org/705664 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> dev-python/git-review/Manifest | 1 + dev-python/git-review/git-review-1.28.0.ebuild | 25 +++++++++++++++++++++++++ 2 files changed, 26 insertions(+) |
1.28.0 Upgrade Notes - Support for auto-configuration of topic names based on the presence of keywords in the commit message is removed. Previously, keywords such as bug, bp or lp followed by a number would result in branch names containing the associated number, e.g. bug/123. This feature was OpenStack specific, was a frequent source of bugs and clearly wasn’t being used that often, given that StoryBoard is a thing now and no one had updated this feature to handle that metadata. Bug Fixes - Fixes gitreview process exit code to align with general UNIX process exit code conventions. Specifically, default exit code changed to 1 which stands for “general error”. - Fixed usepushurl to work when a read-only mirror being used as origin does not contain refs/changes from gerrit. - If a patch has no topic, downloading it will result in a topic of review/{owner}/{ID}. Previously, submitting this would then set the topic to {ID}. This was incorrect behavior and is now resolved.