PyCharm support in Tumbleweed
Hi all, This is probably the wrong thread but I just wonder why not address it to factory list first. I have to answer this question each upgrade to new snapshot for installed PyCarm IDE 2020.3 dep to libavcodec.so.53, currently isntalled libavcodec.so.58. /Distributions-Aktualisierungen werden verarbeitet...// //Problem: libavcodec.so.53()(64bit) benötigt von pycharm-community-jre-2018.3.5-1.3.x86_64 wird nirgends zur Verfügung gestellt// // Lösung 1: Deinstallation von pycharm-community-jre-2018.3.5-1.2.x86_64// // Lösung 2: veraltetes pycharm-community-jre-2018.3.5-1.2.x86_64 beibehalten// // Lösung 3: pycharm-community-jre-2018.3.5-1.3.x86_64 durch Ignorieren einiger Abhängigkeiten brechen// //Wählen Sie aus den obigen Lösungen mittels Nummer oder brechen Sie (a)b [1/2/3/a/d/?] (a): *2*/ As far as I know libavcodec.so is part of Packman repos. So, Tumbleweed doesn't need to care about dep to PyCharm build at all. Probably that's is a stupid questions to Tumbleweed maintainers but why is PyCharm not updated or even part of factory repos ? Isn't PyCharm quite known and worth it like Eclipse? Note, I got my latest build from repos home_Dead_Mozay_pycharm-community but it seems to be maintained for Leap only. Do I need to address it to packaging list instead? Thanks, Torsten
Am 18.01.21 um 21:01 schrieb Torsten Saliwada:
This is probably the wrong thread but I just wonder why not address it to factory list first.
Yes, kinda. See below.
Note, I got my latest build from repos home_Dead_Mozay_pycharm-community but it seems to be maintained for Leap only. Do I need to address it to packaging list instead?
I'd get in touch with the maintainer of this home repo and ask him if he could fix the build. And furthermore maybe he's willing to submit it to factory? You could also have a look at his build and maybe spot where the problem roots from. vinz.
participants (2)
-
Torsten Saliwada
-
Vinzenz Vietzke