You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using bender clone <PKG>, the checked-out repository uses a temporary bender tag. Is there a reason for this?
I would believe most users will change the branch to the specific tag/branch they are working from anyway, so is there a reason for creating tags for these repos, when Bender won't touch them?
A solution is to drop creating this tag and just check out the tag/rev in the manifest.
Bender aims to check out the commit hash specified in the Bender.lock to ensure consistency and reproducibility of a project. To do this, bender internally clones a bare repository in the db directory. Within this, it creates a temporary tag to clone to the project directory because git clone <hash> does not work. See https://github.com/pulp-platform/bender/blob/master/src/sess.rs#L975-L977 for more details.
To work on a working branch for a specific dependency, I suggest utilizing the bender clone <dep> and bender snapshot (and finally bender update) mechanics (described here).
Activity
micprog commentedon Feb 24, 2026
Bender aims to check out the commit hash specified in the
Bender.lockto ensure consistency and reproducibility of a project. To do this, bender internally clones a bare repository in thedbdirectory. Within this, it creates a temporary tag to clone to the project directory becausegit clone <hash>does not work. See https://github.com/pulp-platform/bender/blob/master/src/sess.rs#L975-L977 for more details.To work on a working branch for a specific dependency, I suggest utilizing the
bender clone <dep>andbender snapshot(and finallybender update) mechanics (described here).