View | Details | Raw Unified | Return to bug 228686
Collapse All | Expand All

(-)py-reno/Makefile (+29 lines)
Line 0 Link Here
1
# $FreeBSD$
2
3
PORTNAME=	reno
4
DISTVERSION=	2.9.2
5
CATEGORIES=	textproc python
6
MASTER_SITES=	CHEESESHOP
7
PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
8
9
MAINTAINER=	freebsd_ports@k-worx.org
10
COMMENT=	RElease NOtes manager
11
12
LICENSE=	APACHE20
13
LICENSE_FILE=	${WRKSRC}/LICENSE
14
15
BUILD_DEPENDS=	${PYTHON_PKGNAMEPREFIX}pbr>0:devel/py-pbr@${PY_FLAVOR} \
16
		${PYTHON_PKGNAMEPREFIX}six>=1.9.0:devel/py-six@${PY_FLAVOR} \
17
		${PYTHON_PKGNAMEPREFIX}yaml>=3.1.0:devel/py-yaml@${PY_FLAVOR} \
18
		${PYTHON_PKGNAMEPREFIX}dulwich>=0.15.0:devel/dulwich@${PY_FLAVOR}
19
RUN_DEPENDS=	${PYTHON_PKGNAMEPREFIX}pbr>0:devel/py-pbr@${PY_FLAVOR} \
20
		${PYTHON_PKGNAMEPREFIX}yaml>=3.1.0:devel/py-yaml@${PY_FLAVOR} \
21
		${PYTHON_PKGNAMEPREFIX}six>=1.9.0:devel/py-six@${PY_FLAVOR} \
22
		${PYTHON_PKGNAMEPREFIX}dulwich>=0.15.0:devel/dulwich@${PY_FLAVOR}
23
24
USES=		python
25
USE_PYTHON=	distutils concurrent autoplist
26
27
NO_ARCH=	yes
28
29
.include <bsd.port.mk>
(-)py-reno/distinfo (+3 lines)
Line 0 Link Here
1
TIMESTAMP = 1527350434
2
SHA256 (reno-2.9.2.tar.gz) = 7b720b64a9c9dcec0ab252af3e0551b971a83ec4ebca9ee513e98fb2820f2426
3
SIZE (reno-2.9.2.tar.gz) = 81244
(-)py-reno/files/patch-reno_main.py (+15 lines)
Line 0 Link Here
1
--- reno/main.py.orig	2018-05-13 22:03:42 UTC
2
+++ reno/main.py
3
@@ -86,9 +86,12 @@ def main(argv=sys.argv[1:]):
4
         default=defaults.RELEASE_NOTES_SUBDIR,
5
         help='location of release notes YAML files',
6
     )
7
+    # Fix CLI tool for Python 3.x
8
     subparsers = parser.add_subparsers(
9
         title='commands',
10
+	dest='too few arguments'
11
     )
12
+    subparsers.required = True
13
 
14
     do_new = subparsers.add_parser(
15
         'new',
(-)py-reno/pkg-descr (+20 lines)
Line 0 Link Here
1
Reno is a release notes manager designed with high throughput in mind,
2
supporting fast distributed development teams without introducing additional
3
development processes. The goal is to encourage detailed and accurate release
4
notes for every release.
5
6
Reno uses git to store its data, along side the code being described. This means
7
release notes can be written when the code changes are fresh, so no details are
8
forgotten. It also means that release notes can go through the same review
9
process used for managing code and other documentation changes.
10
11
Reno stores each release note in a separate file to enable a large number of
12
developers to work on multiple patches simultaneously, all targeting the same
13
branch, without worrying about merge conflicts. This cuts down on the need to
14
rebase or otherwise manually resolve conflicts, and keeps a development team
15
moving quickly.
16
17
Reno also supports multiple branches, allowing release notes to be back-ported
18
from master to maintenance branches together with the code for bug fixes.
19
20
WWW: https://docs.openstack.org/reno/

Return to bug 228686