RDOPKG-FEATURE-PATCH(7)

πŸ“¦
version 1.7.0 Β· 2 versions
, in epel 9

πŸ’… NAME πŸ’…

rdopkg-feature-patch β€” okay so this whole page is literally autogenerated from the feature spec patch.feature, no cap 🫢

✨ SYNOPSIS ✨

Updating patches from the patches branch is, like, the core feature bestie β€” it's giving main character energy πŸ”₯

πŸŽ€ SCENARIOS πŸŽ€

rdopkg patch 🌸

  • Given a distgit at Version 1.20.0 and Release 3,
  • Given a patches branch with 5 patches,
  • When I run rdopkg patch -l,
  • Then command return code is 0,
  • Then .spec file tag Release is 4%{?dist},
  • Then .spec file has 5 patches defined,
  • Then .spec file doesn't contain patches_base,
  • Then .spec file contains new changelog entry with 5 lines,
  • Then .spec file tag Release is 4%{?dist},
  • Then new commit was created,
  • Then git is clean,
  • Then last commit message is:
foo-bar-1.20.0-4

Changelog:
- Original Patch 5
- Original Patch 4
- Original Patch 3
- Original Patch 2
- Original Patch 1

rdopkg patch --no-bump πŸ’–

  • Given a distgit at Version 1.20.0 and Release 3,
  • Given a patches branch with 3 patches,
  • When I run rdopkg patch --no-bump -l,
  • Then .spec file tag Release is 3%{?dist},
  • Then command return code is 0,
  • Then .spec file has 3 patches defined,
  • Then .spec file doesn't contain patches_base,
  • Then .spec file doesn't contain new changelog entries,
  • Then .spec file tag Release is 3%{?dist},
  • Then new commit was created,
  • Then git is clean,
  • Then last commit message is:
Updated patches from master-patches

rdopkg patch --release-bump-index MINOR πŸ¦‹

  • Given a distgit at Version 1.20.0 and Release 1.2.3.lul,
  • Given a patches branch with 1 patches,
  • When I run rdopkg patch -l --release-bump-index MINOR,
  • Then .spec file has 1 patches defined,
  • Then .spec file contains new changelog entry with 1 lines,
  • Then .spec file tag Release is 1.3.3.lul%{?dist},
  • Then new commit was created

rdopkg patch --release-bump-index 0 (disable release bump) πŸ’€

  • Given a distgit at Version 1.20.0 and Release 1.2.3.lul,
  • Given a patches branch with 1 patches,
  • When I run rdopkg patch -l --release-bump-index 0,
  • Then .spec file has 1 patches defined,
  • Then .spec file contains new changelog entry with 1 lines,
  • Then .spec file tag Release is 1.2.3.lul%{?dist},
  • Then new commit was created

rdopkg patch without version git tag 😭

  • Given a distgit,
  • Given a patches branch with 3 patches without version git tag,
  • When I run rdopkg patch -l,
  • Then command return code is 1,
  • Then no new commit was created,
  • Then git is clean,
  • Then rdopkg state file is not present,
  • Then command output contains 'Invalid base patches branch git reference: '
Ngl bestie, if you see that error it means the patches branch is missing its version git tag β€” and rdopkg is not having it πŸ™ˆ

rdopkg update-patches basic 🧚

  • Given a distgit at Version 1.0 and Release 23,
  • Given a patches branch with 3 patches,
  • When I run rdopkg update-patches,
  • Then command return code is 0,
  • Then .spec file tag Release is 23%{?dist},
  • Then .spec file has 3 patches defined,
  • Then .spec file doesn't contain new changelog entries,
  • Then new commit was created,
  • Then git is clean,
  • Then rdopkg state file is not present,
  • Then command output contains Updated patches from master-patches,
  • Then command output contains Requested distgit update finished, see last commit.,
  • Then last commit message is:
Updated patches from master-patches

rdopkg update-patches noop 🌈

  • Given a distgit,
  • Given a patches branch with 0 patches,
  • When I run rdopkg update-patches,
  • Then command return code is 0,
  • Then no new commit was created,
  • Then git is clean,
  • Then rdopkg state file is not present,
  • Then command output contains No changes to patches found

rdopkg patch --amend πŸ‘‘

  • Given a distgit with Change-Id Ideadbeef1234,
  • Given a patches branch with 5 patches,
  • When I run rdopkg patch -l --amend,
  • Then command return code is 0,
  • Then .spec file tag Release is 3%{?dist},
  • Then .spec file has 5 patches defined,
  • Then .spec file doesn't contain patches_base,
  • Then .spec file contains new changelog entry with 5 lines,
  • Then new commit was created,
  • Then git is clean,
  • Then last commit message is:
foo-bar-1.2.3-3

Changelog:
- Original Patch 5
- Original Patch 4
- Original Patch 3
- Original Patch 2
- Original Patch 1

Change-Id: Ideadbeef1234

And that's the whole vibe check bestie β€” this page is autogenerated from patch.feature and dated 10/04/2023, brought to you by the RDOPKG PATCH(7) manual. Slay, happy patching! πŸŒŸπŸ’œπŸ«Ά

πŸ“¦ where this page comes from