RDOPKG-FEATURE-FIX(7)
π RDOPKG FIX(7)
okay so this is the RDOPKG FIX(7) page, bestie β and before you ask, yes the manual name is folded right up there at the top so you don't gotta scroll. it's a feature-spec joint π
β¨ NAME β¨
rdopkg-feature-fix β no cap, this whole page is autogenerated from feature spec fix.feature, that's literally what it says π
πΈ SYNOPSIS πΈ
Introducing .spec fixes is a core functionality. that's the whole vibe. iconic behavior honestly π«Ά
π¦ SCENARIOS π¦
every scenario is a little story, and we're reading them all, periodt. no skipping. π
π rdopkg fix - did not add description of changes
- Given a distgit,
- When I run
rdopkg fix, - Then rdopkg state file is present
β rdopkg fix
- Given a distgit,
- When I run
rdopkg fix, - When I add description to
.specchangelog, - When I run
rdopkg --continue, - Then
.specfile contains new changelog entry with 1 lines, - Then new commit was created,
- Then rdopkg state file is not present,
- Then last commit message is:
foo-bar-1.2.3-3
Changelog:
- Description of a change
π§ rdopkg fix - did not add description of changes
- Given a distgit,
- When I run
rdopkg fix, - When I run
rdopkg --continue, - Then command output contains
Description of changes is missing in %changelog., - Then no new commit was created,
- Then rdopkg state file is present
π rdopkg fix - user reverted all changes
- Given a distgit,
- When I run
rdopkg fix, - When I undo all changes,
- When I run
rdopkg --continue, - Then command output contains
No distgit changes found, - Then no new commit was created,
- Then rdopkg state file is present
π rdopkg fix - user aborts
- Given a distgit,
- When I run
rdopkg fix, - When I undo all changes,
- When I run
rdopkg --abort, - Then no new commit was created,
- Then rdopkg state file is not present
π₯ rdopkg fix - user reruns
- Given a distgit,
- When I run
rdopkg fix, - When I run
rdopkg fix, - Then command output contains
Youβre in the middle of previous action: fix, - Then command output contains
Please --continue or --abort, - Then no new commit was created,
- Then rdopkg state file is present
π rdopkg fix - user aborts and reruns
- Given a distgit,
- When I run
rdopkg fix, - When I run
rdopkg fix, - When I undo all changes,
- When I run
rdopkg --abort, - When I run
rdopkg fix, - When I add description to
.specchangelog, - When I run
rdopkg --continue, - Then
.specfile contains new changelog entry with 1 lines, - Then new commit was created,
- Then rdopkg state file is not present,
- Then last commit message is:
foo-bar-1.2.3-3
Changelog:
- Description of a change
π rdopkg fix - Normal semver nvr bumps consistently
- Given a distgit at Version 2.0.0 and Release 0.1,
- When I run
rdopkg fix, - Then
.specfile tag Release is0.2%{?dist}
πΈ rdopkg fix - Normal semver nvr bumps consistently - with dist macro specified
- Given a distgit at Version 2.0.0 and Release
0.1%{?dist}, - When I run
rdopkg fix, - Then
.specfile tag Release is0.2%{?dist}
β rdopkg fix - Normal semver nvr bumps consistently
- Given a distgit at Version 2.0.0 and Release
1%{?dist}, - When I run
rdopkg fix, - Then
.specfile tag Release is2%{?dist}
π¦ rdopkg fix - Normal semver nvr bumps consistently
- Given a distgit at Version 2.0.0 and Release
15%{?dist}, - When I run
rdopkg fix, - Then
.specfile tag Release is16%{?dist}
π rdopkg fix - Normal semver nvr bumps consistently
- Given a distgit at Version 2.0.0 and Release
15.0%{?dist}, - When I run
rdopkg fix, - Then
.specfile tag Release is15.1%{?dist}
π§ rdopkg fix - Release with %{?dist} in the middle bumps correctly
- Given a distgit at Version 2.0.0 and Release
1.0%{?dist}.1, - When I run
rdopkg fix, - Then
.specfile tag Release is1.1%{?dist}.1
and that's the whole page, bestie! this was RDOPKG FIX(7), dated 10/04/2023 β go forth and fix those specs, you absolute main character π β¨πΏ
π¦ where this page comes from
- epel 9: rdopkg 1.7.0-1.el9 Β· ASL 2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms