Hello, trough a hackweek project: https://hackweek.opensuse.org/23/projects/python-modules-mass-update there are some version updates of python modules proposed in home:pgajdos:python. Temporarily, until better process is found, if you are considering to update a python module, you can eventually take it from there as a base for your submission. Petr -- Have a lot of fun..
Am Freitag, 10. November 2023, 12:25:30 CET schrieb pgajdos: Hi Petr,
there are some version updates of python modules proposed in home:pgajdos:python. Temporarily, until better process is found, if you are considering to update a python module, you can eventually take it from there as a base for your submission.
Thanks for sharing. I've looked at one example:
https://build.opensuse.org/package/rdiff/home:pgajdos:python/python-calmjs.parse?opackage=python-calmjs.parse&oproject=devel%3Alanguages%3Apython&rev=6
I see that it does basically a %setup to %autosetup rewrite, which can be
useful (I hope this is from spec-cleaner and not fighting against whatever
spec-cleaner is doing?).
The main challenge I see is with the changelog entry:
Mon Oct 30 12:41:18 UTC 2023 - pgajdos@suse.com
- update to version 1.3.1
* see https://github.com/calmjs/calmjs.parse/blob/master/CHANGES.rst
Besides the missing colon, this links the master changes file. This is
typically a problem with the factory source reviewer team.
See https://en.opensuse.org/
openSUSE:Creating_a_changes_file_(RPM)#Version_updates and the following
sections on why and the policies around that.
My changesgen tool ( https://github.com/dirkmueller/changesgen/tree/main )
produces this instead:
+-------------------------------------------------------------------
+Fri Nov 10 11:43:35 UTC 2023 - Dirk Müller
Hi Dirk, On Fri, Nov 10, 2023 at 12:51:29PM +0100, Dirk Müller wrote:
Am Freitag, 10. November 2023, 12:25:30 CET schrieb pgajdos: Thanks for sharing. I've looked at one example:
I see that it does basically a %setup to %autosetup rewrite, which can be useful (I hope this is from spec-cleaner and not fighting against whatever spec-cleaner is doing?).
I do not use spec-cleaner automatically, no. I thought %autosetup is preferred, so I exchaged it everywhere where possible. It was just a first excercise for training, it can be of course dropped from the process if controversial.
Mon Oct 30 12:41:18 UTC 2023 - pgajdos@suse.com
- update to version 1.3.1 * see https://github.com/calmjs/calmjs.parse/blob/master/CHANGES.rst
Besides the missing colon, this links the master changes file. This is typically a problem with the factory source reviewer team.
Yeah, changes is just an open question, still, see the hackweek project comments for details.
+------------------------------------------------------------------- +Fri Nov 10 11:43:35 UTC 2023 - Dirk Müller
+ +- update to 1.3.1: + * Modified existing ``setup.py`` hook from an install hook to a + build hook to ensure the generated module files are present. + Should any of those modules are missing and the required + dependencies for are not present (i.e. ``ply`` and + ``setuptools``), the build will result in a + non-zero exit status and the documented error message should + reflect which of the required dependencies are missing.
That looks promising if that can be part of automated process. Thank you for suggestions, Petr -- Have a lot of fun..
Am Freitag, 10. November 2023, 13:25:04 CET schrieb pgajdos:
+ non-zero exit status and the documented error message should + reflect which of the required dependencies are missing. That looks promising if that can be part of automated process.
It's not as good as I'd like it for that (it is mostly a side project and never really seen significant love). But we can push it to become better. Greetings, Dirk
participants (2)
-
Dirk Müller
-
pgajdos