python-carbon

Edit Package python-carbon
No description set
Refresh
Refresh
Source Files
Filename Size Changed
carbon-1.1.10.tar.gz 0000077091 75.3 KB
carbon-aggregator.service 0000000372 372 Bytes
carbon-cache.service 0000000357 357 Bytes
carbon-relay.service 0000000357 357 Bytes
carbon-tmpfiles.conf 0000000069 69 Bytes
python-carbon-path.patch 0000003336 3.26 KB
python-carbon-rpmlintrc 0000000092 92 Bytes
python-carbon.changes 0000003434 3.35 KB
python-carbon.spec 0000006188 6.04 KB
Latest Revision
Eric Schirra's avatar Eric Schirra (ecsos) accepted request 1150789 from Eric Schirra's avatar Eric Schirra (ecsos) (revision 14)
- Adjustments patch macro for rpm 4.20.
Comments 14

Dirk Stoecker's avatar

Build python311 for 15.5 which isn't useful. Breaks graphite-web.


Eric Schirra's avatar

Why do you think it breaks graphite-web? Or do you mean only it breaks graphite-web from Tumbleweed?


Dirk Stoecker's avatar

It breaks on 15.5. It installs python-carbon and python-whisper with python311 and the rest with python3.6 and that simply means packages aren't available and it does not start. I had to build python36 packages to get this fixed, but I simply forced it and didn't check yet how to do it proper.

It's strange anyway that 15.5 build python 3.11. 15.4 builds the proper version for 15.4. I suspect there is an underlying problem in the 15.5 scripts to build python packages.


Eric Schirra's avatar

I think there is not a problem in new macro. The Problem in graphite-web is, that graphite-web dependencies are to old. And if you get a package from devel you should also get the rest from devel. Otherwise there are problems or it doesn't work at all.

I just made another small change in python-carbon package. Can you please test it if your problem is gone? But please take all packages from devel.


Dirk Stoecker's avatar

As said: I can't. The dependencies simply don't exist.




Eric Schirra's avatar

I know what you mean. That's what I was talking about when the macro came out. But it wasn't understood or people didn't want to understand it. And Leap is no longer really taken into account. Tumbleweed is the only thing that counts. I've already experienced this several times. That's why I don't argue about it any more, but build the packages myself.

The packages in Server:monitoring can no longer be built this way. That can't work at all. The d:l:p repo would have to be included in the repoconfig.

Without it, it won't work in s:m any more anyway, because more and more packages don't support 2.7, 3.6 and 3.7.

You have to upgrade to >= 3.8. everywhere. As d:l:p has to be integrated.


Dirk Stoecker's avatar

And before you ask. :-) python-Twisted for 3.11 and a lot of other packages are only available in devel:languages:python and don't build for 15.5, so switching to 3.11 for 15.5 is also no option.


Eric Schirra's avatar

So that the python3.11 packages are only built in devel is correct. That is probably so intentional. And the ones in devel with the new macro were also built. Python2. is so dead. Python3.6 is also so dead. And so is python 3.7 by now. So for me the ancient and extremely security critical python2 and 3.6 packages are not an option....


Dirk Stoecker's avatar

That makes Leap unusable. As leap 15.5 has python 3.6 and using any newer version of python wont work there. So for Leap 15.5 we need to build python3.6 packages or software wont simply work on leap.

I totally agree with you that's awful and [censored...], but Leap 15.5 with python3.6 is the newest we get and Tumbleweed is no option for servers.

No, your changes wont help, as they anyway require python3.11 which isn't complete for 15.5 and thus wont work.

I simply added %define python_module() python3-%{**}, dropped the sle macros and added python-module base for my working packages. Can we somehow force building for the distribution python version for Leap?

Otherwise someone at least needs to fix devel:languages:python for 15.5 and there are many packages broken there.


Eric Schirra's avatar

That is not so true that make Leap 15.5 unusable. Calibre 6.22 can now be built and installed for LEap15.5. The last calibre version to be built in 3.6 would be the 4s. Because python 3.6 and now 3.7 is so dead. Several packages in devel:languages:python are now available for Leap 15.5 as python3.11. So if you take that and add it as a dependent repo to yours, the rest will also be built as python3.11. In addition, OBS for Leap 15.5 now always builds a python311 and no longer python3. Unless you override that in your ProjectConfig. I don't necessarily think that's great either. I would have liked it to be like Tumbleweed. But good. Is so. And several new versions of python modules do not build under the normal Leap anymore. Because python 3.6 is out and is no longer supported.

And there should be more and more packages in devel:languages:python which work and build for Leap15.5 as 3.11 Python. At least more than 800. Meanwhile in d:l:p probably more packages are built for Leap than before. Because as I said. Python2, 3.6 and 3.7 are no longer supported by several modules.


Dirk Stoecker's avatar

About 1750 packages aren't build for 15.5. As said, if that gets fixed fine, then it will work. But I'm waiting for several weeks already and progress was minimal. Seems python-Twisted does now build for 15.5 so maybe there is a chance it will work.


Eric Schirra's avatar

I think that for the packages that are not built, the new macro is missing. So 3.6 is still being used for construction. But the modules themselves are already too new.

By the way, Python Twisted is built without errors.

openSUSE Build Service is sponsored by