mbridon commented on issue #1855:
URL: https://github.com/apache/buildstream/issues/1855#issuecomment-1692916386
> I strongly suggest rolling a tarball yourself and testing with Rawhide
while waiting for the release. In case it _still_ will not work, it means
another release behind voting process.
Alright, I did just that.
From the latest git master (with updated `versioneer`) I ran `python
setyup.py sdist` which generated `BuildStream-2.0.1+32.gb2b12b08a.tar.gz`.
I tried to build the Rawhide package with that, but then that tarball
doesn't contain the same tree as the official one. :confused:
I tried to work around that, and then the build process failed because I
hadn't added `python3-Cython` as a build requirement. I'm confused, because I
can't find that in any of the various `requirements` files, where was this
added?
Then it failed because the `gcc` command was not found... WAT? :scream:
Pretty sure that's one of the packages installed by default in any `mock`
build... :confused: Anyway, added it explicitly...
Now the build fails like this:
```
from buildstream import _yaml
ModuleNotFoundError: No module named 'buildstream'
make: *** [Makefile:120: sessions/autotools.run] Error 1
```
That's weird... I wonder if that's not all a side effect of the fact I
didn't create the tarball the right way... So before I continue, how was I
supposed to create it ? :smile:
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
