Re: [packman] build error

2024-03-22 Diskussionsfäden Dave Plater
A duplicate dav1d package in Packman isn't necessary.
Regards
Dave

On Fri, Mar 22, 2024 at 11:40 AM Natasha Ament 
wrote:

> sorry for the noise, they do not build. only unchanged packages seem
> to 'build'  as they are unchanged
>
> Op vr 22 mrt 2024 om 10:38 schreef Natasha Ament  >:
> >
> > The packages seem to build now. problem resolved for now ;-)
> >
> > Op vr 22 mrt 2024 om 08:52 schreef Dave Plater :
> > >
> > > This package is already in the openSUSE build service:
> > > https://build.opensuse.org/package/show/multimedia:libs/dav1d
> > >
> > > On Fri, Mar 22, 2024 at 8:31 AM Natasha Ament <
> stacheldrah...@gmail.com> wrote:
> > >>
> > >> Hi,
> > >>
> > >> I'm trying to build some packages that I got from
> > >> src.fedoraproject.org and build them to Tumbleweed. Local build works
> > >> fine. As soon as I commit it and let it build on pmbs it fails when
> > >> starting the qemu instance.
> > >>
> > >> I would immensely appreciate it if someone could nudge me in the right
> > >> direction. The link to the example is
> > >> https://pmbs.links2linux.org/package/show/home:stacheldrahtje/daf
> > >>
> > >> Thanks in advance.
> > >>
> > >> Kind regards,
> > >>
> > >> Natasha
> > >>
> > >> ___
> > >> Packman mailing list
> > >> Packman@links2linux.de
> > >> https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] build error

2024-03-22 Diskussionsfäden Dave Plater
This package is already in the openSUSE build service:
https://build.opensuse.org/package/show/multimedia:libs/dav1d

On Fri, Mar 22, 2024 at 8:31 AM Natasha Ament 
wrote:

> Hi,
>
> I'm trying to build some packages that I got from
> src.fedoraproject.org and build them to Tumbleweed. Local build works
> fine. As soon as I commit it and let it build on pmbs it fails when
> starting the qemu instance.
>
> I would immensely appreciate it if someone could nudge me in the right
> direction. The link to the example is
> https://pmbs.links2linux.org/package/show/home:stacheldrahtje/daf
>
> Thanks in advance.
>
> Kind regards,
>
> Natasha
>
> ___
> Packman mailing list
> Packman@links2linux.de
> https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
___
Packman mailing list
Packman@links2linux.de
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Streamtuner2 paket bei packman für Opensuse 15.5 Leap

2023-07-17 Diskussionsfäden Dave Plater
On 7/15/23, Jürgen Falbrede  wrote:
> Moin aus dem Norden,
>
> als User ohne tiefergehende Linux Kentnisse weiß ich mir nicht anders zu
> helfen als Ihnen diese Mail zu schreiben.
>
> Es geht um Opensuse Leap 15.5
>
> Im Packman Repo für Opensuse Leap 15.5
>
> URL: https://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Leap_15.5/
>
> ist das folgende streamtuner2 Paket zu finden dessen Abhängigkeiten per
> Yast2 nicht aufzulösen sind.
>
> Ich habe mit meinem wenigen Wissen, unter anderem auch durch den
> erfolglosen Versuch des Einbindens anderer Repos mit Paketen für Python
> gtk, es nicht hinbekommen die Abhängigkeiten zu erfüllen.
>
> Dieses Paket im Packman Repo scheint python 2.7 zu erfordern. Opensuse
> Leap 15.5 enthält aber wohl python 3 in den Standardrepos soweit ich das
> nachvollziehen kann.
>
>  YaST2 conflicts list - generated 2023-07-15 16:18:09  nichts
> stellt 'python-gtk' bereit, das vom zu installierenden
> streamtuner2-2.2.0-150500.9.pm.2.noarch benötigt wird [ ]
> streamtuner2-2.2.0-150500.9.pm.2.noarch durch Ignorieren einiger
> Abhängigkeiten brechen [ ] streamtuner2-2.2.0-150500.9.pm.2.noarch nicht
> installieren  YaST2 conflicts list END ###
>
> Vielleicht können Sie diese Info weiterleiten damit ein für Leap 15.5
> taugliches Paket ins Repo kommt.
>
> Im voraus vielen Dank an alle für Ihre Unterstützung.
>
> J. Falbrede
> ___
> Packman mailing list
> Packman@links2linux.de
> https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Aus einem noch zu ermittelnden Grund ist das Paket „python-gtk“ in
Leap:15.5 vorhanden, wurde aber möglicherweise nie erstellt, weil
SUSE:SLE-15-SP2:GA/python-gtk, von dem das Paket geerbt wird, einen
Fehler aufweist.
Der einzige Rat, den ich Ihnen in der Zwischenzeit geben kann, da es
Risiken birgt, ist die Installation per Yast One Click Install von:
openSUSE-Backports für SLE 15 SP3
Dies ist das einzige verfügbare Paket.

Mit freundlichen Grüßen
Dave
PS. Ich bin gebürtiger Engländer und alle Grammatikfehler werden durch
Google Translate verursacht

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

Re: [packman] HandBrake 1.6.0 - Experiences?

2023-07-12 Diskussionsfäden Dave Plater
On 7/12/23, Manfred Hollstein  wrote:
> 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
>

Hi, I've just updated transcode and can vaguely remember having to
roll back transcode for handbrake to work again.

Regards
Dave

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

Re: [packman] How can I submit my package to the Multimedia project?

2023-06-24 Diskussionsfäden Dave Plater
On 6/23/23, Kaito Udagawa  wrote:
> Hi there,
>
> I have created an obs-studio plugin package for which I am a maintainer.
> https://pmbs.links2linux.org/package/show/home:umireon/obs-backgroundremoval
>
> Is there any way to submit the package I have created for the
> Multimedia project and publish my package?
>
> Best,
>

The easiest way is via the build service web ui, click on submit
package and fill in the details.
Then you should announce the submit request number on this list.

Best regards
Dave

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

2023-05-21 Diskussionsfäden Dave Plater
On 5/20/23, 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!
>
>> Enjoy the rest of your weekend!
>
> Same to you!
>
>> Kind regards,
>> Steven.
>
> Cheers.
>
> l8er
> manfred
>
Hi Manfred, if you want to require the library that the kodi package
was built with you can use a macro like %define  libfmtversion
%(pkg-config --modversion libfmt) replacing "libfmt" with the correct
pkgconfig name eg. "fmt"

Regards
Dave

___
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?

2023-02-03 Diskussionsfäden Dave Plater
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
>
> Cheers.
>
> l8er
> manfred
>

Hope the maintainer doesn't mind, I've also come to the conclusion
that chrpath is the solution. I've accepted your request.
Dave

___
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?

2023-02-03 Diskussionsfäden Dave Plater
On 2/3/23, Manfred Hollstein  wrote:
> 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
>

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?

Thanks
Dave

___
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?

2023-02-03 Diskussionsfäden Dave Plater
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?
Regards
Dave

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

Re: [packman] obs-studio erroneously provides libvulkan.so.1

2022-11-08 Diskussionsfäden Dave Plater
On 11/9/22, Dave Plater  wrote:
> On 11/8/22, Giacomo Comes  wrote:
>> On Tue, Nov 08, 2022 at 08:58:17PM +0100, Hans-Peter Jansen wrote:
>>> Hi,
>>> looking for advise on how to deal with an unpleasant situation:
>>> Look at the handbrake TW build right now:have choice for
>>> libvulkan.so.1()(64bit) needed by libavutil56_70: libvulkan1 obs-studio,
>>> have choice for libvulkan.so.1()(64bit) needed by libavfilter7_110:
>>> libvulkan1 obs-studio
>>> and indeed from the obs-studio build:
>>> [  542s] -- Installing:
>>> /home/abuild/rpmbuild/BUILDROOT/obs-studio-28.1.1-0.x86_64/usr/lib64/obs-plugins/libvulkan.so.1
>>> [  556s] Processing files: obs-studio-28.1.1-0.x86_64[  557s] Provides:
>>> application() application(com.obsproject.Studio.desktop)
>>> libEGL.so()(64bit) libGLESv2.so()(64bit) libcef.so()(64bit)
>>> libobs-frontend-api.so.0()(64bit) libobs-opengl.so.1()(64bit)
>>> libobs-scripting.so.1()(64bit) libobs.so.0()(64bit)
>>> libobsglad.so.1()(64bit) libvk_swiftshader.so()(64bit)
>>> libvulkan.so.1()(64bit) metainfo()
>>> metainfo(com.obsproject.Studio.appdata.xml) obs-studio = 28.1.1-0
>>> obs-studio(x86-64) = 28.1.1-0
>>> Due to the automatic dependency processing, obs-studio now provides a
>>> libvulkan.so.1 plugin, which in turn provides libvulkan.so.1()(64bit) on
>>> the package, which is kind of silly of course. Sure, this could be
>>> solved
>>> by within prjconf with:
>>> Prefer: libvulkan1
>>> but I would rather like to remove this provides from obs-studio build
>>> specifically. Any idea, how to achieve that?
>>
>> Add in the spec file something like:
>> %define __provides_exclude ^(libvulcan\\.so.*|libEGL\\.so.*)$
>>
>> Check the documantation here:
>> https://docs.fedoraproject.org/en-US/packaging-guidelines/AutoProvidesAndRequiresFiltering/
>>
>> Regards,
>> Giacomo
>>
>>> Cheers,Pete--Life without chameleons is possible, but pointless.
>>>
>>>

 Another workaround is #!BuildIgnore: the wrong package in the specfile

Regards
Dave

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

Re: [packman] qmmp 2.1.2 missing plugins

2022-10-28 Diskussionsfäden Dave Plater
On 10/25/22, Frank Steiner  wrote:
> Hi,
>
> just installed qmmp 2.1.2 on our SLED 15 SP4 systems, but it doesn't
> play any mp3 files. I filed a bug at qmmp and they said it looks like
> most plugins are missing and I should contact the packager.
>
> Indeed, comparing what's packaged in 1.5.1 for 15.3 and 2.1.2 for 15.4
> it seems the important plugins are missing:
>
> artemis [20:29] download 4954) rpm -ql
> libqmmp-plugins-1.5.1-pm153.6.5.x86_64 |grep /Input
> /usr/lib64/qmmp-1.5/Input
> /usr/lib64/qmmp-1.5/Input/libaac.so
> /usr/lib64/qmmp-1.5/Input/libcdaudio.so
> /usr/lib64/qmmp-1.5/Input/libcue.so
> /usr/lib64/qmmp-1.5/Input/libffmpeg.so
> /usr/lib64/qmmp-1.5/Input/libflac.so
> /usr/lib64/qmmp-1.5/Input/libgme.so
> /usr/lib64/qmmp-1.5/Input/libmodplug.so
> /usr/lib64/qmmp-1.5/Input/libmpeg.so
> /usr/lib64/qmmp-1.5/Input/libopus.so
> /usr/lib64/qmmp-1.5/Input/libsid.so
> /usr/lib64/qmmp-1.5/Input/libsndfile.so
> /usr/lib64/qmmp-1.5/Input/libvorbis.so
> /usr/lib64/qmmp-1.5/Input/libwavpack.so
>
>
> euler [20:30] tmp 4997) rpm -ql libqmmp-plugins-2.1.2-pm154.6.1.x86_64 |grep
> /Input
> /usr/lib64/qmmp-2.1/Input
> /usr/lib64/qmmp-2.1/Input/libcdaudio.so
> /usr/lib64/qmmp-2.1/Input/libcue.so
> /usr/lib64/qmmp-2.1/Input/libgme.so
> /usr/lib64/qmmp-2.1/Input/libsid.so
> /usr/lib64/qmmp-2.1/Input/libsndfile.so
> /usr/lib64/qmmp-2.1/Input/libwavpack.so
> /usr/lib64/qmmp-2.1/Input/libwildmidi.so
> /usr/lib64/qmmp-2.1/Input/libxmp.so
>
> http://packman.links2linux.de/package/qmmp doesn't show any
> further plugin packages. Have these plugins been forgotten
> to configure?
>
> Thanks a lot!
>
> cu,
> Frank
>

The problem is now solved, qmmp didn't need to be changed only an
updated taglib had to be built in Packman to satisfy the need in qmmp.
I've just installed libqmmp-plugins-2.1.2-pm154.6.2.x86_64.rpm from
Packman and qmmp plays mp3's again.
Regards
Dave

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

[packman] Request 5620 taglib needed by qmmp

2022-10-28 Diskussionsfäden Dave Plater
Hi, I've submitted a multimedia:apps link to taglib to Multimedia
needed for the Leap:15.4 build of qmmp to play mpeg and flac tracks.

Regards
Dave

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

Re: [packman] qmmp 2.1.2 missing plugins

2022-10-27 Diskussionsfäden Dave Plater
On 10/26/22, Frank Steiner  wrote:
> Thanks for caring! I saw your post on the sourceforge ticket.
> In the meantime I will downgrade to qmmp as you proposed!
>
> Thanks!
>

The fix is on the way to openSUSE:Factory so eventually the Packman
package will work.

Regards
Dave

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

Re: [packman] qmmp 2.1.2 missing plugins

2022-10-27 Diskussionsfäden Dave Plater
On 10/25/22, Frank Steiner  wrote:
> Hi,
>
> just installed qmmp 2.1.2 on our SLED 15 SP4 systems, but it doesn't
> play any mp3 files. I filed a bug at qmmp and they said it looks like
> most plugins are missing and I should contact the packager.
>
> Indeed, comparing what's packaged in 1.5.1 for 15.3 and 2.1.2 for 15.4
> it seems the important plugins are missing:
>
> artemis [20:29] download 4954) rpm -ql
> libqmmp-plugins-1.5.1-pm153.6.5.x86_64 |grep /Input
> /usr/lib64/qmmp-1.5/Input
> /usr/lib64/qmmp-1.5/Input/libaac.so
> /usr/lib64/qmmp-1.5/Input/libcdaudio.so
> /usr/lib64/qmmp-1.5/Input/libcue.so
> /usr/lib64/qmmp-1.5/Input/libffmpeg.so
> /usr/lib64/qmmp-1.5/Input/libflac.so
> /usr/lib64/qmmp-1.5/Input/libgme.so
> /usr/lib64/qmmp-1.5/Input/libmodplug.so
> /usr/lib64/qmmp-1.5/Input/libmpeg.so
> /usr/lib64/qmmp-1.5/Input/libopus.so
> /usr/lib64/qmmp-1.5/Input/libsid.so
> /usr/lib64/qmmp-1.5/Input/libsndfile.so
> /usr/lib64/qmmp-1.5/Input/libvorbis.so
> /usr/lib64/qmmp-1.5/Input/libwavpack.so
>
>
> euler [20:30] tmp 4997) rpm -ql libqmmp-plugins-2.1.2-pm154.6.1.x86_64 |grep
> /Input
> /usr/lib64/qmmp-2.1/Input
> /usr/lib64/qmmp-2.1/Input/libcdaudio.so
> /usr/lib64/qmmp-2.1/Input/libcue.so
> /usr/lib64/qmmp-2.1/Input/libgme.so
> /usr/lib64/qmmp-2.1/Input/libsid.so
> /usr/lib64/qmmp-2.1/Input/libsndfile.so
> /usr/lib64/qmmp-2.1/Input/libwavpack.so
> /usr/lib64/qmmp-2.1/Input/libwildmidi.so
> /usr/lib64/qmmp-2.1/Input/libxmp.so
>
> http://packman.links2linux.de/package/qmmp doesn't show any
> further plugin packages. Have these plugins been forgotten
> to configure?
>
> Thanks a lot!
>
> cu,
> Frank
>


I've managed to hack qmmp to build with full mpeg and ffmpeg support
at the expense of projectm and mplayer support, so worse case a link
to Factory's taglib may be needed.

Regards

Dave

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

Re: [packman] qmmp 2.1.2 missing plugins

2022-10-26 Diskussionsfäden Dave Plater
On 10/26/22, Dave Plater  wrote:
> On 10/26/22, Dave Plater  wrote:
>> On 10/25/22, Frank Steiner  wrote:
>>> Hi,
>>>
>>> just installed qmmp 2.1.2 on our SLED 15 SP4 systems, but it doesn't
>>> play any mp3 files. I filed a bug at qmmp and they said it looks like
>>> most plugins are missing and I should contact the packager.
>>>
>>> Indeed, comparing what's packaged in 1.5.1 for 15.3 and 2.1.2 for 15.4
>>> it seems the important plugins are missing:
>>>
>>> artemis [20:29] download 4954) rpm -ql
>>> libqmmp-plugins-1.5.1-pm153.6.5.x86_64 |grep /Input
>>> /usr/lib64/qmmp-1.5/Input
>>> /usr/lib64/qmmp-1.5/Input/libaac.so
>>> /usr/lib64/qmmp-1.5/Input/libcdaudio.so
>>> /usr/lib64/qmmp-1.5/Input/libcue.so
>>> /usr/lib64/qmmp-1.5/Input/libffmpeg.so
>>> /usr/lib64/qmmp-1.5/Input/libflac.so
>>> /usr/lib64/qmmp-1.5/Input/libgme.so
>>> /usr/lib64/qmmp-1.5/Input/libmodplug.so
>>> /usr/lib64/qmmp-1.5/Input/libmpeg.so
>>> /usr/lib64/qmmp-1.5/Input/libopus.so
>>> /usr/lib64/qmmp-1.5/Input/libsid.so
>>> /usr/lib64/qmmp-1.5/Input/libsndfile.so
>>> /usr/lib64/qmmp-1.5/Input/libvorbis.so
>>> /usr/lib64/qmmp-1.5/Input/libwavpack.so
>>>
>>>
>>> euler [20:30] tmp 4997) rpm -ql libqmmp-plugins-2.1.2-pm154.6.1.x86_64
>>> |grep
>>> /Input
>>> /usr/lib64/qmmp-2.1/Input
>>> /usr/lib64/qmmp-2.1/Input/libcdaudio.so
>>> /usr/lib64/qmmp-2.1/Input/libcue.so
>>> /usr/lib64/qmmp-2.1/Input/libgme.so
>>> /usr/lib64/qmmp-2.1/Input/libsid.so
>>> /usr/lib64/qmmp-2.1/Input/libsndfile.so
>>> /usr/lib64/qmmp-2.1/Input/libwavpack.so
>>> /usr/lib64/qmmp-2.1/Input/libwildmidi.so
>>> /usr/lib64/qmmp-2.1/Input/libxmp.so
>>>
>>> http://packman.links2linux.de/package/qmmp doesn't show any
>>> further plugin packages. Have these plugins been forgotten
>>> to configure?
>>>
>>> Thanks a lot!
>>>
>>> cu,
>>> Frank
>>>
>>> --
>>> Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
>>> Lehrstuhl f. BioinformatikMail:
>>> http://www.bio.ifi.lmu.de/~steiner/m/
>>> LMU, Amalienstr. 17   Phone: +49 89 2180-4049
>>> 80333 Muenchen, Germany   Fax:   +49 89 2180-99-4049
>>> * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat.
>>> *
>>>
>>
>>
>> The  qmmp-plugin-pack is failing to build for a reason related to the
>> modplug codec. This codec only exists for sentimental reasons so
>> perhaps one of the multimedia maintainers can disable it.
>>
>> Regards
>> Dave
>>
> Version 1.5.1 exists in the main (Leap:15.4) repository and there
> isn't a patent problem with mp3s anymore. You can try downgrading qmmp
> to that.
>
> Dave
>
on further investigation the problem appears to stem from the official
factory build of qmmp, I'll see if I can fix it.

Regards
Dave

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

Re: [packman] qmmp 2.1.2 missing plugins

2022-10-26 Diskussionsfäden Dave Plater
On 10/26/22, Dave Plater  wrote:
> On 10/25/22, Frank Steiner  wrote:
>> Hi,
>>
>> just installed qmmp 2.1.2 on our SLED 15 SP4 systems, but it doesn't
>> play any mp3 files. I filed a bug at qmmp and they said it looks like
>> most plugins are missing and I should contact the packager.
>>
>> Indeed, comparing what's packaged in 1.5.1 for 15.3 and 2.1.2 for 15.4
>> it seems the important plugins are missing:
>>
>> artemis [20:29] download 4954) rpm -ql
>> libqmmp-plugins-1.5.1-pm153.6.5.x86_64 |grep /Input
>> /usr/lib64/qmmp-1.5/Input
>> /usr/lib64/qmmp-1.5/Input/libaac.so
>> /usr/lib64/qmmp-1.5/Input/libcdaudio.so
>> /usr/lib64/qmmp-1.5/Input/libcue.so
>> /usr/lib64/qmmp-1.5/Input/libffmpeg.so
>> /usr/lib64/qmmp-1.5/Input/libflac.so
>> /usr/lib64/qmmp-1.5/Input/libgme.so
>> /usr/lib64/qmmp-1.5/Input/libmodplug.so
>> /usr/lib64/qmmp-1.5/Input/libmpeg.so
>> /usr/lib64/qmmp-1.5/Input/libopus.so
>> /usr/lib64/qmmp-1.5/Input/libsid.so
>> /usr/lib64/qmmp-1.5/Input/libsndfile.so
>> /usr/lib64/qmmp-1.5/Input/libvorbis.so
>> /usr/lib64/qmmp-1.5/Input/libwavpack.so
>>
>>
>> euler [20:30] tmp 4997) rpm -ql libqmmp-plugins-2.1.2-pm154.6.1.x86_64
>> |grep
>> /Input
>> /usr/lib64/qmmp-2.1/Input
>> /usr/lib64/qmmp-2.1/Input/libcdaudio.so
>> /usr/lib64/qmmp-2.1/Input/libcue.so
>> /usr/lib64/qmmp-2.1/Input/libgme.so
>> /usr/lib64/qmmp-2.1/Input/libsid.so
>> /usr/lib64/qmmp-2.1/Input/libsndfile.so
>> /usr/lib64/qmmp-2.1/Input/libwavpack.so
>> /usr/lib64/qmmp-2.1/Input/libwildmidi.so
>> /usr/lib64/qmmp-2.1/Input/libxmp.so
>>
>> http://packman.links2linux.de/package/qmmp doesn't show any
>> further plugin packages. Have these plugins been forgotten
>> to configure?
>>
>> Thanks a lot!
>>
>> cu,
>> Frank
>>
>> --
>> Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
>> Lehrstuhl f. BioinformatikMail: http://www.bio.ifi.lmu.de/~steiner/m/
>> LMU, Amalienstr. 17   Phone: +49 89 2180-4049
>> 80333 Muenchen, Germany   Fax:   +49 89 2180-99-4049
>> * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
>>
>
>
> The  qmmp-plugin-pack is failing to build for a reason related to the
> modplug codec. This codec only exists for sentimental reasons so
> perhaps one of the multimedia maintainers can disable it.
>
> Regards
> Dave
>
Version 1.5.1 exists in the main (Leap:15.4) repository and there
isn't a patent problem with mp3s anymore. You can try downgrading qmmp
to that.

Dave

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

Re: [packman] qmmp 2.1.2 missing plugins

2022-10-26 Diskussionsfäden Dave Plater
On 10/25/22, Frank Steiner  wrote:
> Hi,
>
> just installed qmmp 2.1.2 on our SLED 15 SP4 systems, but it doesn't
> play any mp3 files. I filed a bug at qmmp and they said it looks like
> most plugins are missing and I should contact the packager.
>
> Indeed, comparing what's packaged in 1.5.1 for 15.3 and 2.1.2 for 15.4
> it seems the important plugins are missing:
>
> artemis [20:29] download 4954) rpm -ql
> libqmmp-plugins-1.5.1-pm153.6.5.x86_64 |grep /Input
> /usr/lib64/qmmp-1.5/Input
> /usr/lib64/qmmp-1.5/Input/libaac.so
> /usr/lib64/qmmp-1.5/Input/libcdaudio.so
> /usr/lib64/qmmp-1.5/Input/libcue.so
> /usr/lib64/qmmp-1.5/Input/libffmpeg.so
> /usr/lib64/qmmp-1.5/Input/libflac.so
> /usr/lib64/qmmp-1.5/Input/libgme.so
> /usr/lib64/qmmp-1.5/Input/libmodplug.so
> /usr/lib64/qmmp-1.5/Input/libmpeg.so
> /usr/lib64/qmmp-1.5/Input/libopus.so
> /usr/lib64/qmmp-1.5/Input/libsid.so
> /usr/lib64/qmmp-1.5/Input/libsndfile.so
> /usr/lib64/qmmp-1.5/Input/libvorbis.so
> /usr/lib64/qmmp-1.5/Input/libwavpack.so
>
>
> euler [20:30] tmp 4997) rpm -ql libqmmp-plugins-2.1.2-pm154.6.1.x86_64 |grep
> /Input
> /usr/lib64/qmmp-2.1/Input
> /usr/lib64/qmmp-2.1/Input/libcdaudio.so
> /usr/lib64/qmmp-2.1/Input/libcue.so
> /usr/lib64/qmmp-2.1/Input/libgme.so
> /usr/lib64/qmmp-2.1/Input/libsid.so
> /usr/lib64/qmmp-2.1/Input/libsndfile.so
> /usr/lib64/qmmp-2.1/Input/libwavpack.so
> /usr/lib64/qmmp-2.1/Input/libwildmidi.so
> /usr/lib64/qmmp-2.1/Input/libxmp.so
>
> http://packman.links2linux.de/package/qmmp doesn't show any
> further plugin packages. Have these plugins been forgotten
> to configure?
>
> Thanks a lot!
>
> cu,
> Frank
>
> --
> Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
> Lehrstuhl f. BioinformatikMail: http://www.bio.ifi.lmu.de/~steiner/m/
> LMU, Amalienstr. 17   Phone: +49 89 2180-4049
> 80333 Muenchen, Germany   Fax:   +49 89 2180-99-4049
> * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
>


The  qmmp-plugin-pack is failing to build for a reason related to the
modplug codec. This codec only exists for sentimental reasons so
perhaps one of the multimedia maintainers can disable it.

Regards
Dave

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

Re: [packman] A_15.4-gstreamer-plugins-libav

2022-06-12 Diskussionsfäden Dave Plater
On 6/12/22, Luigi Baldoni  wrote:
> Sent: Sunday, June 12, 2022 at 8:29 AM
> From: "Dave Plater" 
>>
>> On 6/11/22, Luigi Baldoni  wrote:
>> >   Hello fellow packmen,
>> > can you foresee anything bad by preferring ffmpeg-4 libraries for Leap
>> > 15.4
>> > in the Essentials
>> > project config? Its immediate dependencies don't seem to break, at
>> > least
>> > build-wise.
>> >
>> > It's the only way I could think of to fix the package above or is there
>> > anything more specific?
>> >
>> > Regards
>> >
>>
>> gstreamer-plugins-libav doesn't have to be in Packman it automatically
>> uses whichever ffmpeg libs that are installed on the system.
>> I stopped using the Packman package years ago.
>
> Excellent news. So the link can safely be deleted?
>
> Regards
>
>
Yes, the only libs that you need to install from Packman are ffmpeg's
libav libs.

Regards
Dave

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

Re: [packman] A_15.4-gstreamer-plugins-libav

2022-06-12 Diskussionsfäden Dave Plater
On 6/11/22, Luigi Baldoni  wrote:
>   Hello fellow packmen,
> can you foresee anything bad by preferring ffmpeg-4 libraries for Leap 15.4
> in the Essentials
> project config? Its immediate dependencies don't seem to break, at least
> build-wise.
>
> It's the only way I could think of to fix the package above or is there
> anything more specific?
>
> Regards
>

gstreamer-plugins-libav doesn't have to be in Packman it automatically
uses whichever ffmpeg libs that are installed on the system.
I stopped using the Packman package years ago.

Dave

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

Re: [packman] [PM] aMule 2.3.3.20210426.6d4c03b00-pm153.1.3 (openSUSE_Leap 15.3/x86_64)

2021-10-06 Diskussionsfäden Dave Plater
It should all happen automatically, your package manager yast or
zypper should take care of installing the dependencies. Leap:15.3
requires:
libwx_baseu-suse-nostl.so.3.0.5()(64bit),
libwx_baseu_net-suse-nostl.so.3.0.5()(64bit),
libwx_gtk2u_adv-suse-nostl.so.3.0.5()(64bit) and
libwx_gtk2u_core-suse-nostl.so.3.0.5()(64bit) and all are indicated as
present by the build service's detailed information page.
You shouldn't have to install anything extra and with wxWidgets if the
libraries don't match the ones that the package (aMule in this case)
then it will fail to start with an error. It may be better to
uninstall aMule using zypper rm -u aMule and then reinstall it. Also
make sure your repositories are all pointing to Leap:15.3 and not
another distribution version.

Regards
Dave

On 10/6/21, Maciej Pilichowski  wrote:
> Hello Dave,
>
>> On Wednesday 06 October 2021 15:03:34 Dave Plater wrote:
>
>   Many thanks for the answer. I am still confused a bit, since the new
> amule package dependency seems to be hitting file (library) instead
> of other package (as usual).
>
>> wxWidgets-3_0-nostl libraries, of which libwx_baseu-suse-nostl is
>> one, come from openSUSE and must be available for aMule to build It
>> comes from the main openSUSE:Leap:15.3 repository.
>
> I have it enabled of course but all I see is:
> wxWidgets-3_0-nostl-devel
> package (there is no no-devel one), and another possible relevant
>
> libwx_baseu-suse-nostl3
> containing file /usr/lib64/libwx_baseu-suse-nostl.so.3
>
> And I have it already installed, yet amule package states its
> dependency is not fullfiled because of missing
> libwx_baseu-suse-nostl.so.3.0.5()(64bit)
>
> Thus I wonder what should I install more?
>
> Kind regards,
> --
> http://przypadkopis.wordpress.com/
>

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

Re: [packman] [PM] aMule 2.3.3.20210426.6d4c03b00-pm153.1.3 (openSUSE_Leap 15.3/x86_64)

2021-10-06 Diskussionsfäden Dave Plater
wxWidgets-3_0-nostl libraries, of which libwx_baseu-suse-nostl is one,
come from openSUSE and must be available for aMule to build It comes
from the main openSUSE:Leap:15.3 repository.
The old Leap:42.1 package was enabled for audacity before the main
distribution had the libraries.
It's possible that a package rebuild caused your problem so a refresh
of your Leap:15.3 repository will solve your problem

Best regards
Dave

On 10/4/21, Maciej Pilichowski  wrote:
> Hello,
>
>   Sorry to bother you via email but I don't see any ticket/issue
> system on the site.
>
>   I notice there is new aMule package, however on my openSUSE Leap
> 15.3 it requires:
> libwx_baseu-suse-nostl.so.3.0.5()(64bit)
>
>   and there in no such package that provides such dependency. I found:
> http://packman.links2linux.org/package/wxWidgets-3_0-nostl
>
>   but it the last system it is for is Leap 42.1.
>
>   I would be grateful for advice how I should meet this dependency.
>
> Kind regards,
> --
> http://przypadkopis.wordpress.com/
>
> ___
> Packman mailing list
> Packman@links2linux.de
> https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

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

Re: [packman] Broken ffmpeg-4

2021-04-23 Diskussionsfäden Dave Plater
Seems like ffmpeg-4 is finally in Tumbleweed and you can perform a
zypper dup --no-allow-vendor-change without conflicts, if you have
already allowed openSUSE crippled ffmpeg-4 libs you need to replace
them with packman ones.

Regards
Dave

On 4/21/21, Dave Plater  wrote:
> See my email ffmpeg out of sync.
> If you did a Tumbleweed distribution upgrade it will have replaced
> your ffmpeg libs with restricted ones.
>
> Dave
>
> On 4/21/21, Eduardo Benítez  wrote:
>> Hey ffmpeg is broken once again, I can't play any mp4 video.
>> [image: Screenshot_20210421_011409.png]
>> ___
>> Packman mailing list
>> Packman@links2linux.de
>> https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

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

Re: [packman] Broken ffmpeg-4

2021-04-21 Diskussionsfäden Dave Plater
See my email ffmpeg out of sync.
If you did a Tumbleweed distribution upgrade it will have replaced
your ffmpeg libs with restricted ones.

Dave

On 4/21/21, Eduardo Benítez  wrote:
> Hey ffmpeg is broken once again, I can't play any mp4 video.
> [image: Screenshot_20210421_011409.png]
> ___
> Packman mailing list
> Packman@links2linux.de
> https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

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

[packman] ffmpeg out of sync with Tumbleweed

2021-04-21 Diskussionsfäden Dave Plater
It looks like there needs to be an A_Tumbleweed_ffmpeg-4 package.
Since last week there has been a lot of activity in
multimedia:libs/ffmpeg-4 and this has resulted in
"zypper dup --no-allow-vendor-change" conflicts. The only way to avoid
being forced to change vendor of ffmpeg-4 libs to openSUSE is to keep
"obsolete package" which vlc and friends are built against, this
wouldn't happen if the package was linked to Factory. Of course when
ffmpeg-4 is finally accepted this problem will go away after all the
affected packages rebuild.

Best Regards
Dave

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

Re: [packman] Package availability, was: Re: signing seems to hang somewhere

2021-02-27 Diskussionsfäden Dave Plater
On 2/27/21, Stefan Botter  wrote:
> Hi all,
>
> as I have feared, there are problems with publishing of packages.
>
> Am Mittwoch, den 24.02.2021, 16:25 +0100 schrieb Stefan Botter:
> :
>> Yes, I can confirm this problem. It is connected with the expired GPG
>> key - and probably with something I fscked meanwhile.
>>
>> I have been trying for a while now, and could be the Multimedia
>> project
>> to sign. There might be a problem with
>> - other projects/repositories, and
>> - publishing to the packman server
>
> Exactly that happened.
> This is caused by the unique way we publish built packages to the
> repositories, which are synced to the mirrors:
> PMBS builds packages (the regular OBS way) and signs them with the
> respective repository key. Once all packages for a repo are built, the
> repo gets published - and here we sync them to packman.links2linux.de.
> There is a publishing mechanism, which re-signs the packages with the
> official packman key, puts entries in the database backing the website
> and creates the repositories for the mirrors.
>
> For security reasons the re-signing step checks the signatures, with
> which the packages arrive. There is a positive-list, and only signatures
> on that list are considered "okay" for re-signing and publishing.
>
> As I wrote last Wednesday, the ultimate problem was the expired PMBS
> key, which in turn sings the publishing keys for PMBS's repos, and I had
> to recreate the key for the Multimedia repo.
> This key has changed, and re-signing at packman.links2linux.de fails,
> and the packages are not published to the mirrors.
>
> There are two possible ways to fix this:
> 1. allow the actual Multimedia repo key to be accepted on
> packman.links2linux.de
> 2. reinstate the old Multimedia repo key on PMBS.
>
> The first option needs an action on packman.links2linux.de -> I have to
> ask Marc to do the change (he is busy ATM, and this may take a while).
>
> The second option may work, as I have backups, and the Open Build
> Service keeps such information. I have read somewhere, that manually
> forcing a pre-existing key in a build service instance, but do not know
> - how to do that (probably something with obs_admin), and
> - if this will succeed.
>
> Anyway, the packages will resurface, but it may take time.
> I will announce a downtime for PMBS in my next mail, and can face the
> repo-key issue after I have moved PMBS to its new home at the hosted
> server.
>
>
> Greetings,
>
> Stefan
> --
> Stefan Botter zu Hause
> Bremen
>

Something must have been fixed, avidemux3 is now available in the
normal repository

Dave

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

Re: [packman] avidemux has gone

2021-02-25 Diskussionsfäden Dave Plater
avidemux3 in Multimedia which is the one you see in the Packman
repository is present so maybe there is a problem with the Packman
repository
Regards
Dave

On 2/26/21, Mark Fairbairn  wrote:
> Avidemux (avidemux3) seems to have disappeared from packman (for
> tumbleweed).
> Will it be making a reappearance, or has it gone forever?
>
> ___
> Packman mailing list
> Packman@links2linux.de
> https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

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

Re: [packman] chromium-ffmpeg-extra in OpenSUSE Tumbleweed: how is libffmpeg.so loaded?

2021-01-26 Diskussionsfäden Dave Plater
Just for interest sake, ms have released a linux teams client:
https://techcommunity.microsoft.com/t5/microsoft-teams-blog/microsoft-teams-is-now-available-on-linux/ba-p/1056267

Dave

On 1/19/21, Olaf Hering  wrote:
> Am Tue, 19 Jan 2021 09:00:23 +0100 (CET)
> schrieb Dimitrios Apostolou :
>
>> Where do you find chromium-beta?
>
> It was some test package, which is unintentional still installed:
>
> Build Date  : Tue May  5 14:50:50 2020
> Distribution: network:chromium / openSUSE_Leap_15.1
>
>
> Olaf
>

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

Re: [packman] chromium-ffmpeg-extra in OpenSUSE Tumbleweed: how is libffmpeg.so loaded?

2021-01-16 Diskussionsfäden Dave Plater
On 1/15/21, Dimitrios Apostolou  wrote:
> Hello list, please CC me in your replies as I'm not subscribed.
>
> I'm facing issues with codecs on chromium (Video calls not working on
> Microsoft Teams). Packages I have installed:
>
> $ rpm -qa|grep chromium
> chromium-87.0.4280.141-1.1.x86_64
> chromium-ffmpeg-extra-69.0.3497.100-2.24.x86_64
>
> It seems that chromium-ffmpeg-extra contains only one significant file:
> /usr/lib64/chromium-ffmpeg-extra/libffmpeg.so
>
> How does the `chromium` binary load this file? AFAICT it never loads it.
> Here is what I tried:
>
> + Run `ldd` for /usr/lib64/chromium/chromium and all the .so libraries it
>loads. "libffmpeg.so" is not listed anywhere
>
> + Run `strings` for all of the above, still not listed.
>
> + `strace` chromium as such:
>
>strace -ff -s 128  chromium --enable-logging=stderr --v=2 --debug
>
>Still `libffmpeg.so` is not listed anywhere.
>
> + Up to this point, I'm not so surprised as the shell script
>/usr/bin/chromium sets LD_LIBRARY_PATH to /usr/lib64/chromium
>which has nothing to do with /usr/lib64/chromium-ffmpeg-extra.
>How is chromium supposed to know that path?
>
> + But even setting LD_LIBRARY_PATH explicitly to
>/usr/lib64/chromium-ffmpeg-extra does not help, libffmpeg.so is still
>not getting loaded.
>
> Any ideas?
>
> Thank you in advance,
> Dimitris
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


I'm not sure which codec is involved in "Microsoft Teams" but the
summery for chromium-ffmpeg-extra says "Extra ffmpeg codecs for
browsers based on Chromium" the actual ffmpeg libraries libavcodec
libavformat etc are required by chromium itself. If you know the
specific codec you can find out what your ffmpeg provides with "ffmpeg
-codecs" if you don't have the packman versions of libavcodec, the
actual package that Tubleweed chromium uses is libavcodec58_91, then
this may be your problem.
Regards

Dave

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

Re: [packman] Is it possible to have a packman version for Tumbleweed for the Raspberry Pi 3/4 (aarch64)?

2020-12-02 Diskussionsfäden Dave Plater
On 12/2/20, Olaf Hering  wrote:
> Am Tue, 1 Dec 2020 10:56:20 +0100 (CET)
> schrieb Guillaume GARDET :
>
>> Any objections?
>
> The publisher may need adjustments, perhaps it has a fixed list of
> architectures.
>
> It also means all 'openSUSE_Factory_ARM' *.repo files out there become
> invalid. The published directory may stay on the mirrors, unless someone
> removes it manually and the mirrors pickup this change.
>
> A number of pkg's may need adjustment in case they have special handling for
> a 'openSUSE_Factory_ARM' repository, but not for 'openSUSE_Tumbleweed' or
> 'arch='. Each one should probably be reevaluated if such knob is still
> justified.
>
> Olaf
>
I also had this problem with Factory on a raspberry pi but it seems
that there isn't a problem anymore. I chose Tumbleweed because it had
more built packages and used the same repository definition that I use
for my x86_64 computer. I was able to install the ffmpeg-4 libs which
is all I needed anyway.
The repository definition is:
http://packman.inode.at/suse/openSUSE_Tumbleweed/

Regards
Dave

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

Re: [packman] Cannot play online video in Firefox after ffmpeg/libav update

2020-07-20 Diskussionsfäden Dave Plater
PMBS was down for more than a week.
Dave

On 7/17/20, Guo Yunhe  wrote:
> VLC and Chromium works fine. Firefox cannot play MP4/H.264 video anymore
> after the update today.
>
>
> --
> Guo Yunhe / @guoyunhe / guoyunhe.me
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] ffmpeg and libav* packages: cannot solve dependencies

2020-07-20 Diskussionsfäden Dave Plater
PMBS was down for more than a week as a result ffmpeg is old.
Dave

On 7/16/20, Guo Yunhe  wrote:
> I found that the package libavcodec58 was renamed to libavcode58_91. But no
> "Provides:" and "Obsoletes:" was added to the new package. This in result
> cause people cannot update the package smoothly.
>
> When I do zypper dup in Tumbleweed, it says that you can either keep the old
> package or change repo to openSUSE official repos.
>
> --
> Guo Yunhe / @guoyunhe / guoyunhe.me
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Fwd: ffmpeg-4/Mozilla Firefox problem / [PM] ffmpeg-4 4.3.1-4.1 (openSUSE Tumbleweed/x86_64)

2020-07-20 Diskussionsfäden Dave Plater
PMBS was down for more than a week.
Dave

On 7/19/20, w.pelser  wrote:
>
>
>
>  Weitergeleitete Nachricht 
> Betreff:  ffmpeg-4/Mozilla Firefox problem
> Datum:Sun, 19 Jul 2020 14:59:50 +0200
> Von:  w.pelser 
> An:   bjorn@gmail.com
>
>
>
> Hallo!
>
> My bugzilla account is lost.
>
> So I chose this way. Sorry, if it is unusual or so.
>
> Since update to version 4.3.1 Firefox can´t play videos on my machine
> (OS tumbleweed).
>
> It seems to me,  that Firefox is only searching for files with two
> numbers behind the *.so. , needs a libavcodec.so.58 symlink and can´t
> deal with only a libavcodec.so. 58.91 symlink for instance, which comes
> with the rpm package(s).
>
> My solution is, to add symlinks in /usr/share/lib64 from
> libavcodec.so.58 to libavcodec.so.58.91 and to the other similar files too.
>
> Maybe this mail could be helpful.
>
> Or it is only a special case of my installation, than you can forget
> this mail please.
>
> Thanks
>
> Walther Pelser
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [opensuse-factory] New Tumbleweed snapshot 20200714 released! - Info for Packman users

2020-07-20 Diskussionsfäden Dave Plater
On 7/16/20, ulfb...@gmx.net  wrote:
> Hi,
>
> seams to be an issue with the missing related update from Packman:
>
> problem with installed package libavcodec58-4.2.3-4.5.x86_64
> problem with installed package libavdevice58-4.2.3-4.5.x86_64
> problem with installed package libavfilter7-4.2.3-4.5.x86_64
> problem with installed package libavformat58-4.2.3-4.5.x86_64
> problem with installed package libavutil56-4.2.3-4.5.x86_64
> problem with installed package libpostproc55-4.2.3-4.5.x86_64
> problem with installed package libswresample3-4.2.3-4.5.x86_64
> problem with installed package libswscale5-4.2.3-4.5.x86_64
> libavfilter7-4.2.3-4.5.x86_64 requires libavresample4 = 4.2.3-4.5, but this
> requirement cannot be provided
> libQtAV1-1.13.0-3.2.x86_64 requires libavresample.so.4()(64bit), but this
> requirement cannot be provided
> libQtAV1-1.13.0-3.2.x86_64 requires libavresample.so.4()(64bit), but this
> requirement cannot be provided
>
> Seems to be an issue with ffmpeg-4.
>
> Regards
> Ulf
>

See "[packman] PMBS back up - for now --- was: Re: PMBS down"
for an explanation. Packman build service hasn't been working all week
so the packages in the mirror sites will be stale, several ffrmpeg
updates have happened meanwhile.
Should get back to normal soon.
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] PMBS somewhat borked?

2020-04-07 Diskussionsfäden Dave Plater
On 4/7/20, Bjørn Lie  wrote:
> When trying to branch a package on the webui I get the following
> errormsg (and no branched package):
>
> There has been an internal error. Please try again.
>
> and when trying to use osc commandline
>
> bjolie@drude:~> alias oscpm
> alias oscpm='osc -A https://pmbs-api.links2linux.de'
>
> bjolie@drude:~> oscpm branch Staging/libde265
> BuildService API error: failed to branch:
> /srv/obs/events/lastnotifications: bad last line at
> /usr/lib/obs/server/BSFileDB.pm line 269.
> bjolie@drude:~>
>
> Just me or everyone else?
>
> /Bjørn
>


I couldn't even ping the pmbs ip for two days but this morning it's up again.

Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bug in HandBrakeGUI on Tumbleweed openSUSE

2020-03-22 Diskussionsfäden Dave Plater
On 3/22/20, Freek de Kruijf  wrote:
> Op zaterdag 21 maart 2020 13:34:12 CET schreef Dave Plater:
>> Unfortunately after updating to the same snapshot handbrake still
>> works. Force install handbrake-gtk handbrake and the debug packages,
>> run gdb HandBrakeGUI again and post the result of bt full after the
>> crash.
>>
>> Regards
>> Dave
>
> After the latest upgrade, later today, the versions for i586 and x86_64 are
> the same. So
>
> Output of bt full:
>
> #0  0x73ece6d1 in std::vector std::char_traits, std::allocator >,
> std::allocator,
> std::allocator > > >::_M_realloc_insert [16]>(__gnu_cxx::__normal_iterator std::char_traits, std::allocator >*,
> std::vector,
> std::allocator >, std::allocator std::char_traits, std::allocator > > > >, char const (&) [16])
> (this=0x7fffd4e0, __position=__position@entry=non-dereferenceable
> iterator for std::vector)
> at /usr/include/c++/9/ext/new_allocator.h:119
> __len = 
> __old_start = 
> __old_finish = 
> __elems_before = 
> __new_start = 0x563f8c60
> __new_finish = 0x563f8c80
> #1  0x73ece87b in std::vector std::char_traits, std::allocator >,
> std::allocator,
> std::allocator > > >::emplace_back(char const (&)
> [16]) (this=this@entry=0x7fffd4e0) at /usr/include/c++/9/bits/
> stl_iterator.h:806
> #2  0x73ecdb85 in MFX::LoaderCtx::Init(mfxInitParam&)
> (this=0x564a4c00, par=...)
> at /usr/src/debug/libmfx-19.4.0-1.1.x86_64/api/mfx_dispatch/linux/
> mfxloader.cpp:193
> libs = std::vector of length 0, capacity 0
> mfx_res = 
> #3  0x73ece28a in MFXInitEx(mfxInitParam, mfxSession*) (par=...,
> session=0x7fffd628)
> at /usr/src/debug/libmfx-19.4.0-1.1.x86_64/api/mfx_dispatch/linux/
> mfxloader.cpp:400
> loader = std::unique_ptr = {get() = 0x564a4c00}
> mfx_res = 
> #4  0x73ece3d2 in MFXInit(mfxIMPL, mfxVersion*, mfxSession*)
> (impl=impl@entry=1, ver=ver@entry=0x7fffd624,
> session=session@entry=0x7fffd628)
> at /usr/src/debug/libmfx-19.4.0-1.1.x86_64/api/mfx_dispatch/linux/
> mfxloader.cpp:388
> par =
> {Implementation = 1, Version = {{Minor = 0, Major = 1}, Version
> =
> 65536}, ExternalThreads = 0, {{ExtParam = 0x0, NumExtParam = 0}, reserved2 =
> {0, 0, 0, 0, 0}}, GPUCopy = 0, reserved = {0 }}
> #5  0x555c023c in hb_qsv_info_init () at /usr/src/debug/
> handbrake-1.3.1-4.6.x86_64/libhb/qsv_common.c:688
> session = 0x0
> version = {{Minor = 0, Major = 1}, Version = 65536}
> hw_preference = 256
> init_done = 1
> #6  0x555c023c in hb_qsv_info_init () at /usr/src/debug/
> handbrake-1.3.1-4.6.x86_64/libhb/qsv_common.c:665
> init_done = 1
> #7  0x555fb177 in hb_global_init () at /usr/src/debug/
> handbrake-1.3.1-4.6.x86_64/libhb/hb.c:1690
> result = 0
> #8  0x556160c8 in ghb_backend_init (debug=0) at /usr/src/debug/
> handbrake-1.3.1-4.6.x86_64/gtk/src/hb-backend.c:3356
> #9  0x55624afb in ghb_activate_cb (app=0x55cf50f0, ud= out>)
> --Type  for more, q to quit, c to continue without paging--
> at /usr/src/debug/handbrake-1.3.1-4.6.x86_64/gtk/src/main.c:1062
> provider = 
> ss = 
> widget = 
> textview = 
> buffer = 
> logLevel = 
> source = 
> ghb_window = 
> window_width = 
> window_height = 
> filter = 
> chooser = 
> stack_switcher_children = 
> link = 
> stack_switcher = 
> window = 
> #10 0x77003eb2 in g_closure_invoke () at
> /usr/lib64/libgobject-2.0.so.
> 0
> #11 0x77017884 in  () at /usr/lib64/libgobject-2.0.so.0
> #12 0x770205ae in g_signal_emit_valist () at /usr/lib64/
> libgobject-2.0.so.0
> #13 0x77020bcf in g_signal_emit () at /usr/lib64/libgobject-2.0.so.0
> #14 0x7736c2a8 in  () at /usr/lib64/libgio-2.0.so.0
> #15 0x7736c45a in g_application_run () at /usr/lib64/libgio-2.0.so.0
> #16 0x55595e62 in main (argc=1, argv=0x7fffdd68) at /usr/src/
> debug/handbrake-1.3.1-4.6.x86_64/gtk/src/main.c:1375
> status = 
> ud = 0x55ceb730
>
> --
> fr.gr.
>
> member openSUSE
> Freek de Kruijf


Hi, I tried the force install of handbrake-gtk and zypper also wanted
to change to i586 and install 140 32bit packages, this was because the
i586 package was newer than the x86_64 package. After a zypper ref
this was fixed. The problem appears to be coming from libmfx1 whic

Re: [packman] Bug in HandBrakeGUI on Tumbleweed openSUSE

2020-03-21 Diskussionsfäden Dave Plater
Unfortunately after updating to the same snapshot handbrake still
works. Force install handbrake-gtk handbrake and the debug packages,
run gdb HandBrakeGUI again and post the result of bt full after the
crash.

Regards
Dave

On 3/21/20, Freek de Kruijf  wrote:
> Op zaterdag 21 maart 2020 12:26:23 CET schreef Dave Plater:
>> That definitely looks like handbrake was built against a different
>> libstdc++ than what you have on your system. I should have asked you
>> to type bt full after the illegal instruction and maybe I can pinpoint
>> which library is the culprit. I've got Tumbleweed version 20200314
>> installed will update to 20200318 which is the latest. cat
>> /usr/lib/os-release will show which version you have installed.
>> Dave
>
> Upgraded this morning to 20200318 using "zypper dup".
>
> I have:
> # zypper se -si libstdc
> Gegevens van opslagruimte laden...
> Lezen van geïnstalleerde pakketten...
>
> S  | Naam | Type   | Versie   | Arch   |
> Opslagruimte
> ---+--++--+
> +--
> i  | libstdc++-devel  | pakket | 9-1.6| x86_64 |
> openSUSE-20191023-0
> i+ | libstdc++6   | pakket | 10.0.1+git175037-1.1 | x86_64 |
> openSUSE-20191023-0
> i+ | libstdc++6-32bit | pakket | 10.0.1+git175037-1.1 | x86_64 |
> openSUSE-20191023-0
> i+ | libstdc++6-debuginfo | pakket | 10.0.1+git175037-1.1 | x86_64 |
> openSUSE-Tumbleweed-Debug
> i  | libstdc++6-devel-gcc9| pakket | 9.2.1+git1192-1.1| x86_64 |
> openSUSE-20191023-0
> i+ | libstdc++6-pp-gcc9   | pakket | 9.2.1+git1192-1.1| x86_64 |
> openSUSE-20191023-0
> i+ | libstdc++6-pp-gcc9-32bit | pakket | 9.2.1+git1192-1.1| x86_64 |
> openSUSE-20191023-0
>
> # cat /etc/zypp/repos.d/openSUSE-20191023-0.repo
> [openSUSE-20191023-0]
> name=openSUSE-20191023-0
> enabled=1
> autorefresh=1
> baseurl=http://download.opensuse.org/tumbleweed/repo/oss/
> path=/
> type=rpm-md
> keeppackages=0
>
> --
> fr.gr.
>
> member openSUSE
> Freek de Kruijf
>
>
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bug in HandBrakeGUI on Tumbleweed openSUSE

2020-03-21 Diskussionsfäden Dave Plater
That definitely looks like handbrake was built against a different
libstdc++ than what you have on your system. I should have asked you
to type bt full after the illegal instruction and maybe I can pinpoint
which library is the culprit. I've got Tumbleweed version 20200314
installed will update to 20200318 which is the latest. cat
/usr/lib/os-release will show which version you have installed.
Dave

On 3/21/20, Freek de Kruijf  wrote:
> Op zaterdag 21 maart 2020 07:18:57 CET schreef Dave Plater:
>> On 3/20/20, Hans-Peter Jansen  wrote:
>> > Am Freitag, 20. März 2020, 17:32:14 CET schrieb Freek de Kruijf:
>> >> When I start HandBrakeGUI in openSUSE Tumbleweed, fully updated, I get
>> >> the
>> >> following:
>> >> Illegal instruction (core dumped)
>> >>
>> >> How to proceed?
>>
>> It works for me, install the handbrake-debuginfo,
>> handbrake-gtk-debuginfo and (should be pulled automatically)
>> handbrake-debugsource then run gdb HandBrakeGUI and type run at the
>> command prompt. This will hopefully tell us where the illegal
>> instruction is from.
>> That said, you might have installed handbrake while it was still
>> building against snapshot and simply updating it will solve the
>> problem.
>> Regards
>> Dave
>
> This is part of the output:
>
> Thread 1 "HandBrakeGUI" received signal SIGILL, Illegal instruction.
> 0x73ece6d1 in std::vector std::char_traits, std::allocator >,
> std::allocator,
> std::allocator > > >::_M_realloc_insert (
> this=0x7fffd4e0, __position=__position@entry=non-dereferenceable
> iterator for std::vector)
> at /usr/include/c++/9/ext/new_allocator.h:119
> warning: Source file is more recent than executable.
> 119   deallocate(pointer __p, size_type)
>
>
> --
> fr.gr.
>
> member openSUSE
> Freek de Kruijf
>
>
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bug in HandBrakeGUI on Tumbleweed openSUSE

2020-03-21 Diskussionsfäden Dave Plater
On 3/20/20, Hans-Peter Jansen  wrote:
> Am Freitag, 20. März 2020, 17:32:14 CET schrieb Freek de Kruijf:
>> When I start HandBrakeGUI in openSUSE Tumbleweed, fully updated, I get the
>> following:
>> Illegal instruction (core dumped)
>>
>> How to proceed?
>

It works for me, install the handbrake-debuginfo,
handbrake-gtk-debuginfo and (should be pulled automatically)
handbrake-debugsource then run gdb HandBrakeGUI and type run at the
command prompt. This will hopefully tell us where the illegal
instruction is from.
That said, you might have installed handbrake while it was still
building against snapshot and simply updating it will solve the
problem.
Regards
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Flash is outdated again

2020-03-18 Diskussionsfäden Dave Plater
Can someone accept Request 5030
Dave

On 3/18/20, Dave Plater  wrote:
> Busy updating it
> Dave
>
> On 3/18/20, Stefan Seyfried  wrote:
>> Am 17.03.20 um 22:51 schrieb Tony Mechelynck:
>>
>>> I see. Well, I don't have the necessary abilities to compile it
>>> myself,
>>
>> You do not need to compile anything. You can't because there are no
>> sources.
>> You just need to update the packman package. That's about the most boring
>> packaging job ever.
>>
>> So stop complaining and help yourself out.
>>
>>> Adobe's rpm. (I'd prefer a YaST-compatible repository but you leave me
>>> — and any user still needing Flash — no choice.)
>>
>> It is very easy to get a Packman OBS account and the packaging skills
>> needed
>> to update the flash package are not
>> extraordinary (I'd consider it beginner level).
>>
>> So for the case that you would be willing to give something back to the
>> community, this would be a way to start.
>> --
>> Stefan Seyfried
>>
>> "For a successful technology, reality must take precedence over
>>  public relations, for nature cannot be fooled." -- Richard Feynman
>>
>> ___
>> Packman mailing list
>> Packman@links2linux.de
>> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Flash is outdated again

2020-03-18 Diskussionsfäden Dave Plater
Busy updating it
Dave

On 3/18/20, Stefan Seyfried  wrote:
> Am 17.03.20 um 22:51 schrieb Tony Mechelynck:
>
>> I see. Well, I don't have the necessary abilities to compile it
>> myself,
>
> You do not need to compile anything. You can't because there are no sources.
> You just need to update the packman package. That's about the most boring
> packaging job ever.
>
> So stop complaining and help yourself out.
>
>> Adobe's rpm. (I'd prefer a YaST-compatible repository but you leave me
>> — and any user still needing Flash — no choice.)
>
> It is very easy to get a Packman OBS account and the packaging skills needed
> to update the flash package are not
> extraordinary (I'd consider it beginner level).
>
> So for the case that you would be willing to give something back to the
> community, this would be a way to start.
> --
> Stefan Seyfried
>
> "For a successful technology, reality must take precedence over
>  public relations, for nature cannot be fooled." -- Richard Feynman
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Introduction

2020-02-23 Diskussionsfäden Dave Plater
multimedia:xine/xine-lib
Dave

On 2/24/20, Maurizio Galli  wrote:
> On Mon, Feb 24, 2020 at 2:44 PM Olaf Hering  wrote:
>>
>> Am Mon, 24 Feb 2020 13:51:07 +0800
>> schrieb Maurizio Galli :
>>
>> > To my understanding there isn't and nothing actually builds
>>
>> You are right.
>> I think what you meant to say was that Discord.exe can not be published in
>> OBS because it has (at least) x264 support compiled into the binaries. It
>> could probably be put into 'Extra/discord'.
>>
>
> Not exactly. The tar includes libffmpeg.so with x264 and x265 it which
> cannot be included in OBS. Therefore the package replaces libffmpeg.so
> with the electron version that does not have x264 and x265 support.
> With this modification it was accepted in OBS and Factory.
>
> Maurizio Galli (MauG)
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Introduction

2020-02-23 Diskussionsfäden Dave Plater
try the package multimedia:libs/ffmpeg-4

Dave

On 2/24/20, Maurizio Galli  wrote:
> On Mon, Feb 24, 2020 at 3:34 AM Olaf Hering  wrote:
>>
>> Am Sun, 23 Feb 2020 23:24:26 +0800
>> schrieb Maurizio Galli :
>>
>> > needs to use a pre-bundled ffmpeg
>>
>> Is there no way to turn discord into a sane package and just use the
>> system ffmpeg?
>>
>> Olaf
>
> To my understanding there isn't and nothing actually builds
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Introduction

2020-02-22 Diskussionsfäden Dave Plater
You can normally build against openSUSE's ffmpeg libs and the package
will use the unencumbered ffmpeg libs. Mpeg2 is no longer under
patent.

Dave

On 2/22/20, Maurizio Galli  wrote:
> Hello everyone,
> My name is Maurizio aka mauriziogalli or MauG on other online
> platforms.  I am an openSUSE Member and one of the Xfce devs and
> package maintainer in openSUSE [1][2]. I'd like to contribute to the
> project, in particular by packaging Discord. Although it is packaged
> in openSUSE, it was stripped of some of the libffmpeg codecs due to
> patent issues that would conflict with the distribution. I'm hoping to
> package the full version to include in the Packman repos.
>
> I look forward to hearing from you all.
> Have a lot of fun!
>
> [1] https://connect.opensuse.org/pg/profile/mauriziogalli
> [2] https://en.opensuse.org/User:Mauriziogalli
>
> Maurizio Galli (MauG)
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] kdenlive 19.08.1-lp150.16.2 (openSUSE_Leap 15.0/x86_64)

2020-01-18 Diskussionsfäden Dave Plater
My 15.1 repo says nothing provides rttr-devel but you mention
Leap:15.0 which Packman no longer uses. For 15.1 it's most probably
just a matter of removing the missing requirement from the build.
Dave

On 1/18/20, Админ Хаус  wrote:
> Hi. How difficult is it to build the latest version of kdenlive 19.12.1
> ? Whether help is needed for this.
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] aMule 2.3.3 in openSUSE Leap 15.1

2019-11-13 Diskussionsfäden Dave Plater
On 11/13/19, Massimo Spiller  wrote:
> Hi Dave!
> Thanks for your support, but it's not working better.
>
> I did a quick test and behaviour is the same: after a while (3-5 minutes)
> cpu goes up to 98/100 % and gradually memory (all system memory) is eaten up
> by amule process. If you wait, the system becomes unresponsive, unless you
> kill amule process before  memory consumption is too high.
>
> I'm not on Tumbleweed. I'm on 15.1. I created a new repo
> (http://pmbs-api.links2linux.org:8080/home:/davepl/Leap_15.1/) and got from
> there "amule 2.3.2.20190827.2a1b09233-lp151.9.1-x86_64". Installation of
> your version of amule required (for me) these dependencies:
> libwx_gtk2u_adv-suse-nostl, libwx_baseu-suse-nostl3,
> libwx_gtk2u_core-suse-nostl3, libwx_baseu_net-suse-nostl3 (all of them from
> standard repo - main openSUSE).
>
> I'll try to test a little bit more in the next days.
>
> Thank you very much anyway!
> 

As I said, there isn't much else that can be done, maybe if you still
have problems make an issue at
https://github.com/amule-project/amule/issues
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] aMule 2.3.3 in openSUSE Leap 15.1

2019-11-13 Diskussionsfäden Dave Plater
On 11/12/19, Massimo Spiller  wrote:
> Hi Istvan Gabor,
> in my opinion enabling "wxWidgets >= 3.0" creates the problem.
>
> http://lists.links2linux.de/pipermail/packman/2019-September/016083.html
>

If somebody can overcome the problems with old wxWidgets-wxcontainer
not existing in Tumbleweed, they can try and overcome the abi mismatch
problem that occurs. Meanwhile I'll try building with the nostl
wxwidgets.
I'll post a repo for myou to test when it's built
Dave

>>
>> Hello:
>>
>> I installed aMule-2.3.2.20181119.20afd75fa-lp151.2.1.x86_64.rpm
>> (downloaded from
>> https://ftp5.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.1/Extra/x86_64/)
>> in openSUSE Leap 15.1.
>>
>> After starting aMule in a few minutes it uses 100% CPU and hangs the
>> computer.
>> I must press the reset button because the computer becomes
>> unresponsive.
>> This make this aMule version unusable for me.
>>
>> Any idea, how to fix it, or why this occurs?
>>
>> Thanks,
>>
>> Istvan
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] ffmpeg 4

2019-10-20 Diskussionsfäden Dave Plater
On 10/19/19, Luigi Baldoni  wrote:
>Hello,
> how do you feel about enabling ffmpeg-4 binaries for Leap by setting
> full_build
> in the project config?
>
> I know it would create a conflict, but who does really need both ffmpeg 3
> and 4
> tools?
>
> Regards
>

+1 from me, I have to use rpmbuild to get ffmpeg-4

Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] kdenlive package 19.08 for Leap 15.0 is broken

2019-08-23 Diskussionsfäden Dave Plater
On 8/23/19, Jean B  wrote:
> Hello,
>
> I just wanted to let you know that the kdenlive package (19.08) for Leap
> 15.0 is broken. The program is starting but it does not behave normally.
> It's impossible to cut a video, the clips disappear completely from the
> timeline or jump all over the place, and so on. It's unusable. I'm now using
> the appimage from the official website: kdenlive-19.08.0a-x86_64.appimage
> and everything works normally.
>
>
> Thanks,
>
>
> Jean


The current Tumbleweed kdenlive-19.08 doesn't build for Leaps 15.0 and
15.1 due to a missing dependency. I would recommend that you use the
official Leap version 18.12.3 or if you try a zypper dup from Packman
to ensure you have the correct libraries. The appimage includes all of
the dependencies in the package, that's why it uses so much space.
Best regards
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] aMule for Leap 15.1

2019-08-02 Diskussionsfäden Dave Plater
Submit request 4533
Dave

On 8/2/19, Hans-Peter Jansen  wrote:
> Am Donnerstag, 1. August 2019, 16:35:22 CEST schrieb Rolf Niepraschk:
>> Am 01.08.19 um 15:33 schrieb Dave Plater:
>> > If you use rpm to install things you must struggle with your
>> > dependencies yourself. Try:
>> > zypper in -f
>> > http://pmbs-api.links2linux.org:8080/home:/davepl/Leap_15.1/x86_64/aMule->
>> > > 2.3.2.20181119.20afd75fa-lp151.4.1.x86_64.rpm
>> >
>> > It would be easier to add the repository and install the normal way.
>> > Regards
>> > Dave
>>
>> Yes, you are right.
>>
>> I found my mistake. There was an old version of "amule" in
>> "/usr/local/bin". Sorry for the nuisance.
>
> Well, this statement contradicts, what you said two messages before, but I'm
> glad, you fixed it.
>
> Since this reminds me about a statement one week ago in factory, here it is
> again:
>
> If I'm introduced to a new system to administrate, that contains files under
> /
> usr/local, I consider that system broken!
>
> Thanks,
> Pete
>
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] aMule for Leap 15.1

2019-08-01 Diskussionsfäden Dave Plater
If you use rpm to install things you must struggle with your
dependencies yourself. Try:
zypper in -f 
http://pmbs-api.links2linux.org:8080/home:/davepl/Leap_15.1/x86_64/aMule-2.3.2.20181119.20afd75fa-lp151.4.1.x86_64.rpm

It would be easier to add the repository and install the normal way.
Regards
Dave

On 8/1/19, Rolf Niepraschk  wrote:
> Am 01.08.19 um 14:35 schrieb Hans-Peter Jansen:
> ...
>>
>> Run:
>> rpm -V GeoIP aMule libcryptopp5_6_5 libwx_baseu-2_8-0-wxcontainer \
>> libwx_baseu_net-2_8-0-wxcontainer  libwx_gtk2u_adv-2_8-0-wxcontainer \
>> libwx_gtk2u_core-2_8-0-wxcontainer
>
> No output.
>
>>
>> Check /usr/local for any stray installs - you're not going to install
>> tarballs
>> from time to time, do you?
>
> No, I don't. My installation is relative new.
>
> ...Rolf
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] aMule for Leap 15.1

2019-08-01 Diskussionsfäden Dave Plater
I can't understand why someone has made aMule build against wxWidgets
2.8 and haven't said anything in the changes file, I've just tried
wxWidgets 3 and it builds and runs.
Rolf try installing from:
http://pmbs-api.links2linux.org:8080/home:/davepl/Leap_15.1/

If it works for you I'll submit the package.
Regards
Dave

On 8/1/19, Rolf Niepraschk  wrote:
> Am 01.08.19 um 11:16 schrieb Stefan Seyfried:
>> Am 01.08.19 um 11:07 schrieb Rolf Niepraschk:
>>
>>> Fatal Error: Mismatch between the program and library build
>>> versions detected.
>>> The library used 2.8 (no debug,Unicode,compiler with
>>> C++ ABI 1011,wx containers,compatible with 2.6),
>>> and your program used 2.8 (no debug,Unicode,compiler with
>>> C++ ABI 1013,wx containers,compatible with 2.6).
>>>
>>> Do you have more suggestions?
>>
>> Your libwx* stuff is borken.
>>
>> I did "zypper in aMule", got:
>>
>> Selecting 'aMule-2.3.2.20181119.20afd75fa-1.3.x86_64' from repository
>> 'packman' for installation.
>> Resolving package dependencies...
>> Force resolution: No
>>
>> The following 7 NEW packages are going to be installed:
>>GeoIP   1.6.12-lp151.1.3
>>aMule   2.3.2.20181119.20afd75fa-1.3
>>libcryptopp5_6_55.6.5-lp151.2.3
>>libwx_baseu-2_8-0-wxcontainer   2.8.12-lp151.6.5
>>libwx_baseu_net-2_8-0-wxcontainer   2.8.12-lp151.6.5
>>libwx_gtk2u_adv-2_8-0-wxcontainer   2.8.12-lp151.6.5
>>libwx_gtk2u_core-2_8-0-wxcontainer  2.8.12-lp151.6.5
>>
>> 7 new packages to install.
>> Overall download size: 8.6 MiB. Already cached: 0 B. After the operation,
>> additional 45.2 MiB will be used.
>>
>> This starts just fine.
>>
>
> I have the same package versions installed:
>
> zypper se -is GeoIP aMule libcryptopp5_6_5 libwx_baseu-2_8-0-wxcontainer \
> libwx_baseu_net-2_8-0-wxcontainer  libwx_gtk2u_adv-2_8-0-wxcontainer \
> libwx_gtk2u_core-2_8-0-wxcontainer
>
> S  | Name   | Typ   | Version   | Arch
> | Repository
> ---++---+--++---
> i  | GeoIP  | Paket | 1.6.12-lp151.1.3
> | x86_64 | Haupt-Repository (OSS)
> i  | GeoIP-data | Paket | 1.6.12-lp151.1.3
> | noarch | Haupt-Repository (OSS)
> i+ | aMule  | Paket |
> 2.3.2.20181119.20afd75fa-1.3 | x86_64 | Packman repository
> i+ | libGeoIP-devel | Paket | 1.6.12-lp151.1.3
> | x86_64 | Haupt-Repository (OSS)
> i  | libGeoIP1  | Paket | 1.6.12-lp151.1.3
> | x86_64 | Haupt-Repository (OSS)
> i  | libcryptopp5_6_5   | Paket | 5.6.5-lp151.2.3
> | x86_64 | Haupt-Repository (OSS)
> i  | libwx_baseu-2_8-0-wxcontainer  | Paket | 2.8.12-lp151.6.5
> | x86_64 | Packman repository
> i  | libwx_baseu_net-2_8-0-wxcontainer  | Paket | 2.8.12-lp151.6.5
> | x86_64 | Packman repository
> i  | libwx_gtk2u_adv-2_8-0-wxcontainer  | Paket | 2.8.12-lp151.6.5
> | x86_64 | Packman repository
> i  | libwx_gtk2u_core-2_8-0-wxcontainer | Paket | 2.8.12-lp151.6.5
> | x86_64 | Packman repository
>
> More Ideas?
>
> ...Rolf
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] aMule for Leap 15.1

2019-08-01 Diskussionsfäden Dave Plater
On my 15.1 system:
 zypper se -sx aMule
Loading repository data...
Reading installed packages...

S | Name  | Type   | Version  | Arch   | Repository
--+---++--++---
  | aMule | package| 2.3.2.20181119.20afd75fa-1.3 | x86_64 | pacman
  | aMule | srcpackage | 2.3.2.20181119.20afd75fa-1.3 | noarch | pacman

I checked in the Packman build service and the 15.1 package is built
and present.
Best regards
Dave

On 7/31/19, Rolf Niepraschk  wrote:
> Hello friends,
> I would like to use "aMule" for openSUSE Leap 15.1. Unfortunately there
> is no such package.
>
> I downloaded the source rpm for Tumbleweed. The compilation per
>
> rpmbuild --rebuild aMule-2.3.2.20181119.20afd75fa-1.26.src.rpm
>
> was successful. The program start failed with the following error message:
>
> Fatal Error: Mismatch between the program and library build versions
> detected. The library used 2.8 (no debug,Unicode,compiler with C++ ABI
> 1011,wx containers,compatible with 2.6), and your program used 2.8 (no
> debug,Unicode,compiler with C++ ABI 1013,wx containers,compatible with 2.6).
>
> Can anyone help? Many thanks in advance.
>
> ...Rolf
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] a2jmidid 8-2.20 (openSUSE Tumbleweed/x86_64) Segfaulting

2019-07-26 Diskussionsfäden Dave Plater
There was a jack segfault bug after LTO was enabled in Tumbleweed,
I've fixed this but because jack is a major library it takes longer
than usual to be accepted into Factory. Meanwhile you can use jack
from:
https://download.opensuse.org/repositories/home:/plater/Tumbleweed
Make sure to update both jack and libjack0.
Best regards
Dave

On 7/25/19, S.  wrote:
> Hi, I recent updates to Tumbleweed and a2jmidid are preventing me from using
> Jack and PulseAudio simultaneously via Cadence. I wonder if it has something
> to do with TW's recent switch to LTO compile? This is the A2J error I am
> getting:
>
> ==
>
> Thu Jul 25 11:38:45 2019: 
> Thu Jul 25 11:38:45 2019: JACK MIDI <-> ALSA sequencer MIDI bridge, version
> 8 () built on Thu Jul 11 09:00:26 2019
> Thu Jul 25 11:38:45 2019: Copyright 2006,2007 Dmitry S. Baikov
> Thu Jul 25 11:38:45 2019: Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov
> Thu Jul 25 11:38:45 2019: 
> Thu Jul 25 11:38:45 2019: Activated.
> Thu Jul 25 11:38:45 2019: Hardware ports will be exported.
> Thu Jul 25 11:38:45 2019: Bridge starting...
> Thu Jul 25 11:38:45 2019: Using JACK server 'default'
> Thu Jul 25 11:38:45 2019: Hardware ports will be exported.
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: Segmentation Fault!
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: info.si_signo = 11
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: info.si_errno = 0
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: info.si_code  = 1
> (SEGV_MAPERR)
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: info.si_addr  = 0x5625ab4a3a69
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[00]   =
> 0x5627db495ee8
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[01]   =
> 0x0044
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[02]   =
> 0xf8cb
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[03]   =
> 0x0206
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[04]   =
> 0x5625ab4a3958
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[05]   =
> 0x7fffd5380aa0
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[06]   =
> 0x7f079f48e2f0
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[07]   =
> 0x5627db4d34f0
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[08]   =
> 0x7fffd5380c20
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[09]   =
> 0x7fffd5380aa0
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[10]   =
> 0x5625ab4a3958
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[11]   =
> 0x5627db4d34f0
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[12]   =
> 0x7fffd5380c30
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[13]   =
> 0x0003
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[14]   =
> 0x0010
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[15]   =
> 0x7fffd5380aa0
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[16]   =
> 0x7f079f48db57
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[17]   =
> 0x00010246
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[18]   =
> 0x002b0033
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[19]   =
> 0x0004
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[20]   =
> 0x000e
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[21]   =
> 0x1000
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: reg[22]   =
> 0x5625ab4a3a69
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv: Stack trace:
> Thu Jul 25 11:38:45 2019: ERROR: signal_segv:  1: 0x7f079f48db57
> <(null)+2672352087> (/usr/lib64/libjack.so.0)
> Thu Jul 25 11:38:50 2019: 
> Thu Jul 25 11:38:50 2019: JACK MIDI <-> ALSA sequencer MIDI bridge, version
> 8 () built on Thu Jul 11 09:00:26 2019
> Thu Jul 25 11:38:50 2019: Copyright 2006,2007 Dmitry S. Baikov
> Thu Jul 25 11:38:50 2019: Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov
> Thu Jul 25 11:38:50 2019: 
> Thu Jul 25 11:38:50 2019: Activated.
>
> ===
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [Leap][all]Problem: nothing provides /usr/bin/bash needed by tovid-0.35.2-1.1.noarch

2019-07-18 Diskussionsfäden Dave Plater
The request was accepted, problem should be fixed.
Dave

On 7/15/19, Dave Plater  wrote:
> I've fixed it in:
> https://pmbs.links2linux.de/request/show/4521
> When somebody accepts it the requirement will become /bin/bash
> Regards
> Dave
>
> On 7/13/19, Felix Miata  wrote:
>> # grep RETT /etc/os-release
>> PRETTY_NAME="openSUSE Leap 15.1"
>> # zypper ve
>> Problem: nothing provides /usr/bin/bash needed by tovid-0.35.2-1.1.noarch
>> # zypper se -six bash
>> S | Name | Type| Version| Arch   | Repository
>> --+--+-+++---
>> i | bash | package | 4.4-lp151.9.53 | x86_64 | OSS
>>
>> The tovid packages for the various openSUSE releases all "require" an
>> apparently ancient version of bash.
>>
>> # rpm -qi tovid
>> Name: tovid
>> Version : 0.35.2
>> Release : 1.1
>> Architecture: noarch
>> Install Date: Fri Jul 12 19:38:17 2019
>> Group   : Productivity/Multimedia/Video/Editors and Convertors
>> Size: 1536731
>> License : GPL-2.0-or-later
>> Signature   : RSA/SHA1, Sun May 26 14:25:07 2019, Key ID 45a1d0671abd1afb
>> Source RPM  : tovid-0.35.2-1.1.src.rpm
>> Build Date  : Sun May 26 14:13:45 2019
>> Build Host  : swkj03
>> Relocations : (not relocatable)
>> Packager: packman@links2linux.de
>> Vendor  : http://packman.links2linux.de
>> URL : http://tovid.wikia.com/wiki/Tovid_Wiki
>> Summary : Video conversion and DVD authoring tools
>> Description :
>> tovid is a suite of utilities designed to make DVD
>> authoring a little less painful. tovid can create MPEG output
>> from arbitrary video formats, help you identify video files,
>> generate graphical menus for DVD (animated or static),
>> generate DVD directories with the appropriate file structure,
>> and optionally burn them to disk.
>> Distribution: Multimedia / openSUSE_Leap_15.1
>> --
>> Evolution as taught in public schools is religion, not science.
>>
>>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>>
>> Felix Miata  ***  http://fm.no-ip.com/
>>
>> ___
>> Packman mailing list
>> Packman@links2linux.de
>> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [Leap][all]Problem: nothing provides /usr/bin/bash needed by tovid-0.35.2-1.1.noarch

2019-07-15 Diskussionsfäden Dave Plater
I've fixed it in:
https://pmbs.links2linux.de/request/show/4521
When somebody accepts it the requirement will become /bin/bash
Regards
Dave

On 7/13/19, Felix Miata  wrote:
> # grep RETT /etc/os-release
> PRETTY_NAME="openSUSE Leap 15.1"
> # zypper ve
> Problem: nothing provides /usr/bin/bash needed by tovid-0.35.2-1.1.noarch
> # zypper se -six bash
> S | Name | Type| Version| Arch   | Repository
> --+--+-+++---
> i | bash | package | 4.4-lp151.9.53 | x86_64 | OSS
>
> The tovid packages for the various openSUSE releases all "require" an
> apparently ancient version of bash.
>
> # rpm -qi tovid
> Name: tovid
> Version : 0.35.2
> Release : 1.1
> Architecture: noarch
> Install Date: Fri Jul 12 19:38:17 2019
> Group   : Productivity/Multimedia/Video/Editors and Convertors
> Size: 1536731
> License : GPL-2.0-or-later
> Signature   : RSA/SHA1, Sun May 26 14:25:07 2019, Key ID 45a1d0671abd1afb
> Source RPM  : tovid-0.35.2-1.1.src.rpm
> Build Date  : Sun May 26 14:13:45 2019
> Build Host  : swkj03
> Relocations : (not relocatable)
> Packager: packman@links2linux.de
> Vendor  : http://packman.links2linux.de
> URL : http://tovid.wikia.com/wiki/Tovid_Wiki
> Summary : Video conversion and DVD authoring tools
> Description :
> tovid is a suite of utilities designed to make DVD
> authoring a little less painful. tovid can create MPEG output
> from arbitrary video formats, help you identify video files,
> generate graphical menus for DVD (animated or static),
> generate DVD directories with the appropriate file structure,
> and optionally burn them to disk.
> Distribution: Multimedia / openSUSE_Leap_15.1
> --
> Evolution as taught in public schools is religion, not science.
>
>  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
>
> Felix Miata  ***  http://fm.no-ip.com/
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] DVDStyler for TW

2019-04-07 Diskussionsfäden Dave Plater
On 4/7/19, Dave Plater  wrote:
> On 4/6/19, Luigi Baldoni  wrote:
>> Sent: Saturday, April 06, 2019 at 5:22 PM
>> From: "Rolf Niepraschk" 
>>>
>>> Am 06.04.19 um 16:43 schrieb Luigi Baldoni:
>>> > Sent: Saturday, April 06, 2019 at 1:34 PM
>>> > From: "Rolf Niepraschk" 
>>> >>
>>> >> I would like to use the packman version of DVDStyler under
>>> >> Tumbleweed,
>>> >> but I can't find such package. Can anyone create the missing
>>> >> DVDStyler
>>> >> package? Thanks in advance,
>>> >
>>> > Why, what's the difference?
>>> >
>>>
>>> The difference: The program crash if I try to change the directory
>>> before including video files.
>>
>> If so, I recommend you file a bug report on bugzilla.opensuse.org.
>>
>> Regards
>>
> Please add yourself to:
> https://bugzilla.novell.com/show_bug.cgi?id=1131765
> The Packman DVDStyler is a link of openSUSE:Factory which is why there
> aren't any Tumbleweed packages available.
> I can duplicate the bug so I can fix it but any fixed package will be
> available via the bug first.
> Dave
>
I've added everyone to the bug.
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Kodi Leia PVR Addons: Fail to build due to an error in a tarball in a tarball...

2019-01-17 Diskussionsfäden Dave Plater
On 1/17/19, Manfred Hollstein  wrote:
> Moin,
>
> the current package sources from home:sagiben/kodi.binary-addons contain
> a line:
>
>   Source3:kodi.binary-addons.tar
>
> which itself contains a file "build/download/vfs.libarchive-master.tar.gz"
> which then fails during compilation (for openSUSE_Leap_42.3) due to two
> undefined types:
>
>
> /home/abuild/rpmbuild/BUILD/xbmc-18.0rc5-Leia/cmake/addons/build/vfs.libarchive/src/ArchiveFile.cpp:184:10:
>   error: 'la_ssize_t' does not name a type; did you mean '__ssize_t'?
>
> /home/abuild/rpmbuild/BUILD/xbmc-18.0rc5-Leia/cmake/addons/build/vfs.libarchive/src/ArchiveFile.cpp:194:10:
>   error: 'la_int64_t' does not name a type; did you mean 'u_int64_t'?
>
> After unpacking the tarball(s) I fail to see these two types being
> defined anywhere - however, compilation on openSUSE_Leap_15.0 succeeds.
> Could it be that this file should
>
> extern "C" {
> #include 
> }
>
> which would then #include  for the missing types? Don't
> know, though, where the #define for 'la_ssize_t' and 'la_int64_t' should
> then come from, but that is probably the usual configure trickery.
>
> How is such a file in a tarball in a tarball supposed to be patched? Or,
> how is the first tarball generated?
>
> HTH, TIA, cheers.
>
> l8er
> manfred
>
With great difficulty, you have go past the %cmake stage after which
all the sources are unpacked in the right places and then make your
patch using diff. There are two patches applied at that stage atm.
Regards
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] packaging issue in kodi.binary-addons

2018-12-19 Diskussionsfäden Dave Plater
I had to update taglib for clementine but it does indeed look as if
kodi-binary-addons are failing on the new taglib.
I'll have a look.
Dave

On 12/19/18, Christian Mahr  wrote:
> Dear all
>
> I am using tumblweed in combination with kodi from packman repository.
>
> when trying to upgrade from Tumbleweed-20181205 to latest tumbleweed
> version I get the following problem:
>
> --
>
> Problem: kodi.binary-addons-17.6-1.11.x86_64 requires libtag1 = 1.11.1,
> but this requirement cannot be provided
>    deleted providers: libtag1-1.11.1-4.1.x86_64
>   Solution 1: deinstallation of kodi.binary-addons-17.6-1.11.x86_64
>   Solution 2: keep obsolete libtag1-1.11.1-4.1.x86_64
>   Solution 3: break kodi.binary-addons-17.6-1.11.x86_64 by ignoring some
> of its dependencies
>
> -
>
> Please note that the be version of libtag1 is now
> "libtag1-1.11.1+git20181028-1.1.x86_64" .
>
> It seems kodi  kodi.binary-addons-17.6-1.11.x86_64 was built with
> requiring "= 1.11.1" rather than ">= 1.11.1".
>
> So can you change the packaging of kodi.binary-addons-17.6-1.11.x86_64
> from "=" to a ">=" to allow any newer libtag1 version?
>
> Thank you for you consideration!
>
> Christian
>
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Essentials nvidia bcond

2018-09-05 Diskussionsfäden Dave Plater
It was disabled because it confuses browsers into thinking that h264
is available on non nvidia hardware but this is only a problem with
ffmpeg built without libx264. This was intended to be enabled for
Packman.
Dave

On 9/4/18, Stasiek Michalski  wrote:
> Hi,
>
> I was wondering, what is the reasoning behind disabling bcond nvidia
> for Leap 15.0 for Essentials?
>  From my testing ffmpeg with nvidia stuff enabled builds fine and works
> fine afterwards, but it can't really be easily executed for essentials
> due to that bcond. Would be really nice if nvidia users could use Leap
> 15 to its full potential with ffmpeg (and other packages) :D
> LCP [Stasiek]
> https://lcp.world
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] [PM] calf 0.0.60-lp150.4.6 (openSUSE_Leap 15.0/x86_64)

2018-09-05 Diskussionsfäden Dave Plater
I see that calf is updated to 0.90.1 the latest release. calf-lv2 is a
sub package.
Dave

On 9/3/18, Marcelo  wrote:
> Good night
>
> How can I download this version of calf and calf-lv2?  I need then to use
> with
> audacity, the latest version (0.0.90) do not work.
>
> Thanks in advance
> --
> Marcelo Vivan Borro
> Linux User # 277064
>
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] mythweb packaging error?

2018-07-23 Diskussionsfäden Dave Plater
After I sent the reply to you I noticed that Olaf Herring had fixed
the spec file. Maybe Olaf can answer your questions.
Dave

On 7/23/18, pack...@howorth.org.uk  wrote:
> On Mon, 23 Jul 2018 09:48:52 +0200
> Dave Plater  wrote:
>
>>I've just looked at the package and it now shows php7 requirements,
>>must have rebuilt.
>>Regards
>>Dave
>
> How very confusing. So after I forced a refresh of the repository I
> could see it and installed it with no errors or hints to look at a
> readme or whatever that I could see. Then I restarted apache but now
> apache won't start. It says:
>
> Jul 23 10:31:54 acer-suse start_apache2[27762]: AH00526: Syntax error
> on line 111 of /etc/apache2/conf.d/mythweb.conf: Jul 23 10:31:54
> acer-suse start_apache2[27762]: Invalid command 'php_value', perhaps
> misspelled or defined by a module not included in the server
> configuration
>
> Looking at the /etc/apache2/conf.d/mythweb.conf installed by the
> package, I can see the php_value commands, but this is a file installed
> by packman designed to work with opensuse leap 15.0 so why would it use
> a command that appears not to be supported by that release? Or am I
> supposed to do something else to apache?
>
> I'm also confused why there is a reference to
>  
> in the file. Why hasn't that been changed to
> a /srv/ww/htdocs/? Is that a mistake or is it deliberate?
>
> The INSTALL file also says I need mod_rewrite but that doesn't seem to
> be installed by openSUSE as standard. So am I supposed to edit the
> loadmodule.conf file? Are there instructions describing how to get this
> package working on Leap 15 somewhere, or is it a guessing game?
>
>>On 7/22/18, Dave Howorth  wrote:
>>> Hello,
>>>
>>> First post. I think there's a packaging error in the mythweb package
>>> for Leap 15.0. I'm not sure how to report bugs for packman, so I'm
>>> trying here.
>>>
>>> When I try to install mythweb from packman (i.e.
>>> mythweb-0.28.2+git.20180201.af896aee-lp150.1.1.noarch.rpm) I see an
>>> error:
>>>
>>> nothing provides apache2-mod_php5
>>>
>>> But the only PHP module for apache from opensuse repositories seems
>>> to be v7: apache2-mod_php7 - PHP7 module for the Apache 2.x webserver
>>>
>>> Now according to <https://code.mythtv.org/trac/ticket/12588> this
>>> version issue was encountered three years ago and was fixed in
>>> mythweb two years ago apparently in v0.27. So 0.28 should be OK.
>>>
>>> But when I look at
>>> mythweb-0.28.2+git.20180201.af896aee-lp150.1.1.src.rpm and
>>> specifically at mythweb.spec I see:
>>>
>>> # spec file for package mythweb-0_27
>>> #
>>> # Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany.
>>> # Copyright (c) 2011,2012 Herbert Graeber
>>>
>>> and
>>>
>>> Requires:   apache2-mod_php5
>>> Requires:   php5
>>> Requires:   php5-mysql
>>>
>>> I also see
>>>
>>> # Please submit bugfixes or comments via http://bugs.opensuse.org/
>>>
>>> So I think that an old spec file has been partially updated to a
>>> later release. Is it possible to update the requires as well please?
>>> Also, I'm not sure whether the opensuse bugzilla is still the
>>> correct place. There's no place I can specify a packman bug?
>>>
>>> ___
>>> Packman mailing list
>>> Packman@links2linux.de
>>> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>>
>>___
>>Packman mailing list
>>Packman@links2linux.de
>>http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] mythweb packaging error?

2018-07-23 Diskussionsfäden Dave Plater
I've just looked at the package and it now shows php7 requirements,
must have rebuilt.
Regards
Dave

On 7/22/18, Dave Howorth  wrote:
> Hello,
>
> First post. I think there's a packaging error in the mythweb package
> for Leap 15.0. I'm not sure how to report bugs for packman, so I'm
> trying here.
>
> When I try to install mythweb from packman (i.e.
> mythweb-0.28.2+git.20180201.af896aee-lp150.1.1.noarch.rpm) I see an
> error:
>
> nothing provides apache2-mod_php5
>
> But the only PHP module for apache from opensuse repositories seems to
> be v7: apache2-mod_php7 - PHP7 module for the Apache 2.x webserver
>
> Now according to  this
> version issue was encountered three years ago and was fixed in mythweb
> two years ago apparently in v0.27. So 0.28 should be OK.
>
> But when I look at
> mythweb-0.28.2+git.20180201.af896aee-lp150.1.1.src.rpm and specifically
> at mythweb.spec I see:
>
> # spec file for package mythweb-0_27
> #
> # Copyright (c) 2016 SUSE LINUX GmbH, Nuernberg, Germany.
> # Copyright (c) 2011,2012 Herbert Graeber
>
> and
>
> Requires:   apache2-mod_php5
> Requires:   php5
> Requires:   php5-mysql
>
> I also see
>
> # Please submit bugfixes or comments via http://bugs.opensuse.org/
>
> So I think that an old spec file has been partially updated to a later
> release. Is it possible to update the requires as well please? Also,
> I'm not sure whether the opensuse bugzilla is still the correct place.
> There's no place I can specify a packman bug?
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Bug: Package vlc for openSUSE Leap 15 doesn't create shortcuts in KDE's application launcher

2018-07-16 Diskussionsfäden Dave Plater
xine-ui and xine-libs aka. libxine2, haven't been updated since
January 23 Update to 1.2.9. and an update to 0.99.10 for xine-ui at
the same time.
The problem is most likely caused by a library that xine was built
against not being present on the problem system due to a 42.3 build
failure.

Dave

On 7/15/18, Timo Sigurdsson  wrote:
> Hi again,
>
>
> I got held up with other things in the meantime, but I finally got around to
> testing this more. It seems with current installs of Leap 15, I cannot
> reproduce this issue anymore on any filesystem (I tested btrfs, xfs and ext4
> again). So, it might have been fixed already in an update.
>
> Regards,
>
> Timo
>
> Hans-Peter Jansen schrieb am 05.06.2018 10:50:
>
>> On Dienstag, 5. Juni 2018 01:28:41 Timo Sigurdsson wrote:
>>> Hi Pete,
>>>
>>> Hans-Peter Jansen schrieb am 04.06.2018 11:19:
>>> > Since you changed the filesystems during install, I suspect, the issue
>>> > is
>>> > related. May I ask you to:
>>> >
>>> > 1) show us your /etc/fstab and "grep '/ ' /proc/mounts", please?
>>>
>>> Sure.
>>>
>>> $ cat /etc/fstab
>>> UUID=113c1ead-0f91-4c8c-88e9-1a72016c9af0  swap   swap  defaults
>>>
>>> 0  0 UUID=67915582-f239-4230-894f-0ffb7f982822  /
>>> ext4
>>>  acl,user_xattr   0  1
>>> UUID=1e6d57d4-d834-443f-b2f2-dcc798151c58  /home  ext4
>>> data=ordered,acl,user_xattr  0  2 UUID=6C9A-CC7B
>>>
>>>  /boot/efi  vfat  defaults 0  0
>>>
>>> $ grep '/ ' /proc/mounts
>>> /dev/sdb2 / ext4 rw,relatime,data=ordered 0 0
>>
>> Hmm, no esoteric mount options. That smells strongly like a bug.
>> Question is, in which area... Might be kernel (ext4, inotify), might be
>> dbus
>> or KF5 related.
>>
>>> > 2) (optionally) redo your test with btr or xfs as root (/usr) FS?
>>>
>>> I'll try to find time for that on the weekend.
>>
>> That will give us another important data point here.
>>
>> Thank you for your effort.
>>
>> Cheers,
>> Pete
>>
>>
>> ___
>> Packman mailing list
>> Packman@links2linux.de
>> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Xine + VLC beta don't play

2018-07-14 Diskussionsfäden Dave Plater
Which openSUSE version do you run?
Xine-ui-0.99.10-lp150.61.21 + (libxine2,
libxine2-codecs)-1.2.9-lp150.134.1, all from Packman, works for me on
Leap:15.0.

Best regards
Dave
xine maintainer openSUSE

On 7/13/18, Hartmut Krummrei  wrote:
> Hello,
>
> Since some time:
> "xine Videos/video.ext" where ext can be mpg, mp4, avi, webm
>
> gives this output:
> "Gleitkomma-Ausnahme (Speicherabzug geschrieben)"
>
> Was OK in May before my long journey. Now I updated ...
>
> I changed VLC-beta to VLC and that works. Dragon Player works too.
>
> --
> 
> "Ich habe keine besondere Begabung, sondern bin nur leidenschaftlich
> neugierig." (Einstein)
> spielmops.org 
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] flowblade on OpenSUSE Leap 15 crash on start-up

2018-05-26 Diskussionsfäden Dave Plater
Have you tried shotcut from openSUSE? If it fails you can file a bug
and assign it to me.
Dave

On 5/26/18, Ralf Nachtsheim  wrote:
> Hello,
>
> I installed
>
> flowblade-1.16-lp150.1.1.noarch.rpm
> flowblade-lang-1.16-lp150.1.1.noarch.rpm
>
> on fresh OpenSuse Leap 15 and have the following problem after
> starting with flowblade:
>
> ...
> MLT detection succeeded, 160 formats, 97 video codecs and 70 audio
> codecs found. 733 MLT services found.
> Loading render profiles...
> Loading filters...
> Brightness dropped, MLT version too low for this filter.
> Loading transitions...
> RGB Adjustment dropped for Color Adjustment
> Hue dropped for Color Adjustment
> Gamma dropped for Lift Gain Gamma
> G'MIC NOT found
> Natron not found
> Player initialized with profile:  DV/DVD PAL
> Selected color NOT detected
> BG color detected
> Create SDL1 consumer...
> [swscaler @ 0x7f241c379320] Warning: data is not aligned! This can lead
> to a speed loss Speicherzugriffsfehler (Speicherabzug geschrieben)
>
> Any idea, any other information needed?
>
> As far as I remember I had the same behavior on OpenSUSE 42.3. Is not
> so important - I need video software twice a year and I can use
> Openshot or kdenlive.
>
> But I liked flowblade in the past very well.
>
> best regards
>
> Ralf
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] GStreamer problems preventing MTP sync

2018-05-08 Diskussionsfäden Dave Plater
On 5/6/18, IBBoard  wrote:
> I've posted about this on the openSUSE forums[1], but no-one has been
> able to help me yet.
>
> My basic problem is that audio plays perfectly fine, but I can't sync
> music to my Android phone over MTP using Rhythmbox because of a
> GStreamer error.
>
>  From what I've been told then this is normally because of "mixing"
> openSUSE and Packman versions of GStreamer, but as I'm running openSUSE
> Tumbleweed then it seems to be impossible to avoid using Tumbleweeds
> GST-good and Packman's GST-Bad/Ugly.
>

You don't need any gst from Packman in Tumbleweed. As long as you have
gstreamer-plugins-libav all you need from packman are the ffmpeg
libraries.

Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] Request 4176 for xine-skins

2018-02-10 Diskussionsfäden Dave Plater
Hi I maintain multimedia:xine in obs and just noticed xine-skins
conflicts with xine-ui, I need to fix this. Please accept sr#4176
Thanks
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] [PM] libQtWebKit4 4.8.7+2.3.4-2.17 (openSUSE Tumbleweed/x86_64)

2018-02-05 Diskussionsfäden Dave Plater
libQtWebKit4 is being retired any package that requires it should have
it removed.
Dave

On 2/4/18, Sebastian  wrote:
> Hi,
>
> The package libQtWebKit4 is available in TW OSS repos too, in the same
> version. Leads to "problems" during zypper dup upgrades. Is there a
> reason to have the package in packman too?
>
> Sebastian
>
> --
> python programming - mail server - photo - video - https://sebix.at
> cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers
>
>
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Please disable audacity for Tumbleweed.

2017-12-17 Diskussionsfäden Dave Plater
Thanks, I've disabled and erased Tumbleweed.
Dave

On 12/17/17, Stefan Seyfried <stefan.seyfr...@googlemail.com> wrote:
> Hi Dave,
>
> Am 17.12.2017 um 13:41 schrieb Dave Plater:
>> Hi, can someone please disable the Tumbleweed build and wipe the
>> binaries of Multimedia:audacity or give me maintainer rights and I'll
>> do it myself.
>
> It looks like someone already did this:
>
> seife@susi:~> posc meta pkg Multimedia audacity
> 
>   A Free, Cross-Platform Digital Audio Editor
>   Audacity is a program that manipulates digital audio wave
> forms. In
> addition to recording sounds directly from within the program, it
> imports many sound file formats, including WAV, AIFF, AU, IRCAM, MP,
> and Ogg Vorbis.  With Audacity, you can edit wave data larger than the
> physical memory size of your computer.
> 
>   
>   
> 
> 
>   
> 
>
>> Thanks
>> Dave
>> user davepl
> --
> Stefan Seyfried
>
> "For a successful technology, reality must take precedence over
>  public relations, for nature cannot be fooled." -- Richard Feynman
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] Please disable audacity for Tumbleweed.

2017-12-17 Diskussionsfäden Dave Plater
Hi, can someone please disable the Tumbleweed build and wipe the
binaries of Multimedia:audacity or give me maintainer rights and I'll
do it myself.
Thanks
Dave
user davepl

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] qmmp 1.2 no longer plays mp3 files

2017-11-28 Diskussionsfäden Dave Plater
I just had a look at the package and it seems that
qmmp-plugin-pack-mpg123 is used for mp3 playback. I assume you are on
Tumbleweed because it no longer builds for Leaps.
Dave

On 11/28/17, Frank Steiner  wrote:
> Hi,
>
> just upgraded from qmmp 1.1.12 to 1.2 and it stopped playing mp3 files.
>
> Indeed, libmad.so and some others have vanished from /usr/lib64/qmmp/Input/
> and are no longer part of libqmmp-plugins.
>
> Am I missing some other package or did sth. go wrong with the build
> of qmmp 1.2?
>
> cu,
> Frank
>
> --
> Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
> Lehrstuhl f. BioinformatikMail: http://www.bio.ifi.lmu.de/~steiner/m/
> LMU, Amalienstr. 17   Phone: +49 89 2180-4049
> 80333 Muenchen, Germany   Fax:   +49 89 2180-99-4049
> * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Kodi doesn't play videos with latest ffmpeg

2017-11-23 Diskussionsfäden Dave Plater
Fixed kodi, confirmed by email. Submitted sr#4048
Dave

On 11/21/17, Dave Plater <davejpla...@gmail.com> wrote:
> Kodi is made to build with it's internal (from github.com/xbmc/FFmpeg)
> ffmpeg until kodi 1.8x is released which has been rewritten to build
> with ffmpeg 3.4.
> It already builds with "internal" libdvdcss, libdvdnav and libdvdread.
> These have become a problem since the internal ffmpeg build. These
> libs are statically linked.
> See the bug references at the beginning of this thread.
> Dave
>
> On 11/21/17, Olaf Hering <o...@aepfle.de> wrote:
>> On Tue, Nov 21, Dave Plater wrote:
>>
>>> What I don't understand is none of these are related to ffmpeg and why
>>> tis wasn't a problem before.
>>
>> Before we try to force a different libffmpeg into kodi, it must be
>> checked
>> if the other libraries in the kodi process make some use of libffmpeg.
>> If they do, there will be most likely a runtime conflict and kodi must
>> be fixed to work with "any" libffmpeg.
>>
>> In case of no conflict it is likely easier to build a private ffmpeg in
>> %_libdir/ffmpeg3x and build kodi with RPATH pointing to that directory.
>>
>>
>> Olaf
>>
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Kodi doesn't play videos with latest ffmpeg

2017-11-21 Diskussionsfäden Dave Plater
Kodi is made to build with it's internal (from github.com/xbmc/FFmpeg)
ffmpeg until kodi 1.8x is released which has been rewritten to build
with ffmpeg 3.4.
It already builds with "internal" libdvdcss, libdvdnav and libdvdread.
These have become a problem since the internal ffmpeg build. These
libs are statically linked.
See the bug references at the beginning of this thread.
Dave

On 11/21/17, Olaf Hering <o...@aepfle.de> wrote:
> On Tue, Nov 21, Dave Plater wrote:
>
>> What I don't understand is none of these are related to ffmpeg and why
>> tis wasn't a problem before.
>
> Before we try to force a different libffmpeg into kodi, it must be checked
> if the other libraries in the kodi process make some use of libffmpeg.
> If they do, there will be most likely a runtime conflict and kodi must
> be fixed to work with "any" libffmpeg.
>
> In case of no conflict it is likely easier to build a private ffmpeg in
> %_libdir/ffmpeg3x and build kodi with RPATH pointing to that directory.
>
>
> Olaf
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Kodi doesn't play videos with latest ffmpeg

2017-11-21 Diskussionsfäden Dave Plater
I've got past the libdvdcss configure error by requiring
pkgconfig(libidn2) for Tumbleweed. now I need to find out why
libdvdread configure fails to find libdvdcss.
What I don't understand is none of these are related to ffmpeg and why
tis wasn't a problem before.
Dave

On 11/20/17, Andrei Dziahel  wrote:
> Hi Sagi,
>
> Unfortunately latest kodi RPM requires libva-x11.so.1()(64bit) thus
> being uninstallable to regular (well, my) Tumbleweed.
>
> In the meantime, could you take a look at attempt (unsuccessful so
> far) to build kodi with Kodi-compatible patched ffmpeg at
> https://pmbs.links2linux.de/package/show/home:develop7:branches:Multimedia/kodi?
>
> Thank you in advance.
>
> 2017-11-07 0:20 GMT+03:00 Sagi Ben-Akiva :
>> Hi Peter,
>>
>> Kodi for openSUSE is build against ffmpeg from openSUSE repositories and
>> not from Kodi source.
>> I pushed an update to my repo
>> https://pmbs.links2linux.de/package/show/home:sagiben/kodi
>> you can try it, once the build finish.
>>
>> Sagi.
>>
>>
>>
>> On Sun, Nov 5, 2017 at 2:46 PM, Peter Snauwaert
>> 
>> wrote:
>>
>>> Hi,
>>>
>>> I noticed Kodi is no longer able to play videos. It was suggested on the
>>> Kodi forum that this could be the reason:
>>> https://github.com/xbmc/xbmc/commit/5ba6eb7cadc41d5eb86ef94e3661b8
>>> 33b62953ff
>>>
>>> From that link:
>>> # required ffmpeg library versions
>>> +# note to distro maintainers:
>>> +# only ffmpeg 3.1 is supported for Krypton!
>>> +# our ffmpeg 3.1 version carries two important patches:
>>> https://github.com/xbmc/FFmpeg/commits/release/3.1-xbmc
>>> set(REQUIRED_FFMPEG_VERSION 3.1)
>>>
>>> How can I work around this until it does work with the latest ffmpeg?
>>>
>>> thanks
>>> ___
>>> Packman mailing list
>>> Packman@links2linux.de
>>> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>>>
>> ___
>> Packman mailing list
>> Packman@links2linux.de
>> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>
>
>
> --
> Regards,
> Andrei Dziahel
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] [PM] gstreamer-0_10-plugins-ugly 0.10.19-20.1 (openSUSE_Leap 42.1/x86_64)

2017-11-09 Diskussionsfäden Dave Plater
Your subject states openSUSE_Leap 42.1/x86_64 but you say you are a
Leap:42.3 user.
For a full multimedia playback in Leap:42.3 you only need to install
gstreamer-plugins-libav and ffmpeg from Packman the rest of the
packages can come from openSUSE official repositories and the update
repo. The easiest installation medium is Yast2, the control panel has
applets for registering the update repository, performing an update,
managing repositories and installing additional software.
These applets are:
"Online Update Configuration", "Online Update", "Software
Repositories" and "Software Management"
Under "Software Repositories" > Add > Next > Give a name to the repo
and paste in:
"http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_42.3/; >
Next and the Packman repository is added.

Regards
Dave

On 11/8/17, Vicente Crestani  wrote:
> Hi,here is my problem, I am an openSUSE LEAP 42.3 user and I cannot
> enter the FAQ thread of UBUNTU1 to ask for some help.
>
> Therefore, I wondered if you could help me directly?
>
> Anyhow, this is my issue: I tried to use the ONEclick install for the
> gstreamer plugin (as you can surely see ;D) on three attempts: 1 time,
> the install was not successful, the second time it seemed to be all
> right but then when I tried to use Sound converter, the plugin didn't
> seem to have done the job I assumed it should do and the third time
> same story as the second time. If you don't find the time to help me
> out or don't wanna I would be thrilled if you could point me to a
> reliable source of information on the subject. This what the
> "successful" installing process looked like:
>
>
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Ruby] bin/y2start:16 y2base
> called with ["OneClickInstallUI", "--arg",
> "/tmp/mozilla_Vanadium0/gstreamer-0_10-plugins-ugly.ymp", "qt"]
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [ui-component]
> YUIComponentCreator.cc(createInternal):124 Creating UI component for ""
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Interpreter] bin/y2start:56
> Calling YaST client OneClickInstallUI
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Ruby] yast/wfm.rb:295 Call
> client /usr/share/YaST2/clients/OneClickInstallUI.rb
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> PkgModule.cc(instance):68 Redirecting ZYPP log to y2log
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Ruby]
> modules/PackageCallbacks.rb:135 PackageCallbacks constructor
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2631 Pkg Builtin called:
> CallbackProcessStart
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2634 Pkg Builtin called:
> CallbackProcessProgress
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2637 Pkg Builtin called:
> CallbackProcessNextStage
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2640 Pkg Builtin called:
> CallbackProcessDone
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2646 Pkg Builtin called:
> CallbackStartProvide
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2649 Pkg Builtin called:
> CallbackProgressProvide
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2652 Pkg Builtin called:
> CallbackDoneProvide
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2655 Pkg Builtin called:
> CallbackStartPackage
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2661 Pkg Builtin called:
> CallbackProgressPackage
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2664 Pkg Builtin called:
> CallbackDonePackage
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2672 Pkg Builtin called:
> CallbackStartDeltaDownload
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2675 Pkg Builtin called:
> CallbackProgressDeltaDownload
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2678 Pkg Builtin called:
> CallbackProblemDeltaDownload
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2681 Pkg Builtin called:
> CallbackFinishDeltaDownload
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2685 Pkg Builtin called:
> CallbackStartDeltaApply
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2688 Pkg Builtin called:
> CallbackProgressDeltaApply
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2691 Pkg Builtin called:
> CallbackProblemDeltaApply
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2694 Pkg Builtin called:
> CallbackFinishDeltaApply
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> modules/PackageCallbacks.rb:2583 Pkg Builtin called:
> CallbackSourceCreateStart
> 2017-11-08 11:58:29 <1> linux-m5ea(4591) [Pkg]
> 

Re: [packman] xlocale.h problems in kodi.binary-addons (was: Re: Kodi 17.4 - any chance to submit it to Multimedia?)

2017-10-02 Diskussionsfäden Dave Plater
On 9/29/17, Manfred Hollstein <manfre...@gmx.net> wrote:
> Hi Dave,
>
> On Fri, 29 Sep 2017, 15:56:39 +0200, Dave Plater wrote:
>> I think it's fixed but the build is now blocked for Tumbleweed.
>
> thanks a lot for your effort! If I'm not mistaken, your version is for
> Kodi 17.3, isn't it? I was rather hoping to finally get version 17.4 ;)
>
> But the fixes you have applied are probably very similar to those needed
> to get 17.4 going.
>
>> Dave
>
> Cheers.
>
> l8er
> manfred
>
Finally fixed now someone must accept sr#3982
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] xlocale.h problems in kodi.binary-addons (was: Re: Kodi 17.4 - any chance to submit it to Multimedia?)

2017-09-29 Diskussionsfäden Dave Plater
I think it's fixed but the build is now blocked for Tumbleweed.
Dave

On 9/29/17, Dave Plater <davejpla...@gmail.com> wrote:
> On 9/29/17, Dave Plater <davejpla...@gmail.com> wrote:
>> On 9/29/17, Manfred Hollstein <manfre...@gmx.net> wrote:
>>> On Fri, 29 Sep 2017, 08:42:36 +0200, Dave Plater wrote:
>>>> [...]
>>>> Look at home:davepl/kodi.binary-addons, the xlocale.h error is fixed
>>>> but there's more errors that are possibly gcc7 errors.
>>>
>>> <https://pmbs.links2linux.org/public/build/home:davepl/openSUSE_Tumbleweed/x86_64/kodi.binary-addons/_log>:
>>>
>>> there is only one error: in your build log, too, and it's the exact same
>>> as in Sagi's one?!? So, there is no fix for xlocale.h afaics.
>>>
>>>> Dave
>>>
>>> Cheers.
>>>
>>> l8er
>>> manfred
>>>
>> That's strange, yesterday it passed the xlocale.h error and got to a
>> std:: something error.
>> I'll look a bit harder, it's very difficult to work with as Locale.hh
>> is only generated by cmake.
>> I'll have to patch Locale.hh after cmake.
>> Dave
>>
> Ok now it goes to :
> error: 'std::function' has not been declared as it did yesterday don't
> know what changed. The -DXLOCALE_NOT_USED=1 build flag is rejected by
> cmake. Anyway that error is fixed by #include  while I'm
> on a roll might as well try and fix that.
> Dave
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] xlocale.h problems in kodi.binary-addons (was: Re: Kodi 17.4 - any chance to submit it to Multimedia?)

2017-09-29 Diskussionsfäden Dave Plater
On 9/29/17, Manfred Hollstein <manfre...@gmx.net> wrote:
> On Fri, 29 Sep 2017, 08:42:36 +0200, Dave Plater wrote:
>> [...]
>> Look at home:davepl/kodi.binary-addons, the xlocale.h error is fixed
>> but there's more errors that are possibly gcc7 errors.
>
> <https://pmbs.links2linux.org/public/build/home:davepl/openSUSE_Tumbleweed/x86_64/kodi.binary-addons/_log>:
>
> there is only one error: in your build log, too, and it's the exact same
> as in Sagi's one?!? So, there is no fix for xlocale.h afaics.
>
>> Dave
>
> Cheers.
>
> l8er
> manfred
>
That's strange, yesterday it passed the xlocale.h error and got to a
std:: something error.
I'll look a bit harder, it's very difficult to work with as Locale.hh
is only generated by cmake.
I'll have to patch Locale.hh after cmake.
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] xlocale.h problems in kodi.binary-addons (was: Re: Kodi 17.4 - any chance to submit it to Multimedia?)

2017-09-29 Diskussionsfäden Dave Plater
On 9/29/17, Manfred Hollstein <manfre...@gmx.net> wrote:
> Hi David,
>
> On Wed, 27 Sep 2017, 09:16:06 +0200, Dave Plater wrote:
>> On 9/26/17, Manfred Hollstein <manfre...@gmx.net> wrote:
>> > Hi Sagi,
>> >
>> > do you have an update on this issue? AFAICS, the xlocale.h issue still
>> > seems to be in error.
>> >
>> > TIA, cheers.
>> >
>> > l8er
>> > manfred
>> >
>> > On Wed, 06 Sep 2017, 08:57:30 +0200, Manfred Hollstein wrote:
>> >> Moin,
>> >>
>> >> On Thu, 31 Aug 2017, 06:13:41 +0200, Sagi Ben-Akiva wrote:
>> >> > Hi,
>> >> >
>> >> > Work in progress :
>> >> > https://pmbs.links2linux.org/package/show/home:sagiben/kodi
>> >> >
>> >> > but still have a build issue with the binary addons
>> >>
>> >> the issue appears to happen because the include file xlocale.h has
>> >> been
>> >> removed from the latest glibc release. There was a discussion about
>> >> this
>> >> on the opensuse-factory mailing list where Dave Plater described the
>> >> problem, his findings and a solution in the end. Perhaps reading the
>> >> thread at
>> >>
>> >>   <https://lists.opensuse.org/opensuse-factory/2017-08/msg00551.html>
>> >>
>> >> helps with your problem, too.
>> >
>> I just had a quick look and the xlocale.h issue is easily solved by
>> adding -DXLOCALE_NOT_USED=1 as stated in Locale.hh but although this
>> doesn't affect the 42.2/3 build there are more errors to be fixed,
>> possibly gcc7 errors. Needs to be done by someone who knows the build.
>
> I'm not sure about any gcc7 errors, because the only "error:" shown in
> the build log is this:
>
>   In file included from
>
> /home/abuild/rpmbuild/BUILD/xbmc-17.4-Krypton/project/cmake/addons/build/pvr.mediaportal.tvserver/src/lib/live555/liveMedia/Locale.cpp:22:0:
>
> /home/abuild/rpmbuild/BUILD/xbmc-17.4-Krypton/project/cmake/addons/build/pvr.mediaportal.tvserver/src/lib/live555/liveMedia/include/Locale.hh:47:10:
> fatal error: xlocale.h: No such file or directory
>
> It may be there once this is fixed there will be more errors, but so far
> I cannot see that his is gcc7 related.
>
>> Dave Plater
>
> Cheers.
>
> l8er
> manfred
>
Look at home:davepl/kodi.binary-addons, the xlocale.h error is fixed
but there's more errors that are possibly gcc7 errors.
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] xlocale.h problems in kodi.binary-addons (was: Re: Kodi 17.4 - any chance to submit it to Multimedia?)

2017-09-27 Diskussionsfäden Dave Plater
On 9/26/17, Manfred Hollstein <manfre...@gmx.net> wrote:
> Hi Sagi,
>
> do you have an update on this issue? AFAICS, the xlocale.h issue still
> seems to be in error.
>
> TIA, cheers.
>
> l8er
> manfred
>
> On Wed, 06 Sep 2017, 08:57:30 +0200, Manfred Hollstein wrote:
>> Moin,
>>
>> On Thu, 31 Aug 2017, 06:13:41 +0200, Sagi Ben-Akiva wrote:
>> > Hi,
>> >
>> > Work in progress :
>> > https://pmbs.links2linux.org/package/show/home:sagiben/kodi
>> >
>> > but still have a build issue with the binary addons
>>
>> the issue appears to happen because the include file xlocale.h has been
>> removed from the latest glibc release. There was a discussion about this
>> on the opensuse-factory mailing list where Dave Plater described the
>> problem, his findings and a solution in the end. Perhaps reading the
>> thread at
>>
>>   <https://lists.opensuse.org/opensuse-factory/2017-08/msg00551.html>
>>
>> helps with your problem, too.
>
I just had a quick look and the xlocale.h issue is easily solved by
adding -DXLOCALE_NOT_USED=1 as stated in Locale.hh but although this
doesn't affect the 42.2/3 build there are more errors to be fixed,
possibly gcc7 errors. Needs to be done by someone who knows the build.
Dave Plater

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] Transcode fails to build

2017-07-22 Diskussionsfäden Dave Plater
Hi, transcode now fails to build due to the removal of a patch and
mm_accel.h from a52dec.
Regards
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] FFmpeg build options

2017-06-27 Diskussionsfäden Dave Plater
On 6/28/17, Dave Plater <davejpla...@gmail.com> wrote:
> On 6/27/17, Wolfgang Bauer <e9325...@student.tuwien.ac.at> wrote:
>> Am Donnerstag, 22. Juni 2017, 11:34:03 CEST schrieb Martin Herkt:
>>> Is there any reason why FFmpeg is built with --disable-cuda and
>>> --disable-cuvid? Neither requires NVIDIA SDK headers anymore—it’s loaded
>>> at
>>> runtime. I’d like to use those features.
>>
>> It causes problems for non-NVIDIA users. See the package changelog:
>> * Wed May 31 2017 davejpla...@gmail.com
>> - Disable cuda extensions to fix boo#1041794:
>>   ffmpeg 3.3 enablement of h264_cuvid causes browsers not to select
>>   webm
>>
>> And the bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1041794
>>
>> Kind Regards,
>> Wolfgang
>>
>>
> I've enabled cuvid and nvidia and submitted to Factory but
> unfortunately the 42.2 update version remains without it. The above
> bug doesn't affect browsers if the full version of ffmpeg is installed
> they only attempt to use the cuvid codec if there isn't an
> alternative. The other bug concerning the full ffmpeg version which
> only affected users with nvidia hardware was fixed in
> gstreamer-plugins-libav.
> Best regards
> Dave
>
The full version of Tumbleweed ffmpeg will have cuvid and cuda when it
is accepted.
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] FFmpeg build options

2017-06-27 Diskussionsfäden Dave Plater
On 6/27/17, Wolfgang Bauer  wrote:
> Am Donnerstag, 22. Juni 2017, 11:34:03 CEST schrieb Martin Herkt:
>> Is there any reason why FFmpeg is built with --disable-cuda and
>> --disable-cuvid? Neither requires NVIDIA SDK headers anymore—it’s loaded
>> at
>> runtime. I’d like to use those features.
>
> It causes problems for non-NVIDIA users. See the package changelog:
> * Wed May 31 2017 davejpla...@gmail.com
> - Disable cuda extensions to fix boo#1041794:
>   ffmpeg 3.3 enablement of h264_cuvid causes browsers not to select
>   webm
>
> And the bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1041794
>
> Kind Regards,
> Wolfgang
>
>
I've enabled cuvid and nvidia and submitted to Factory but
unfortunately the 42.2 update version remains without it. The above
bug doesn't affect browsers if the full version of ffmpeg is installed
they only attempt to use the cuvid codec if there isn't an
alternative. The other bug concerning the full ffmpeg version which
only affected users with nvidia hardware was fixed in
gstreamer-plugins-libav.
Best regards
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Package 4pane fails to upgrade (4pane-4.0-4.14.x86_64.rpm)

2017-04-27 Diskussionsfäden Dave Plater
I've submitted to Extra/4pane sr#3792

Dave

On 4/27/17, Carlos E. R.  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> Hi,
>
> I get:
>
> Telcontar:/var/cache/zypp/packages.link # rpm --upgrade --verbose
> EXT_Packman/Extra/x86_64/4pane-4.0-4.14.x86_64.rpm
> Preparing packages...
> 4pane-4.0-4.14.x86_64
> error: unpacking of archive failed on file
> /usr/share/4Pane/bitmaps/DnDSelectedCursor.png;590129b3: cpio: link
> error: 4pane-4.0-4.14.x86_64: install failed
> error: 4pane-4.0-2.3.x86_64: erase skipped
> Telcontar:/var/cache/zypp/packages.link #
>
>
> An strace reveals:
>
> utime("/usr/share/locale/vi/LC_MESSAGES/4Pane.mo", [2017/04/20-19:34:14,
> 2017/04/20-19:34:14]) = 0
> getuid()= 0
> umask(0777) = 022
> open("/usr/share/doc/packages/4Pane/DnDSelectedCursor.png;590129e9",
> O_WRONLY|O_CREAT|O_TRUNC, 0666) = 21
> fcntl(21, F_SETFD, FD_CLOEXEC)  = 0
> umask(022)  = 0777
> write(21,
> "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\0\20\0\0\0\20\10\6\0\0\0\37\363\377"...,
> 181) = 181
> close(21)   = 0
> link("/usr/share/doc/packages/4Pane/DnDSelectedCursor.png;590129e9",
> "/usr/share/4Pane/bitmaps/DnDSelectedCursor.png;590129e9") = -1 EXDEV
> (Invalid cross-device link)
> lstat("/usr/share/doc/packages/4Pane/DnDSelectedCursor.png;590129e9",
> {st_mode=S_IFREG, st_size=181, ...}) = 0
> unlink("/usr/share/doc/packages/4Pane/DnDSelectedCursor.png;590129e9") = 0
> munmap(0x7f7e2116b000, 8392704) = 0
> close(20)   = 0
> munmap(0x7f7e24ccb000, 4096)= 0
> write(2, "error: ", 7)  = 7
> write(2, "unpacking of archive failed on f"..., 104) = 104
> close(19)   = 0
> write(2, "error: ", 7)  = 7
> write(2, "4pane-4.0-4.14.x86_64: install f"..., 38) = 38
> write(2, "error: ", 7)  = 7
> write(2, "4pane-4.0-2.3.x86_64: erase skip"..., 36) = 36
> umask(022)  = 022
> close(4)= 0
>
>
>
> The problem is that the package is using now hardlinks, across devices, and
> of course, it fails.
> This did not happen previously, on 4pane-4.0-4.9.x86_64.rpm
>
>
>
> - --
> Cheers,
> Carlos E. R.
> (from 42.2 x86_64 "Malachite" at Telcontar)
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iEYEARECAAYFAlkBLPgACgkQtTMYHG2NR9UmSACaAiouvEPdIpZ+fP9mu1CmG3mn
> aR8An3xRCqNHD4Kl+VQwpMFXT6SNGcT3
> =yOvF
> -END PGP SIGNATURE-
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Warning I'm submitting dvdauthor to openSUSE

2017-04-06 Diskussionsfäden Dave Plater
I think that some packages couldn't use the new version, I'm going
through the dependent packages. So far I've updated 360_burn and am
busy with opendvdproducer. dvdshrink no longer supplies source and
devede should be deleted, it was replaced by devedeng a long time ago.
Maybe the old dvdauthor is needed for dvdshrink. The biggest problem
is these packages only require dvdauthor and old packages may not work
with the new dvdauthor.

Dave

On 4/6/17, Olaf Hering <o...@aepfle.de> wrote:
> Am Wed, 5 Apr 2017 12:26:10 +0200
> schrieb Dave Plater <davejpla...@gmail.com>:
>
>> I don't understand why all these packages are still using a very old
>> dvdauthor but if it's necessary then the old dvdauthor should be named
>> dvdauthor06.
>
> dvdauthor07 Provides/Obsoletes dvdauthor, so I'm sure everyone already runs
> this version. Its unclear why dvdauthor07 was introduced, osc log gives no
> hints about what has happened back in 2011.
>
> Olaf
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Please link Factory flac for 42.1/2 and suil for 42.1 New Audacity needs them to build.

2017-03-23 Diskussionsfäden Dave Plater
C++ built libraries have a tendancy to change at every release. They
should all have three digit sonames IMHO. I'll patch flac in the near
future. The strange thing is the audacity developer that builds with
Ubuntu 14.04 claimed that "my system libflac is claimed as
"1.3.0-2ubuntu0.14.04.1"
which again I can build Audacity against.".

Dave

On 3/23/17, Olaf Hering <o...@aepfle.de> wrote:
> Am Wed, 22 Mar 2017 08:18:07 +0100
> schrieb Olaf Hering <o...@aepfle.de>:
>
>> Am Wed, 22 Mar 2017 07:19:27 +0200
>> schrieb Dave Plater <davejpla...@gmail.com>:
>>
>> > Audacity-2.1.3 needs flac > 1.3.0 in Leap:42.1 and 2 also suil > 0.8.1
>> > to build for 42.1
>>
>> How does upstream justify the requirement for a newer flac?
>> Does it fail to build/run with 1.3.0?
>
> flac is now a _link to Factory.
>
> I wonder if the C++ part is really ABI compatible. At least chromium seems
> to buildrequire flac++. But this command finds only a few other pkgs:
>
> zypper se -snt package --requires 'libFLAC++.so.6()(64bit)'
>
> So its probably just about those few we need to worry about.
>
> Olaf
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Why isn't mediainfo in openSUSE

2017-02-27 Diskussionsfäden Dave Plater
Thanks, I just wondered why it was never submitted before, I accepted
libmediainfo and libzen yesterday.

Dave

On 2/27/17, Martin Pluskal <mar...@pluskal.org> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2017-02-27 at 10:25 +0200, Dave Plater wrote:
>> Hi, does anybody know of a valid legal reason why mediainfo can't be
>> in openSUSE distribution?
>> Thanks
>> Dave Plater
> Not sure about reasons why it was not, but its being submitted now:
> https://build.opensuse.org/request/show/460559
> https://build.opensuse.org/request/show/460566
> https://build.opensuse.org/request/show/460565
>
> Cheers
>
> M
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEwQnJ+Ps8HqIKhK3yWyRdZ/3eaFcFAliz7JEACgkQWyRdZ/3e
> aFcTSw//RLiGIU4M12S+XxDMHahA5//sp/eeF+EHzvp7OBgRBP9tHVGn40AryVpx
> vtRdgU8bBa1PxhGCXMs88QGrsGdPWY5jM943irUHTMbPxgwy4Nprbsn7qMqF4fEw
> 8UfXnETsxhTvCNt/TWaIz3tpSMYt/X5lM6HYeD2oif4pYl7IMTGFIOaVgnKcqifo
> uP/68CY0dCcrx4vja96sQSnhYXTCR9QB73mZCD2Kb0w5iKygZA4PHdEvHeK4nj0Y
> koY32lc8P9427LfPP2rn27KmYCNPfnAIaA1Q9JmqprvzG6FcxT1i5QhFuYWlAvEN
> X30/gpy3jBClYlAUpK/jgY+5rQQ2eLI2lM7WhJ/ARO8dZgYL2D1HRbmGfzkPAVhm
> wCNFFanQfBNZ9+GXRL8ulzxB2jftUTP+9NEiSW5Q683V02+5okmiGSl2wLgIeb7F
> AdVJDkdPqJ4LglAnzT5TPIE2r5dpueZedeeei437MsSGHzqBseSCKWLgpiwMEha9
> Dh1hcr/J67/1rB7372ooPdK7W87NKBvvyh5n4Ak0K7qTQItxmDcJsaqzZJzTUcK/
> vuHy+APeSCc1FMrP90G19cmtQhQY70PRjq9QVwbMIGfHWyiU78vm/8IsfvB78is6
> Nq0HwFM+6IRvS5ch2YwEHsMkTDAxJBdEmjkb1ccxT4n4dJYZkX8=
> =Y0fO
> -END PGP SIGNATURE-
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] Why isn't mediainfo in openSUSE

2017-02-27 Diskussionsfäden Dave Plater
Hi, does anybody know of a valid legal reason why mediainfo can't be
in openSUSE distribution?
Thanks
Dave Plater

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] what happened to libslv2?

2017-02-23 Diskussionsfäden Dave Plater
AFAIR multimedia:libs/lv2 replaced slv2 but that was around 2012,
don't know what happened to the Packman one. There shouldn't be
anything building against it, I introduced it to openSUSE
multimedia:libs.
Dave

On 2/22/17, Mathias Homann  wrote:
> Hi,
>
> whatever happened to the slv2 package?
>
> I have this installed on my system:
>
> kirika:~ # rpm -qi libslv2-9
> Name: libslv2-9
> Version : 0.6.6
> Release : 4.7
> Architecture: x86_64
> Install Date: Fri Dec 16 22:29:23 2016
> Group   : System/Libraries
> Size: 56592
> License : GPLv2+
> Signature   : RSA/SHA1, Thu Dec 15 17:30:36 2016, Key ID 45a1d0671abd1afb
> Source RPM  : slv2-0.6.6-4.7.src.rpm
> Build Date  : Thu Dec 15 11:23:04 2016
> Build Host  : swkj16
> Relocations : (not relocatable)
> Packager: packman@links2linux.de
> Vendor  : http://packman.links2linux.de
> URL : http://drobilla.net/software/slv2/
> Summary : Library for slv2
> Description :
> The libslv2-9 package contains the slv2 library.
> Distribution: Essentials / openSUSE_Leap_42.2
>
>
> ...but it is not on packman anymore! and uninstalling it from my system
> would
> uninstall all number of gstreamer related stuff, and also any number of apps
>
> that use gstreamer...
>
> Where did that package disappear to?
>
> cheers
> MH
>
> --
> gpg key fingerprint: 5F64 4C92 9B77 DE37 D184  C5F9 B013 44E7 27BD 763C
>
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Packaging request - VidCutter

2017-02-15 Diskussionsfäden Dave Plater
>Those files also have a sync problem, but I have an ffmpeg command that 
>corrects it. Let's see >if I can find it... It would be another way to process 
>with vidcutter, use the already processed >stream.
A quick fix for sync problems, should be embedded in future ffmpeg
versions, is to start your ffmpeg command with ffmpeg -fflags genpts

Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] DVDStyler with dvdisaster

2017-01-11 Diskussionsfäden Dave Plater
Hi, I've recreated the dvdisaster package for DVDStyler but it's
sr#3191 has been waiting for 5 days so far. Any reason?
Thanks
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] [PM] transcode 1.1.7-2.3 (openSUSE_Leap 42.1/x86_64)

2016-10-31 Diskussionsfäden Dave Plater
I'll look into this during the week.
Dave

On 10/30/16, pit  wrote:
>
>   Hi,
>
> I am converting DVDs to TS streams for VDR.  One step is conversion of the
> AC3 audio track to stereo mp2.
> I am using transcode from the Multimdia repository for Leap 42.1
> This fails if the output file contains special characters, because the
> spawned command is not properly escaped (on the input side it is!)
>
> Here's the snippet of the code:
>
> TITLE="19_Angriff_der_Aliens_(2)"
> VSCALE=2.082
> transcode -i "${TITLE}.ac3" -o "${TITLE}.mp2" -x null,ac3 -y null,mp2 -s
> $VSCALE
> transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team
> 
> [transcode] V: auto-probing | 19_Angriff_der_Aliens_(2).ac3 (OK)
> [transcode] V: import format| (null) in AC3 (module=null)
> [transcode] A: auto-probing | 19_Angriff_der_Aliens_(2).ac3 (OK)
> [transcode] A: import format| AC3 in AC3 (module=ac3)
> .
> [import_ac3.so] AC3->PCM
> [import_ac3.so] tcextract -a 0 -i "19_Angriff_der_Aliens_(2).ac3" -x ac3 -d
> 0 | tcdecode -x ac3 -d 0 -s 1.00,1.00,1.00 -A 0
> [export_mp2.so] ffmpeg -y -f s16le -ac 2 -ar 48000 -i - -ab 128k -ar 48000
> -f mp2 19_Angriff_der_Aliens_(2).mp2.mpa >/dev/null 2>&1
> sh: -c: line 0: syntax error near unexpected token `('
>
> The import thread properly protects the () by placing the filename in "".
> export_mp2 does not, and the command fails
>
>
> --
> Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit
> Institute for Solar Physics
> Tel.: +34 922 405 590  (Spain) p.suetter...@royac.iac.es
>   +46 8 5537 8559  (Sweden)peter.suetter...@astro.su.se
>
> ___
> Packman mailing list
> Packman@links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
>

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] ffmpeg & gstreamer mess

2016-07-22 Diskussionsfäden Dave Plater
On 7/22/16, Sergey Kondakov <virtuous...@gmail.com> wrote:
> On 20.06.2016 00:36, Richard Brown wrote:
>> On 19 June 2016 at 16:41, Dave Plater <davejpla...@gmail.com> wrote:
>>>> The pkg in multimedia:libs is about one hundred, thousand, million
>>>> times more at risk of being broken than the pkg in Factory
>>>
>>> Not if it's well maintained
>>
>> There is _NO SUCH THING_ as a well maintained Devel Project.
>>
>> https://en.opensuse.org/openSUSE:Factory_development_model
>>
>> They EXIST to be where things are put together, broken and ultimately
>> fixed before being submitted to Factory for testing into Tumbleweed
>>
>> A Devel Project which doesn't break from time to time is not doing
>> it's job properly.
>>
>
> You may repeat that as long as you like just to make en excuse for your
> team's
> bad maintenance practices of OBS but no actual user will ever believe that.
> Also, minuscule and specific testing in virtual machines or whatever you do
> in
> that "openQA" has never saved from actual problems even while using 100%
> official packages. Probably not because it's bad but because it's not enough
> to
> negate dumb human decisions, overcomplex bureaucracy with the lack of
> well-structured up-to-date human-readable guides to deal with it, lack of
> actual
> usage and belief that your dysfunctional defaults (once again, screw KDE5,
> Gnome3, VLC, pulseaudio, wicked, kernel-default and, especially, BTRFS !) is
> the
> one and only way to do things.
>
>>>>
>>>> Because it's a devel project, where packages are MEANT to be broken
>>>> from time to time, meanwhile we KNOW the ffmpeg packages in Factory
>>>> work as they get tested in openQA as part of the VLC testing.
>>>>
>>>> I've said it before and I'll say it again Packman building against
>>>> multimedia:libs has always been silly
>>>
>>> Once Packman packages weren't linked and that resulted in many
>>> problems with incompatible libraries and out of sync maintenance.
>>
>>
>> In short, this is dangerous, wrong, stupid and downright idiotic.. and
>> I'm being polite and holding back what i really think about it.
>>
>> At the very LEAST ffmpeg in Packman should be linked to
>> Factory/Tumbleweed
>>
>> Packman for Leap should be linked to the version in Leap, so that
>> users do not have to suffer needless risk upgrading their packages.
>
> For once we agree ! Building anything against non-official repo version of
> something so fundamental as ffmpeg is almost as idiotic and irresponsible as
>
> removing distribution installer from the official repo of that
> distribution.
> -
> Instead, "TW" should get kick in the ass to update its ffmpeg version.
>
> VLC and mpv aren't the only packages depending on it, you know ! But then
> again,
> we're talking about the people who seem to removed 32bit gstreamer packages
> from
> Packman's TW repo even though wine's A/V capabilities are dependant upon
> them.
> And because of things like that whole wine bugtracker is filled with
> complaints
> for years ( https://bugs.winehq.org/show_bug.cgi?id=9127 ) from users who's
>
> distribution doesn't build it properly. Goodbye, pre-rendered cutscenes in
> games
> and multimedia applications in general.
> -
> Why the hell there is there "Factory" and "TW" repoes with different
> configuration and packages ? Which one a normal person should use ?
>
> You both, TW team and Packman team, are at fault here.
> * Just update ffmpeg in TW.
> * Link ffmpeg and gstreamer and any other
>framework for each distro independently.
> * Work on better unnecessary rebuild-avoidance for OBS.
> * Whatever commercial entity owns openSUSE should buy Packman servers,
> since
>it purposely made any openSUSE desktop installation 100% dependant upon
> it.
>Novell had a Russian office, Russian law spits on software patenting,
>they can have them there legally.
>
> I would say that if anything happens with Packman then, most likely,
> openSUSE
> will lose all its non-server installations.
>
>>> Packman is a safe way for users to get the newest packages, especially
>>> Leap users because it rarely gets new packages. It's a pity somebody
>>> doesn't donate some extra server power to Packman to speed up the
>>> build cycle. Maintaining the Packman packages in multimedia apps and
>>> libs has taken away the old volatility that used to come from Packman.
>>> It's a far better option to enabling multiple obs repositories fo

[packman] Need help debuging DVDStyler SIGSEGV

2016-07-02 Diskussionsfäden Dave Plater
I'm trying to find out the reason for a user's Tumbleweed DVDStyler SIGSEGV at :
(gdb) run
Starting program: /usr/bin/dvdstyler
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffddb07700 (LWP 24425)]
[New Thread 0x7fffdd306700 (LWP 24426)]
[New Thread 0x7fffdcb05700 (LWP 24427)]
[New Thread 0x7fffc700 (LWP 24428)]
[Thread 0x7fffdcb05700 (LWP 24427) exited]

Thread 1 "dvdstyler" received signal SIGSEGV, Segmentation fault.
0x74a01ed8 in wxSVGCanvasPathCairo::GetResultBBox (this=0x11d1ef0,
style=..., matrix=...) at SVGCanvasPathCairo.cpp:57
57  cairo_matrix_init(, matrix.GetA(),
matrix.GetB(), matrix.GetC(), matrix.GetD(), matrix.GetE(),
matrix.GetF());

(gdb) bt
#0  0x74a01ed8 in
wxSVGCanvasPathCairo::GetResultBBox(wxCSSStyleDeclaration const&,
wxSVGMatrix const&) (this=0x11d1ef0, style=..., matrix=...)
at SVGCanvasPathCairo.cpp:57
#1  0x74a0273b in wxSVGCanvasTextCairo::InitText(wxString
const&, wxCSSStyleDeclaration const&, wxSVGMatrix*) (this=0x11d1d00,
text=..., style=..., matrix=) at
SVGCanvasTextCairo.cpp:136
#2  0x749de277 in wxSVGCanvasText::AddChunk(wxString const&,
wxCSSStyleDeclaration const&, wxSVGMatrix*) (this=0x11d1d00, text=...,
style=..., matrix=0x0) at SVGCanvasItem.cpp:1122
#3  0x749e145a in
wxSVGCanvasText::InitChildren(wxSVGTextPositioningElement&,
wxCSSStyleDeclaration const&, wxSVGMatrix*) (this=0x11d1d00,
element=..., style=..., matrix=0x0) at SVGCanvasItem.cpp:1099
#4  0x749d974f in wxSVGCanvasText::Init(wxSVGTextElement&,
wxCSSStyleDeclaration const&, wxSVGMatrix*) (this=0x11d1d00,
element=..., style=..., matrix=0x0) at SVGCanvasItem.cpp:1035
#5  0x74a017d8 in
wxSVGCanvasCairo::CreateItem(wxSVGTextElement*, wxCSSStyleDeclaration
const*, wxSVGMatrix*) (this=0x122f5f0, element=0x11cc9b0, style=0x0,
matrix=0x0) at SVGCanvasCairo.cpp:99
#6  0x7496cb7b in wxSVGTextElement::GetBBox(wxSVG_COORDINATES)
(this=0x11cc9b0, coordinates=wxSVG_COORDINATES_USER) at
SVGTextElement.cpp:18
#7  0x7496ce27 in
wxSVGTextElement::GetResultBBox(wxSVG_COORDINATES) (this=0x11cc9b0,
coordinates=wxSVG_COORDINATES_USER) at SVGTextElement.cpp:30
#8  0x749667c5 in
wxSVGLocatable::GetElementResultBBox(wxSVGElement const*,
wxSVG_COORDINATES) (element=element@entry=0x11cc9b0,
coordinates=coordinates@entry=wxSVG_COORDINATES_USER) at
SVGLocatable.cpp:58
#9  0x004b52f2 in MenuObject::CalcSize(MenuObjectSize&, bool)
(this=this@entry=0x7fffa560, size=..., width=width@entry=true) at
MenuObject.cpp:498
#10 0x004b54d4 in MenuObject::FixSize(int&, int&)
(this=this@entry=0x7fffa560, width=@0x7fff82d0: 8,
height=@0x7fff82d4: 8)
at MenuObject.cpp:529
#11 0x004bb6c2 in MenuObject::UpdateSize()
(this=this@entry=0x7fffa560) at MenuObject.cpp:549
#12 0x004bfc91 in MenuObject::Init(wxString, int, int,
wxString) (this=this@entry=0x7fffa560, fileName=..., x=x@entry=0,
y=y@entry=0, param=...)
at MenuObject.cpp:188
#13 0x004c0879 in MenuObject::MenuObject(Menu*, bool,
wxString, int, int, wxString) (this=0x7fffa560, menu=, vmg=, fileName=..., x=0, y=0, param=...) at
MenuObject.cpp:66
#14 0x0053a210 in MenuEditor::MenuEditor(wxWindow*, int)
(this=0xdfee00, parent=, id=) at
MenuEditor.cpp:330
#15 0x005addf2 in MainWin::MainWin() (this=0xef3b80) at MainWin.cpp:199
#16 0x005b7aba in DVDStyler::OnInit() (this=0x0) at dvdstyler.cpp:170
#17 0x769b83f2 in wxEntry(int&, wchar_t**) ()
at /usr/lib64/libwx_baseu-suse.so.1
#18 0x00442bf2 in main(int, char**) (argc=,
argv=) at dvdstyler.cpp:52

The user has tried on three different Tumbleweed installations, one of
which was a clean install. The only library which is different to Leap
is libxcb and xcb-proto which were updated a month ago. I'm unable to
install Tumbleweed and DVDStyler works on my Leap installation. libxcb
has api changes, mostly types but according to abi-compliance-checker
is abi compatible, I previously checked this looking for the reason
for the xine-lib Tumbleweed build failure.

Thanks
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] New package wxWidgets-3_0-nostl for audacity-2.1.2 to build

2016-06-28 Diskussionsfäden Dave Plater
Please ignore the request for multimedia:libs link and accept sr#2802
Thanks
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] Please link to obs multimedia:libs/wxWidgets-3_0-nostl for audacity-2.1.2 to build

2016-06-28 Diskussionsfäden Dave Plater
Or copy the _link file from pmbs home:davepl/wxWidgets-3_0-nostl.
I've submitted it to Factory but it will take weeks to get there. Make
me maintainer and I'll disable the Factory and Tumbleweed builds when
it gets there.
Thanks
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] DVDStyler crashed (Tumbleweed)

2016-06-28 Diskussionsfäden Dave Plater
On 6/28/16, Dave Plater <davejpla...@gmail.com> wrote:
> On 6/28/16, Rolf Niepraschk <rolf.niepras...@gmx.de> wrote:
>>
>>
>>> Gesendet: Montag, 27. Juni 2016 um 23:43 Uhr
>>> Von: "Dave Plater" <davejpla...@gmail.com>
>>> An: "Rolf Niepraschk" <rolf.niepras...@gmx.de>
>>> Betreff: Re: [packman] DVDStyler crashed (Tumbleweed)
>>>
>>> This will take a while due to the fact that I'm going to be away,
>>> meanwhile you should do a zypper dup for Tumbleweed, I don't know
>>> which older library you have as yet, it;s definitely not libwxsvg3,
>>> you have the latest.  If you wish to go step by step start off with
>>> anything that starts with libcairo, there are several. The only bug is
>>> not handling the problem that caused the segfault, not sure if it's
>>> DVDStyler or wxsvg but it's an upstream bug.
>>>
>>> Regards
>>> Dave
>>>
>>
>> I did a lot of removes and reinstallations. I'm using no more
>> "gnome_factory" and reinstalled all "libwx*" and "*cairo*" and many other
>> gtk/gnome libraries. No success at all. The dvdstyler still crashed.
>>
>> My next try: I added the packman repository to the zypper configuration
>> of
>> another PC with a fresh (!) up-to-date tumpleweed installation. No
>> non-standard manipulations! And dvdstyler crashed here too!
>>
>> I'm helpless and don't know what to do ;-(
>>
>> ...Rolf
>>
>>
> I've filed a bug :
> https://sourceforge.net/p/dvdstyler/bugs/630/
> and asked for help
>
> Dave
>
Can you also see if you can find the core dump file, if you look
through your kernel logs, Yast2 journal and search for SIGSEGV and
maybe it will at least give you the name of the file. I think it's
/var/crash or something. I've only ever traced segfaults on my own
machine.
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] DVDStyler crashed (Tumbleweed)

2016-06-28 Diskussionsfäden Dave Plater
On 6/28/16, Rolf Niepraschk <rolf.niepras...@gmx.de> wrote:
>
>
>> Gesendet: Montag, 27. Juni 2016 um 23:43 Uhr
>> Von: "Dave Plater" <davejpla...@gmail.com>
>> An: "Rolf Niepraschk" <rolf.niepras...@gmx.de>
>> Betreff: Re: [packman] DVDStyler crashed (Tumbleweed)
>>
>> This will take a while due to the fact that I'm going to be away,
>> meanwhile you should do a zypper dup for Tumbleweed, I don't know
>> which older library you have as yet, it;s definitely not libwxsvg3,
>> you have the latest.  If you wish to go step by step start off with
>> anything that starts with libcairo, there are several. The only bug is
>> not handling the problem that caused the segfault, not sure if it's
>> DVDStyler or wxsvg but it's an upstream bug.
>>
>> Regards
>> Dave
>>
>
> I did a lot of removes and reinstallations. I'm using no more
> "gnome_factory" and reinstalled all "libwx*" and "*cairo*" and many other
> gtk/gnome libraries. No success at all. The dvdstyler still crashed.
>
> My next try: I added the packman repository to the zypper configuration of
> another PC with a fresh (!) up-to-date tumpleweed installation. No
> non-standard manipulations! And dvdstyler crashed here too!
>
> I'm helpless and don't know what to do ;-(
>
> ...Rolf
>
>
I've filed a bug :
https://sourceforge.net/p/dvdstyler/bugs/630/
and asked for help

Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


[packman] Audacity-2.1.2 needs multimedia:libs/wxWidgets-3_0-nostl to build

2016-06-27 Diskussionsfäden Dave Plater
Can someone please link multimedia:libs/wxWidgets-3_0-nostl to Packman
so that I can update multimedia:apps/audacity.
Thanks
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


Re: [packman] Audacity does start on suse tumbleweed

2016-06-27 Diskussionsfäden Dave Plater
On 6/27/16, Marguerite Su  wrote:
>>> @spectre-nm:~> audacity
>>> Fatal Error: Mismatch between the program and library build versions
>>> detected.
>>> The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,STL
>>> containers,compatible with 2.6),
>>> and your program used 2.8 (no debug,Unicode,compiler with C++ ABI
>>> 1010,STL containers,compatible with 2.6).
>>> Annullato (core dump creato)
>
> Hi,
>
> If some dependencies of audacity was built w/ gcc 5, while audacity is
> built
> w/ gcc 6, this ABI breakage will happen.
>
> It happens often and only in Factory(Tumbleweed), because in order to avoid
> endless rebuild, our factory maintainers may have some special repository
> configurations that prevents dependencies from rebuilding.
>
> This can be resolved by a rebuild of the things audacity needed.
>
> You should report it to openSUSE bugzilla against audacity and ask its
> maintainer to find out which one.
>
> Marguerite
>
AFAIK audacity links to multimedia:apps, I'm in the process of a long
overdue update that's been held up because version 2.1.2 builds
against wxWidgets-3_0 but won't build on openSUSE because of STL. All
the other distributions build wxWidgets without STL so the audacity
maintainers aren't interested in fixing the problem. I'm finishing of
a wxWidgets for audacity and then I'll update. I suspect that this
will solve the problem. wxWidgets 2 are a PITN.
Dave

___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman


  1   2   >