Re: [packman] Enable all Packman builds for Slowroll?

[Manfred Hollstein]

On Thu, 06 Jun 2024, 17:42:18 +0200, Manfred Hollstein wrote:
> On Thu, 06 Jun 2024, 13:02:23 +0200, Manfred Hollstein wrote:
> > [...]
> > I would vote for building for openSUSE:Slowroll:Base as otherwise one of
> > the packages I am co-maintainer for does not build due to unresolvables:
> > 
> >   $ osc buildinfo home:manfred-h:server:messaging telegram-desktop 
> > openSUSE_Slowroll x86_64
> >> repository="openSUSE_Slowroll" package="telegram-desktop" 
> > downloadurl="https://download.opensuse.org/repositories;>
> > x86_64
> > unresolvable: nothing provides qt6-core-private-devel = 6.7.0 
> > needed by qt6-waylandclient-private-devel, (got version 
> > 6.7.1-1.0.4.2.sr20240429), nothing provides qt6-gui-private-devel = 6.7.0 
> > needed by qt6-waylandclient-private-devel, (got version 
> > 6.7.1-1.0.4.2.sr20240429)
> > bb83310b8cc8a2f2ff3021e8aa0b554c
> > 272448165fc29b0fd3ca3bd35d018956
> > 127
> > telegram-desktop.spec
> > telegram-desktop.spec
> > 5.1.2-406
> > 1
> > 406.1
> > 0
> >   
> > 
> > With openSUSE:Slowroll:Base everything is fine.
> > 
> > While this is not actually a Packman package, similar stuff can happen
> > here, too.
> 
> To make it really clear, I added a new repo "openSUSE_Slowroll_daily"
> to my project:
> 
>   <https://build.opensuse.org/projects/home:manfred-h:server:messaging/meta>
> 
> with these results:
> 
>   
> <https://build.opensuse.org/package/show/home:manfred-h:server:messaging/telegram-desktop>
> 
> > > Ciao
> > > Bernhard M.
> > > 
> > > [1] https://en.opensuse.org/openSUSE:Slowroll
> 
> I think I'm going to change the entries for Slowroll in Packman
> accordingly.

Hmm, somebody beat me to this. Who made the change in Essential's repo :-) ?

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Enable all Packman builds for Slowroll?

[Manfred Hollstein]

On Thu, 06 Jun 2024, 13:02:23 +0200, Manfred Hollstein wrote:
> Hi Bernhard,
> 
> On Sun, 02 Jun 2024, 17:47:48 +0200, Bernhard M. Wiedemann wrote:
> > Dear PackMan maintainers,
> > 
> > My openSUSE Slowroll distribution [1] has matured nicely in recent months.
> > I'll soon start to call it "Beta" instead of "Experimental".
> > 
> > Now, some users are already interested to have more Packman packages
> > available.
> > 
> > The most reliable way would be to use the same as in
> > https://pmbs.links2linux.de/projects/Essentials/meta .
> > The openSUSE:Slowroll repo would get minor version updates daily.
> > 
> > If you want to save build power, you could instead build for
> > openSUSE:Slowroll:Base that only changes once per month.
> > The updated Slowroll packages should mostly be minor updates that keep
> > ABI-compatibility during that time.
> > 
> > What do you think?
> 
> I would vote for building for openSUSE:Slowroll:Base as otherwise one of
> the packages I am co-maintainer for does not build due to unresolvables:
> 
>   $ osc buildinfo home:manfred-h:server:messaging telegram-desktop 
> openSUSE_Slowroll x86_64
>repository="openSUSE_Slowroll" package="telegram-desktop" 
> downloadurl="https://download.opensuse.org/repositories;>
> x86_64
> unresolvable: nothing provides qt6-core-private-devel = 6.7.0 
> needed by qt6-waylandclient-private-devel, (got version 
> 6.7.1-1.0.4.2.sr20240429), nothing provides qt6-gui-private-devel = 6.7.0 
> needed by qt6-waylandclient-private-devel, (got version 
> 6.7.1-1.0.4.2.sr20240429)
> bb83310b8cc8a2f2ff3021e8aa0b554c
> 272448165fc29b0fd3ca3bd35d018956
> 127
> telegram-desktop.spec
> telegram-desktop.spec
> 5.1.2-406
> 1
> 406.1
> 0
>   
> 
> With openSUSE:Slowroll:Base everything is fine.
> 
> While this is not actually a Packman package, similar stuff can happen
> here, too.

To make it really clear, I added a new repo "openSUSE_Slowroll_daily"
to my project:

  <https://build.opensuse.org/projects/home:manfred-h:server:messaging/meta>

with these results:

  
<https://build.opensuse.org/package/show/home:manfred-h:server:messaging/telegram-desktop>

> > Ciao
> > Bernhard M.
> > 
> > [1] https://en.opensuse.org/openSUSE:Slowroll

I think I'm going to change the entries for Slowroll in Packman
accordingly.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Enable all Packman builds for Slowroll?

[Manfred Hollstein]

Hi Bernhard,

On Sun, 02 Jun 2024, 17:47:48 +0200, Bernhard M. Wiedemann wrote:
> Dear PackMan maintainers,
> 
> My openSUSE Slowroll distribution [1] has matured nicely in recent months.
> I'll soon start to call it "Beta" instead of "Experimental".
> 
> Now, some users are already interested to have more Packman packages
> available.
> 
> The most reliable way would be to use the same as in
> https://pmbs.links2linux.de/projects/Essentials/meta .
> The openSUSE:Slowroll repo would get minor version updates daily.
> 
> If you want to save build power, you could instead build for
> openSUSE:Slowroll:Base that only changes once per month.
> The updated Slowroll packages should mostly be minor updates that keep
> ABI-compatibility during that time.
> 
> What do you think?

I would vote for building for openSUSE:Slowroll:Base as otherwise one of
the packages I am co-maintainer for does not build due to unresolvables:

  $ osc buildinfo home:manfred-h:server:messaging telegram-desktop 
openSUSE_Slowroll x86_64
  https://download.opensuse.org/repositories;>
x86_64
unresolvable: nothing provides qt6-core-private-devel = 6.7.0 needed 
by qt6-waylandclient-private-devel, (got version 6.7.1-1.0.4.2.sr20240429), 
nothing provides qt6-gui-private-devel = 6.7.0 needed by 
qt6-waylandclient-private-devel, (got version 6.7.1-1.0.4.2.sr20240429)
bb83310b8cc8a2f2ff3021e8aa0b554c
272448165fc29b0fd3ca3bd35d018956
127
telegram-desktop.spec
telegram-desktop.spec
5.1.2-406
1
406.1
0
  

With openSUSE:Slowroll:Base everything is fine.

While this is not actually a Packman package, similar stuff can happen
here, too.

> Ciao
> Bernhard M.
> 
> [1] https://en.opensuse.org/openSUSE:Slowroll

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] [For maintainers] ffmpeg-7 for your application, or not?

[Manfred Hollstein]

Hi there,

if you are maintaining a program/package/application which makes use of
ffmpeg, and you are wondering if it works with ffmpeg-7, here's a hint
in case it does not - I just found out that kodi does not build with
ffmpeg-7.

Here's the list of BuildRequires: used by kodi and kodi.binary-addons:

  BuildRequires:  (pkgconfig(libavcodec) >= 60 with pkgconfig(libavcodec) < 61)
  BuildRequires:  (pkgconfig(libavfilter) >= 9 with pkgconfig(libavfilter) < 10)
  BuildRequires:  (pkgconfig(libavformat) >= 60 with pkgconfig(libavformat) < 
61)
  BuildRequires:  (pkgconfig(libavutil) >= 58 with pkgconfig(libavutil) < 59)
  BuildRequires:  (pkgconfig(libpostproc) >= 57 with pkgconfig(libpostproc) < 
58)
  BuildRequires:  (pkgconfig(libswresample) >= 4 with pkgconfig(libswresample) 
< 5)
  BuildRequires:  (pkgconfig(libswscale) >= 7 with pkgconfig(libswscale) < 8)

The syntax is not that obvious, so I though I'd share it with other
maintainers.

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi Eric,

On Wed, 08 May 2024, 16:03:38 +0200, Eric Schirra wrote:
> 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

Good to hear.

> 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

I see this, too, but only on Tumbleweed! I just ran kodi again on my
Leap 15.5 system and it terminated cleanly. Is your system up-to-date?

> So i'm return to 20.

Please give it another try :-)

> Regards
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Good morning,

On Fri, 10 May 2024, 03:31:36 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : 
>   Date & Time: Thu, 9 May 2024 13:32:45 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MN> > I have no idea what you are talking about.
>  
> MN> > It plays fine on my kodi, but not kodi from Packman.
> 
> MH>  That is what I'm talking about! Of course, I use kodi *and* ffmpeg from
> MH>  Packman, and playing back your videos works fine for me!
> [...]
> 
> When I went to bed last night, I had it all figured out.
> 
> When I went to bed last night, I had it all figured out.
> 
> My problem with Packman kodi is that I have installed mainstream
> ffmpeg instead of Packman.
> 
> I have no intention of using the Packman repository.

well, then please don't report your issues here in the Packman mailing
list!

> Best Regards.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi Masaru,

On Thu, 09 May 2024, 12:33:31 +0200, Masaru Nomiya wrote:
> [...]
> MN> > 
> https://drive.google.com/file/d/174yntQlgHZhCrfrvq6dSF_qJWkJsWkYR/view?usp=drive_link
>  
> MH> > 
> https://drive.google.com/file/d/1rvJnDoEm-RlSWpKmnkuVQ-BqjApsl5lj/view?usp=sharing
>  
> MH> > 
> https://drive.google.com/file/d/17cEw66Ai1i-EN7G6QtzLDxQsLZ_23nsG/view?usp=sharing
> 
> MH>  I just downloaded all three, put them into one directory, added that
> MH>  directory as a video source in Kodi, and Kodi then played them all back
> MH>  without any issue. To me this looks like something is wrong with your
> MH>  ffmpeg configuration.
> 
> I have no idea what you are talking about.
> 
> It plays fine on my kodi, but not kodi from Packman.

That is what I'm talking about! Of course, I use kodi *and* ffmpeg from
Packman, and playing back your videos works fine for me!

> So why are you talking about ffmpeg settings?

Because you said you are including ffmpeg (and spdlog) in *your*
local build as static libraries, hence you configure them yourself.

> First of all, I have never heard of ffmpeg settings related to kodi.

> If that's your case, I'd like to see your ffmpeg settings.

I meant the "configure" settings for ffmpeg which define which codecs to
include or exclude; you find them from line 550 to 684 in

  


> Best Regards.

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi Masaru,

On Thu, 09 May 2024, 02:56:26 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : 
>   Date & Time: Wed, 8 May 2024 16:13:31 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MN> > Anyway, all I can say is that the sound changes a lot depending on the
> MN> > settings.
> MN> > Of course, it really shows off Van Halen's greatness. v(^o^)
> 
> MH>  OK, so no general issue, but your user specific configuration.
> 
> I use 10 files for configuration, of which only two are specific to
> me, the rest are included in the pipewire package.
> 
> In my 60 years of audio experience, I have never experienced such
> freedom to change the sound, which is why I am so impressed with
> pipewire.
> 
> If you play electric guitar too, you know that the only way to improve
> sound quality is to buy a new guitair and/or amp, which inevitably
> leads to a bottomless pit of money.

I know what you are talking about... Collected a two digit number of
guitars over the years myself ;-)

> I think it is no exaggeration to say that pipewire is the hero that
> will rescue us from that bottomless pit.

To be honest, I prefer my real amp with the Helix over playing via the
PC.

> [...]
> MN> > There are a few, but what about these?
> MN> >   https://youtu.be/SlhIQYd-qAg
> 
> MH>  Clicked on most of them and downdloaded a few, but they were all VP9
> MH>  format. Please send me a real link to a h264 encoded file and to an rv40
> MH>  encoded file which don't work for you.
> 
> Sorry, Sony's file format has been changed, and now one rv40 file has
> been deleted from the email attachment.
> 
> I have uploaded the files as follows, so please use these;
> 
> https://drive.google.com/file/d/174yntQlgHZhCrfrvq6dSF_qJWkJsWkYR/view?usp=drive_link
> 
> https://drive.google.com/file/d/1rvJnDoEm-RlSWpKmnkuVQ-BqjApsl5lj/view?usp=sharing
> 
> https://drive.google.com/file/d/17cEw66Ai1i-EN7G6QtzLDxQsLZ_23nsG/view?usp=sharing

I just downloaded all three, put them into one directory, added that
directory as a video source in Kodi, and Kodi then played them all back
without any issue. To me this looks like something is wrong with your
ffmpeg configuration.

> Kind Regards.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi Masaru,

On Wed, 08 May 2024, 12:58:06 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : 
>   Date & Time: Wed, 8 May 2024 11:38:06 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> MH>  Hi Masaru (or is Nomiya your first name?),
> 
> Masaru is first name.
> In Japanese, I write Nomiya Masaru.

Yes, this is what I know, but did not know if you are using one way or
the other ;)

> [...]
> MH>  Based on your "fix for pipewire" below, is it right that it does work
> MH>  now?
> 
> Yes.

Great!

> MN> > [...]
> MN> > I've found the cause.
> 
> MN> > I found a problem with the pipedwire configuration, fixed it, and
> MN> > everything works fine.
> 
> MH>  Great! Do you mind sharing the "problem with the pipewire
> MH>  configuration"? Perhaps the fix should go into the official pipewire
> MH>  packages...
> 
> Most users do not have any settings of pipewire.
> In fact, they don't even have to do anything to hear the sound.
> Maybe that's why Google didn't give me any advice.
> 
> BTW, I was curious about the many filter files in the pipewire package,
> and I was challenged by the idea that these meant that the sound could
> be customized.
> Finally, I'm able to create a sound that I like.
> I enjoy my music every day.
> 
> Surprisingly, I am having difficulty playing Taylor Swift, and am
> wondering if her songs are the reference audio for the settings.
> (But I don't know how good her songs are... (^^;;).
> 
> Anyway, all I can say is that the sound changes a lot depending on the
> settings.
> Of course, it really shows off Van Halen's greatness. v(^o^)

OK, so no general issue, but your user specific configuration.

> [...]
> MN> > As I wrote in a previous email, you are right, in the case of the
> MN> > pilseaido system, --audio-backend=pulseaudio must be added.
> 
> MH>  Yep, that's what my patch added.
> 
> Sorry, I missed.
> 
> [...]
> MH>  On Tumbleweed my patch does not change anything. So you're right in that
> MH>  the change was only relevant for Leap. The more I think about it, I
> MH>  agree with you that we should disable all PW stuff on Leap, but leave PA
> MH>  and PW enabled for Tumbleweed.
> 
> I do agree.

Creat!

> [...]
> MN> > BTW, I have question.
>  
> MN> > The packman kodi can't display videos;
>  
> MN> >   1. codec is h264  
>  
> MN> >   2. codec is rv40
> 
> MH>  Do you have examples for these? h264 can be played here without issues.
> 
> There are a few, but what about these?
> 
>   https://youtu.be/SlhIQYd-qAg

Clicked on most of them and downdloaded a few, but they were all VP9
format. Please send me a real link to a h264 encoded file and to an rv40
encoded file which don't work for you.

> MN> > My kodi plays fine, but are these specifications?
> 
> MH>  Which ffmpeg packages are you using?
> 
> I forgot to mention that I build ffmpeg and many other files such as
> spdlog in the form of static libraries to avoid conflicts with system
> libraries, so I have been using ffmpeg 6.1.1 since late last year.
> Needless to say, I have not changed the program structure of kodi.
> 
> But I don't think the problem of not being able to play has anything
> to do with this.

Hmm, will wait for the files which do not work for you...

> Best Regards & Good Night.

Cheers and have a good one!

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi there,

On Wed, 08 May 2024, 11:38:06 +0200, Manfred Hollstein wrote:
> [...]
> > But Tumbleweed, as you know, is not a pulseaudio system, but a
> > pipewire system, and --audio-backend=pulseaudio is to make the kodi
> > sound via pipewire-pulse. Does it make sense?
> > I think it's rather unnecessary.
> 
> On Tumbleweed my patch does not change anything. So you're right in that
> the change was only relevant for Leap. The more I think about it, I
> agree with you that we should disable all PW stuff on Leap, but leave PA
> and PW enabled for Tumbleweed.

This is now <https://pmbs.links2linux.org/request/show/6048>; once Sagi
approves it, Kodi on Leap does not consider any Pipewire stuff at all
and defaults to use PulseAudio only. Nothing is changed on Tumbleweed,
as the default setup works; depending on the user specific configuration
or setup, one can still specify which audio-backend should be used -
the default on Tumbleweed remains Pipewire with a _normal_ installation,
i.e. no locks to rule-out Pipewire. If pipewire-pulseaudio does not
exist, like on two of my systems used as HTPCs, and pulseaudio exists,
then the start script automatically adds "--audio-backend=pulseaudio",
but again, this is not a _normal_ installation!

@Sagi: can you please review this change?

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[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.

> Regards
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi Masaru (or is Nomiya your first name?),

I strip lots of stuff below to make it more readable.

On Wed, 08 May 2024, 11:04:39 +0200, Masaru Nomiya wrote:
> [...]
> MH>  let me ask one question first: did kodi-21 from Packman work for you at
> MH>  all? If so, when did the problem start?
> 
> Good question.
> 
> Thepackman kodi worked with --audio-backend=pulseaudio as well as my
> own build of kodi.

Based on your "fix for pipewire" below, is it right that it does work
now?

> [...]
> I've found the cause.
> 
> I found a problem with the pipedwire configuration, fixed it, and
> everything works fine.

Great! Do you mind sharing the "problem with the pipewire
configuration"? Perhaps the fix should go into the official pipewire
packages...

> [...]
> Why do you want users to add --audio-backend=pulseaudio?

Because it does not work on Leap otherwise...

> [...]
> MH>1. /usr/bin/pulseaudio is installed
> MH>2. /usr/bin/pipewire is installed
> MH>3. /usr/bin/pipewire-pulse is NOT installed
> 
> MH>  If all three items are true, we will not get any sound unless we
> MH>  explicitly force kodi to use "--audio-backend=pulseaudio". If one item
> MH>  is not true, we don't force anything.
> 
> As I wrote in a previous email, you are right, in the case of the
> pilseaido system, --audio-backend=pulseaudio must be added.

Yep, that's what my patch added.

> But Tumbleweed, as you know, is not a pulseaudio system, but a
> pipewire system, and --audio-backend=pulseaudio is to make the kodi
> sound via pipewire-pulse. Does it make sense?
> I think it's rather unnecessary.

On Tumbleweed my patch does not change anything. So you're right in that
the change was only relevant for Leap. The more I think about it, I
agree with you that we should disable all PW stuff on Leap, but leave PA
and PW enabled for Tumbleweed.

> [..]
> MN> > It still works, but installing pulseaudio instead of
> MN> > pipewire-pulseaudio is not in line with the basic idea of pipewire
> MN> > development, is it?
> 
> MH>  I'm not a pipewire developer, so I don't know. I just try to figure out,
> MH>  what needs to be done to make kodi work on both Tumbleweed and Leap.
> 
> As I mentioned in a previous email, in Leap, the pulseaudio system is
> the default and the transition to the pipewire system is
> optional.
> But, in Tumbleweed, the pipewire system is the default state. 
> The idea that the same kodi can be used in both Leap and Tumbleweed is
> quite understandable. However, the fact that it asks you to start with
> --audio-backend=pul;seaudio is not

Kodi does *not* ask the user to add that parameter! Instead it finds out
if the parameter must be added to produce sound at all, without any user
interaction - the user still can override if wanted/necessary due to the
user specific environment and setup.

> In other words, kodi is not the only one that provides source for both
> pulseaudio and pipewire, but as far as I know, there are audacious,
> deadbeef, and mpd.
> 
> And, their build conditions for these are the same as for kodi, and
> pulseaudio is compatible with both pipewire and kodi.
> 
> That is, it is up to the builders to decide whether to support
> pulseaudio or pipewire. I found that audacious, deadbeef, and mpd all
> support puseaudio on Leap, and pipewire on Tumbleweed.
> I think kodi should do the same, shouldn't you?

See above, I'll push my change to Kodi to disable pipewire for Leap.

> BTW, I have question.
> 
> The packman kodi can't display videos;
> 
>   1. codec is h264  
> 
>   2. codec is rv40

Do you have examples for these? h264 can be played here without issues.

> My kodi plays fine, but are these specifications?

Which ffmpeg packages are you using?

> Best Regards.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Packman issue on MicroOS Kalpa (openSUSE)

[Manfred Hollstein]

Hi Andrea,

On Wed, 01 May 2024, 22:56:14 +0200, Seth wrote:
> Dear all
> 
> I'm an happy user and I'm really greatful of all your hard work.
> I recently moved from Tumbleweed to MicroOS Kalpa and I'm facing an important 
> issue with Packman: I need to install the broadcom-wl package, however when I 
> try to install it it gives me a weird error message (please see attached) and 
> the installation get aborted. Even tho I force the installation of the 
> package, it simply won't work.
> Really hope you can help and I wish to thank you all once again

I used to maintain the broadcom-wl package years ago when I had that
hardware in some of my systems. Right now I don't have such hardware
anymore, but still care to ensure it builds.

I'm on Leap 15.5 and Tumbleweed only, so I don't know anything about
MicroOS Kalpa, but you could help to actually show the error message
which you obviously wanted to attach, but it most likely got scrubbed by
the mailing list management system.

> Kind Regards
> Andrea

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Moin,

let me ask one question first: did kodi-21 from Packman work for you at
all? If so, when did the problem start?

Please find further stuff below.

On Thu, 02 May 2024, 02:02:35 +0200, Masaru Nomiya wrote:
> Hello,
> 
> I write my mail on two PC's to check my correspondence to the Mailing
> list, one is a desktop PC and the other is a laptop, both with
> Tumbleweed as the platform.
> 
> The Tumbleweed on the laptop is in the state of the one provided by
> openSUSE and I have not modified it in any way.
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : 
>   Date & Time: Wed, 1 May 2024 12:16:16 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MH>  As I wrote several times before, I cannot reproduce what you see! Both
> MH>  variants work for me here and produce sound. May I suggest that you
> MH>  create an issue upstream? Please include all details such as OS platform
> MH>  and the version of pipewire including where you got them from.
> 
> I can't understand what you are talking about.

I asked you to go to

  https://github.com/xbmc/xbmc/issues

and click on "New issue" in which you describe your current problem. As
I don't have that problem, I cannot do it for you. Note, if you don't
already have a Github account, you must create one before.

> Do you understand what your proposal is?

I don't understand your question?

> In the Message; 
> 
>   Subject: [packman] Kodi 21.0 Omega - Update against sound issues on Leap
>   Message-ID : <20240429115933.ga8...@saturn.hollstein.homelinux.org>
>   Date & Time: Mon, 29 Apr 2024 13:59:33 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MH>  We have therefore extended the /usr/bin/kodi script to detect, if the
> MH>  installation is kind of broken:
> 
> MH># Work around a possibly broken installation of pipewire on openSUSE 
> Leap
> MH># see 'https://bugzilla.opensuse.org/show_bug.cgi?id=1222636'
> MH>if [ -x ${prefix}/bin/pulseaudio ] &&
> MH>   [ -x ${prefix}/bin/pipewire ] &&
> MH>   [ ! -x ${prefix}/bin/pipewire-pulse ]; then
> MH>  ENV_ARGS="--audio-backend=pulseaudio"
> MH>fi
> 
> MH>  This means that a default installation of Leap 15.5 or 15.6 will cause
> MH>  kodi to add "--audio-backend=pulseaudio" by itself. Please note, you can
> MH>  still override this by adding your own preference by adding one of the
> MH>  following yourself:
> 
> MH>  --audio-backend= Select which audio backend to use.
> MH>Available audio backends are: alsa, pipewire, 
> pulseaudio, alsa+pulseaudio
> [...]
> 
> Your proposal means;
> 
>  kodi, which by default starts by activating the API to pipewire,
>  should be replaced by activating the API to pulseaudio, since
>  this will not play sound.

Nope, the if [ ... ] means:

  1. /usr/bin/pulseaudio is installed
  2. /usr/bin/pipewire is installed
  3. /usr/bin/pipewire-pulse is NOT installed

If all three items are true, we will not get any sound unless we
explicitly force kodi to use "--audio-backend=pulseaudio". If one item
is not true, we don't force anything.

BTW, if kodi-21 worked for you once, but not now, you could remve the "if
[ ... ] fi" statement above from the /usr/bin/kodi script (lines 193 to
200) and test again, please. This was the only change in
kodi-21.0-1699.3.pm.1.x86_64.  If it still crashes, the reason is
something else caused by your concrete installation.

Another test would be to start with Kodi's default settings. For this
you should move your existing configuration to a safe place, followed by
starting kodi to see if that works or still crashes:

  $ mv ~/.kodi ~/.kodi.save
  $ kodi
  $ rm -rf ~/.kodi; mv ~/.kodi.save ~/.kodi

> Naturally, this switch is only for the API, and sound is played via
> pipewire.
> 
> Furthermore, can't you understand that kodi built with the
> -DENABLE_PIPEWIRE=OFF switch does the same thing as kodi start up with
> the pulseaudio API enabled (ie., --audio-backend=pulseaudio)?

Of course, I do understand that. What makes you believe I don't?
> 
> I ask because this is a good time to ask;
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : <20240430072150.ga3...@saturn.hollstein.homelinux.org>
>   Date & Time: Tue, 30 Apr 2024 09:21:50 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MH>  This is the situation that a Leap installation with all updates
> MH>  installed is in. It has /usr/bin/pul

Re: [packman] Kodi 21.0 Omega - Update against sound issues on Leap

[Manfred Hollstein]

Hi,

On Wed, 01 May 2024, 12:10:47 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : 
>   Date & Time: Wed, 1 May 2024 11:08:59 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...] 
> MN> > You two SHOULD ask Google.
> 
> MH>  I did so several times, and I also looked at issues in github, but
> MH>  haven't found clear indications that it's absolutely not ready yet.
> 
> Hmmm, keywords are bad.
> 
> Cf;
> 
>   https://forum.kodi.tv/showthread.php?tid=377077
> 
>[...]
>I use Alsa, because in Pulseaudio passthrough does not work, at
>least here on my side. Pipewire does not work with Kodi 20 and it
>seems that there are enough troubles with Kodi 21 and Pipewire?!
>So, what else should i use than Alsa?
>[...]
>   
> MH>  FWIW, I have a change sitting in
> 
> MH>https://pmbs.links2linux.org/package/show/home:manfred-h/kodi
> 
> MH>  which introduces a new conditional "kodi_without_pipewire" defaulting to
> MH>  omit pipewire for now. Will create a new SR when the builds are
> MH>  finished.
> 
> FYI.
> 
> 1. Under pipewire + pipewire-pulseaudio, kodi crashes on startup.
>   However, kodi --audio-backend=pulseaudio starts, but no sound.
> 
> 2. Under pipewire + pulseaudio, kodi starts up but no sound.
>   However, kodi --audio-backend=pulseaudio make sounds.
>   kodi is playing sound via pipewire. It is not unreasonable to assume
>   that pipewire is functioning properly.
>   
> Anyway, I think you should file a bug report upstream immediately?

As I wrote several times before, I cannot reproduce what you see! Both
variants work for me here and produce sound. May I suggest that you
create an issue upstream? Please include all details such as OS platform
and the version of pipewire including where you got them from.

> Best Regards & Good Night.

See you tomorrow!

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Moin,

On Wed, 01 May 2024, 10:49:32 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : 
>   Date & Time: Wed, 1 May 2024 10:07:58 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> MH>  Dear Sagi,
> 
> MH>  what do you think? Shall we disable Pipewire in Kodi? As it works for
> MH>  me, I am undecided, but would do it if you think it's not ready yet.
> 
> You two SHOULD ask Google.

I did so several times, and I also looked at issues in github, but
haven't found clear indications that it's absolutely not ready yet.

FWIW, I have a change sitting in

  https://pmbs.links2linux.org/package/show/home:manfred-h/kodi

which introduces a new conditional "kodi_without_pipewire" defaulting to
omit pipewire for now. Will create a new SR when the builds are
finished.

> Best Regards.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Dear Sagi,

what do you think? Shall we disable Pipewire in Kodi? As it works for
me, I am undecided, but would do it if you think it's not ready yet.

TIA, cheers.

l8er
manfred

On Wed, 01 May 2024, 02:47:36 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : 
>   Date & Time: Tue, 30 Apr 2024 14:16:26 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MN>  > I installed Packman's kodi, started it, and it crashed. The log shows
> MN>  > the following error;
> MN>  > 
> MN>  >error : DBus error: org.freedesktop.DBus.Error.InvalidArgs
> MN>  > 
> MN>  > However, if I run kodi with --audio-backend=pulseaudio switch, it
> MN>  > starts and works fine.
> MN>  > 
> MN>  > In other words, it starts fine with pulseaudio, but fails to start and
> MN>  > crashes with pipewire.
> MN>  > 
> MN>  > Something is wrong . (_ _?
> 
> MH>  Is this on Tumbleweed or Leap?
> 
> MN>  > Have you checked the source code?
> 
> MH>  I tested the packages on Leap 15.5 and Tumbleweed. In fact, I just ran
> MH>  this on Tumbleweed 20240428.
> 
> I get it!
> 
> There is a bug in kodi's handling of pipewire.
> 
> I haven't followed the source code yet, but a temporary workaround is
> to build with the -DENABLE_PIPEWIRE=OFF switch.
> 
> I checked with the very latest git head.
> 
> Best Regards.
> 
> ---
> ┏━━┓彡  Masaru Nomiya   mail-to: nomiya @ lake.dti.ne.jp
> ┃＼／彡
> ┗━━┛  "Play the guitar, play it again, my Johnny
>   Maybe you're cold but you're so warm inside"
> 
>   -- Johnny Guitar --


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

On Tue, 30 Apr 2024, 14:17:38 +0200, Manfred Hollstein wrote:
> On Tue, 30 Apr 2024, 14:16:26 +0200, Manfred Hollstein wrote:
> > Hi,
> > 
> > On Tue, 30 Apr 2024, 13:52:19 +0200, Masaru Nomiya wrote:
> > > Hello,
> > > 
> > > I'm going to bed, so I'll be brief.
> > > 
> > > I installed Packman's kodi, started it, and it crashed. The log shows
> > > the following error;
> > > 
> > >error : DBus error: org.freedesktop.DBus.Error.InvalidArgs
> > > 
> > > However, if I run kodi with --audio-backend=pulseaudio switch, it
> > > starts and works fine.
> > > 
> > > In other words, it starts fine with pulseaudio, but fails to start and
> > > crashes with pipewire.
> > > 
> > > Something is wrong . (_ _?
> > 
> > Is this on Tumbleweed or Leap?
> > 
> > > Have you checked the source code?
> > 
> > I tested the packages on Leap 15.5 and Tumbleweed. In fact, I just ran
> > this on Tumbleweed 20240428.
> 
> Forgot to mention, this is with Pipewire on one system and with
> Pulseaudio on another.

Also, I test this on XFCE; maybe the DBus stuff depends on the desktop
environment, too.

> > > Best Regards & Good Night.
> > 
> > Have a good one!
> > 
> > Cheers.
> > 
> > l8er
> > manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

On Tue, 30 Apr 2024, 14:16:26 +0200, Manfred Hollstein wrote:
> Hi,
> 
> On Tue, 30 Apr 2024, 13:52:19 +0200, Masaru Nomiya wrote:
> > Hello,
> > 
> > I'm going to bed, so I'll be brief.
> > 
> > I installed Packman's kodi, started it, and it crashed. The log shows
> > the following error;
> > 
> >error : DBus error: org.freedesktop.DBus.Error.InvalidArgs
> > 
> > However, if I run kodi with --audio-backend=pulseaudio switch, it
> > starts and works fine.
> > 
> > In other words, it starts fine with pulseaudio, but fails to start and
> > crashes with pipewire.
> > 
> > Something is wrong . (_ _?
> 
> Is this on Tumbleweed or Leap?
> 
> > Have you checked the source code?
> 
> I tested the packages on Leap 15.5 and Tumbleweed. In fact, I just ran
> this on Tumbleweed 20240428.

Forgot to mention, this is with Pipewire on one system and with
Pulseaudio on another.

> > Best Regards & Good Night.
> 
> Have a good one!
> 
> Cheers.
> 
> l8er
> manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi,

On Tue, 30 Apr 2024, 13:52:19 +0200, Masaru Nomiya wrote:
> Hello,
> 
> I'm going to bed, so I'll be brief.
> 
> I installed Packman's kodi, started it, and it crashed. The log shows
> the following error;
> 
>error : DBus error: org.freedesktop.DBus.Error.InvalidArgs
> 
> However, if I run kodi with --audio-backend=pulseaudio switch, it
> starts and works fine.
> 
> In other words, it starts fine with pulseaudio, but fails to start and
> crashes with pipewire.
> 
> Something is wrong . (_ _?

Is this on Tumbleweed or Leap?

> Have you checked the source code?

I tested the packages on Leap 15.5 and Tumbleweed. In fact, I just ran
this on Tumbleweed 20240428.

> Best Regards & Good Night.

Have a good one!

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Moin,

On Tue, 30 Apr 2024, 11:15:14 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21.0 Omega - Update against sound issues on 
> Leap
>   Message-ID : <20240430072150.ga3...@saturn.hollstein.homelinux.org>
>   Date & Time: Tue, 30 Apr 2024 09:21:50 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> MH>  Good morning,
> 
> Guten Morgen, aber in Japan, guten Abend. 
> 
> Anyway,
> 
> [...]
> MH>>>  This will take priority over an implicitly added option for pulseaudio.
>  
> MN> > I have two questions about what is written here.
>  
> MN> > 1. If pipewire-pulseaudio is not installed, then there should be a lot
> MN> >   of sound-related problems?
> 
> MH>  Without the latest fix, yes, there was no sound at all.
> 
> MN> >   As I mentioned before, there are apps that use pulseaudio rather
> MN> >   than pipewire.
> 
> MH>  Which is exactly the situation as tested by the added if ... fi part.
> MH>  This is the situation that a Leap installation with all updates
> MH>  installed is in. It has /usr/bin/pulseaudio and /usr/bin/pipewire, but
> MH>  no /usr/bin/pipewire-pulseaudio. In that configuration Kodi believes it
> MH>  should use Pipewire, but that doesn't work. That's why we instruct Kodi
> MH>  to use "--audio-backend=pulseaudio".
> 
> Pulseaudio and pipewrire-pulse are exclusive, so if you install
> pulseaudio, you cannot install pipewire-pulse, but you should still be
> able to play sound, although kodi will have no sound.

Correct.

> MN> > 2. Under the current situation of the sound related apps, wouldn't it
> MN> >   be correct to encourage the installation of pipewire-pulseaudio?
> 
> MH>  Yes, that's what I tried to force the SUSE guys to do, but as can be
> MH>  seen in the bugzilla, they neglected to do that. Hence we came up with
> MH>  the work-around.
> 
> I understand your anger, but wouldn't it be faster to rebuild with
> -DENABLE_PULSEAUDIO=AUTO option?

I understand the AUTO that PA gets enabled if the files for it are
installed at compile time; if not, you don't get an error message.

> Of course, you need libpulse-devel.

Sure, and that would mean the same as -DENABLE_PULSEAUDIO=YES, you would
however not see an error message at build time when there is no
libpulse-devel (see above).

This whole mess is not an issue at compile/build time, but at run time.
Kodi should not just blindly assume, PW is usable when it finds a
/usr/bin/pipewire program.

> Best Regards.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Good morning,

On Tue, 30 Apr 2024, 02:15:10 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: [packman] Kodi 21.0 Omega - Update against sound issues on Leap
>   Message-ID : <20240429115933.ga8...@saturn.hollstein.homelinux.org>
>   Date & Time: Mon, 29 Apr 2024 13:59:33 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> MH>  Hi there,
> 
> MH>  Kodi apparently has issues on Leap when both, PulseAudio and Pipewire,
> MH>  are installed. The reason is that Leap does not install
> MH>  pipewire-pulseaudio, leaving Kodi assuming it should use Pipewire as its
> MH>  audio backend - unfortunately, this does not produce any sound at all :-(
> 
> MH>  We have therefore extended the /usr/bin/kodi script to detect, if the
> MH>  installation is kind of broken:
> 
> MH># Work around a possibly broken installation of pipewire on openSUSE 
> Leap
> MH># see 'https://bugzilla.opensuse.org/show_bug.cgi?id=1222636'
> MH>if [ -x ${prefix}/bin/pulseaudio ] &&
> MH>   [ -x ${prefix}/bin/pipewire ] &&
> MH>   [ ! -x ${prefix}/bin/pipewire-pulse ]; then
> MH>  ENV_ARGS="--audio-backend=pulseaudio"
> MH>fi
> 
> MH>  This means that a default installation of Leap 15.5 or 15.6 will cause
> MH>  kodi to add "--audio-backend=pulseaudio" by itself. Please note, you can
> MH>  still override this by adding your own preference by adding one of the
> MH>  following yourself:
> 
> MH>  --audio-backend= Select which audio backend to use.
> MH>Available audio backends are: alsa, pipewire, 
> pulseaudio, alsa+pulseaudio
> 
> MH>  This will take priority over an implicitly added option for pulseaudio.
> 
> I have two questions about what is written here.
> 
> 1. If pipewire-pulseaudio is not installed, then there should be a lot
>   of sound-related problems?

Without the latest fix, yes, there was no sound at all.

>   As I mentioned before, there are apps that use pulseaudio rather
>   than pipewire.

Which is exactly the situation as tested by the added if ... fi part.
This is the situation that a Leap installation with all updates
installed is in. It has /usr/bin/pulseaudio and /usr/bin/pipewire, but
no /usr/bin/pipewire-pulseaudio. In that configuration Kodi believes it
should use Pipewire, but that doesn't work. That's why we instruct Kodi
to use "--audio-backend=pulseaudio".

> 2. Under the current situation of the sound related apps, wouldn't it
>   be correct to encourage the installation of pipewire-pulseaudio?

Yes, that's what I tried to force the SUSE guys to do, but as can be
seen in the bugzilla, they neglected to do that. Hence we came up with
the work-around.

> Best Regards.

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Kodi 21.0 Omega - Update against sound issues on Leap

[Manfred Hollstein]

Hi there,

Kodi apparently has issues on Leap when both, PulseAudio and Pipewire,
are installed. The reason is that Leap does not install
pipewire-pulseaudio, leaving Kodi assuming it should use Pipewire as its
audio backend - unfortunately, this does not produce any sound at all :-(

We have therefore extended the /usr/bin/kodi script to detect, if the
installation is kind of broken:

  # Work around a possibly broken installation of pipewire on openSUSE Leap
  # see 'https://bugzilla.opensuse.org/show_bug.cgi?id=1222636'
  if [ -x ${prefix}/bin/pulseaudio ] &&
 [ -x ${prefix}/bin/pipewire ] &&
 [ ! -x ${prefix}/bin/pipewire-pulse ]; then
ENV_ARGS="--audio-backend=pulseaudio"
  fi

This means that a default installation of Leap 15.5 or 15.6 will cause
kodi to add "--audio-backend=pulseaudio" by itself. Please note, you can
still override this by adding your own preference by adding one of the
following yourself:

--audio-backend= Select which audio backend to use.
  Available audio backends are: alsa, pipewire, 
pulseaudio, alsa+pulseaudio

This will take priority over an implicitly added option for pulseaudio.

Thanks to Sagi for reviewing this change!

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi stop launching

[Manfred Hollstein]

Hi Masaru,

On Mon, 15 Apr 2024, 12:57:21 +0200, Masaru Nomiya wrote:
> Hello,
> 
> Are you a maintainer, Manfred?

Yes, Sagi and I do the work on Kodi and its addons.

> Anyway,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi stop launching
>   Message-ID : 
>   Date & Time: Mon, 15 Apr 2024 12:24:30 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> TK>>>  Do you know what might be wrong with the upgrade?
>  
> MN>  > What's the result of 'rpm -q libass9"?
> 
> MH>  on Leap 15.5 libass9 must be installed from the same repository as kodi.
> MH>  Please take a look at the following thread
> 
> The error message Thomas got was related to libass9. I checked and
> found that libass9 was updated on April 6, but I thought Thomas might
> not have updated it, so I asked him about it.

It won't get updated unless you explicitly force zypper to do so
(--allow-vendor-change).

> MH>  It may happen that your audio won't work afterwards; this is caused by a
> MH>  missing package "pipewire-pulseaudio" which doesn't get installed on
> MH>  Leap by default. I have documented all the potential caveats in the
> MH>  above thread.
> 
> I'm sorry, but I can't understand what you are trying to say.
> I thought libass had nothing to do with audio.

Correct, but when the libass problem is solved, sound won't work :(
Remember the thread we had with Eric last week?

> Besides, I am a Tumbleweed user.

I test the stuff on Leap and Tumbleweed.

> Best Regards & Good Night.

Have a good one!

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi stop launching

[Manfred Hollstein]

Hi there,

On Mon, 15 Apr 2024, 11:56:06 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: [packman] Kodi stop launching
>   Message-ID : <18ed37e14f4.b75063f7201453.6898389696216688...@zoho.com>
>   Date & Time: Fri, 12 Apr 2024 20:08:20 +0200
> 
> [TK] == Tomáš Klouček  has written:
> 
> TK>  Hello
> 
> TK>  After "today's" update my Kodi stopped launching. Prior the latest 
> update the Kodi works ok. The startup ends with the error: 
> /usr/lib64/kodi/kodi.bin: symbol lookup error: /usr/lib64/kodi/kodi.bin: 
> undefined symbol: ass_track_set_feature
> 
> TK>  Package version: kodi-21.0-150500.1.pm.1.x86_64
> 
> TK>  Architecture: x86_64
> 
> TK>  Repository: http://packman.links2linux.de
> TK>   OS: openSUSE Leap 15.5
> 
> TK>  Do you know what might be wrong with the upgrade?
> 
> What's the result of 'rpm -q libass9"?

on Leap 15.5 libass9 must be installed from the same repository as kodi.
Please take a look at the following thread

  

especially at

  

It may happen that your audio won't work afterwards; this is caused by a
missing package "pipewire-pulseaudio" which doesn't get installed on
Leap by default. I have documented all the potential caveats in the
above thread.

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

Hi,

On Thu, 11 Apr 2024, 12:37:14 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21 - crash
>   Message-ID : 
>   Date & Time: Thu, 11 Apr 2024 09:58:45 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MN> > The use of pavucontrol (included in pulseaudio-utils) will solve your
> MN> > problem.
> 
> MH>  No, unfortunately it's more difficult. It's a Line6 (now Yamaha) Helix
> MH>  Rack, which gets its input from the PC via a Jack configuration. Someone
> MH>  claimed that he got it to work with Pipewire, too, but it did not work
> MH>  for me last night, so I'm back with my working configuration.
> 
> I have been playing guitar for about 60 years, but I don't know
> anything about electric guitars because I played classical guitar.
> 
> Do you compose music?

No, I only use the playback from the PC to jam along with The Beatles,
Eagles, Deep Purple, Supertramp, ... you got it. Playing with/against
Ritchie Blackmore can be challenging... :-)

> If so, this pipewire is the way to go;
> 
>
> https://build.opensuse.org/package/show/home%3AX0F%3Abranches%3Amultimedia/pipewire

I'll certainly take a look, thanks for the link!

> I think it's well thought out, but I only listen, so latency is not an
> issue.
> 
> Best Regards & Good Night.

Have a good one!

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

Moin,

On Thu, 11 Apr 2024, 09:50:49 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21 - crash
>   Message-ID : 
>   Date & Time: Thu, 11 Apr 2024 09:24:56 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MH>  After I installed pipewire-pulseaudio myself, everything worked. With
> MH>  that package missing, it didn't work.
> 
> I know, right.
> 
> Many applications still only support pulseaudio, but the sound is
> played without problems via pipewire-pulse.

Yes, I agree.

> MH>  However, I cannot get my sound set up so that I can feed the PC
> MH>  sound into the external guitar amplifier which is why I disabled
> MH>  all the pipewire stuff again. Tried it once again last night, but
> MH>  couldn't get it to work, so PA remains my first choice.
> 
> The use of pavucontrol (included in pulseaudio-utils) will solve your
> problem.

No, unfortunately it's more difficult. It's a Line6 (now Yamaha) Helix
Rack, which gets its input from the PC via a Jack configuration. Someone
claimed that he got it to work with Pipewire, too, but it did not work
for me last night, so I'm back with my working configuration.

> Kind Regards.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

Hi,

On Thu, 11 Apr 2024, 09:11:08 +0200, Masaru Nomiya wrote:
> Hello,
> 
> I had to go out, so I wrote the e-mail in a hurry, but it is not
> right, so I will ask again.
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi 21 - crash
>   Message-ID : <20240410113214.gb3...@saturn.hollstein.homelinux.org>
>   Date & Time: Wed, 10 Apr 2024 13:32:14 +0200
> 
> [MH] == Manfred Hollstein  has written:
> 
> [...]
> MH>  Still Kodi wants to use pipewire by default if it finds it installed.
> MH>  kodi --help tells us the following:
> [...]
> 
> Please show the results of;
> 
> 1. $ pactl info
> 
> 2. $ rpm -q pipewire-pulseaudio
> 
> 3. $ systemctl --user status pipewire-pulse

After I installed pipewire-pulseaudio myself, everything worked. With
that package missing, it didn't work. However, I cannot get my sound
set up so that I can feed the PC sound into the external guitar
amplifier which is why I disabled all the pipewire stuff again. Tried it
once again last night, but couldn't get it to work, so PA remains my
first choice.

> Kind Regards.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

On Wed, 10 Apr 2024, 16:09:17 +0200, Manfred Hollstein wrote:
> On Wed, 10 Apr 2024, 15:46:21 +0200, Eric Schirra wrote:
> > [...]
> OK, then you're on your own. I'm going to open a bug report for Leap's
> pipewire updates...
> 
> Cheers.
> 
> l8er
> manfred
> 
> PS: Now, what is the issue with "Das spec darin ist auch nicht
> fehlerfrei!" Instead of only complaining the way you always do, please
> consider to share your findings ;)

  <https://bugzilla.opensuse.org/show_bug.cgi?id=1222636>

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi v21.0 Omega has been released

[Manfred Hollstein]

On Wed, 10 Apr 2024, 16:23:39 +0200, Manfred Hollstein wrote:
> Hi there again,
> 
> On Mon, 08 Apr 2024, 17:21:39 +0200, Manfred Hollstein wrote:
> > Hi there,
> > 
> > On Sun, 07 Apr 2024, 20:00:02 +0200, Manfred Hollstein wrote:
> > > Hi there,
> > > 
> > > JFYI
> > > 
> > >   <https://kodi.tv/article/kodi-21-0-omega-release/>
> > > 
> > > For me the most obvious issue was, that the former default skin
> > > "Confluence" is no longer supported/compatible - switching to the
> > > "Estuary" skin is easy, though.
> > > 
> > > Packages will be available in the usual Multimedia repository from
> > > Packman, depends on the speed of your mirrors.
> > 
> > The packages have apparently arrived, but it appears that there might be
> > issues with them on Leap 15.5 and 15.6 :( In case your updated Kodi
> > version doesn't work, the reason probably is an outdated version of
> > package libass9 provided by Leap. When you're hit by this issue, you
> > should:
> > 
> >   sudo zypper up allow-vendor-change --from "Your-PMBS-Multimedia.repo" 
> > libass9
> > 
> > Thanks to Eric Schirra for his feedback!
> 
> after some debugging sessions it became apparent that the pipewire
> packages installed on Leap systems are not providing a functioning sound
> server. Comparing this with Tumbleweed, Leap updates fail to install the
> package "pipewire-pulseaudio" leaving the installed pipewire packages
> unusable for packages that have native support for pipewire like Kodi.
> 
> There are several options:
> 
>   1. Add "--audio-backend=pulseaudio" as an argument for starting kodi
>   2. Get rid of installed pipewire packages by removing them and locking
>  them afterwards to ensure they won't get re-installed.
>   3. Install the missing "pipewire-pulseaudio" package which will pull
>  in some additional packages and then replace your existing
>  pulseaudio packages.
> 
> I have now tested all three options and got them to work, however, on
> Leap, I chose to use variant 2 when pipewire showed up. Depending on
> your use-case, option 3 may work very well, but for me it wasn't an
> option due to (a) raw passthrough for DTS etc. over HDMI and (b) using a
> Jack configuration which re-directs my PA audio to a guitar amplifier;
> whis works for me which is why I decided to (b)lock pipewire, at least
> on Leap!
> 
> HTH, cheers.
> 
> l8er
> manfred
> 
> PS: I'll open a bug report for the pipewire packages on Leap, as they
> should be installed in a similar way as on Tumbleweed. As long as
> this is not the case, Pipewire doesn't work for Pipewire
> applications and therefore shouldn't be installed by default!

  <https://bugzilla.opensuse.org/show_bug.cgi?id=1222636>

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi v21.0 Omega has been released

[Manfred Hollstein]

Hi there again,

On Mon, 08 Apr 2024, 17:21:39 +0200, Manfred Hollstein wrote:
> Hi there,
> 
> On Sun, 07 Apr 2024, 20:00:02 +0200, Manfred Hollstein wrote:
> > Hi there,
> > 
> > JFYI
> > 
> >   <https://kodi.tv/article/kodi-21-0-omega-release/>
> > 
> > For me the most obvious issue was, that the former default skin
> > "Confluence" is no longer supported/compatible - switching to the
> > "Estuary" skin is easy, though.
> > 
> > Packages will be available in the usual Multimedia repository from
> > Packman, depends on the speed of your mirrors.
> 
> The packages have apparently arrived, but it appears that there might be
> issues with them on Leap 15.5 and 15.6 :( In case your updated Kodi
> version doesn't work, the reason probably is an outdated version of
> package libass9 provided by Leap. When you're hit by this issue, you
> should:
> 
>   sudo zypper up allow-vendor-change --from "Your-PMBS-Multimedia.repo" 
> libass9
> 
> Thanks to Eric Schirra for his feedback!

after some debugging sessions it became apparent that the pipewire
packages installed on Leap systems are not providing a functioning sound
server. Comparing this with Tumbleweed, Leap updates fail to install the
package "pipewire-pulseaudio" leaving the installed pipewire packages
unusable for packages that have native support for pipewire like Kodi.

There are several options:

  1. Add "--audio-backend=pulseaudio" as an argument for starting kodi
  2. Get rid of installed pipewire packages by removing them and locking
 them afterwards to ensure they won't get re-installed.
  3. Install the missing "pipewire-pulseaudio" package which will pull
 in some additional packages and then replace your existing
 pulseaudio packages.

I have now tested all three options and got them to work, however, on
Leap, I chose to use variant 2 when pipewire showed up. Depending on
your use-case, option 3 may work very well, but for me it wasn't an
option due to (a) raw passthrough for DTS etc. over HDMI and (b) using a
Jack configuration which re-directs my PA audio to a guitar amplifier;
whis works for me which is why I decided to (b)lock pipewire, at least
on Leap!

HTH, cheers.

l8er
manfred

PS: I'll open a bug report for the pipewire packages on Leap, as they
should be installed in a similar way as on Tumbleweed. As long as
this is not the case, Pipewire doesn't work for Pipewire
applications and therefore shouldn't be installed by default!


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

On Wed, 10 Apr 2024, 15:46:21 +0200, Eric Schirra wrote:
> 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.

OK, then you're on your own. I'm going to open a bug report for Leap's
pipewire updates...

Cheers.

l8er
manfred

PS: Now, what is the issue with "Das spec darin ist auch nicht
fehlerfrei!" Instead of only complaining the way you always do, please
consider to share your findings ;)


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

On Wed, 10 Apr 2024, 14:35:38 +0200, Manfred Hollstein wrote:
> 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 ;)
> 
> > 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.
> 
> 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.

FWIW, I just verified that this works with or without specifying an
explicit audio-backend. Without passing anything, Kodi uses Pipewire and
sound works; calling it via "kodi --audio-backend=pulseaudio", it uses
Pipewire's "pulseaudio" and sound works, too. Please give it a try!

> > Gruß
> >  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[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 ;)

> 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.

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.

> Gruß
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[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.

> Let's see what comes of it.

I doubt they'll accept that issue due to Leap not setting up pipewire
properly...

> Thanks anyway.
> 
> Regards
> Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

Hi there,

On Wed, 10 Apr 2024, 12:54:16 +0200, Masaru Nomiya wrote:
> 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.

Thanks for jumping in!

> Es wäre besser,
> 
>$ kodi > kodi.log 2>&1
> 
> in einem Terminal auszuführen und das kodi.log hochzuladen.

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...

> Grüße.
> 
> ---
> ┏━━┓彡  Masaru Nomiya   mail-to: nomiya @ lake.dti.ne.jp

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

On Wed, 10 Apr 2024, 07:21:39 +0200, Eric Schirra wrote:
> 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

It definitively does on all my systems.

> Andere habe ich nicht getestet.
> Getestet habe ich mit den Addons ARD-Mediathek und Prime.

I use plugin.video.ardundzdf on a daily basis, plus
kodi.binary-addons-pvr.vuplus on both Leap 15.5 and Tumbleweed; both
work as expected.

> 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.

> 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 ;)

> 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!

> Gruß
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

On Mon, 08 Apr 2024, 20:24:54 +0200, Eric Schirra wrote:
> 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.

I thought you were saying it doesn't work?

> >> 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.

Kodi 20 is no longer supported - not by us, nor by upstream. It's really
a rolling application, although it takes a long time to actually roll...

> . 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.

I'm sure this will help! Again, it surely depends on your concrete
environment, but without any details...

> [...]
> 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?

You can get that directly from PMBS: 

  https://pmbs.links2linux.org/package/revisions/Multimedia/kodi

> Regards
> Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

Hi Eric,

On Mon, 08 Apr 2024, 18:17:26 +0200, Eric Schirra wrote:
> Am Montag, 8. April 2024, 17:15:48 CEST schrieb Manfred Hollstein:
> > [...]
> > 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.

What type of sound device are you using? 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?

> Addons no longer work. No ARD or ZDF mediathek.

Works for me!

> No Prime addon either.

Sorry, that's not supported at all.

> Would say that 21 is not yet "mature".

Perhaps you should have joined the "Kodi: Want to test the upcoming
release Omega 21?" But now that the child is in the well, please
describing your actual setup (OS, hardware, kodi addons) as detailed as
possible. 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.

> 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.

> Regards
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi v21.0 Omega has been released

[Manfred Hollstein]

Hi there,

On Sun, 07 Apr 2024, 20:00:02 +0200, Manfred Hollstein wrote:
> Hi there,
> 
> JFYI
> 
>   <https://kodi.tv/article/kodi-21-0-omega-release/>
> 
> For me the most obvious issue was, that the former default skin
> "Confluence" is no longer supported/compatible - switching to the
> "Estuary" skin is easy, though.
> 
> Packages will be available in the usual Multimedia repository from
> Packman, depends on the speed of your mirrors.

The packages have apparently arrived, but it appears that there might be
issues with them on Leap 15.5 and 15.6 :( In case your updated Kodi
version doesn't work, the reason probably is an outdated version of
package libass9 provided by Leap. When you're hit by this issue, you
should:

  sudo zypper up allow-vendor-change --from "Your-PMBS-Multimedia.repo" 
libass9

Thanks to Eric Schirra for his feedback!

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[Manfred Hollstein]

Hi Eric,

please follow up on the mailing list, thx!

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

> Or is it something else?
> 
> 
> Regards
> Eric

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi 21 - crash

[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

  libass9
  libdisplay-info1

from the Multimedia repository, too!

> Gruß
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Kodi v21.0 Omega has been released

[Manfred Hollstein]

Hi there,

JFYI

  

For me the most obvious issue was, that the former default skin
"Confluence" is no longer supported/compatible - switching to the
"Estuary" skin is easy, though.

Packages will be available in the usual Multimedia repository from
Packman, depends on the speed of your mirrors.

Enjoy the new release!

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi: Want to test the upcoming release Omega 21?

[Manfred Hollstein]

Hi there again,

On Sat, 06 Apr 2024, 21:32:22 +0200, Manfred Hollstein wrote:
> [...]
> Kodi v21.0 Omega has come to live today. I have created two requests to
> submit the packages to the usual Multimedia project. Sagi will be
> reviewing them and hopefully release them to the project.
> 
> In case you accepted my proposal to test the RC2 packages from my home
> project, you should then disable that project again and dup the packages
> from Multimedia in order to receive normal updates then. This depends on
> the approval of the two SRs, of course. Once that will have happened,
> I'll inform you again with instructions how to get back onto the normal
> track.

Here it goes: packages are currently building, it may be that i586 has
issues, which will be looked at later (cause they built in my private
repo).

If you did not subscribe to

  home:manfred-h:kodi-next

then please stop reading immediately!

If you did, you should have a look at

  https://pmbs.links2linux.org/package/show/Multimedia/kodi
  https://pmbs.links2linux.org/package/show/Multimedia/kodi.binary-addons

When your preferred target has been built, you should probably wait 6
to 12 hours depending how fast your Packman mirror synchronizes with
PMBS. Then:

  sudo zypper mr -d kodi-next.obs
  sudo zypper rr kodi-next.obs
  sudo zypper ref
  sudo zypper in --oldpackage -r "packman-multimedia.obs" kodi  \
$(rpm -qa --qf '%{name}\n' kodi.*)

In the above line replace "packman-multimedia.obs" with the name you use
for Packman's Multimedia repo (can be found out with "zypper lr -E").

In case all this does not work for you, just shout ;)

Have a great weekend!

Cheers.

l8er
manfred

> On Wed, 27 Mar 2024, 16:28:49 +0100, Manfred Hollstein wrote:
> > Hi there,
> > 
> > while I had hoped that Kodi 21 Omega will be released early this year,
> > it did not happen. We had several minor releases for Kodi 20 Nexus (up
> > to 20.5), but they only fixed minor issues.
> > 
> > We are currently in the situation that
> > 
> >   (a) Kodi Nexus 20.5 no longer builds on Tumbleweed due to some
> >   packages being too new for the old code base; we (Sagi and myself)
> >   don't plan to fix this anymore. The built packages should still be
> >   installable though.
> >   (b) Kodi Omega 21 has an RC2, which I thought I'd point your attention
> >   at. The packages are available in home:manfred-h:kodi-next. I test
> >   them sine the early beta versions without any issues.
> > 
> > If you're brave enough, I'd encourage you to test them on your system(s)
> > and would highly appreciate your feedback!
> > 
> > This is what you would have to do on your Tumbleweed system(s):
> > 
> >   sudo zypper ar 
> > http://pmbs-api.links2linux.de:8080/home:/manfred-h:/kodi-next/openSUSE_Tumbleweed/
> >  kodi-next.obs
> >   sudo zypper ref
> >   sudo zypper dup --allow-vendor-change --from kodi-next.obs
> > 
> > This will install kodi-21.0rc2-1699.2.pm.2.x86_64 along with updated
> > versions of thouse kodi.binary-addons you are currently using.
> > 
> > The same procedure would be possible for Leap 15.5 and 15.6, you'd just
> > need to exchange "openSUSE_Tumbleweed" with "15.5" or "15.6" depending
> > on your OS release.
> > 
> > TIA, cheers.
> > 
> > l8er
> > manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi: Want to test the upcoming release Omega 21?

[Manfred Hollstein]

Hi here,

Kodi v21.0 Omega has come to live today. I have created two requests to
submit the packages to the usual Multimedia project. Sagi will be
reviewing them and hopefully release them to the project.

In case you accepted my proposal to test the RC2 packages from my home
project, you should then disable that project again and dup the packages
from Multimedia in order to receive normal updates then. This depends on
the approval of the two SRs, of course. Once that will have happened,
I'll inform you again with instructions how to get back onto the normal
track.

Have a great weekend!

Cheers.

l8er
manfred

On Wed, 27 Mar 2024, 16:28:49 +0100, Manfred Hollstein wrote:
> Hi there,
> 
> while I had hoped that Kodi 21 Omega will be released early this year,
> it did not happen. We had several minor releases for Kodi 20 Nexus (up
> to 20.5), but they only fixed minor issues.
> 
> We are currently in the situation that
> 
>   (a) Kodi Nexus 20.5 no longer builds on Tumbleweed due to some
>   packages being too new for the old code base; we (Sagi and myself)
>   don't plan to fix this anymore. The built packages should still be
>   installable though.
>   (b) Kodi Omega 21 has an RC2, which I thought I'd point your attention
>   at. The packages are available in home:manfred-h:kodi-next. I test
>   them sine the early beta versions without any issues.
> 
> If you're brave enough, I'd encourage you to test them on your system(s)
> and would highly appreciate your feedback!
> 
> This is what you would have to do on your Tumbleweed system(s):
> 
>   sudo zypper ar 
> http://pmbs-api.links2linux.de:8080/home:/manfred-h:/kodi-next/openSUSE_Tumbleweed/
>  kodi-next.obs
>   sudo zypper ref
>   sudo zypper dup --allow-vendor-change --from kodi-next.obs
> 
> This will install kodi-21.0rc2-1699.2.pm.2.x86_64 along with updated
> versions of thouse kodi.binary-addons you are currently using.
> 
> The same procedure would be possible for Leap 15.5 and 15.6, you'd just
> need to exchange "openSUSE_Tumbleweed" with "15.5" or "15.6" depending
> on your OS release.
> 
> TIA, cheers.
> 
> l8er
> manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi: Want to test the upcoming release Omega 21?

[Manfred Hollstein]

On Wed, 27 Mar 2024, 16:28:49 +0100, Manfred Hollstein wrote:
> Hi there,
> 
> while I had hoped that Kodi 21 Omega will be released early this year,
> it did not happen. We had several minor releases for Kodi 20 Nexus (up
> to 20.5), but they only fixed minor issues.
> 
> We are currently in the situation that
> 
>   (a) Kodi Nexus 20.5 no longer builds on Tumbleweed due to some
>   packages being too new for the old code base; we (Sagi and myself)
>   don't plan to fix this anymore. The built packages should still be
>   installable though.
>   (b) Kodi Omega 21 has an RC2, which I thought I'd point your attention
>   at. The packages are available in home:manfred-h:kodi-next. I test
>   them sine the early beta versions without any issues.
> 
> If you're brave enough, I'd encourage you to test them on your system(s)
> and would highly appreciate your feedback!
> 
> This is what you would have to do on your Tumbleweed system(s):
> 
>   sudo zypper ar
>   
> http://pmbs-api.links2linux.de:8080/home:/manfred-h:/kodi-next/openSUSE_Tumbleweed/
>  kodi-next.obs
>   sudo zypper ref
>   sudo zypper dup --allow-vendor-change --from kodi-next.obs
> 
> This will install kodi-21.0rc2-1699.2.pm.2.x86_64 along with updated
> versions of thouse kodi.binary-addons you are currently using.
> 
> The same procedure would be possible for Leap 15.5 and 15.6, you'd just
> need to exchange "openSUSE_Tumbleweed" with "15.5" or "15.6" depending
> on your OS release.

Forgot to mention, issues can also (preferably) be reported at

  <https://github.com/xbmc/xbmc/issues>

I have one open issue there:

  <https://github.com/xbmc/xbmc/issues/24830>

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Kodi: Want to test the upcoming release Omega 21?

[Manfred Hollstein]

Hi there,

while I had hoped that Kodi 21 Omega will be released early this year,
it did not happen. We had several minor releases for Kodi 20 Nexus (up
to 20.5), but they only fixed minor issues.

We are currently in the situation that

  (a) Kodi Nexus 20.5 no longer builds on Tumbleweed due to some
  packages being too new for the old code base; we (Sagi and myself)
  don't plan to fix this anymore. The built packages should still be
  installable though.
  (b) Kodi Omega 21 has an RC2, which I thought I'd point your attention
  at. The packages are available in home:manfred-h:kodi-next. I test
  them sine the early beta versions without any issues.

If you're brave enough, I'd encourage you to test them on your system(s)
and would highly appreciate your feedback!

This is what you would have to do on your Tumbleweed system(s):

  sudo zypper ar
  
http://pmbs-api.links2linux.de:8080/home:/manfred-h:/kodi-next/openSUSE_Tumbleweed/
 kodi-next.obs
  sudo zypper ref
  sudo zypper dup --allow-vendor-change --from kodi-next.obs

This will install kodi-21.0rc2-1699.2.pm.2.x86_64 along with updated
versions of thouse kodi.binary-addons you are currently using.

The same procedure would be possible for Leap 15.5 and 15.6, you'd just
need to exchange "openSUSE_Tumbleweed" with "15.5" or "15.6" depending
on your OS release.

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] All repositories for Leap 15.5 and 15.6 are broken

[Manfred Hollstein]

Hi Robert,

On Thu, 25 Jan 2024, 15:36:50 +0100, Robert Herb wrote:
> Hi Manfred,
> 
> I had the same issue on our OBS at the company today.
> I just a triggered a rebuild of one package and that solved it. 

just tried that, but it did not help - status remains "The repository
setup is broken, build or publish not possible". Strange enough that

  $ osc buildinfo home:manfred-h MakeMKV 15.5 x86_64

doesn't see/show any problem.

> Best regards
> Robert

Cheers.

l8er
manfred

> Am 25. Januar 2024 15:16:54 schrieb Manfred Hollstein :
> 
> 
> Hi there,
> 
> looking at e.g. Essentials in PMBS
> 
>   https://pmbs.links2linux.org/project/show/Essentials
> 
> shows the repository setup as broken for openSUSE_Leap_15.5 and
> openSUSE_Leap_15.6. Interestingly this also happens for SLE_15 and
> x86_64, but not for aarch64.
> 
> AFAICS, nothing has changed in the repository setup, because the same
> problems are also shown in completely unrelated projects like Extra,
> Multimedia, or the home projects.
> 
> Does anybody have an idea what could be the reason for this? Could it be
> that some server side processes on PMBS have failed and should be
> restarted?


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] All repositories for Leap 15.5 and 15.6 are broken

[Manfred Hollstein]

Hi there,

looking at e.g. Essentials in PMBS

  https://pmbs.links2linux.org/project/show/Essentials

shows the repository setup as broken for openSUSE_Leap_15.5 and
openSUSE_Leap_15.6. Interestingly this also happens for SLE_15 and
x86_64, but not for aarch64.

AFAICS, nothing has changed in the repository setup, because the same
problems are also shown in completely unrelated projects like Extra,
Multimedia, or the home projects.

Does anybody have an idea what could be the reason for this? Could it be
that some server side processes on PMBS have failed and should be
restarted?

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] ffmpeg-6 upgrade on TW is uninstallable

[Manfred Hollstein]

On Wed, 17 Jan 2024, 23:37:15 +0100, Andrei Dziahel wrote:
> Hi list,
> 
> The ffmpeg-6 upgrade to 6.1 is uninstallable on my TW installation.
> Here's `zypper dup` output:
> https://paste.opensuse.org/pastes/e75e32c78fb2
> 
> Is it just me or someone else got affected? Is it something undesirable?

You're not alone... This happens from time to time, when packages linked
from openSUSE.org:openSUSE:Factory are not yet released in an official
Tumbleweed snapshot. Packages get built on PMBS in their latest version,
but the then current TW snapshot does *not* necessarily have them.
One solution would be to link our packages against the sources of the
latest TW snapshot instead of openSUSE.org:openSUSE:Factory, but I
haven't found a solution for that; I asked on the buildservice mailing
list, but haven't received an answer yet.

If this happens, one needs to wait for the next TW snapshot :(
20240116 has just been released, so it should be installable again.

> TIA
> -- 
> Regards,
> Andrei Dziahel

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] ffmpeg-6 6.1.1-1699.3.pm.2 (openSUSE Tumbleweed/x86_64)

[Manfred Hollstein]

On Wed, 17 Jan 2024, 19:25:06 +0100, Rick Kunath wrote:
> I am not sure this is the correct address to report a package issue or not?
> 
> There is an update error on Suse Tumbleweed:
> 
> Problem: nothing provides 'libjxl.so.0.9' needed by the to be installed
> libavcodec60-32bit-6.1.1-1699.3.pm.2.x86_64
> 
>  because the SUSE provided libjxl is only at version 0.8
> 
> and:
> 
> Problem: the installed libavfilter9-32bit-6.0.1-2.2.x86_64 requires
> 'libswresample.so.4(LIBSWRESAMPLE_4.10_SUSE)', but this requirement cannot
> be provided
> 
> Possibly the second is related but the first is for a Packman package as is
> the second.

You're not alone... This happens from time to time, when packages linked
from openSUSE.org:openSUSE:Factory are not yet released in an official
Tumbleweed snapshot. Packages get built on PMBS in their latest version,
but the then current TW snapshot does *not* necessarily have them.
One solution would be to link our packages against the sources of the
latest TW snapshot instead of openSUSE.org:openSUSE:Factory, but I
haven't found a solution for that; I asked on the buildservice mailing
list, but haven't received an answer yet.

If this happens, one needs to wait for the next TW snapshot :(
20240116 has just been released, so it should be installable again.

> Thanks in advance,
> 
> nath

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] ffmpeg-4 in Essentials out of sync

[Manfred Hollstein]

Hi Olaf,

On Wed, 03 Jan 2024, 21:26:00 +0100, Olaf Hering wrote:
> Wed, 3 Jan 2024 16:42:29 +0100 Manfred Hollstein :
> 
> > What do you think?
> 
> The purpose of the fork was to deal with the unmaintained multimedia
> packages in SLE15. Hopefully the ffmpeg-4 package will continue to
> support SLE15 in the future. I have restored the _link to Factory now.

+1

Thx! When such problems will show up again in Leap or SLE15, we can deal
with them again. Jan was pretty helpful in that regard during the past
few months.

> Olaf

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] ffmpeg-4 in Essentials out of sync

[Manfred Hollstein]

Hi Olaf,

I see that you update Essentials/A_tw-ffmpeg-4 pulling in some changes
from openSUSE:Factory/ffmpeg-4 from time to time. The package isn't
building due to vmaf being >= 3 in TW.

To be honest I cannot actually see any Packman specific changes, so
shouldn't we replace it with a link to

  openSUSE.org:openSUSE:Factory/ffmpeg-4

just the same way as we handle A_tw-ffmpeg-5 and A_tw-ffmpeg-6?

What do you think?

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi Tom,

On Wed, 27 Dec 2023, 12:31:11 +0100, Tom Weinmann wrote:
> Hello Manfred
> 
> Thanks  for your help. I can confirm that 20.2-150500.5.pm.1 solves my issues
> with addons.

thanks for your feedback, too!

> Best, Tom

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
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

[Manfred Hollstein]

Hi Eric,

On Wed, 27 Dec 2023, 11:08:57 +0100, Eric Schirra wrote:
> 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. :-)

good to hear - thanks for your feedback!

> Regards
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Kodi vs python - next update will use python-3.11

[Manfred Hollstein]

Hi there,

some of you might remember some heated discussions about the old version
of Python used by kodi. I looked into this issue further and found out,
that it is actually pretty simple to use a newer version than what is
used by default on a Linux OS. The patch below shows what's needed to
be able to use python-3.11 on all supported versions of openSUSE (Leap
15.5, 15.6, Slowroll, and Tumbleweed).

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.

FWIW, Kodi 21 Omega will be released some time early next year. I'll
make sure we'll have a similar Python environment in the new version,
too. I am currently building/testing Kodi 21 Beta2 Omega in my private
build environment and everything looks OK for now. So, once the next
Kodi version will be freely available, we shall have updated packages
for openSUSE in a very short timeframe, too.

Cheers.

l8er
manfred

>>>>>>>>>>>>>>>>>>>>>>> PATCH to use Python 3.11 <<<<<<<<<<<<<<<<<<<<<<<
Index: kodi.changes
===
--- kodi.changes (revision 98)
+++ kodi.changes (revision 12)
@@ -1,4 +1,9 @@
 ---
+Mon Dec 25 17:13:19 UTC 2023 - Manfred Hollstein 
+
+- Use python3.11 on all platforms.
+
+---
 Tue Dec  5 12:31:48 UTC 2023 - Manfred Hollstein 
 
 - Unban fmt10, but add new patch fix_building_with_fmt10.patch
Index: kodi.spec
===
--- kodi.spec (revision 98)
+++ kodi.spec (revision 12)
@@ -121,7 +121,8 @@
 BuildRequires:  fstrcmp-devel
 BuildRequires:  pkgconfig(fmt)
 BuildRequires:  pkgconfig(RapidJSON) >= 1.0.2
-BuildRequires:  pkgconfig(python3)
+BuildRequires:  python(abi) >= 3.11
+BuildRequires:  pkgconfig(python-3.11)
 BuildRequires:  libmysqlclient-devel
 BuildRequires:  pkgconfig(libass)
 BuildRequires:  pkgconfig(libcurl)
@@ -425,6 +426,7 @@
 -DAPP_RENDER_SYSTEM=gl \
 -DX11_RENDER_SYSTEM=gl \
 -DBUILD_SHARED_LIBS=1 \
+-DPYTHON_VER=3.11 \
 ${NULL}
 
 #-DRapidJSON_URL=%{SOURCE25}
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> End of PATCH <<<<<<<<<<<<<<<<<<<<<<<<<<<<<


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] kodi 20.2-150400.4.pm.1 (openSUSE_Leap 15.4/x86_64)

[Manfred Hollstein]

Hi Tom,

On Mon, 25 Dec 2023, 17:55:36 +0100, Manfred Hollstein wrote:
> Hi Tom,
> 
> On Mon, 25 Dec 2023, 11:37:29 +0100, Tom Weinmann wrote:
> > Dear packman
> > 
> > We are using Kodi on Leap 15.5. Some AddOns are failing with: Error
> > Contents: future feature annotations is not defined ...
> > Apparently this is to be expected since default python3 refers to python3.6
> > on leap15.5 and future annotations requires at least 3.7.
> > 
> > Is there a simple way to specify the python interpreter at Kodi launch? (I
> > don't like to mess with our systems default python interpreter path).
> > 
> > Since standard Leap repos provide python3.10 (or newer) would it be an
> > option to add that dependency and compile Kodi to use this newer interpreter
> > by default (something like -DPYTHON_PATH=... -DPYTHON_VER=...)?
> 
> I'll look what I can change. As python3.11 does not come with all usual
> python modules, I'm not sure if it would work. Keep you posted!

I have now built kodi which requires libpython3_11-1_0 instead of
libpython3_6m1_0. Works for me, but can you please give it a test, too?
Download it from here:

  
http://pmbs.links2linux.de:8080/home:/manfred-h/15.5/x86_64/kodi-20.2-150500.16.pm.1.x86_64.rpm

I'll then submit my changes (which are pretty little) to the official
package in Multimedia.

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] kodi 20.2-150400.4.pm.1 (openSUSE_Leap 15.4/x86_64)

[Manfred Hollstein]

Hi Tom,

On Mon, 25 Dec 2023, 11:37:29 +0100, Tom Weinmann wrote:
> Dear packman
> 
> We are using Kodi on Leap 15.5. Some AddOns are failing with: Error
> Contents: future feature annotations is not defined ...
> Apparently this is to be expected since default python3 refers to python3.6
> on leap15.5 and future annotations requires at least 3.7.
> 
> Is there a simple way to specify the python interpreter at Kodi launch? (I
> don't like to mess with our systems default python interpreter path).
> 
> Since standard Leap repos provide python3.10 (or newer) would it be an
> option to add that dependency and compile Kodi to use this newer interpreter
> by default (something like -DPYTHON_PATH=... -DPYTHON_VER=...)?

I'll look what I can change. As python3.11 does not come with all usual
python modules, I'm not sure if it would work. Keep you posted!

> Best regards,
> Tom

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Ffmpeg-6 only for Tumbleweed/Slowroll?

[Manfred Hollstein]

On Wed, 20 Dec 2023, 20:32:46 +0100, Olaf Hering wrote:
> Wed, 20 Dec 2023 09:45:12 +0100 Manfred Hollstein :
> 
> > OK to enable Leap 15.5 and 15.6 in A_tw-ffmpeg-6?
> 
> It is already enabled, and I submitted changes for both affected packages.

Perfect, thanks! I have moved my kodi-next work into
home:manfred-h:kodi-next where both kodi and kodi.binary-addons (21.0b2)
successfully build.

> Olaf

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Ffmpeg-6 only for Tumbleweed/Slowroll?

[Manfred Hollstein]

Hi Olaf,

On Wed, 20 Dec 2023, 07:21:45 +0100, Olaf Hering wrote:
> Tue, 19 Dec 2023 15:56:00 +0100 Manfred Hollstein :
> 
> > Does anybody know of a reason why we shouldn't enable the latter two, too?
> 
> There are already "Prefer:" settings for ffmpeg, which makes it safe
> for most packages. But for some reason xine-lib and chromium need
> further tweaking of the existing Prefer settings.

xine-lib-12 seems easy, it just needs some explicit versions numbers for
libavutils and libpostproc, too. Now it builds with ffmpeg-6. SR:

  https://pmbs.links2linux.org/request/show/5912

By "chromium" do you mean "chromium-ffmpeg-extra" from the Extra
project? It currently doesn't even build for Tumbleweed (some "epoxy"
piece is missing), but I'll check the ffmpeg dependencies, too.

> Olaf

OK to enable Leap 15.5 and 15.6 in A_tw-ffmpeg-6?

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Ffmpeg-6 only for Tumbleweed/Slowroll?

[Manfred Hollstein]

On Tue, 19 Dec 2023, 15:56:00 +0100, Manfred Hollstein wrote:
> Hi there,
> 
> I am currently working on getting the upcoming new version of Kodi 21
> Omega (currently at beta 2) to build in PMBS. Amongst several updates,
> one of the most crucial issues is that it needs ffmpeg-6 and refuses to
> build with anything before that.
> 
> Currently we only enable Tumbleweed and Slowroll in
> Essentials/A_tw-ffmpeg-6, but we would also need openSUSE_Leap_15.5 and
> openSUSE_Leap_15.6. Does anybody know of a reason why we shouldn't
> enable the latter two, too?

FWIW, it builds without any issue:

  <https://pmbs.links2linux.org/package/show/home:manfred-h/A_tw-ffmpeg-6>

Shall/Can I enable it in Essentials?

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Ffmpeg-6 only for Tumbleweed/Slowroll?

[Manfred Hollstein]

Hi there,

I am currently working on getting the upcoming new version of Kodi 21
Omega (currently at beta 2) to build in PMBS. Amongst several updates,
one of the most crucial issues is that it needs ffmpeg-6 and refuses to
build with anything before that.

Currently we only enable Tumbleweed and Slowroll in
Essentials/A_tw-ffmpeg-6, but we would also need openSUSE_Leap_15.5 and
openSUSE_Leap_15.6. Does anybody know of a reason why we shouldn't
enable the latter two, too?

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Issue Kodi 20.2-1699.3.pm.7 auf Opensuse Tumbleweed

[Manfred Hollstein]

Hi there,

Sagi has approved the patch one hour ago - thanks, Sagi!

New packages will shown up on the mirrors, soon.

Cheers.

l8er
manfred

On Wed, 06 Dec 2023, 14:51:45 +0100, Manfred Hollstein wrote:
> Hi Thomas,
> 
> On Wed, 06 Dec 2023, 14:29:13 +0100, Thomas Lauks wrote:
> > Hallo,
> > 
> > while starting Kodi on Opensuse Tumbleweed the issue below occours:
> > 
> > /usr/lib64/kodi/kodi.bin: symbol lookup error: /usr/lib64/kodi/kodi.bin:
> > undefined symbol: _ZN6spdlog7details7log_msgC1ENS_
> > 10source_locEN3fmt2v917basic_string_viewIcEENS_5level10level_enumES6_
> 
> yes, thanks for your report! This was to be expected due to integration
> of fmt10 in one of the last TW snapshots.
> 
> I have created a fix for it and submitted it to be reviewed by Sagi, the
> other Kodi maintainer. If he doesn't respond until Saturday due to
> private reasons, I'll self-approve it then:
> 
>   https://pmbs.links2linux.org/request/show/5883
> 
> > Greets
> > 
> > Thomas Lauks
> 
> Cheers.
> 
> l8er
> manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Issue Kodi 20.2-1699.3.pm.7 auf Opensuse Tumbleweed

[Manfred Hollstein]

Hi Thomas,

On Wed, 06 Dec 2023, 14:29:13 +0100, Thomas Lauks wrote:
> Hallo,
> 
> while starting Kodi on Opensuse Tumbleweed the issue below occours:
> 
> /usr/lib64/kodi/kodi.bin: symbol lookup error: /usr/lib64/kodi/kodi.bin:
> undefined symbol: _ZN6spdlog7details7log_msgC1ENS_
> 10source_locEN3fmt2v917basic_string_viewIcEENS_5level10level_enumES6_

yes, thanks for your report! This was to be expected due to integration
of fmt10 in one of the last TW snapshots.

I have created a fix for it and submitted it to be reviewed by Sagi, the
other Kodi maintainer. If he doesn't respond until Saturday due to
private reasons, I'll self-approve it then:

  https://pmbs.links2linux.org/request/show/5883

> Greets
> 
> Thomas Lauks

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] conflict when updating to yt-dlp-2023.10.13-150500.4.pm.1.noarch

[Manfred Hollstein]

Hi there,

On Thu, 26 Oct 2023, 15:17:10 +0200, Adam Mizerski wrote:
> W dniu 26.10.2023 o 14:29, Carlos E. R. pisze:
> > Hi,
> > 
> > I have this conflict when updating:
> > 
> >  YaST2 conflicts list - generated 2023-10-26 12:34:12 
> > 
> > nothing provides 'python3-yt-dlp' needed by the to be installed
> > yt-dlp-2023.10.13-150500.4.pm.1.noarch
> > 
> >  [x] do not install yt-dlp-2023.10.13-150500.4.pm.1.noarch
> > 
> >  [ ] break yt-dlp-2023.10.13-150500.4.pm.1.noarch by ignoring some
> > of its dependencies
> > 
> > 
> >  YaST2 conflicts list END ###
> 
> You just need to wait for mirrors to sync fully.
> 
> This usually happens, when one source package builds arch specific package
> (like i586 or x86_64) and noarch. If the i586 build is done earlier, your
> system sees the noarch package as ready to update, but the x86_64 is not
> ready yet.

while this is true in principle, it is not here! python311 got
introduced to Leap 15.5 recently as an update. The package
yt-dlp-2023.10.13-150500.4.pm.1.noarch.rpm requires 

  python3-yt-dlp

but now a package python311-yt-dlp-2023.10.13-150500.4.pm.1.noarch.rpm
is built which, of course, does not provide python3-yt-dlp

Some Python/RPM/macros expert needs to step up here to get this
resolved - and that's not me!

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi + Amazon

[Manfred Hollstein]

On Sat, 14 Oct 2023, 15:04:47 +0200, Eric Schirra wrote:
> 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

Cannot decypher this sentence.

> >> 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'm not aggressive at all, I just stated that it's not Packman's job to
deal with the short-comings of Leap. When you see packages not working
in Leap because of unresolved/wrong dependencies, please open a
bugzilla.

> 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.

So far, nobody said Kodi isn't working for him. You pulled in something
outside the Kodi on Packman world, which apparently has some
requirements which cannot be fulfilled on Leap, then it is not a failure
of our Kodi package.

> 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.

You are absolutely free to chose a different OS!

> Gruß
> Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi + Amazon

[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.

> 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!

> 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.

> Regards
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi + Amazon

[Manfred Hollstein]

On Sat, 14 Oct 2023, 13:11:01 +0200, Eric Schirra wrote:
> 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
> > > > > >
> > > > > > ^
> > > > > > 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!

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi + Amazon

[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.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/

OK, found that in the meantime, too.

> > 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.

Did you try the Beta version which is mentioned on that page?

Perhaps Amazon changed their API?

> Regards
> Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi + Amazon

[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/

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

> > Gruß
> >  Eric

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi + Amazon

[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

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.

> Gruß
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Error with Broadcom-Wl install

[Manfred Hollstein]

Hi Andrew,

On Sat, 12 Aug 2023, 00:57:03 +0200, lazerousz wrote:
> Hello,
> 
> I have been trying to install the broadcom-wl package in a brand new
> OpenSuse Leap 15.5 install and I'm getting the following error message -
> "nothing provides 'ksym(default:unregister_netdev) = 7666e162' need by the
> to be installed
> broadcom-wl-kmp-default-6.30.223.271_k4.12.14_lp150.11.44.x86_64"

where did you get that package from? This one is really ancient! Please
use the package from the Essentials project for openSUSE_Leap_15.5:

  sudo zypper addrepo 
http://pmbs.links2linux.de:8080/Essentials/openSUSE_Leap_15.5/ \
pm_Essentials

Then you can install the proper package using the following command:

  sudo zypper in 
broadcom-wl-kmp-default-6.30.223.271_k5.14.21_150500.55.12-150500.18.pm.12.x86_64.rpm

As you can see, this package has been built for kernel k5.14.21_150500.55.12,
which is the current kernel on Leap 15.5

> Andrew

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi+Wayland+Widevine

[Manfred Hollstein]

Moin,

On Wed, 19 Jul 2023, 07:50:19 +0200, Ailin Nemui wrote:
> Hey,
> 
> Manfred wrote:
> 
> > BUT, if you can share the changes you did, I can test if those will 
> > work on my configuration, too, which is X11 on an Intel on-CPU GPU 
> > (various models). We can then see how to move forward.
> 
> thanks for your message. I have prepared the diff (which is quite
> small, just enable the bcond and add a missing dependency & define) as
> well as you can probably just download the binaries from obs to try
> them:
> 
> https://pmbs-api.links2linux.de/package/rdiff/home:ailin_nemui:branches:Multimedia/kodi?opackage=kodi=Multimedia=5
> 
> 
> This will compile kodi with GLES instead of GL, and fix/workaround the
> Netflix/DRM issue in the meantime. I have also opened an issue on
> https://github.com/xbmc/xbmc/issues/23525 in case this problem can be
> fixed in Kodi for Wayland/GL later by them.
> 
> Let me know what you think and if these packages work for you as well.

This patch results in not using the hardware based decoding capabilities
of the GPU which in effect raises the system load quite significantly.
I'd suggest we wait for responses from upstream.

> Best,

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] HandBrake 1.6.0 - Experiences?

[Manfred Hollstein]

Hi Pete,

thanks for your work on getting HB 1.6.0 introduced:

  https://pmbs.links2linux.org/request/show/5793

As I have had some serious issues when new releases got introduced
(especially with my own presets), do you have any experience with the
new release? I'd like to get it accepted, but thought I'd better ask
before...

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] OBS Studio 29.1.2

[Manfred Hollstein]

Hi Pete,

On Sun, 04 Jun 2023, 13:25:43 +0200, Hans-Peter Jansen wrote:
> Am Mittwoch, 31. Mai 2023, 18:22:16 CEST schrieb Sylvain Baril:
> > Hi,
> > 
> > I'm using a lot of OBS Studio on OpenSuse Tumbleweed x86_64.
> > 
> > But version 29.1.2 has been there since May 28th and I still see an "old"
> > 29.0.2 version of it on PackMan.
> > 
> > There's a lot of bug fixes and new features in this 29.1.2 release.
> > 
> > Could it be possible to update to the newest release please?
> 
> Hi, 
> 
> 29.1.2 is on the way.
> 
> It builds now with Qt6 on Tumbleweed.
> 
> Somebody with admin foo for the Multimedia project will need to
> link aiso from openSUSE.org:openSUSE:Backports:SLE-15-SP5/asio to Multimedia/
> A_15.4_asio and limit it building for 15.4 in order to fulfill OBS build deps 
> for 15.4.

done.

> Cheers,
> Pete

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Something wrong with the Multimedia RPM exporter?

[Manfred Hollstein]

Hi Stefan,

I updated MakeMKV yesterday and all packages built fine:

  https://pmbs.links2linux.org/package/show/Multimedia/MakeMKV

However, packages at

  http://pmbs.links2linux.de:8080/Multimedia/openSUSE_Tumbleweed/x86_64/?C=M;O=D

stay at the date of "2023-05-27 11:06"

Do you know if there is something wrong wrt/ exporting packages from
Tumbleweed? It doesn't seem to happen for Essentials at least.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi Tumbleweed symbol not found error - Kodi won't start!

[Manfred Hollstein]

Hi Steven,

On Sat, 20 May 2023, 21:08:14 +0200, Steven Swart wrote:
> Just had a thought, Manfred - would it be worth publishing this issue on the
> forums? Just in case anyone else out there runs into the same problem?
> 
> In which case, rather you do it than me. I am not sure if I would get it
> right...

TBH, I really don't like forums - perhaps I'm too old for that. The
issue really is about having arbitrary repos enabled which are not
thought for a daily use - this is why they are called "devel" repos.
When you use such repo, you are on your own to ensure you know the
implications.

If someone would write this up properly, I certainly wouldn't be against
it - it's just not me!

> Kind regards,
> Steven.

Cheers.

l8er
manfred

> On Sat, 20 May 2023, 21:04 Manfred Hollstein  wrote:
> 
> On Sat, 20 May 2023, 20:43:44 +0200, Steven Swart wrote:
> > Thank you for your feedback as well, Manfred, I will do as you advise.
> 
> Just checked if the newly built packages have a direct dependency on
> libfmt9 - they don't :( Since libfmt appears to be only required by
> *some* addons, adding a hard "Require: libfmt9" would punish all users
> of addons which don't actually need libfmt at all. I'm now going to
> remove the "BuildRequire: ..." again, as it does not solve your problem.
> 
> Please check all packages you have installed from the devel:*
> repos/projects!


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi Tumbleweed symbol not found error - Kodi won't start!

[Manfred Hollstein]

On Sat, 20 May 2023, 20:43:44 +0200, Steven Swart wrote:
> Thank you for your feedback as well, Manfred, I will do as you advise.

Just checked if the newly built packages have a direct dependency on
libfmt9 - they don't :( Since libfmt appears to be only required by
*some* addons, adding a hard "Require: libfmt9" would punish all users
of addons which don't actually need libfmt at all. I'm now going to
remove the "BuildRequire: ..." again, as it does not solve your problem.

Please check all packages you have installed from the devel:*
repos/projects!

> Enjoy the rest of your weekend!

Same to you!

> Kind regards,
> Steven.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi Tumbleweed symbol not found error - Kodi won't start!

[Manfred Hollstein]

Hi Steven,

On Sat, 20 May 2023, 18:30:15 +0200, Steven Swart wrote:
> Greetings, Packmans!
> 
> Just a quick report back.

thanks for your feedback!

>   Installing the new Packman version of the ProjectM
> music visualiser addon still didn't solve my problem. I was still getting 
> this:
> 
> steven@linux-ll3r:~> kodi
> /usr/lib64/kodi/kodi.bin: symbol lookup error: /usr/lib64/kodi/kodi.bin:
> undefined symbol:
> _ZN6spdlog7details7log_msgC1ENS_10source_locEN3fmt2v917basic_string_viewIcEENS_5level10level_enumES6_
> 
> So, upon investigation, this was the problem. I checked which version of
> libfmt10 I had installed:
> 
> steven@linux-ll3r:~> zypper info libfmt10
> Loading repository data...
> Reading installed packages...
> 
> 
> Information for package libfmt10:
> -
> Repository     : devel:libraries:c_c++

This is the source of your problem! Adding any devel: projects may
result in a lot of problems; we just recently had that with some issues
when openssl stopped working properly... I'd suggest you lower the
priority of all such devel: repos/projects to something higher than 99
and check all packages you have installed from any of these devel:
repos/projects!

> [...]
> I am not a maintainer, but perhaps this means that the Kodi requires should
> change, and maybe that Kodi itself needs to be built against libfmt10?

I just added a BuildRequire: to ban any fmt version >= 10!

> In other news, I now have a Leap 15.4 machine running the ProjectM visualiser
> as well, and another Leap 15.4 machine that I plan to install it on at some
> stage.
> 
> All in all, a big win all around for all SUSE users who use Kodi, thank you so
> much, Manfred! :-)

Thank you, Steven, to drill down this mess!

> Kind regards,
> Steven.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi Tumbleweed symbol not found error - Kodi won't start!

[Manfred Hollstein]

Hi Steven,

On Thu, 18 May 2023, 13:12:50 +0200, Steven Swart wrote:
> Thank you, all, and Manfred!
> 
> After some investigation and experimentation, I located the source of the
> problem. It was my hacky method of installing the ProjectM visualisation 
> addon.
> 
> Briefly, libspdlog was updated from v 1.9.2 to 1.11 at some point. The Flatpak
> version has received no updates for quite some time. I tried various hacky
> methods again, like changing the symlinks to the .so files, but they are 
> binary
> incompatible, and that just doesn't work.
> 
> The only solution is to build the ProjectM addon from source.
> 
> I will do that shortly, and post an update about how to do that.

I have just checked if the projectm addon still cannot be built, but
that was apparently only a failure with Leap 15.3. I have therefore
re-added the addon for all currently supported OSes Leap 15.4, 15.4 and
Tumbleweed. You should soon see a new package on PMBS or its mirrors.

> Kind regards,
> Steven.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi Tumbleweed symbol not found error - Kodi won't start!

[Manfred Hollstein]

On Thu, 18 May 2023, 12:20:42 +0200, Manfred Hollstein wrote:
> Hi Steven,
> 
> On Thu, 18 May 2023, 10:43:45 +0200, Steven Swart wrote:
> > Good day, Manfred, Sagi!
> > 
> > The only weird thing I have done with this installation of Kodi is this:
> > 
> > https://www.dropbox.com/s/xmk1wb3qw1d2gny/
> > Quick.Way.to.add.the.ProjectM.Visualisation.Addon.to.a.Packman.Kodi.Installation.pdf?
> > dl=0
> 
> You should be able to install the addon directly from the Kodi
> repository:
> 
>   <https://kodi.tv/addons/nexus/visualization.projectm/>
> 
> I remember we had problems with exactly this addon, because it was using
> a member datadir which did not exist in all OS versions we use to build
> kodi and the kodi.binary-addons packages for. You can however install
> any missing addons directly from within Kodi. Perhaps you give it try.

Embarrassing... :( it's not available for Linux, which is probably why
you followed the Quick.Way... in the first place.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi Tumbleweed symbol not found error - Kodi won't start!

[Manfred Hollstein]

Hi Steven,

On Thu, 18 May 2023, 10:43:45 +0200, Steven Swart wrote:
> Good day, Manfred, Sagi!
> 
> The only weird thing I have done with this installation of Kodi is this:
> 
> https://www.dropbox.com/s/xmk1wb3qw1d2gny/
> Quick.Way.to.add.the.ProjectM.Visualisation.Addon.to.a.Packman.Kodi.Installation.pdf?
> dl=0

You should be able to install the addon directly from the Kodi
repository:

  

I remember we had problems with exactly this addon, because it was using
a member datadir which did not exist in all OS versions we use to build
kodi and the kodi.binary-addons packages for. You can however install
any missing addons directly from within Kodi. Perhaps you give it try.

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi Tumbleweed symbol not found error - Kodi won't start!

[Manfred Hollstein]

Moin,

On Thu, 18 May 2023, 09:15:46 +0200, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [packman] Kodi Tumbleweed symbol not found error - Kodi 
> won't start!
>   Message-ID : <634c1a9c-47ab-4c2b-9dee-da431f007...@ssis.sm>
>   Date & Time: Thu, 18 May 2023 08:37:13 +0200
> 
> [DE] == Diego Ercolani  has written:
> 
> DE> Probably you need to wait for a rebuild trigger and the new
> DE> symbols will be imported automatically. Please  see 
> DE> https://openbuildservice.org/ the system used by opensuse and
> DE> packman
> 
> The reason is that fmt has been updated to 10.0.0.

where do you find fmt 10.0.0? openSUSE:Factory still has 9.1.0.

> kodi does not support this fmt at the moment, so the only solution is
> to install the libfmt9.

He ought to have libfmt9 installed, either directly or as a dependency
of kodi. FWIW, I just upgraded my systems to TW snapshot 20230517, and
kodi runs successfully.

@Diego, please show us the error message you get in the console window,
as Sagi already suggested!

> Regards.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] PMBS is dead

[Manfred Hollstein]

Hi there,

it looks as if PMBS is completely dead.

@Stefan: can you please have a look?

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Multimedia Key Expires in 12 days

[Manfred Hollstein]

Hi there,

running "zypper ref" shows this for the Packman Multimedia repository:

The gpg key signing file 'repomd.xml' will expire in 12 days.
  Repository:   packman-multimedia.obs
  Key Fingerprint:  5302 7CA5 85A8 0281 6CB3 B2C3 CB78 7E2A 6058 7B34
  Key Name: Multimedia OBS Project 
  Key Algorithm:RSA 2048
  Key Created:  Fri Mar 19 12:04:21 2021
  Key Expires:  Sat Apr 15 02:38:25 2023 (expires in 12 days)
  Rpm Name: gpg-pubkey-60587b34-60548535

Shall I extend its lifetime using

  osc -A pmbs signkey --extend Multimedia

or what's the suggested method?

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Request to join your project

[Manfred Hollstein]

Hi Dmitry,

On Fri, 24 Feb 2023, 10:13:01 +0100, Dmitry Balakin wrote:
> Could you please send the required information as mentioned at
> http://packman.links2linux.org ?

please go to  and enter your
data. When you send your chosen Username to this list, it'll be enabled.

HTH, cheers.

l8er
manfred

> чт, 23 февр. 2023 г. в 12:34, Dmitry Balakin :
> 
> > Hello.
> > My name is Dima. I want to join your project.


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] A_tw-libqt4 is a linked package but differs from the link source

[Manfred Hollstein]

Hi Stefan,

On Wed, 22 Feb 2023, 18:06:35 +0100, Stefan Seyfried wrote:
> On 22.02.23 15:25, Manfred Hollstein wrote:
> > On Wed, 22 Feb 2023, 12:46:59 +0100, Manfred Hollstein wrote:
> > > Hi there,
> > > 
> > > the package A_tw-libqt4 fails since quite some time due to a patch which
> > > cannot be applied. I took a look and found out the following:
> > > 
> > >1. Multimedia/A_tw-libqt4 links to remote openSUSE.org:KDE:Qt/libqt4
> > >2. Comparing both packages results in lots of differences, e.g. the
> > >   failing patch does not even exist in openSUSE.org:KDE:Qt/libqt4
> > > 
> > > Does anybody have an idea, what could be reason for this? I would have
> > > expected that both packages are identical...
> > > 
> > > I could remove and re-create the package again, but I prefer to actually
> > > know, how this could develop!
> > 
> > I have now branched the same package to our Staging project using:
> > 
> >$ osc -A pmbs branch openSUSE.org:KDE:Qt libqt4 Staging A_tw-libqt4
> > 
> > and enabled openSUSE_Tumbleweed as the only build architecture. Build
> > doesn't start and checking the package doesn't look good either:
> > 
> >$ osc -A pmbs buildinfo Staging A_tw-libqt4 openSUSE_Tumbleweed x86_64
> > > package="A_tw-libqt4" downloadurl="http://pmbs-api.links2linux.de:8080;>
> >  x86_64
> >  excluded
> >  0d715460b0515c112503c2adef548560
> >  9b8490225476a74f0c0575d5df297074
> >  1
> >  0
> >
> > 
> > @Stefan, could this indicate some problems with the pmbs-api interface?
> 
> I don't think so (different Stefan, but anyway :-)
> 
> You linked a package with two spec file but your link has a name not
> matching those spec files, so OBS does not know what to build and thus
> excludes both spec files.
> 
> You need to add a _multibuild file or remove one of those spec files.

Of course, I hate these package with multiple .spec files... Thanks for
the hint/explanation!

Does anybody know if that package is still needed? I mean
https://build.opensuse.org/project/show/KDE:Qt probably doesn't include
the message

  Note that Qt 4 support ended in 2015 and these packages should not be used 
anymore.

without a reason...

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] A_tw-libqt4 is a linked package but differs from the link source

[Manfred Hollstein]

On Wed, 22 Feb 2023, 15:25:53 +0100, Manfred Hollstein wrote:
> On Wed, 22 Feb 2023, 12:46:59 +0100, Manfred Hollstein wrote:
> > Hi there,
> > 
> > the package A_tw-libqt4 fails since quite some time due to a patch which
> > cannot be applied. I took a look and found out the following:
> > 
> >   1. Multimedia/A_tw-libqt4 links to remote openSUSE.org:KDE:Qt/libqt4
> >   2. Comparing both packages results in lots of differences, e.g. the
> >  failing patch does not even exist in openSUSE.org:KDE:Qt/libqt4
> > 
> > Does anybody have an idea, what could be reason for this? I would have
> > expected that both packages are identical...
> > 
> > I could remove and re-create the package again, but I prefer to actually
> > know, how this could develop!
> 
> I have now branched the same package to our Staging project using:
> 
>   $ osc -A pmbs branch openSUSE.org:KDE:Qt libqt4 Staging A_tw-libqt4
> 
> and enabled openSUSE_Tumbleweed as the only build architecture. Build
> doesn't start and checking the package doesn't look good either:
> 
>   $ osc -A pmbs buildinfo Staging A_tw-libqt4 openSUSE_Tumbleweed x86_64
>package="A_tw-libqt4" downloadurl="http://pmbs-api.links2linux.de:8080;>
> x86_64
> excluded
> 0d715460b0515c112503c2adef548560
> 9b8490225476a74f0c0575d5df297074
> 1
> 0
>   
> 
> @Stefan, could this indicate some problems with the pmbs-api interface?

looks like I always focus on the wrong packages to be fixed... According
to https://build.opensuse.org/project/show/KDE:Qt

  Note that Qt 4 support ended in 2015 and these packages should not be used 
anymore.

While that they should not be used anymore is clear, I did not know that
they can be excluded via api somehow.

Anyway, I'll disable building the package now, but leave already built
packages available for other packages that probably "should not be used
anymore" ...

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] A_tw-libqt4 is a linked package but differs from the link source

[Manfred Hollstein]

On Wed, 22 Feb 2023, 12:46:59 +0100, Manfred Hollstein wrote:
> Hi there,
> 
> the package A_tw-libqt4 fails since quite some time due to a patch which
> cannot be applied. I took a look and found out the following:
> 
>   1. Multimedia/A_tw-libqt4 links to remote openSUSE.org:KDE:Qt/libqt4
>   2. Comparing both packages results in lots of differences, e.g. the
>  failing patch does not even exist in openSUSE.org:KDE:Qt/libqt4
> 
> Does anybody have an idea, what could be reason for this? I would have
> expected that both packages are identical...
> 
> I could remove and re-create the package again, but I prefer to actually
> know, how this could develop!

I have now branched the same package to our Staging project using:

  $ osc -A pmbs branch openSUSE.org:KDE:Qt libqt4 Staging A_tw-libqt4

and enabled openSUSE_Tumbleweed as the only build architecture. Build
doesn't start and checking the package doesn't look good either:

  $ osc -A pmbs buildinfo Staging A_tw-libqt4 openSUSE_Tumbleweed x86_64
  http://pmbs-api.links2linux.de:8080;>
x86_64
excluded
0d715460b0515c112503c2adef548560
9b8490225476a74f0c0575d5df297074
1
0
  

@Stefan, could this indicate some problems with the pmbs-api interface?

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] A_tw-libqt4 is a linked package but differs from the link source

[Manfred Hollstein]

Hi there,

the package A_tw-libqt4 fails since quite some time due to a patch which
cannot be applied. I took a look and found out the following:

  1. Multimedia/A_tw-libqt4 links to remote openSUSE.org:KDE:Qt/libqt4
  2. Comparing both packages results in lots of differences, e.g. the
 failing patch does not even exist in openSUSE.org:KDE:Qt/libqt4

Does anybody have an idea, what could be reason for this? I would have
expected that both packages are identical...

I could remove and re-create the package again, but I prefer to actually
know, how this could develop!

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] A_tw-freshplayerplugin - shouldn't it be disabled/removed?

[Manfred Hollstein]

On Thu, 02 Feb 2023, 15:02:15 +0100, Manfred Hollstein wrote:
> Hi there,
> 
> the package Essentials/A_tw-freshplayerplugin fails since quite some
> time. IIUC, it is a plugin for the former Mozilla plugin interface to
> render flash apps in Firefox. IIRC, that plugin interface is long gone,
> so I'd vote for disabling and removing this particular package.
> 
> Any thoughts about this?

Update: I asked the same question to the maintainers on OBS and they
have promptly removed the package in multimedia:apps. It's gone in PMBS
now, too.

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] PMBS vs OBS - what are the differences wrt/ project configurations?

[Manfred Hollstein]

On Fri, 03 Feb 2023, 15:08:21 +0100, Dave Plater wrote:
> On 2/3/23, Manfred Hollstein  wrote:
> > On Fri, 03 Feb 2023, 14:41:16 +0100, Manfred Hollstein wrote:
> >> On Fri, 03 Feb 2023, 14:11:27 +0100, Dave Plater wrote:
> >> > [...]
> >> > Maybe it's better to use the patch you mentioned, there is a make
> >> > install issue when I tried a no examples build. Where can I find the
> >> > patch?
> >>
> >> grrh, I thought it was attached to the initial e-mail in this thread,
> >> but it got stripped off. Anyway, here's it inline:
> >>
> >> $ osc -A pmbs rdiff openSUSE.org:openSUSE:Factory libheif Essentials
> >
> > FWIW, this is the OBS SR: https://build.opensuse.org/request/show/1063030
> 
> Hope the maintainer doesn't mind, I've also come to the conclusion
> that chrpath is the solution. I've accepted your request.

Thanks a lot!

> Dave

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] PMBS vs OBS - what are the differences wrt/ project configurations?

[Manfred Hollstein]

On Fri, 03 Feb 2023, 14:41:16 +0100, Manfred Hollstein wrote:
> On Fri, 03 Feb 2023, 14:11:27 +0100, Dave Plater wrote:
> > [...]
> > Maybe it's better to use the patch you mentioned, there is a make
> > install issue when I tried a no examples build. Where can I find the
> > patch?
> 
> grrh, I thought it was attached to the initial e-mail in this thread,
> but it got stripped off. Anyway, here's it inline:
> 
> $ osc -A pmbs rdiff openSUSE.org:openSUSE:Factory libheif Essentials

FWIW, this is the OBS SR: https://build.opensuse.org/request/show/1063030

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] PMBS vs OBS - what are the differences wrt/ project configurations?

[Manfred Hollstein]

On Fri, 03 Feb 2023, 14:11:27 +0100, Dave Plater wrote:
> [...]
> Maybe it's better to use the patch you mentioned, there is a make
> install issue when I tried a no examples build. Where can I find the
> patch?

grrh, I thought it was attached to the initial e-mail in this thread,
but it got stripped off. Anyway, here's it inline:

$ osc -A pmbs rdiff openSUSE.org:openSUSE:Factory libheif Essentials
Index: libheif.changes
===
--- libheif.changes (revision 15)
+++ libheif.changes (revision 1)
@@ -1,4 +1,10 @@
 ---
+Thu Feb  2 19:25:04 UTC 2023 - Manfred Hollstein 
+
+- Use chrpath during build to delete otherwise illegal runtime
+  directories stored as RPATH in the executables
+
+---
 Fri Jan 27 14:32:03 UTC 2023 - Dirk Müller 
 
 - add 2ca02a128b2f76f7f293aa86a2ce1e04a8306c65.patch
Index: libheif.spec
===
--- libheif.spec (revision 15)
+++ libheif.spec (revision 1)
@@ -41,6 +41,7 @@
 Patch0: b6812284a2d70f29a5121ec3dbe652da07fdbbb7.patch
 # rebased from 
https://github.com/strukturag/libheif/commit/2ca02a128b2f76f7f293aa86a2ce1e04a8306c65.patch
 Patch1: 2ca02a128b2f76f7f293aa86a2ce1e04a8306c65.patch
+BuildRequires:  chrpath
 BuildRequires:  cmake
 BuildRequires:  fdupes
 BuildRequires:  gcc-c++
@@ -161,6 +162,7 @@
  heif-thumbnailer
  do
 install -m 0755 build/examples/$e %{buildroot}%{_bindir}/$e
+chrpath --delete %{buildroot}%{_bindir}/$e
 install -m 0644 examples/$e.1 %{buildroot}%{_mandir}/man1/$e.1
  done
 %else

> Thanks
> Dave

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] PMBS vs OBS - what are the differences wrt/ project configurations?

[Manfred Hollstein]

On Fri, 03 Feb 2023, 13:11:10 +0100, Dave Plater wrote:
> On 2/3/23, Manfred Hollstein  wrote:
> > Moin,
> >
> > On Fri, 03 Feb 2023, 12:20:17 +0100, Henne Vogelsang wrote:
> >> Hey,
> >>
> >> On 03.02.23 10:14, Manfred Hollstein wrote:
> >>
> >> > I've been fighting with the package libheif not building in PMBS during
> >> > the past few days. I always fails due to the build directory being
> >> > stored in the built programs as an internal RPATH. The package is
> >> > linked
> >> > from openSUSE.org:openSUSE:Factory where no error occurs. I found a
> >> > patch for it using "chrpath" to delete such RPATH elements in a
> >> > program.
> >> >
> >> > Can anyone explain why this is necessary when building in PMBS and it
> >> > is
> >> > not needed when building in OBS? I fail to see a reason...
> >>
> >> This has nothing to do with OBS instances. It's the repository that
> >> matters.
> >> Just because a repository is called openSUSE_Tumbleweed it isn't
> >> neccesarry
> >> openSUSE Tumbleweed. The name doesn't matter, the included paths do. In
> >> this
> >> case
> >>
> >> Staging/openSUSE_Tumbleweed
> >> is Multimedia/openSUSE_Tumbleweed
> >> is Essentials/openSUSE_Tumbleweed
> >> is openSUSE.org:openSUSE:Tumbleweed/standard
> >>
> >> While openSUSE.org:openSUSE:Factory builds only against the last path in
> >> your chain.
> >
> > it's actually much easier... Due to the BUILD_ORIG macro being set to 1
> > on PMBS, it builds more than what is built on openSUSE:Factory, where
> > these additional arguments are passed to cmake:
> >
> >   -DWITH_LIBDE265=OFF -DWITH_X265=OFF -DWITH_EXAMPLES=OFF
> >
> > Note the -DWITH_EXAMPLES=OFF, which results in no executables being
> > built/installed at all. I think I need to send my patch to the
> > multimedia:libs project, so that we (PMBS) don't have to patch the
> > linked package for each update.
> >
> >> Henne
> >
> > Thanks for your help anyway!
> >
> > Cheers.
> >
> > l8er
> > manfred
> >
> 
> All that's needed is a -DWITH_EXAMPLES=OFF correct?

In principle yes, but that would loose the Heif thumbnailer which also
gets built as an example, but ends up in a separate package heif-thumbnailer
so I'd rather prefer to get the issue properly resolved.

> Regards
> Dave

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] PMBS vs OBS - what are the differences wrt/ project configurations?

[Manfred Hollstein]

Moin,

On Fri, 03 Feb 2023, 12:20:17 +0100, Henne Vogelsang wrote:
> Hey,
> 
> On 03.02.23 10:14, Manfred Hollstein wrote:
> 
> > I've been fighting with the package libheif not building in PMBS during
> > the past few days. I always fails due to the build directory being
> > stored in the built programs as an internal RPATH. The package is linked
> > from openSUSE.org:openSUSE:Factory where no error occurs. I found a
> > patch for it using "chrpath" to delete such RPATH elements in a program.
> > 
> > Can anyone explain why this is necessary when building in PMBS and it is
> > not needed when building in OBS? I fail to see a reason...
> 
> This has nothing to do with OBS instances. It's the repository that matters.
> Just because a repository is called openSUSE_Tumbleweed it isn't neccesarry
> openSUSE Tumbleweed. The name doesn't matter, the included paths do. In this
> case
> 
> Staging/openSUSE_Tumbleweed
> is Multimedia/openSUSE_Tumbleweed
> is Essentials/openSUSE_Tumbleweed
> is openSUSE.org:openSUSE:Tumbleweed/standard
> 
> While openSUSE.org:openSUSE:Factory builds only against the last path in
> your chain.

it's actually much easier... Due to the BUILD_ORIG macro being set to 1
on PMBS, it builds more than what is built on openSUSE:Factory, where
these additional arguments are passed to cmake:

  -DWITH_LIBDE265=OFF -DWITH_X265=OFF -DWITH_EXAMPLES=OFF

Note the -DWITH_EXAMPLES=OFF, which results in no executables being
built/installed at all. I think I need to send my patch to the
multimedia:libs project, so that we (PMBS) don't have to patch the
linked package for each update.

> Henne

Thanks for your help anyway!

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi crash

[Manfred Hollstein]

Hi Eric,

On Fri, 03 Feb 2023, 11:57:24 +0100, Eric Schirra wrote:
> Am Freitag, 3. Februar 2023, 10:36:41 CET schrieb Manfred Hollstein:
> > Moin,
> > 
> > On Fri, 03 Feb 2023, 09:31:44 +0100, Stefan Botter wrote:
> > > Hi Eric,
> > > 
> > > On Thu, 2023-02-02 at 16:34 +0100, Eric Schirra wrote:
> > > > Since probably kodi version 20, kodi crashes under Leap 15.4.
> > > > Is this only happening to me or to others as well?
> > > 
> > > At least for my players kodi 20 is working without problem on 15.4. I
> > > have 4 instances, 2 are NUCs, one is an older Intel Celeron S with
> > > buildin graphics and the last one is my workstation with NVidia
> > > graphics.
> > 
> > Kodi runs very well for me, too. All my systems use Intel CPU based
> > graphics, mixture of DisplayPort, HDMI, and built-in Display with sound
> > passthru and without, ie. normal sound via PulseAudio. Every instance
> > also uses a PVR to access TV and Radio from a dreambox.
> > 
> > How does it crash for you? Does it start at all, or does it suddenly
> > crash when you're e.g. playing some special video? When it is running,
> > you will find more details in ~/.kodi/temp/kodi.log
> 
> Strange. Then it is probably somehow with me.
> The only difference is that you have Intel CPU and I have AMD. As well as 
> graphic nvidia.
> Could that be the reason?
> kodi starts, but kodi import the addons then comes: 

This was obviously the first time Kodi 20 started which caused some
migration phase. I had different behaviour on all systems, especially
the one running on Winblows didn't want to talk to the PVR at all; it
even complained about the Enigma2 addon being incompatible! I tried it
the day after and, guess what, everything worked as before.

When such a major update is apparent, I usually save my whole ~/.kodi
directory elsewhere. When problems appear, I restart by copying the
content of the saved directory back to ~/.kodi

IIRC, such major updates always behaved different and need several
restarts of the application - on Winblows even a reboot of the system.

> Now I did this a few times in the console and now the error is gone?. Very 
> very strange.
> In the meantime I had uninstalled the zattoo addon from packman. After that, 
> the error still came at least once. 
> Now currently runs but kodi.
> I do not understand this. :-(

See above, I believe this could explain the behaviour you are seeing.

> Thanks for your answers though. Let's see if it stays like this.
> 
> 
> Regards
>  Eric

Cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi crash

[Manfred Hollstein]

Moin,

On Fri, 03 Feb 2023, 09:31:44 +0100, Stefan Botter wrote:
> Hi Eric,
> 
> On Thu, 2023-02-02 at 16:34 +0100, Eric Schirra wrote:
> > Since probably kodi version 20, kodi crashes under Leap 15.4.
> > Is this only happening to me or to others as well?
> 
> At least for my players kodi 20 is working without problem on 15.4. I
> have 4 instances, 2 are NUCs, one is an older Intel Celeron S with
> buildin graphics and the last one is my workstation with NVidia
> graphics.

Kodi runs very well for me, too. All my systems use Intel CPU based
graphics, mixture of DisplayPort, HDMI, and built-in Display with sound
passthru and without, ie. normal sound via PulseAudio. Every instance
also uses a PVR to access TV and Radio from a dreambox.

How does it crash for you? Does it start at all, or does it suddenly
crash when you're e.g. playing some special video? When it is running,
you will find more details in ~/.kodi/temp/kodi.log

HTH, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] PMBS vs OBS - what are the differences wrt/ project configurations?

[Manfred Hollstein]

Hi there,

I've been fighting with the package libheif not building in PMBS during
the past few days. I always fails due to the build directory being
stored in the built programs as an internal RPATH. The package is linked
from openSUSE.org:openSUSE:Factory where no error occurs. I found a
patch for it using "chrpath" to delete such RPATH elements in a program.

Can anyone explain why this is necessary when building in PMBS and it is
not needed when building in OBS? I fail to see a reason...

FWIW, the patch is attached to this e-mail.

TIA, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] A_tw-freshplayerplugin - shouldn't it be disabled/removed?

[Manfred Hollstein]

Hi there,

the package Essentials/A_tw-freshplayerplugin fails since quite some
time. IIUC, it is a plugin for the former Mozilla plugin interface to
render flash apps in Firefox. IIRC, that plugin interface is long gone,
so I'd vote for disabling and removing this particular package.

Any thoughts about this?

Thx, cheers.

l8er
manfred


signature.asc
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman