rootbld fails if abuild.conf is symbolic link
When running abuild rootbld
it appears to fail if my $HOME/.abuild/abuild.conf
is a symbolic link (e.g. for me it links to $HOME/.env/abuild.conf
).
Looking through the source for abuild
it looks like abuild-sign --installed
is checked (before entering bwrap
) and confirms my key is setup but once we're in the chroot, the link probably no longer resolves and therefore my config/key can't be found.
I'm just doing some simple, local packaging - I've attached the log for reference though the only warning/error is the failed signing. I've locally resolved this by making my abuild.conf
a regular file