Re: [packman] Packman repo issue
Am Samstag, 1. Juni 2024, 01:05:25 CEST schrieb Jonathon Duvall: > Hi team > > Apologies if this is the wrong method to do this but I found a piece of > pretty out of date software in the repo and wanted to call it to attention > when someone has time. If you want, you can use my repo under software.opensuse.org For Tumbleweed and Leap 15.6 it exist in version 30.1.2 Repo: home:ecsos:obs-studio Leap 15.5 is to old. No chance. For Leap 15.5 you can use my repo home:ecsos. Here obs-studio is in version 30.0.2 Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21.0 Omega - Update against sound issues on Leap
Am Mittwoch, 8. Mai 2024, 13:44:28 CEST schrieb Manfred Hollstein:
> Hi Eric,
>
> On Wed, 08 May 2024, 13:12:59 +0200, Eric Schirra wrote:
> > Am Mittwoch, 8. Mai 2024, 11:38:06 CEST schrieb Manfred Hollstein:
> > > > [...]
> > > > Why do you want users to add --audio-backend=pulseaudio?
> > >
> > > Because it does not work on Leap otherwise...
> >
> > I'll chime in for a moment.
> >
> > Is --audio-backend=pulseaudio included in the current package or not?
> > In other words, does kodi now run under a standard Leap system without
> > manual customization?
> >
> > My understanding, and if I've followed the thread correctly, is that
> > --audio- backend=pulseaudio belongs in Leap. But not in the Tumbleweed
> > package. The maintainer has to take care of that in his spec file.
> >
> > Is this done now?
>
> Yes, this is checked by my last change. Kodi is now supposed to work out
> of the box on a _standard_ installation of Leap, i.e. no particular
> locks for/agains pipewire.
Okay.
It's running now under Leap 15.5
But
Fatal Python error: drop_gil: drop_gil: GIL is not locked
Python runtime state: initialized
Thread 0x7f9cda7fc700 (most recent call first):
File "/usr/lib64/python3.11/threading.py", line 1590 in _shutdown
/usr/bin/kodi: Zeile 224: 24092 Abgebrochen (Speicherabzug
geschrieben) ${KODI_BINARY} ${ENV_ARGS} $SAVED_ARGS
So i'm return to 20.
Regards
Eric
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am Mittwoch, 10. April 2024, 14:35:38 CEST schrieb Manfred Hollstein: > On Wed, 10 Apr 2024, 14:24:01 +0200, Eric Schirra wrote: > > Am Mittwoch, 10. April 2024, 12:54:16 CEST schrieb Masaru Nomiya: > > > Hallo, > > > > > > In the Message; > > > > > > Subject: Re: [packman] Kodi 21 - crash > > > Message-ID : <2687776.vuYhMxLoTh@client1> > > > Date & Time: Wed, 10 Apr 2024 10:54:51 +0200 > > > > > > [ES] == Eric Schirra has written: > > > > > > [...] > > > ES> Have you also read everything correctly here? > > > ES> The rpm from packman does not work. > > > ES> But the package from flatpack works. > > > ES> So the packaman package is definitely broken! > > > > > > Ich baue und verwende selbst die neuesten Git-Quellen, aber ich glaube > > > nicht, dass das von Pacman bereitgestellte Kodi irgendwelche Fehler > > > enthält. > > > > > > Es wäre besser, > > > > > >$ kodi > kodi.log 2>&1 > > > > > > in einem Terminal auszuführen und das kodi.log hochzuladen. > > > > Zeigt überhaupt nichts. > > Und wie gesagt das Flatpack funktioniert. > > > > Und wenn ich mir so den Code anschaue im flatpack und ich das das richtige > > verstehe, verwendet das flatpack auch nur pulseaudio. Da steht nichts von > > pipewire. > > Yeah, but Leap decided to introduce pipewire, but failed to configure it > properly - see my other post. The flatpack has the same packages > installed like I do by blocking pipewire ;) Exactly, then please configure the spec file on the build server just like that. So don't remove anything by default, but create the spec so that kodi is started with pulseaudio. Just like upstream itself does. > > Je nachdem was von kodi zurück kommt, sollte das packman kodi paket > > dahingehend angepasst werden, ebenfalls nur pulseaudio zu verwenden. > > Eben so wie es upstream auch tut. > > Nope, the OS has to configure the sound server/system properly. On > Tumbleweed pipewire is initialized correctly and sound in Kodi works out > of the box! > > You should either get rid of pipewire on your Leap system, or install > the missing pipewire-pulseaudio which will remove/replace your > PulseAudio packages with those needed by a pipewire server replacing > your pulseaudio server. Nope. I simply use the flatpack from upstream if there is no solution here. Or my own. ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am Mittwoch, 10. April 2024, 14:30:57 CEST schrieb Manfred Hollstein: > On Wed, 10 Apr 2024, 14:08:29 +0200, Eric Schirra wrote: > > Am Mittwoch, 10. April 2024, 13:32:14 CEST schrieb Manfred Hollstein: > > > I just installed a new machine with Leap 15.5 and did not block pipewire > > > > > > this time. Still Pulseaudio appears to be the default sound server: > > > $ pacmd info > > > ... > > > Name des Servers: pulseaudio > > > > > > Still Kodi wants to use pipewire by default if it finds it installed. > > > > > > kodi --help tells us the following: > > > --audio-backend= Select which audio backend to use. > > > > > > Available audio backends are: alsa, pipewire, > > > > > > pulseaudio, alsa+pulseaudio > > > > > > Starting kodi with the argument "--audio-backend=pulseaudio" results in > > > PulseAudio being used as the sound interface and sound works again. > > > > > > I deliberately refused to get pipewire installed on my normal systems > > > due to my special use-cases, but here either activating pipewire at the > > > OS level, or specifying the audio backend to be used should be the way > > > to go. > > > > > > I'll open an issue at Kodi's github that Kodi should not just blindly > > > select the preferred audio backend, but rather take a look at e.g. > > > "pacmd info"'s output... > > > > Very nice. > > That's how I see it too. > > Then my, let's say, not letting up, has something good after all. :-) > > Because even if that would work as a parameter, I don't think it's a good > > idea. There are also many people who don't know their way around the > > console. Or don't want to use it in this case. > > I just installed a completely new Tumbleweed system with pipewire > included, followed by the usual updates from Packman and then Kodi. > Pipewire apparently has been setup properly on Tumbleweed and sound in > Kodi works out of the box. > > To me it looks like a bug in Leap's offering to install pipewire via > updates, but to omit the required pipewire-pulseaudio. When you install > that package on Leap 15.5 manually, your pulseaudio gets replaced by the > pipewire infrastructure and Kodi also works. To me2, I still don't like > pipewire which is why I still block pipewire and wireplumber from > getting installed. Unfortunately, this is not a solution for. I don't want pipewire because it doesn't run without errors and causes problems elsewhere. > > Let's see what comes of it. > > I doubt they'll accept that issue due to Leap not setting up pipewire > properly... Upstream does not use Pipewire itself! They also use pulseaudio in their official flatpack! Gruß Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am Mittwoch, 10. April 2024, 12:54:16 CEST schrieb Masaru Nomiya: > Hallo, > > In the Message; > > Subject: Re: [packman] Kodi 21 - crash > Message-ID : <2687776.vuYhMxLoTh@client1> > Date & Time: Wed, 10 Apr 2024 10:54:51 +0200 > > [ES] == Eric Schirra has written: > > [...] > ES> Have you also read everything correctly here? > ES> The rpm from packman does not work. > ES> But the package from flatpack works. > ES> So the packaman package is definitely broken! > > Ich baue und verwende selbst die neuesten Git-Quellen, aber ich glaube > nicht, dass das von Pacman bereitgestellte Kodi irgendwelche Fehler > enthält. > > Es wäre besser, > >$ kodi > kodi.log 2>&1 > > in einem Terminal auszuführen und das kodi.log hochzuladen. Zeigt überhaupt nichts. Und wie gesagt das Flatpack funktioniert. Und wenn ich mir so den Code anschaue im flatpack und ich das das richtige verstehe, verwendet das flatpack auch nur pulseaudio. Da steht nichts von pipewire. Darin ist: --socket=pulseaudio -DENABLE_PULSEAUDIO=ON Also verwendet selbst kodi selbst nicht pipewire, sondern explizit pulseaudio. Je nachdem was von kodi zurück kommt, sollte das packman kodi paket dahingehend angepasst werden, ebenfalls nur pulseaudio zu verwenden. Eben so wie es upstream auch tut. Gruß Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am Mittwoch, 10. April 2024, 13:32:14 CEST schrieb Manfred Hollstein: > I just installed a new machine with Leap 15.5 and did not block pipewire > this time. Still Pulseaudio appears to be the default sound server: > > $ pacmd info > ... > Name des Servers: pulseaudio > > Still Kodi wants to use pipewire by default if it finds it installed. > kodi --help tells us the following: > > --audio-backend= Select which audio backend to use. > Available audio backends are: alsa, pipewire, > pulseaudio, alsa+pulseaudio > > Starting kodi with the argument "--audio-backend=pulseaudio" results in > PulseAudio being used as the sound interface and sound works again. > > I deliberately refused to get pipewire installed on my normal systems > due to my special use-cases, but here either activating pipewire at the > OS level, or specifying the audio backend to be used should be the way > to go. > > I'll open an issue at Kodi's github that Kodi should not just blindly > select the preferred audio backend, but rather take a look at e.g. > "pacmd info"'s output... Very nice. That's how I see it too. Then my, let's say, not letting up, has something good after all. :-) Because even if that would work as a parameter, I don't think it's a good idea. There are also many people who don't know their way around the console. Or don't want to use it in this case. Let's see what comes of it. Thanks anyway. Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am Mittwoch, 10. April 2024, 09:42:19 CEST schrieb Manfred Hollstein: > > Beide mal funktioniert kein Sound. > > Bei der ARD-Mediathek ruckelt das Video und bricht dann auch ziemlich > > schnell komplett ab. > > Unter ->Einstellungen->System-Audio sehe ich unter Audiogeräte Default > > Output Device (PIPEWIRE). Andere kann ich nicht einstellen, da keine > > weiteren angeboten werde. > > I blocked installation of pipewire packages here. Pipewire is installed as part of a standard installation. Since you block the installations, your installation is not a reference. And if kodi 21 only runs if I uninstall all pipewire packages, then the kodi package 21 is definitely defective / broken. > > Danach habe ich mir Kodi 20.5 aus den SRPM von Packaman selbst gebaut. > > (Das spec darin ist auch nicht fehlerfrei!). > > Contributions will be valued ;) You have read: "Das spec darin is auch nicht fehlerfrei"? > > Nachdem ich dann einen Downgrade auf 20.5 durchgeführte hatte, läuft > > wieder > > alles perfekt. > > Film ohne Ruckeln bei ARD-Mediathek. > > Bei MEdiathek und Prime kommt wieder Sound. > > Es erfolgt kein Abbruch der Filme. > > > > Unter Systemeinstellungen Sound steht nun wieder Default Output Device > > (PULSEAUDIO). Und ich könnte noch zwei weitere auswählen. Nämlich meine > > beiden Sounddevices direkt. > > > > Kodi 21 von flatpack funktioniert im übrigen fehlerfrei. > > Hier steht auch ebenso Pulseaudio unter Audiogerät wie unter dem RPM Kodi > > 20. > > > > Es ist also definitiv ein Fehler im Kodi 21 Paket von Packman! > > > > Ich bleib nun erstmal bei 20.5 aus meinem eigenen Repo. > > Good luck! Have you also read everything correctly here? The rpm from packman does not work. But the package from flatpack works. So the packaman package is definitely broken! Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am Montag, 8. April 2024, 20:48:54 CEST schrieb Manfred Hollstein: > > Or do you still have the old spec and other files, then I would build it > > myself again? > You can get that directly from PMBS: > > https://pmbs.links2linux.org/package/revisions/Multimedia/kodi Ich antworte nun mal auf deutsch. Kodi 21 funktioniert definitiv nicht unter Leap 15.5 Andere habe ich nicht getestet. Getestet habe ich mit den Addons ARD-Mediathek und Prime. Beide mal funktioniert kein Sound. Bei der ARD-Mediathek ruckelt das Video und bricht dann auch ziemlich schnell komplett ab. Unter ->Einstellungen->System-Audio sehe ich unter Audiogeräte Default Output Device (PIPEWIRE). Andere kann ich nicht einstellen, da keine weiteren angeboten werde. Danach habe ich mir Kodi 20.5 aus den SRPM von Packaman selbst gebaut. (Das spec darin ist auch nicht fehlerfrei!). Nachdem ich dann einen Downgrade auf 20.5 durchgeführte hatte, läuft wieder alles perfekt. Film ohne Ruckeln bei ARD-Mediathek. Bei MEdiathek und Prime kommt wieder Sound. Es erfolgt kein Abbruch der Filme. Unter Systemeinstellungen Sound steht nun wieder Default Output Device (PULSEAUDIO). Und ich könnte noch zwei weitere auswählen. Nämlich meine beiden Sounddevices direkt. Kodi 21 von flatpack funktioniert im übrigen fehlerfrei. Hier steht auch ebenso Pulseaudio unter Audiogerät wie unter dem RPM Kodi 20. Es ist also definitiv ein Fehler im Kodi 21 Paket von Packman! Ich bleib nun erstmal bei 20.5 aus meinem eigenen Repo. Gruß Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am 8. April 2024 19:36:01 MESZ schrieb Manfred Hollstein : >> Okay. >> Now I have libass9 from packman. >> Kodi can now be started. >> >> But that's it. >> No sound. > >What type of sound device are you using? Pulseaudio. No pipewire. Pipewire makes problems. It works for me on an onboard >sound (Dell and Intel), and via HDMI. Are you sure it works in other >applications? Sound is not muted? No. Amarok and other apps works well. >> Addons no longer work. No ARD or ZDF mediathek. > >Works for me! > >> No Prime addon either. > >Sorry, that's not supported at all. Work all under 21. >> Would say that 21 is not yet "mature". > >Perhaps you should have joined the "Kodi: Want to test the upcoming >release Omega 21?" I do a normal update. And then Kodi will also update. Normal. Should I now control all packages and block some? I don't think this is the right way. One possible could be to make an extra package for kodi20, kodi21 and so on. . In addition you could enable debugging output in Kodi and have >a look at ~/.kodi/temp/kodi.log. When you find something in there, >please let us know. Perhaps I will try. >> Is there still a possibility to switch back to version 20? > >No, it's very similar to when you requested a python version for Leap >which wasn't possible/available at that time. Not a good comparison. I guess I have no choice but to switch back to Flatpack. But what I hate. Or do you still have the old spec and other files, then I would build it myself again? Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am Montag, 8. April 2024, 17:15:48 CEST schrieb Manfred Hollstein: > Hi Eric, > > please follow up on the mailing list, thx! Sorry. No no intention. > On Mon, 08 Apr 2024, 16:57:38 +0200, Eric Schirra wrote: > > Am Montag, 8. April 2024, 16:35:34 CEST schrieb Manfred Hollstein: > > > Moin, > > > > > > On Mon, 08 Apr 2024, 16:24:59 +0200, Eric Schirra wrote: > > > > Hallo, > > > > > > > > nach dem heutigen Update auf kodi 21 startet dieses nicht mehr. > > > > > > > > Es kommt der Fehler: > > > > > > > > /usr/lib64/kodi/kodi.bin: symbol lookup error: > > > > /usr/lib64/kodi/kodi.bin: > > > > undefined symbol: ass_track_set_feature > > > > > > I guess this is on Leap, isn't it? If so, you need to update/upgrade > > > > Yes it is Leap 15.5 > > > > > libass9 > > > libdisplay-info1 > > > > This are installed: > > S | Name| Type | Version | Arch | Repository > > > > --+-+---+--++-- > > i | libass9 | Paket | 0.14.0-15.3.13.1 | x86_64 | update-sle (15.5) > > > > > > S | Name | Type | Version | Arch | Repository > > --+--+---+-+ > > +-- > > i | libdisplay-info1 | Paket | 0.1.1-150500.2.pm.1 | x86_64 | Packman > > Repository 15.5 (ftp.gwdg.de) > > libdisplay-info1 was a new package, while libass9 was installed, but > from a different vendor, which is why it wasn't upgraded. Upstream added > additional functionality to that package but did not increment the > SOname, hence libass9 appeared to be up2date enough when you installed > kodi-21.0. > > > > from the Multimedia repository, too! > > > > From openSUSE:lib:multimedia:libs? > > > > So if kodi requires a higher version than 0.14.0 of libass9, but this is > > not available, kodi 21 should never have been installed. So something > > would be missing in the spec file! > > No, this is only because of the too old libass9 in Leap 15.5 *and* 15.6 > (as usual), why we needed to link the package from openSUSE:Factory to > PMBS Multimedia/A_15.x-libass - but the real reason is, Upstream should > have increased the SOname/number - unfortunately, they didn't. > > Your solution would be > > sudo zypper up allow-vendor-change --from "Your-PMBS-Multimedia.repo" > libass9 Okay. Now I have libass9 from packman. Kodi can now be started. But that's it. No sound. Addons no longer work. No ARD or ZDF mediathek. No Prime addon either. Would say that 21 is not yet "mature". Is there still a possibility to switch back to version 20? Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi 21 - crash
Am Montag, 8. April 2024, 16:35:34 CEST schrieb Manfred Hollstein: > Moin, > > On Mon, 08 Apr 2024, 16:24:59 +0200, Eric Schirra wrote: > > Hallo, > > > > nach dem heutigen Update auf kodi 21 startet dieses nicht mehr. > > > > Es kommt der Fehler: > > > > /usr/lib64/kodi/kodi.bin: symbol lookup error: /usr/lib64/kodi/kodi.bin: > > undefined symbol: ass_track_set_feature > > I guess this is on Leap, isn't it? If so, you need to update/upgrade Yes it is Leap 15.5 > libass9 > libdisplay-info1 This are installed: S | Name| Type | Version | Arch | Repository --+-+---+--++-- i | libass9 | Paket | 0.14.0-15.3.13.1 | x86_64 | update-sle (15.5) S | Name | Type | Version | Arch | Repository --+--+---+-+ +-- i | libdisplay-info1 | Paket | 0.1.1-150500.2.pm.1 | x86_64 | Packman Repository 15.5 (ftp.gwdg.de) > from the Multimedia repository, too! From openSUSE:lib:multimedia:libs? So if kodi requires a higher version than 0.14.0 of libass9, but this is not available, kodi 21 should never have been installed. So something would be missing in the spec file! Or is it something else? Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Kodi 21 - crash
Hallo, nach dem heutigen Update auf kodi 21 startet dieses nicht mehr. Es kommt der Fehler: /usr/lib64/kodi/kodi.bin: symbol lookup error: /usr/lib64/kodi/kodi.bin: undefined symbol: ass_track_set_feature Gruß Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] obs-studio (openSUSE Tumbleweed x86_64) fails to start
Am Montag, 26. Februar 2024, 10:43:49 CET schrieb Konstantinos Sk: > Hello, > > Apologies for sending an email if it is not the appropriate way of > reporting bugs, I am very knew to all of this. > > OpenSUSE Tumbleweed had a recent update on qt6 that broke obs-studio. > Whenever I try to start it, it closes itself. Running it from the terminal > results in this error: > > obs: symbol lookup error: obs: undefined symbol: > _Zls6QDebugRK11QDockWidget, version Qt_6 > > I was told to report it to the packman packagers. No problem with my own obs-studio package. Runs without problems under Leap and also under Tumbleweed. Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi vs python - next update will use python-3.11
Am Dienstag, 26. Dezember 2023, 17:47:18 CET schrieb Manfred Hollstein: > The next update for Kodi Nexus 20.2 will introduce that change and might > result in needing libpython3_11-1_0 on your Leap 15.5 installation/ > system in case you don't already have that installed. As a result, the > addons will run in a Python 3.11 environment, which should help all > users who had been involved in the earlier discussions (see above), e.g. > Eric Schirra and Tom Weinmann to name just two. Users on Tumbleweed > should not see any difference. Hello Manfred, thank you for your Work. First tests with kodi-20.2-150500.5.pm.1 are positiv. Amazon plugin is working again. :-) Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi + Amazon
Am Montag, 16. Oktober 2023, 07:40:19 CEST schrieb Stefan Seyfried:
> On 14.10.23 13:50, Eric Schirra wrote:
> > Do you know %{?sle15_python_module_pythons}?
> > With this you can build python311 packages for Leap.
> > I myself have in my Homerepo now about 800 package in 311 for Leap. Why
> > this is not done centrally is not clear to me. Everyone must do this for
> > themselves. In my opinion a complete nonsense. But well, maybe I do not
> > understand the reason.
> > But couldn't it be done that way in Packman?
>
> would you provide the build power to do that? We're already struggling
> with people building stuff like kodi in their $HOME and not cleaning up
> the old, probably unused branches / test projects.
> I see that very clearly as I'm the provider of ~80% of the ARM build
> power available to OBS ;-)
> Let's see if this improves once newer, more powerful ARM boards are
> available, then I might upgrade the workers.
Unfortunately, I can not.
I also meant in my homerepo of opensuse.
As for creating packages in the homerepo I have such a guess.
The packages in the repos are once too old. On the other hand they do not
work. And third, people don't want to bother with the existing maintainers.
There come as abstruse and completely unnecessary demands.
The people just have something better to do. So to argue unnecessarily.
As said. Just a guess from me. And I refer only to the Repos under opensuse.
Whether it is the same with Packman, I can not judge.
But in opensuse obs you get delete requests from time to time. I think this is
done by script. But who does that and how i don't know.
> > Then you could also offer a working kodi with 311.
> > So kodi is more or less broken under Leap.
>
> Only the amazon plugin AFAICT, which packman does not even provide. You
> could as well fix the amazon plugin to also work with python 3.6.
I am not a programmer. And to bend a package which needs from upstream python
> 3.6, that it also works with <= 3.6 can't be the solution. If it would work
at all.
The problem is plain and simple, python in Leap is clearly too old and long
dead.
And whether this is only the Amazon plugin, I may also doubt.
It seems to me that kodi now uses python 3.11
https://kodi.tv/article/kodi-20-1-nexus-release/
> The other solution, if kodi really needs python > 3.6 would be to
> disable building it for anything older than Tumbleweed.
Exactly that.
Or just check before if the new version builds and runs and if not, keep the
old one.
Regards
Eric
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi + Amazon
Am 14. Oktober 2023 14:21:18 MESZ schrieb Manfred Hollstein :
>On Sat, 14 Oct 2023, 13:50:18 +0200, Eric Schirra wrote:
>> Am Samstag, 14. Oktober 2023, 13:24:41 CEST schrieb Manfred Hollstein:
>> > > > > > > > import soupsieve
>> > > > > > > >
>> > > > > > > > File
>> > > > > > > > "//.kodi/addons/script.module.soupsieve/lib
>> > > > > > > > /
>> > > > > > > >
>> > > > > > > > soupsieve/__init__.py", line 28
>> > > > > > > >
>> > > > > > > > from __future__ import annotations
>> > > > > > > >
>> > > > > > > > ^
>> > > > > > > > SyntaxError: future feature
>> > > > > > > > annotations
>> > > > > > > >
>> > > > > > > > is not defined
>> >
>> > I believe this is the source of your problem! "from __future__ import
>> > annotations" is only available from Python3.7 onwards, but Leap 15.5
>> > only has 3.6
>> >
>> > While there are python3.9, up to python3.11 available, almost all
>> > additional python modules do not exist for 3.9 or 3.11, though, so I'm
>> > afraid you're stuck on Leap 15.5. Tumbleweed would be the way to go I
>> > think!
>>
>> I already suspected that.
>> But then you must not update the package for Leap if it does not run. I
>> notice
>> this more often. In Packman but also in suse obs. There are simply built
>> package, which are built without error, but due to missing dependencies
>> later
>> do not run.
>>
>> Especially in python this happens more often because of the long dead python
>> in Leap.
>> Tumblewedd I do not like, because too unstable for me. I know it is super
>> stable etc. In the mailing list you just read other things. Especiallys, if
>> you also want to run a server with it. But is another topic.
>
>Strange, I run TW on all my systems for quite some time now. Agreed,
>there are some hickups sometime, but usually it actually works really
>well.
The demands on a stable system are probably different. A not please of the
server system is a no go
>> Do you know %{?sle15_python_module_pythons}?
>> With this you can build python311 packages for Leap.
>
>Then just do it! SUSE is apparently not willing to support newer python
>versions for their ancient SLE versions. I too don't like it, but that's
>it. If you need newer versions, TW is there for you.
>
>> I myself have in my Homerepo now about 800 package in 311 for Leap. Why this
>> is not done centrally is not clear to me. Everyone must do this for
>> themselves. In my opinion a complete nonsense. But well, maybe I do not
>> understand the reason.
>
>*I* absolutely don't need 311 for Leap, but it's you who needs it.
>Perhaps you can argue with some of the SUSE product managers and
>convince them, why it would be benefitial. If you already have them, why
>don't you create the SRs to submit the packages to the related
>openSUSE:Leap:15.5:Backports project?
>
>> But couldn't it be done that way in Packman?
>
>Nope, this is not Packman's job!
Why so aggressive?
I was just asking a question.
I also did not say that I absolutely want 3.11-python.
Whereas this ancient and since forever dead Python 3.6 is for me a security
risk and causes unnecessary work. But for me.
Packages that are important to me I bring to 3.11. For me, because the
unnecessary strife is too stupid for me.
But again I don't demand 3.11.
I only expect a working package under Leap. And if this is no longer possible,
because a newer Python is needed, which you have recognized yourself, then one
must not offer the current kodi. And you also have to use and query in spec the
required version for building.
I also don't need the latest KODi. Just a working one.
And that I am one of the very few who wants to access Amazon Prime under KODi,
I may doubt times quite strongly.
>> Then you could also offer a working kodi with 311.
>> So kodi is more or less broken under Leap.
>
>Apparently for you, nobody else complained that Kodi doesn't work on
>Leap.
Maybe because it makes less and less sense in/for opensuse.
Gruß
Eric
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi + Amazon
Am Samstag, 14. Oktober 2023, 13:24:41 CEST schrieb Manfred Hollstein:
> > > > > > > import soupsieve
> > > > > > >
> > > > > > > File
> > > > > > > "//.kodi/addons/script.module.soupsieve/lib
> > > > > > > /
> > > > > > >
> > > > > > > soupsieve/__init__.py", line 28
> > > > > > >
> > > > > > > from __future__ import annotations
> > > > > > >
> > > > > > > ^
> > > > > > > SyntaxError: future feature
> > > > > > > annotations
> > > > > > >
> > > > > > > is not defined
>
> I believe this is the source of your problem! "from __future__ import
> annotations" is only available from Python3.7 onwards, but Leap 15.5
> only has 3.6
>
> While there are python3.9, up to python3.11 available, almost all
> additional python modules do not exist for 3.9 or 3.11, though, so I'm
> afraid you're stuck on Leap 15.5. Tumbleweed would be the way to go I
> think!
I already suspected that.
But then you must not update the package for Leap if it does not run. I notice
this more often. In Packman but also in suse obs. There are simply built
package, which are built without error, but due to missing dependencies later
do not run.
Especially in python this happens more often because of the long dead python
in Leap.
Tumblewedd I do not like, because too unstable for me. I know it is super
stable etc. In the mailing list you just read other things. Especiallys, if
you also want to run a server with it. But is another topic.
Do you know %{?sle15_python_module_pythons}?
With this you can build python311 packages for Leap.
I myself have in my Homerepo now about 800 package in 311 for Leap. Why this
is not done centrally is not clear to me. Everyone must do this for
themselves. In my opinion a complete nonsense. But well, maybe I do not
understand the reason.
But couldn't it be done that way in Packman?
Then you could also offer a working kodi with 311.
So kodi is more or less broken under Leap.
Regards
Eric
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi + Amazon
Am Samstag, 14. Oktober 2023, 13:01:41 CEST schrieb Manfred Hollstein: > On Sat, 14 Oct 2023, 12:53:51 +0200, Eric Schirra wrote: > > Am Samstag, 14. Oktober 2023, 11:58:16 CEST schrieb Manfred Hollstein: > > > Hi Eric, > > > > > > On Sat, 14 Oct 2023, 11:50:40 +0200, Eric Schirra wrote: > > > > Am Sonntag, 1. Oktober 2023, 13:53:08 CEST schrieb Eric Schirra: > > > > > Hallo, > > > > > > > > > > das kodi paket von packman lief nun mehrere Jahre ohne Probleme. > > > > > Nun funtioniert das amazon plugin aber nicht mehr. > > > > > Ich habe noch mal ganz von vorne begonnen. > > > > > Sandman Repo installiert aus zip. > > > > > Dann aus dem repo das plugin installiert. > > > > > Wenn ich dann das Plugin aufrufe kommt ein Fehler und es bricht ab. > > > > > > > > > > Der Fehler im Log: > > > > > > > > > > error : EXCEPTION Thrown (PythonToCppException) : -->Python > > > > > callback/ script returned the following error<-- > > > > > - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS! > > > > > Error Type: > > > > > Error Contents: future feature annotations is not defined > > > > > (__init__.py, > > > > > line 28) > > > > > Traceback (most recent call last): > > > > > File > > > > > "//.kodi/addons/plugin.video.amazon-test/default. > > > > > py", > > > > > line 3, in > > > > > > > > > >from resources.lib.startup import EntryPoint > > > > > > > > > > File > > > > > "//.kodi/addons/plugin.video.amazon-test/ > > > > > > > > > > resources/lib/startup.py", line 7, in > > > > > > > > > >from .network import * > > > > > > > > > > File > > > > > "//.kodi/addons/plugin.video.amazon-test/ > > > > > > > > > > resources/lib/network.py", line 10, in > > > > > > > > > >import mechanicalsoup > > > > > > > > > > File > > > > > "//.kodi/addons/script.module.mechanicalsou > > > > > p/ > > > > > > > > > > lib/mechanicalsoup/__init__.py", line 2, in > > > > > > > > > >from .browser import Browser > > > > > > > > > > File > > > > > "//.kodi/addons/script.module.mechanicalsou > > > > > p/ > > > > > > > > > > lib/mechanicalsoup/browser.py", line 2, in > > > > > > > > > >import bs4 > > > > > > > > > > File > > > > > "//.kodi/addons/script.module.beautifulsoup > > > > > 4/ > > > > > > > > > > lib/bs4/__init__.py", line 37, in > > > > > > > > > >from .builder import ( > > > > > > > > > > File > > > > > "//.kodi/addons/script.module.beautifulsoup > > > > > 4/ > > > > > > > > > > lib/bs4/builder/__init__.py", line 9, in > > > > > > > > > >from bs4.element import ( > > > > > > > > > > File > > > > > "//.kodi/addons/script.module.beautifulsoup > > > > > 4/ > > > > > > > > > > lib/bs4/element.py", line 12, in > > > > > > > > > >from bs4.css import CSS > > > > > > > > > > File > > > > > "//.kodi/addons/script.module.beautifulsoup > > > > > 4/ > > > > > > > > > > lib/bs4/css.py", line 5, in > > > > > > > > > >import soupsieve > > > > > > > > > > File > > > > > "//.kodi/addons/script.module.soupsieve/lib > > > > > / > > > > > > > > > > soupsieve/__init__.py", line 28 > > > > > > > > > >from __future__ import annotations > > > > > > > > > > ^
Re: [packman] Kodi + Amazon
Am Samstag, 14. Oktober 2023, 11:58:16 CEST schrieb Manfred Hollstein: > Hi Eric, > > On Sat, 14 Oct 2023, 11:50:40 +0200, Eric Schirra wrote: > > Am Sonntag, 1. Oktober 2023, 13:53:08 CEST schrieb Eric Schirra: > > > Hallo, > > > > > > das kodi paket von packman lief nun mehrere Jahre ohne Probleme. > > > Nun funtioniert das amazon plugin aber nicht mehr. > > > Ich habe noch mal ganz von vorne begonnen. > > > Sandman Repo installiert aus zip. > > > Dann aus dem repo das plugin installiert. > > > Wenn ich dann das Plugin aufrufe kommt ein Fehler und es bricht ab. > > > > > > Der Fehler im Log: > > > > > > error : EXCEPTION Thrown (PythonToCppException) : -->Python > > > callback/ script returned the following error<-- > > > - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS! > > > Error Type: > > > Error Contents: future feature annotations is not defined (__init__.py, > > > line 28) > > > Traceback (most recent call last): > > > File > > > "//.kodi/addons/plugin.video.amazon-test/default.py", > > > line 3, in > > > > > >from resources.lib.startup import EntryPoint > > > > > > File "//.kodi/addons/plugin.video.amazon-test/ > > > > > > resources/lib/startup.py", line 7, in > > > > > >from .network import * > > > > > > File "//.kodi/addons/plugin.video.amazon-test/ > > > > > > resources/lib/network.py", line 10, in > > > > > >import mechanicalsoup > > > > > > File > > > "//.kodi/addons/script.module.mechanicalsoup/ > > > > > > lib/mechanicalsoup/__init__.py", line 2, in > > > > > >from .browser import Browser > > > > > > File > > > "//.kodi/addons/script.module.mechanicalsoup/ > > > > > > lib/mechanicalsoup/browser.py", line 2, in > > > > > >import bs4 > > > > > > File > > > "//.kodi/addons/script.module.beautifulsoup4/ > > > > > > lib/bs4/__init__.py", line 37, in > > > > > >from .builder import ( > > > > > > File > > > "//.kodi/addons/script.module.beautifulsoup4/ > > > > > > lib/bs4/builder/__init__.py", line 9, in > > > > > >from bs4.element import ( > > > > > > File > > > "//.kodi/addons/script.module.beautifulsoup4/ > > > > > > lib/bs4/element.py", line 12, in > > > > > >from bs4.css import CSS > > > > > > File > > > "//.kodi/addons/script.module.beautifulsoup4/ > > > > > > lib/bs4/css.py", line 5, in > > > > > >import soupsieve > > > > > > File > > > "//.kodi/addons/script.module.soupsieve/lib/ > > > > > > soupsieve/__init__.py", line 28 > > > > > >from __future__ import annotations > > > > > > ^ > > > SyntaxError: future feature > > > annotations > > > > > > is not defined > > > -->End of Python script error report<-- > > > > > > > > > Installiere ich das Plugin auf genau die gleiche Weise in einem flatpak > > > Paket, tritt der Fehler nicht auf und das Plugin funktioniert. > > > > Hallo maintainer des Paketes, > > > > warum keine Antwort? > > Oder tritt das Problem nur bei mir auf? > > I have to admit I don't even know what the "amazon plugin" is. Can you > please give some more details as to Amazon Prime Video under Kodi. > a) which OS are you using? Leap 15.5 > b) what is the "amazon plugin" and where do you get it from? The normal way as describe here: https://www.kodi-tipps.de/amazon-prime-kodi-addon-installieren-amazon-vod/ > Maybe someone will then be able to properly analyze that. hm. Many years it runs without problems. And it runs without problems under flatpak. Install both the same way. Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi + Amazon
Am Samstag, 14. Oktober 2023, 12:05:09 CEST schrieb Manfred Hollstein: > On Sat, 14 Oct 2023, 11:58:16 +0200, Manfred Hollstein wrote: > > Hi Eric, > > > > On Sat, 14 Oct 2023, 11:50:40 +0200, Eric Schirra wrote: > > > [...] > > > > I have to admit I don't even know what the "amazon plugin" is. Can you > > please give some more details as to > > > > a) which OS are you using? > > b) what is the "amazon plugin" and where do you get it from? > > > > Maybe someone will then be able to properly analyze that. > > I found this in the meantime: > > https://www.kodi-tipps.de/amazon-prime-kodi-addon-installieren-amazon-vod/ This is exactly how I proceeded. In kodi from packman. And also in kodi from flatpak. Packman does not run. Flatpalk run without problems. > Can you take a look at it please and try to follow it? There is also a > remark about a new Beta version which helped one user on Kodi 20.1 The kodi version of Packman is exactly the same from flatpak. An i use version 0.9.8 from plugin in flatpak. But all versions from plugin, 0.9.8 and all betas not run in packman kodi. I have send in my first post the logfile. I suspect there are some python packages not fitting. Gruß Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Kodi + Amazon
Am Sonntag, 1. Oktober 2023, 13:53:08 CEST schrieb Eric Schirra: > Hallo, > > das kodi paket von packman lief nun mehrere Jahre ohne Probleme. > Nun funtioniert das amazon plugin aber nicht mehr. > Ich habe noch mal ganz von vorne begonnen. > Sandman Repo installiert aus zip. > Dann aus dem repo das plugin installiert. > Wenn ich dann das Plugin aufrufe kommt ein Fehler und es bricht ab. > > Der Fehler im Log: > > error : EXCEPTION Thrown (PythonToCppException) : -->Python > callback/ script returned the following error<-- > - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS! > Error Type: > Error Contents: future feature annotations is not defined (__init__.py, line > 28) > Traceback (most recent call last): > File > "//.kodi/addons/plugin.video.amazon-test/default.py", > line 3, in >from resources.lib.startup import EntryPoint > File "//.kodi/addons/plugin.video.amazon-test/ > resources/lib/startup.py", line 7, in >from .network import * > File "//.kodi/addons/plugin.video.amazon-test/ > resources/lib/network.py", line 10, in >import mechanicalsoup > File "//.kodi/addons/script.module.mechanicalsoup/ > lib/mechanicalsoup/__init__.py", line 2, in >from .browser import Browser > File "//.kodi/addons/script.module.mechanicalsoup/ > lib/mechanicalsoup/browser.py", line 2, in >import bs4 > File "//.kodi/addons/script.module.beautifulsoup4/ > lib/bs4/__init__.py", line 37, in >from .builder import ( > File "//.kodi/addons/script.module.beautifulsoup4/ > lib/bs4/builder/__init__.py", line 9, in >from bs4.element import ( > File "//.kodi/addons/script.module.beautifulsoup4/ > lib/bs4/element.py", line 12, in >from bs4.css import CSS > File "//.kodi/addons/script.module.beautifulsoup4/ > lib/bs4/css.py", line 5, in >import soupsieve > File "//.kodi/addons/script.module.soupsieve/lib/ > soupsieve/__init__.py", line 28 >from __future__ import annotations > ^ > SyntaxError: future feature annotations > is not defined > -->End of Python script error report<-- > > > Installiere ich das Plugin auf genau die gleiche Weise in einem flatpak > Paket, tritt der Fehler nicht auf und das Plugin funktioniert. Hallo maintainer des Paketes, warum keine Antwort? Oder tritt das Problem nur bei mir auf? Gruß Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Kodi + Amazon
Hallo, das kodi paket von packman lief nun mehrere Jahre ohne Probleme. Nun funtioniert das amazon plugin aber nicht mehr. Ich habe noch mal ganz von vorne begonnen. Sandman Repo installiert aus zip. Dann aus dem repo das plugin installiert. Wenn ich dann das Plugin aufrufe kommt ein Fehler und es bricht ab. Der Fehler im Log: error : EXCEPTION Thrown (PythonToCppException) : -->Python callback/ script returned the following error<-- - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS! Error Type: Error Contents: future feature annotations is not defined (__init__.py, line 28) Traceback (most recent call last): File "//.kodi/addons/plugin.video.amazon-test/default.py", line 3, in from resources.lib.startup import EntryPoint File "//.kodi/addons/plugin.video.amazon-test/ resources/lib/startup.py", line 7, in from .network import * File "//.kodi/addons/plugin.video.amazon-test/ resources/lib/network.py", line 10, in import mechanicalsoup File "//.kodi/addons/script.module.mechanicalsoup/ lib/mechanicalsoup/__init__.py", line 2, in from .browser import Browser File "//.kodi/addons/script.module.mechanicalsoup/ lib/mechanicalsoup/browser.py", line 2, in import bs4 File "//.kodi/addons/script.module.beautifulsoup4/ lib/bs4/__init__.py", line 37, in from .builder import ( File "//.kodi/addons/script.module.beautifulsoup4/ lib/bs4/builder/__init__.py", line 9, in from bs4.element import ( File "//.kodi/addons/script.module.beautifulsoup4/ lib/bs4/element.py", line 12, in from bs4.css import CSS File "//.kodi/addons/script.module.beautifulsoup4/ lib/bs4/css.py", line 5, in import soupsieve File "//.kodi/addons/script.module.soupsieve/lib/ soupsieve/__init__.py", line 28 from __future__ import annotations ^ SyntaxError: future feature annotations is not defined -->End of Python script error report<-- Installiere ich das Plugin auf genau die gleiche Weise in einem flatpak Paket, tritt der Fehler nicht auf und das Plugin funktioniert. Gruß Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Streamtuner2 paket bei packman für Opensuse 15.5 Leap
Am Samstag, 15. Juli 2023, 16:44:29 CEST schrieb Jürgen Falbrede: > Moin aus dem Norden, > > als User ohne tiefergehende Linux Kentnisse weiß ich mir nicht anders zu > helfen als Ihnen diese Mail zu schreiben. > > Es geht um Opensuse Leap 15.5 > > Im Packman Repo für Opensuse Leap 15.5 > > URL: https://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Leap_15.5/ > > ist das folgende streamtuner2 Paket zu finden dessen Abhängigkeiten per > Yast2 nicht aufzulösen sind. > > Ich habe mit meinem wenigen Wissen, unter anderem auch durch den > erfolglosen Versuch des Einbindens anderer Repos mit Paketen für Python > gtk, es nicht hinbekommen die Abhängigkeiten zu erfüllen. > > Dieses Paket im Packman Repo scheint python 2.7 zu erfordern. Opensuse > Leap 15.5 enthält aber wohl python 3 in den Standardrepos soweit ich das > nachvollziehen kann. python2.7 ist sowas von tot. Selbst python3.6 ist sowas von tot. Und selbst 3.7 ist glaub nun tot. Hast du mal steamtuner von meinem repo versucht? https://build.opensuse.org/package/show/home:ecsos/streamtuner2 Gruß Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Kodi crash
Since probably kodi version 20, kodi crashes under Leap 15.4. Is this only happening to me or to others as well? Greetings Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] yt-dlp 2022.08.08 broken on 15.3
Am 12. August 2022 03:38:50 MESZ schrieb Jason Craig : >On 8/11/2022 17:53, Eric Schirra wrote: >> >> And I think this packages are not in Leap or sles for python 3.9 or 3.10. >> >> Python 3.6 is simple dead. >> And Leap, also 15.4, rides a dead horse. >> >> Only solutions are build all require modules for python 3.9/3.10 yourself, >> put the require modules in yt-dlp package, use Tumbleweed or another >> distribution. >> >Well, since those packages are all available via PyPi as wheels there is the >alternative of > >$ python3.10 -m venv [dir] >$ [dir]/bin/pip install yt-dlp >$ [dir]/bin/yt-dlp [whatever you want to do] > >Subbing of course whatever updated version of Python is available on 15.3 that >you have installed, as well as having installed python310-virtualenv (or >whatever version). > >You do waste some space on those duplicated packages from above (it is about >56M for me, but on Tumbleweed), and you have to keep things updated via pip in >that venv, so there are drawbacks. But this is probably the easiest option if >no one is going to build those packages for Leap. Mixing different installation types (rpm / pip) is never good. Even after a short time, it can no longer be traced. This can then cause other problems at a later point in time. And the real problem was that the rpm package yt-dlp does not work. And under given conditions, a functioning rpm package cannot be created. Of course, you can install everything manually. With all its disadvantages. But this is nothing for the masses. And certainly not a functioning rpm package. Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] yt-dlp 2022.08.08 broken on 15.3
Am 11. August 2022 22:06:17 MESZ schrieb Olaf Hering :
>Thu, 11 Aug 2022 12:32:01 +0200 Luigi Baldoni :
>
>> Keep an eye on sr#994385.
>
>This works only Leap 15.4, which happens to have python39-devel.
>But there is no such package in SP4. SLE-Module-Python3-15-SP4 has only 3.10.
>
>I think an additional change should enforce python310-devel for
>"0%{?sle_version} > 150300", and perhaps drop the -xml pkg in all cases.
I think this is not enough.
Yt-dlp also requires:
mutagen
pycryptodomex
websockets
brotli; platform_python_implementation=='CPython'brotlicffi;
platform_python_implementation!='CPython'
certifi
See setup.py from source.
And I think this packages are not in Leap or sles for python 3.9 or 3.10.
Python 3.6 is simple dead.
And Leap, also 15.4, rides a dead horse.
Only solutions are build all require modules for python 3.9/3.10 yourself, put
the require modules in yt-dlp package, use Tumbleweed or another distribution.
Regards
Eric
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] yt-dlp 2022.08.08 broken on 15.3
Am Donnerstag, 11. August 2022, 14:43:20 CEST schrieb Masaru Nomiya: > MN> > The solution in Leap 15.3 is installing python 3.8 (3.7 isn't > MN> > availlable, is it?) and use update-laternatives. > > Eric> Not so simple as it seems. > > No, you may be asked to install some additional packages, but it is > not so difficult. > > Eric> All python-modules in Leap are build against default dead > Eric> python 3.6. > > I know it well. > Switching to python 3.8 and building with update-alternatives has no > effect on a python 3.6 system. > > Eric> So you can not simple use 3.8 to build, because modules are not > Eric> build against 3.8. > > Just try it with update-alternatives and you'll understand what I mean. With this package you are lucky that the only dependency it requires is python39-xml. And this is included in the python39-base package. That's why it works so easily here. Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] youtube-dl replacement
Am Dienstag, 4. Januar 2022, 13:59:10 CET schrieb Mathias Homann: > Am Montag, 20. Dezember 2021, 08:36:28 CET schrieb Mathias Homann: > > I'm going to work on having my autobuild method work with the new > > sources as well - might take a few days or so. > > I have a working package in https://pmbs.links2linux.de/package/show/ > home:lemmy04:branches:Multimedia/youtube-dl, the automated building similar > to what is happening with Multimedia/youtube-dl works. > > I think we should switch - the original youtube-dl seems to be abandoned... Think not. http://ytdl-org.github.io/youtube-dl/ https://github.com/ytdl-org/youtube-dl/ Regards Eric ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] dvdinfo 0.9.2-pm152.2.7 (openSUSE_Leap 15.2/x86_64)
Hm. Da bin ich mir nicht so ganz sicher. Denn hier gibt es qt4: https://build.opensuse.org/package/show/openSUSE%3ABackports%3ASLE-15/libqt4 Gruß Eric Am 10. Juni 2021 18:52:55 MESZ schrieb Olaf Hering : >Am Mon, 7 Jun 2021 22:17:47 +0200 >schrieb Markus Reckwerth : > >> ist es möglich openSUSE_Leap 15.3 als build target hinzuzufügen? > >Es gibt kein Qt4 in 15.3. > >Vielleicht hilft es die 15.2 Leap und Packman repos mit niedriger Priorität >hinzuzufügen. > >Olaf ___ Packman mailing list Packman@links2linux.de https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Mediatomb no binary
Am 03.02.2013 08:51, schrieb Ralf Lang: #Am 03.02.2013 07:58, schrieb Curtis J Blank: Sorry to bother you but.. Just did an online update which updated to mediatomb-0.12.1.svn2103-2.4.x86_64 now this happens on startup: /usr/bin/mediatomb not installed In looking at the file list of the rpm package there does not appear to be any binary included? I think this is a problem with symlink. An symlink mediatomb to mediatomb-sqlite or mediatomb-mysql is missing. After each update. This link ist missing. I wrote this for a long time ago. Gruß eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Can't install kdenlive
Am 12.08.2012 22:47, schrieb Eric Schirra: Am 12.08.2012 11:15, schrieb Cristian Morales Vega: And i must rename libmltjackrack.so, so it does not crash. I can't reproduce that problem. When I use the libmlt5-modules-package from packman kdenlive crashes. When I use the libmlt5-modules from packman, and rename libmltjackrack, then kdenlive runs. When i use die libmlt5-modules from opensuse:KR49 kdenlive runs too and i must not rename libmltjackrack. New Info after tests. With mlt from opensuse i can not open mpg-files. So i switch back to libmlt5 from packman. Now it crashes. I rename libmltjackrack.so kdenlive from packman starts and i can open mpg's. It's now running well. eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Can't install kdenlive
Am 11.08.2012 13:50, schrieb Dmitriy Perlow: Eric Schirra e...@schirra.net писал(а) в своём письме Sat, 11 Aug 2012 13:56:47 +0300: Hello. Seems to be broken because of libmlt only existance. Hello, i wan't install kdenlive on openSUSE 12.1 64bit, but it is not possible. Yast says: mlt needs, but no repository offer it. Can someone please correct this? Thank you for your fast help. But why does it now work? I look in your BuildServer and it seams the spec-files is the same, or not? I have some things too. I must manuell install libmlt5-data and libmlt5-modules. Yast does it not automatically. And i must rename libmltjackrack.so, so it does not crash. And i must change mlt to mlt-5 at first start from kdenlive in the path for profiles. And kdenlive is not found over search in KDE-Menu. eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Can't install kdenlive
Am 12.08.2012 11:15, schrieb Cristian Morales Vega: And i must rename libmltjackrack.so, so it does not crash. I can't reproduce that problem. When I use the libmlt5-modules-package from packman kdenlive crashes. When I use the libmlt5-modules from packman, and rename libmltjackrack, then kdenlive runs. When i use die libmlt5-modules from opensuse:KR49 kdenlive runs too and i must not rename libmltjackrack. eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Can't install kdenlive
Hello, i wan't install kdenlive on openSUSE 12.1 64bit, but it is not possible. Yast says: mlt needs, but no repository offer it. Can someone please correct this? Thank you very much, Gruß eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] openttd + naev
Hallo Liste, bei 64bit fehlen die aktuellen Paketversionen openttd und naev. Die openttd-data und die naev-data sind aktueller als die anderen beiden. Kann das bitte jemand korrigieren? Danke. Gruß Eric ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] openttd + naev
Am 21.04.2012 16:17, schrieb Pascal Bleser: On 2012-04-21 12:35:35 (+0200), Eric Schirra e...@schirra.net wrote: bei 64bit fehlen die aktuellen Paketversionen openttd und naev. Die openttd-data und die naev-data sind aktueller als die anderen beiden. Kann das bitte jemand korrigieren? Beide Pakete sind im games Repository auf build.opensuse.org, und nicht bei Packman :) Oh. Sorry. Natürlich. Wie komme ich jetzt auf Packaman... Gruß Eric ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Mediatomb Bitte
Hallo, bitte korrigiert mal den Fehler bei Mediatomb mit dem fehlenden symbolischen Link. Nach jedem Update ist dieser fort und muss manuell neu angelegt werden. Sonst lässt sich mediatomb über rcmediatomb nicht starten. Gruß eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] mediatomb symlink
Hallo, es wurde hier schon mehrmals über das Problem des fehlenden Links von mediatomb auf z.B mediatomb-sqlite berichtet. Nach jedem Update ist mein selbst erstellter symbolische Link von mediatomb auf mediatomb-sqlite weg. Kann man denn nicht in endlich mal in den spec-file angeben, das die entsprechenden Links bei einem Update gesetzt werden? Gruß eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Problem liborc und libgstvp
Am 10.02.2011 22:45, schrieb Eric Schirra: gstreamer-bad lässt sich immer noch nicht installieren, da die Abhängigkeit von libgstvd nicht stimmt. Aktuell ist sie auf liborc0_4-0. Diese Paket gibt es nicht. Es lautet mittlerweile liborc-0_4-0. Würdet ihr das bitte korrigieren? Leider ist der Fehler immer noch nicht behoben. Es wird immer die lib liborc0_4-0 gesucht. Diese ist aber nicht vorhanden. Es ist die liborc-0_4-0 vorhanden. Gruß eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Fehler im gstreamer-plugin-bad 11.3, 64bit
Hallo, das gstreamer-plugin-bad für 11.3 64bit lässt sich nicht installieren. Es kommt in Yast die Meldung: liborc0_4-0 = 0.4.6, benötigt von libgstvdp-0_10-0-0.10.21-99.pm.1014.x86_64, wird von keinem Repository angegeben. Ebenso lassen sich dioe Pakete libgstphotography-0_10-0-0.10.21-999.pm.1014.x86_64, libgstsignalprocessor-0_10-0-0.10.21-999.pm.1014.x86_64 und libgstbasevideo-0_10-0-0.10.21-999.pm.1014.x86_64 ebenso mit der Fehlermeldung von liborc nicht installieren. Gruß eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] mlt 64bit missing
Hello, 64bit-packages missing for: mlt libmlt++ libmlt2 libfaad faad2 libgstvdp eRiC ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] gstreamer 64bit-Pakete fehlen
Hallo Packman-Team, für 11.3 fehlen etliche 64-Pakete von gestreamer. Manche sind vorhanden. Andere wiederum nicht. Gruß Eric ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Fehler hplip und KDE4
Hallo Packman-Team, leider läuft hplip nicht richtig unter KDE4. Das hp-systray Icon erscheint nicht in dem Systemabschnitt der Kontrollleiste, sondern oben Links auf dem Desktop. Meiner Meinung nach fehlt der qt4-Support. hp-toolbox lässt sich nicht mit hp-toolbox --qt4 starten. Meine Umgebung: KDE 4.2 64bit aktuell aus den Build-Repositories. Wäre toll Ihr könntet das beheben. Gruß Eric ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Speicherzugriffsfehler qdvdauthor
Hallo, qdvdauthor läuft bei mir nicht. Und zwar auf zwei verschiedenen Mainboards mit selben Fehler. Bei beiden kommt ein Speicherzugriffsfehler, wenn ich ein Bild zu einer Slideshow hinzufügen möchte. Und zwar in dem Moment, wenn ich nach der Auswahl des Bildes OK drücke. Es betrifft meinen 32bit- und 64bit-Rechner. Benutzte ich aber den grafischen installer/configurator aus den Quellen von qdvdauthor und führe hier execute aus, kann ich ein Bild hinzufügen. Kompiliere ich dann daraus und starte qdvdauthor mit anschließender Auswahl des Bildes stürzt die Anwendnung wieder ab. Kann ich zur Hilfe irgendwelche Debugmeldungen schicken? Wenn ja wie? Gruß Eric ___ Packman mailing list Packman@links2linux.de http://212.112.227.138/cgi-bin/mailman/listinfo/packman
[packman] (no subject)
Hallo, qdvdauthor läuft bei mir nicht. Und zwar auf zwei verschiedenen Mainboards mit selben Fehler. Bei beiden kommte ein Speicherzugriffsfehler, wenn ich ein Bild zu einer Slideshow hinzufügen möchte. Und zwar in dem Moment, wenn ich nach der Auswahl des Bildes OK drücke. Es betrifft meinen 32bit- und 64bit-Rechner. Benutzte ich aber den grafischen installer/configurator aus den Quellen von qdvdauthor und führe hier execute aus, kann ich ein Bild hinzufügen. Kompiliere ich dann daraus und starte qdvdauthor mit anschließendem auswahl des Bildes stürtzt die Anwednung wieder ab. Kann ich zur Hilfe irgendwelche debugmeldugen schicken? Wenn ja wie? -- Gruß eRiC ___ Packman mailing list Packman@links2linux.de http://212.112.227.138/cgi-bin/mailman/listinfo/packman
