buildsubdir needs %autosetup or %setup parsing #64

Open
opened 2026-04-29 12:28:01 +02:00 by yestax · 1 comment
Owner

To define buildsubdir, %setup or %autosetup need to be parsed. Even if it is just a comment like # %autosetup!

do rpmspec --parse to see the actuel specfile resolved

See https://github.com/rpm-software-management/rpm/issues/3890

This issue is to follow what will happen in future versions of RPM and maybe simplify the package generation.

To define buildsubdir, %setup or %autosetup need to be parsed. Even if it is just a comment like # %autosetup! do rpmspec --parse to see the actuel specfile resolved See https://github.com/rpm-software-management/rpm/issues/3890 This issue is to follow what will happen in future versions of RPM and maybe simplify the package generation.
Author
Owner

This is to say that: for buildsubdir to be defined. %setup or %autosetup needs to be parsed even if it is just in a comment.

This means that removing a # %autosetup will break the specfile as it does not init buildubdir anymore.

The github issue shows a workaround and tracks this bug.

This is to say that: for buildsubdir to be defined. %setup or %autosetup needs to be parsed even if it is just in a comment. This means that removing a # %autosetup will break the specfile as it does not init buildubdir anymore. The github issue shows a workaround and tracks this bug.
yestax changed title from Update setup.spec to buildsubdir needs %autosetup or %setup parsing 2026-05-29 00:30:00 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
yestax/setup#64
No description provided.