Skip to content

Using /backport skill claude puts bogus date into spec file if not reminded about current date #506

@zdohnal

Description

@zdohnal

What happened? What is the problem?

Using /backport skill and if verified ways of bumping spec fail (f.e. rpmdev-bumpspec fails because the spec is old - f.e. has old syntax for applying patches, or date was not called), it creates the date in spec changelog manually and creates bogus date.

Note: if rpmdev-bumpspec -c 'mesage' *.spec (or its rightmost bump version) fails, the release number is bumped correctly and changelog message is almost correct - the only thing missing in spec changelog is NVR.

log3.txt

What did you expect to happen?

Generate correct date at first try.

Example URL(s)

No response

Steps to reproduce

1. start Claude Code v2.1.145, opus 4.6
2. /backport CVE-2026-35177 fix to rhel-9.8.0 and c8s
3. get into backport to rhel-9.8.0, where rpmdev-bumpspec fails - claude will try to guess the date by itself, but incorrectly

Workaround

  • There is an existing workaround that can be used until this issue is fixed.

Participation

  • I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions