1RDOPKG NEW-VERSION(7)                                    RDOPKG NEW-VERSION(7)
2
3
4

NAME

6       rdopkg-feature-new-version - autogenerated from feature spec
7       `new-version.feature`
8

SYNOPSIS

10       Updating package to new version is a core feature
11

SCENARIOS

13   rdopkg new-version --bump-only
14       •   Given a distgit at Version 2.0.0 and Release 3,
15
16       •   When I run rdopkg new-version --bump-only -n 2.1.0,
17
18       •   Then command output contains Action finished,
19
20       •   Then .spec file tag Version is 2.1.0,
21
22       •   Then .spec file tag Release is 1%{?dist},
23
24       •   Then .spec file doesn’t contain patches_base,
25
26       •   Then .spec file contains new changelog entry with 1 lines,
27
28       •   Then new commit was created,
29
30       •   Then git is clean,
31
32       •   Then last commit message is:
33
34           """
35           foo-bar-2.1.0-1
36
37
38           Changelog:
39           - Update to 2.1.0
40           """
41
42   rdopkg new-version with upstream patches
43       •   Given a distgit at Version 0.1 and Release 0.1,
44
45       •   Given a patches branch with 5 patches,
46
47       •   Given a new version 1.0.0 with 2 patches from patches branch,
48
49       •   When I run rdopkg new-version -lntU 1.0.0,
50
51       •   Then command output contains Action finished,
52
53       •   Then .spec file tag Version is 1.0.0,
54
55       •   Then .spec file tag Release is 1%{?dist},
56
57       •   Then .spec file doesn’t contain patches_base,
58
59       •   Then .spec file has 3 patches defined,
60
61       •   Then .spec file contains new changelog entry with 1 lines,
62
63       •   Then new commit was created,
64
65       •   Then git is clean,
66
67       •   Then last commit message is:
68
69           """
70           foo-bar-1.0.0-1
71
72
73           Changelog:
74           - Update to 1.0.0
75           """
76
77   rdopkg new-version with patches_ignore filtering
78       •   Given a distgit at Version 0.1 and Release 0.1 with magic comments:
79
80           """
81           # patches_ignore=DROP-IN-RPM|Wololo
82           # patches_base=0.1
83           """
84
85       •   Given a patches branch with following patches:
86
87           """
88           Banana Patch DROP-IN-RPM
89           Mango Patch
90           Wololo Patch
91           Kiwi Patch
92           """
93
94       •   Given a new version 1.0.0,
95
96       •   When I run rdopkg new-version -ltU 1.0.0,
97
98       •   Then command output contains Action finished,
99
100       •   Then .spec file tag Version is 1.0.0,
101
102       •   Then .spec file tag Release is 1%{?dist},
103
104       •   Then .spec file has 2 patches defined,
105
106       •   Then .spec file contains patches_base=1.0.0,
107
108       •   Then .spec file contains new changelog entry with 1 lines,
109
110       •   Then new commit was created,
111
112       •   Then git is clean,
113
114       •   Then last commit message is:
115
116           """
117           foo-bar-1.0.0-1
118
119
120           Changelog:
121           - Update to 1.0.0
122           """
123
124   rdopkg new-version --bump-only --bug <id>
125       •   Given a distgit at Version 2.0.0 and Release 3,
126
127       •   When I run rdopkg new-version --bump-only -n 2.1.0 --bug
128           rhbz#12345,
129
130       •   Then command output contains Action finished,
131
132       •   Then .spec file contains new changelog entry with rhbz#12345,
133
134       •   Then new commit was created,
135
136       •   Then git is clean,
137
138       •   Then last commit message contains rhbz#12345,
139
140       •   Then last commit message is:
141
142           """
143           foo-bar-2.1.0-1
144
145
146           Changelog:
147           - Update to 2.1.0 (rhbz#12345)
148
149
150           Resolves: rhbz#12345
151           """
152
153   rdopkg new-version --bump-only --commit-header-file <file>
154       •   Given a distgit at Version 2.0.0 and Release 3,
155
156       •   Given a local file commitmsg containing "Testing Alternate Commit
157           Header",
158
159       •   When I run rdopkg new-version --bump-only -n --commit-header-file
160           commitmsg 2.1.0,
161
162       •   Then command output contains Action finished,
163
164       •   Then new commit was created,
165
166       •   Then git is clean,
167
168       •   Then last commit message is:
169
170           """
171           Testing Alternate Commit Header
172
173
174           Changelog:
175           - Update to 2.1.0
176           """
177
178   rdopkg new-version --bump-only --bug <id> -H <file>
179       •   Given a distgit at Version 2.0.0 and Release 3,
180
181       •   Given a local file commitmsg:
182
183           """
184           Testing
185
186
187           Multiline
188           Commit
189           Header
190           """
191
192       •   When I run rdopkg new-version --bump-only -n --bug
193           rhbz#12345,rhbz#232323 -H commitmsg 2.1.0,
194
195       •   Then command output contains Action finished,
196
197       •   Then .spec file contains new changelog entry with rhbz#12345,
198
199       •   Then .spec file contains new changelog entry with rhbz#232323,
200
201       •   Then new commit was created,
202
203       •   Then git is clean,
204
205       •   Then last commit message contains rhbz#12345,
206
207       •   Then last commit message contains rhbz#232323,
208
209       •   Then last commit message is:
210
211           """
212           Testing
213
214
215           Multiline
216           Commit
217           Header
218
219
220           Changelog:
221           - Update to 2.1.0 (rhbz#12345,rhbz#232323)
222
223
224           Resolves: rhbz#12345
225           Resolves: rhbz#232323
226           """
227
228   rdopkg new-version without starting version git tag
229       •   Given a distgit at Version 0.1 and Release 0.1,
230
231       •   Given a patches branch with 2 patches without version git tag,
232
233       •   When I run rdopkg new-version -l 1.0.0,
234
235       •   Then no new commit was created,
236
237       •   Then git is clean,
238
239       •   Then command output contains Invalid base patches branch git
240           reference:
241
242   rdopkg new-version without new version git tag
243       •   Given a distgit at Version 0.1 and Release 0.1,
244
245       •   Given a patches branch with 2 patches,
246
247       •   When I run rdopkg new-version -l 2.2.2,
248
249       •   Then no new commit was created,
250
251       •   Then git is clean,
252
253       •   Then command output contains Invalid git reference: 2.2.2
254
255   rdopkg new-version --bump-only with macro in Name
256       •   Given a distgit at Version 2.0.0 and Release 3,
257
258       •   When I prepend .spec file with:
259
260           """
261           %global lib foo
262           """
263
264       •
265
266       •   When I run rdopkg new-version --bump-only -n 2.1.0,
267
268       •   Then command output contains Action finished,
269
270       •   Then new commit was created,
271
272       •   Then git is clean,
273
274       •   Then last commit message contains python-foo-foo,
275
276       •   Then last commit message is:
277
278           """
279           python-foo-foo-2.1.0-1
280
281
282           Changelog:
283           - Update to 2.1.0
284           """
285
286
287
288                                  10/04/2023             RDOPKG NEW-VERSION(7)