I've got a similar problem here for automatic alpine packaging.
GNUnet tarballs used to have a folder named %{name}-%{version}. This is
also standard for the alpine build process. Now the suffix
"-1-gad3ced416" is causing trouble to abuild which is asking to specify
the $builddir.
>>> gnunet: Unpacking /var/cache/distfiles/gnunet-0.26.2.tar.gz...
>>> ERROR: gnunet: Is $builddir set correctly?
>>> ERROR: gnunet: prepare failed
Best
xrs
On Thu, 25 Dec 2025 16:42:48 +0100
Andreas Stieger <[email protected]> wrote:
> I noticed that the v0.26.2 tarball is packaged so:
>
> $ tar -xf gnunet-0.26.2.tar.gz gnunet-0.26.2-1-gad3ced416/.version -O
> 0.26.2-1-gad3ced416
>
> Tar root directories other than %{name}-%{version} are a bit clunky.
> But using composite string in .version and ingesting it into meson
> project (via scripts/get_version.sh) has issues: Specifically it
> affects automatic dependency generation in rpm when using the project
> version with double separator:
>
> [ 198s] RPM build warnings:
> [ 198s] Invalid version (double separator '-'):
> 0.26.2-1-gad3ced416
>
> The work-around is trivial, but could you consider reviewing the
> tarball release procedure?
>
> Andreas
>
>
--
GPG-Key: https://keys.openpgp.org/vks/v1/by-keyid/3E1C76778215233B
GPG-Fpr: 06C2 0E71 4C71 D336 A233 A0B6 3E1C 7677 8215 233B
