Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-29 Diskussionsfäden Manfred Hollstein
On Sat, 29 Jan 2022, 19:07:17 +0100, Syds Bearda wrote: > [...] > Is the 15.4 repo available already then? I don’t see it for Broadcom-wl yet. I'll enable builds for 15.4 as soon as PMBS is available again. @Stefan: dunno if you've seen, but PMBS is completely dead! > /Syds Cheers. l8er

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-29 Diskussionsfäden Syds Bearda
On Sat, 29 Jan 2022, at 16:01, Bjørn Lie wrote: >> lø., jan. 29 2022 at kl. 13.21 +0100 +0100 skrev Olaf Hering >> følgende: >>> >>> Three are also two pkg containers for 15.4, to be populated. >>> >>> >>> Olaf >> >> Thank you, I will get to those later today or tomorrow, most likely >>

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-29 Diskussionsfäden Bjørn Lie
lø., jan. 29 2022 at kl. 13.21 +0100 +0100 skrev Olaf Hering følgende: Three are also two pkg containers for 15.4, to be populated. Olaf Thank you, I will get to those later today or tomorrow, most likely today. /Bjørn Packages for 15.4 now in place. I did add baselibs.conf, even

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-29 Diskussionsfäden Bjørn Lie
lø., jan. 29 2022 at kl. 13.21 +0100 +0100 skrev Olaf Hering følgende: Sat, 29 Jan 2022 12:01:11 +0100 Bjørn Lie : Thank you, even if that moved a bit quicker than I expected. Three are also two pkg containers for 15.4, to be populated. Olaf Thank you, I will get to those later

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-29 Diskussionsfäden Olaf Hering
Sat, 29 Jan 2022 12:01:11 +0100 Bjørn Lie : > Thank you, even if that moved a bit quicker than I expected. Three are also two pkg containers for 15.4, to be populated. Olaf pgp7Zp5oSE4wc.pgp Description: Digitale Signatur von OpenPGP ___ Packman

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-29 Diskussionsfäden Bjørn Lie
lø., jan. 29 2022 at kl. 10.27 +0100 +0100 skrev Olaf Hering følgende: Fri, 28 Jan 2022 18:05:08 +0100 Olaf Hering : In the end someone needs to create, submit and maintain the required packages. I moved the codec packages to Essentials, and removed the other packages. This change may

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-29 Diskussionsfäden Olaf Hering
Fri, 28 Jan 2022 18:05:08 +0100 Olaf Hering : > In the end someone needs to create, submit and maintain the required packages. I moved the codec packages to Essentials, and removed the other packages. This change may appear on the mirrors around noon UTC. You may want to announce this new

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Manfred Hollstein
Hi Bjørn, On Fri, 28 Jan 2022, 18:53:09 +0100, Bjørn Lie wrote: > fr., jan. 28 2022 at kl. 18.15 +0100 +0100 skrev Manfred Hollstein > følgende: > > On Fri, 28 Jan 2022, 18:05:08 +0100, Olaf Hering wrote: > > > Fri, 28 Jan 2022 17:52:04 +0100 Bjørn Lie : > > > > > > > Ok so as I said, you

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Bjørn Lie
fr., jan. 28 2022 at kl. 18.15 +0100 +0100 skrev Manfred Hollstein følgende: On Fri, 28 Jan 2022, 18:05:08 +0100, Olaf Hering wrote: Fri, 28 Jan 2022 17:52:04 +0100 Bjørn Lie : > Ok so as I said, you want to do an old style linked package, witch we > now do via _multibuild (see >

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Manfred Hollstein
On Fri, 28 Jan 2022, 18:05:08 +0100, Olaf Hering wrote: > Fri, 28 Jan 2022 17:52:04 +0100 Bjørn Lie : > > > Ok so as I said, you want to do an old style linked package, witch we > > now do via _multibuild (see > > https://build.opensuse.org/package/show/openSUSE:Factory/webkit2gtk3 as > > an

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Olaf Hering
Fri, 28 Jan 2022 17:52:04 +0100 Bjørn Lie : > Ok so as I said, you want to do an old style linked package, witch we > now do via _multibuild (see > https://build.opensuse.org/package/show/openSUSE:Factory/webkit2gtk3 as > an example). > My initial rejection stands, Factory maintainers will

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Bjørn Lie
fr., jan. 28 2022 at kl. 17.12 +0100 +0100 skrev Olaf Hering følgende: Fri, 28 Jan 2022 12:28:57 +0100 Bjørn Lie : As to adding the "naugthy" bits in a separate spec - There is no way I can get those specs into Factory, as they will not be able to build on the main obs at all, since

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Olaf Hering
Fri, 28 Jan 2022 12:28:57 +0100 Bjørn Lie : > As to adding the "naugthy" bits in a separate spec - There is no way I > can get those specs into Factory, as they will not be able to build on > the main obs at all, since the dependencies are not available. > If you mean doing it as a a

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Carlos E. R.
On 28/01/2022 15.46, Bjørn Lie wrote: fr., jan. 28 2022 at kl. 12.43 +0100 +0100 skrev Carlos E. R. følgende: On 28/01/2022 12.28, Bjørn Lie wrote: The way I have it in my home repo here on pmbs, will allow users to just add packman repo, type zypper inr, and bad/ugly-extra packages and their

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Bjørn Lie
fr., jan. 28 2022 at kl. 12.43 +0100 +0100 skrev Carlos E. R. følgende: On 28/01/2022 12.28, Bjørn Lie wrote: The way I have it in my home repo here on pmbs, will allow users to just add packman repo, type zypper inr, and bad/ugly-extra packages and their deps will automagically install.

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Carlos E. R.
On 28/01/2022 12.28, Bjørn Lie wrote: The way I have it in my home repo here on pmbs, will allow users to just add packman repo, type zypper inr, and bad/ugly-extra packages and their deps will automagically install. Why make it harder than it is needed to be? Lets provide endusers with as

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-28 Diskussionsfäden Bjørn Lie
to., jan. 27 2022 at kl. 18.22 +0100 +0100 skrev Olaf Hering følgende: Thu, 27 Jan 2022 11:06:19 +0100 Bjørn Lie : This could however all have been avoided if we switched packman to only build the extra codecs in orig addon. If gstreamer is really modular, remove all conditionals from

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Olaf Hering
Thu, 27 Jan 2022 13:17:54 +0100 Bjørn Lie : > Would it not be a better solution to disable use for build flag instead? This may not be propagated into the Multimedia project. Olaf pgpOiQCoKzYYu.pgp Description: Digitale Signatur von OpenPGP ___

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Olaf Hering
Thu, 27 Jan 2022 11:06:19 +0100 Bjørn Lie : > This could however all have been avoided if we switched packman to only > build the extra codecs in orig addon. If gstreamer is really modular, remove all conditionals from gstreamer-plugins-bad/ugly and split the problematic parts into a separate

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Bjørn Lie
to., jan. 27 2022 at kl. 13.13 +0100 +0100 skrev Bjørn Lie følgende: Now I'm really confused, no changes done over at obs, nor checked into Factory (ref to gst-bad), yet suddenly gstreamer-plugins-bad builds just fine on the pmbs? From what I can tell, no changes done to prjconf for

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Bjørn Lie
Now I'm really confused, no changes done over at obs, nor checked into Factory (ref to gst-bad), yet suddenly gstreamer-plugins-bad builds just fine on the pmbs? From what I can tell, no changes done to prjconf for essential either. Anyone able to shead some light on this? /Bjørn

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Bjørn Lie
to., jan. 27 2022 at kl. 11.42 +0100 +0100 skrev Olaf Hering følgende: Thu, 27 Jan 2022 11:23:47 +0100 Olaf Hering : I only remember a discussion about it, with the outcome "fdk_aac is not compatible with GPL". fdk-aac-free-2.0.0 does not come with a license, so it is unclear if this

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Bjørn Lie
to., jan. 27 2022 at kl. 11.31 +0100 +0100 skrev Bjørn Lie følgende: Well I only used the non pkgconfig for "Packmans" benefit, so fine by me, I'll change it back to using pkgconfig(). /Bjørn But again - the REAL solution is to stop rebuilding the whole gst-plugins-bad/ugly saga, and

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Olaf Hering
Thu, 27 Jan 2022 11:23:47 +0100 Olaf Hering : > I only remember a discussion about it, with the outcome "fdk_aac is not > compatible with GPL". fdk-aac-free-2.0.0 does not come with a license, so it is unclear if this statement even changed. Olaf pgpKpdt0DlwlD.pgp Description: Digitale

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Olaf Hering
Thu, 27 Jan 2022 11:23:47 +0100 Olaf Hering : > As a result ffmpeg does dlopen to use its functionality. I guess the ffmpeg maintainers may need to revisit this part as well. Olaf pgpO5RqTmwAQh.pgp Description: Digitale Signatur von OpenPGP ___

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Bjørn Lie
to., jan. 27 2022 at kl. 11.23 +0100 +0100 skrev Olaf Hering følgende: If an expanded package name is requested, there will be a conflict due to exact %version-%release Requires in the devel package. Hence the established practice to refer to capabilities via pkgconfig() instead of

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Olaf Hering
Thu, 27 Jan 2022 11:20:21 +0100 Bjørn Lie : > %define _without_fdk_aac 1 set in Essential prjconf. I guess this needs to be revisited now. This define is correct due to the license implications. All packages which currently use an expanded package name need to be changed to pkgconfig(), to

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Olaf Hering
Thu, 27 Jan 2022 11:06:19 +0100 Bjørn Lie : > No I added that one due to knowing that you on packman did not want to > build it with full fdk-aac in the past. I only remember a discussion about it, with the outcome "fdk_aac is not compatible with GPL". As a result ffmpeg does dlopen to use

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Bjørn Lie
to., jan. 27 2022 at kl. 11.06 +0100 +0100 skrev Bjørn Lie følgende: No I added that one due to knowing that you on packman did not want to build it with full fdk-aac in the past. Hence I did it this way, so that it would be built with the altered sources we have in main obs, and not the

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Bjørn Lie
to., jan. 27 2022 at kl. 10.42 +0100 +0100 skrev Manfred Hollstein følgende: On Thu, 27 Jan 2022, 10:26:28 +0100, Olaf Hering wrote: Thu, 27 Jan 2022 10:19:05 +0100 Manfred Hollstein mailto:manfre...@gmx.net>>: > Can someone please branch it to Staging and Essentials please? This will

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Manfred Hollstein
On Thu, 27 Jan 2022, 10:26:28 +0100, Olaf Hering wrote: > Thu, 27 Jan 2022 10:19:05 +0100 Manfred Hollstein : > > > Can someone please branch it to Staging and Essentials please? > > This will lead to a conflict because both provide the same API, and hopefully > even the same ABI due to

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Olaf Hering
Thu, 27 Jan 2022 10:19:05 +0100 Manfred Hollstein : > Can someone please branch it to Staging and Essentials please? This will lead to a conflict because both provide the same API, and hopefully even the same ABI due to identical SONAME. Does fdk-aac provide something which is not provided by

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Manfred Hollstein
On Thu, 27 Jan 2022, 10:13:08 +0100, Manfred Hollstein wrote: > On Thu, 27 Jan 2022, 10:00:42 +0100, Olaf Hering wrote: > > Thu, 27 Jan 2022 09:48:38 +0100 Manfred Hollstein : > > > > > @Olaf, would you mind to give it a try? > > > > I kicked the scheduler. > > Thanks! > > > But as long as

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Manfred Hollstein
On Thu, 27 Jan 2022, 10:00:42 +0100, Olaf Hering wrote: > Thu, 27 Jan 2022 09:48:38 +0100 Manfred Hollstein : > > > @Olaf, would you mind to give it a try? > > I kicked the scheduler. Thanks! > But as long as openSUSE.org:openSUSE:Factory/gstreamer-plugins-bad remains > broken, the package

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Olaf Hering
Thu, 27 Jan 2022 09:48:38 +0100 Manfred Hollstein : > @Olaf, would you mind to give it a try? I kicked the scheduler. But as long as openSUSE.org:openSUSE:Factory/gstreamer-plugins-bad remains broken, the package will not start to build. Olaf pgps6T2pE32qr.pgp Description: Digitale Signatur

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Andrei Dziahel
In OBS staging, that's what I meant by "upstream" On Thu, Jan 27, 2022, 09:48 Manfred Hollstein wrote: > On Thu, 27 Jan 2022, 09:08:51 +0100, Andrei Dziahel wrote: > > Ya, experiencing this for couple of days now too. The upstream seems to > fix the > > issue and the package is in the staging

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Manfred Hollstein
On Thu, 27 Jan 2022, 09:08:51 +0100, Andrei Dziahel wrote: > Ya, experiencing this for couple of days now too. The upstream seems to fix > the > issue and the package is in the staging now. The package in Staging is a link to the one in Essentials and there are no source changes at all:

Re: [packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-27 Diskussionsfäden Andrei Dziahel
Ya, experiencing this for couple of days now too. The upstream seems to fix the issue and the package is in the staging now. On Wed, Jan 26, 2022, 14:44 Manfred Hollstein wrote: > Hi there, > > trying to "zypper dup" atm results in various issues: > > 15 Problems: > Problem: problem with

[packman] Problems with gstreamer-plugins-bad and related packages from Packman on TW

2022-01-26 Diskussionsfäden Manfred Hollstein
Hi there, trying to "zypper dup" atm results in various issues: 15 Problems: Problem: problem with the installed gstreamer-plugins-bad-1.18.5-6.2.x86_64 Problem: problem with the installed gstreamer-plugins-bad-lang-1.18.5-6.2.noarch Problem: problem with the installed