Ahh i didn't see that. As i have this as a dep of a dep of a package I want to update, let me first get to a point where i can actually update it. Still struggling a bit, because as far as I can see python-curl-cffi needs internet for building (in its default way)
Not sure, what’s the current status of this package, but let me add a couple of more comments:
BuildRequires: %{python_module pytest-cov} … we usually rather remove with sed line in pytest.ini (or wherever this configuration is stored) calling for the coverage measure. It really doesn’t make any sense to count coverage for packaging test run. The same applies to that coveralls package, which you use somewhere else. It makes even less sense to use the client for some specific server, when we are really not interested in the results.
%description\n%{summary}. … that’s just lazy. Could you please elaborate a little bit on what this package does, what specifying functionality can be proxied (for example)? Think about %description as an advertisement for your potential user. Why should she install this package?
Can you update the changelog to match the current version?
In any case, we removed this package one month ago [1]. Do we want it back? What do you think @bnavigator?
[1] https://build.opensuse.org/request/show/1154921
Ahh i didn't see that. As i have this as a dep of a dep of a package I want to update, let me first get to a point where i can actually update it. Still struggling a bit, because as far as I can see python-curl-cffi needs internet for building (in its default way)
Not sure, what’s the current status of this package, but let me add a couple of more comments:
BuildRequires: %{python_module pytest-cov}… we usually rather remove withsedline inpytest.ini(or wherever this configuration is stored) calling for the coverage measure. It really doesn’t make any sense to count coverage for packaging test run. The same applies to thatcoverallspackage, which you use somewhere else. It makes even less sense to use the client for some specific server, when we are really not interested in the results.%description\n%{summary}.… that’s just lazy. Could you please elaborate a little bit on what this package does, what specifying functionality can be proxied (for example)? Think about%descriptionas an advertisement for your potential user. Why should she install this package?@StevenK, @TheBlackCat, @alarrosa, @aplanas, @dgarcia, @dirkmueller, @glaubitz, @mcalabkova, @mcepl, @mimi_vx, @ojkastl_buildservice, @posophe, @rjschwei, @sleep_walker, @tbechtold: review reminder