salt fails to build with Python 3.10:
RPM build errors:
File not found: /builddir/build/BUILDROOT/salt-3002.1-1.fc34.x86_64/usr/lib/python3.10/site-packages/salt-*-py?.?.egg-info
This was fixed:
And later reverted:
BTW When the revert happened, there was small email exchange between us, but so far the problem still exists. Opening this for tracking purposes.
For the build logs, see:
For all our attempts to build salt with Python 3.10, see:
Testing and mass rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with Python 3.10:
Let us know here if you have any questions.
Python 3.10 will be included in Fedora 35. To make that update smoother, we're building Fedora packages with early pre-releases of Python 3.10.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires), so if this package is required a lot, it's important for us to get it fixed soon.
We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side.
I was looking at the dates in the changelog and I am puzzled as to how the reversion could be due to my changes.
- * Wed Jul 29 2020 Fedora Release Engineering <firstname.lastname@example.org> - 3001-2
- - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
+ * Mon Jul 27 2020 SaltStack Packaging Team <email@example.com> - 3001.1-1
+ - Update to feature release 3001.1-1 for Python 3
The Fedora builds are done by SaltStack after general Linux releases for a point release, but the changes are always corrected for the day the actual works is done, since the Fedora builds are done by hand. Hence the changes were done on Monday 27th July, which kind of makes it hard to revert a change made on Wednesday 29th July, two days later.
Understand we had some email about this at the time, but the issue with the dates I just became aware of.
However, I am wondering what is going on in the process that a change from two days earlier reverts a change from two days later.
I am very sure of the date Mon Jul 27, as I am rigorous about ensuring the date is correct in the changelog.
But I do see the dates on the changes Aug 11th, almost two weeks after the Monday, which is odd. I could expect a couple of days difference but two weeks is too large.
However will work to get the issue corrected so that this is not a problem going forward.
Note: the maintainer has been changed to firstname.lastname@example.org (our email addresses changed with the VMware buy of SaltStack)
I don't understand how do you manage the spec file or what is the problem with the dates.
On Aug 11 a commit was pushed that had the date" "Jul 27" in the changelog. The commit overrode any changes made in the Fedora dist-git since the last push by the maintainer(s).
I returned the original fix https://src.fedoraproject.org/rpms/salt/c/f04c3c3febfddbcea6b1e82ac867c21ef14adf08?branch=master
Do we need to fix the changelog too? if so, do we make david's changelog entry match the date it was committed or leave the dates as is and be out of order?
FEDORA-2020-5c5ff2deec has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-5c5ff2deec
> I returned the original fix https://src.fedoraproject.org/rpms/salt/c/f04c3c3febfddbcea6b1e82ac867c21ef14adf08?branch=master
> Do we need to fix the changelog too?
FEDORA-2020-5c5ff2deec has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.