Re: [packman] libkdcraw2 provides libkdcraw.so.3, but nothing provides libkdcraw.so.2 anymore :-(

Moin Detlef, On Tue, 29 Apr 2008, 21:10:26 +0200, Detlef Reichelt wrote: Am Tue, 29 Apr 2008 20:40:07 +0200 schrieb Detlef Reichelt [EMAIL PROTECTED]: fuck! mist, ich downgrade libkdcraw... Detlef PS: Mal ebend updaten :( Gemacht, vielen Dank! ;-) Cheers. l8er manfred

Re: [packman] libgpod3 update package carries wrong version number

Moin, On Fri, 23 Jan 2009, 10:43:23 +0100, Manfred Hollstein wrote: Hi Pascal, I see this on my openSUSE 10.3 (x86_64) system: $ rpm -qp libgpod3-0.6.0-100.pm.1.i586.rpm --changelog * Wed Jan 21 2009 Pascal Bleser g...@unixtech.be 0.7.0-100.pm.1 - update to 0.7.0 Shouldn't

Re: [packman] Packman repo und Versionsrückschritt

Hi Namensvetter, das Thema ist ja eigentlich eher fuer die Packmaenner interessant, daher habe ich auch mal die entsprechende Liste auf die Copy-Liste gesetzt. mir ist es auch schon ein paar Mal in den vergangenen Monaten aufgefallen, dass solche Version-Rueckschritte stattgefunden haben; dank

Re: [packman] Packman repo und Versionsrückschritt

Nochmal Moin, On Sun, 29 Nov 2009, 11:11:53 +0100, Manfred Hollstein wrote: Hi Namensvetter, das Thema ist ja eigentlich eher fuer die Packmaenner interessant, daher habe ich auch mal die entsprechende Liste auf die Copy-Liste gesetzt. mir ist es auch schon ein paar Mal in den vergangenen

Re: [packman] openSUSE 11.1 x86_64 Repo inconsistent?

On Wed, 24 Nov 2010, 23:16:55 +0100, Pascal Bleser wrote: On 2010-11-24 15:03:32 (+0100), Manfred Hollstein manfre...@gmx.net wrote: On Wed, 24 Nov 2010, 01:09:40 +0100, rlee wrote: There was a long discussion on the legality of libfaac it turned out that Packman could not keep its

[packman] Trouble with packages either missing or non-functional on SLE_11/Evergreen

Hi there, due to the new structure of the packman repo(s), I've been left with some packages which are no longer available anywhere, or which are already installed on my systems, but render unusable due to recently released updates for the SLE_11 and/or Evergreen repos. Here are the packages

[packman] [openSUSE-12.2] Multimedia/x86_64/libwxsvg0-1.1.9-2.2.x86_64.rpm

Hi there, the package Multimedia/x86_64/libwxsvg0-1.1.9-2.2.x86_64.rpm requires libavutil.so.52()(64bit), but this is not (yet) available from the usual repositories for openSUSE 12.2 Has this been an oversight, or (when) will the required package become available? TIA, cheers. l8er manfred

Re: [packman] [openSUSE-12.2] Multimedia/x86_64/libwxsvg0-1.1.9-2.2.x86_64.rpm

On Thu, 10 Jan 2013, 19:59:17 +0100, Manfred Tremmel wrote: Am Mittwoch, 9. Januar 2013, 17:21:45 schrieb Manfred Hollstein: Hi there, the package Multimedia/x86_64/libwxsvg0-1.1.9-2.2.x86_64.rpm requires libavutil.so.52()(64bit), but this is not (yet) available from the usual

[packman] [openSUSE-12.1] libx264.so.128()(64bit) required by avidemux, but not available

Hi there, the package Multimedia/x86_64/avidemux-2.5.6-9000.4.x86_64.rpm requires libx264.so.128()(64bit), but this is no longer provided by the recently released package Essentials/x86_64/libx264-129-0.129svn20130224-2.1.x86_64.rpm This is on openSUSE-12.1 with all updates installed. Will/can

Re: [packman] [openSUSE-12.1] libx264.so.128()(64bit) required by avidemux, but not available

Hi Stefan, On Tue, 12 Mar 2013, 08:25:24 +0100, Stefan Seyfried wrote: Hi Manfred, Am 11.03.2013 17:35, schrieb Manfred Hollstein: Hi there, the package Multimedia/x86_64/avidemux-2.5.6-9000.4.x86_64.rpm requires libx264.so.128()(64bit), but this is no longer provided by the recently

[packman] MPlayer-1.1.1+r36500 now requires arts - is this intentional?

Hi there, I was just trying to update to the latest version of MPlayer on openSUSE-12.3 (x86_64): $ rpm -Uvh --test /nobackup/update-mirror/packman/suse/12.3/Essentials/x86_64/MPlayer-1.1.1+r36500-1.2.x86_64.rpm error: Failed dependencies: libartsc.so.0()(64bit) is needed by

Re: [packman] [openSUSE_*] winff not available as x86_64 version - on purpose?

Moin, On Mon, 18 Nov 2013, 12:37:52 +0100, Manfred Hollstein wrote: Hi there, it appears that there is no 64-bit x86_64 version of the winff package available in any openSUSE related repository, just the 32-bit i586 one. this is not exactly true... just the 1.5.* versions have not been

Re: [packman] Strange repositories for openshot

Hi Stefan, On Wed, 04 Nov 2015, 09:43:26 +0100, Stefan Botter wrote: > Hi Manfred, > > On Tue, 3 Nov 2015 15:33:46 +0100 > Manfred Hollstein <manfre...@gmx.net> wrote: > > > I just upgraded my openSUSE_13.2 installation to Leap_42.1. There is > > only one p

[packman] Strange repositories for openshot

Hi there, I just upgraded my openSUSE_13.2 installation to Leap_42.1. There is only one package missing which I don't find in packman anymore: "openshot". I then looked at the pmbs and the repositories defined for openshot look strange, at least: Build on i586 is enabled for all standard Intel

Re: [packman] kodi vs. pulseaudio-7

auch hier wieder mit PA unter Tumbleweed. Vielleicht ist's ja fuer andere Kodi Nutzer interessant - ich werde jedenfalls ab sofort immer ein Backup von ~/.kodi behalten... ;) Cheers. l8er manfred On Fri, 16 Oct 2015, 17:17:46 +0200, Manfred Hollstein wrote: > Nochmal Moin, > > On Fri, 16

[packman] kodi vs. pulseaudio-7

Moin, ich habe gerade mein Tumbleweed System auf den letzten Stand gebracht (sowohl TW selbst als auch die Packman Pakete). Leider muss ich wg. Skype Pulseaudio verwenden, und nun habe ich (wieder) ein Problem, weswegen ich PA schon mal vor einiger Zeit verbannt hatte. Wenn Kodi startet, steht

Re: [packman] kodi vs. pulseaudio-7

Nochmal Moin, On Fri, 16 Oct 2015, 11:27:08 +0200, Manfred Hollstein wrote: > ich habe gerade mein Tumbleweed System auf den letzten Stand gebracht > (sowohl TW selbst als auch die Packman Pakete). Leider muss ich wg. > Skype Pulseaudio verwenden, und nun habe ich (wieder) ein Problem, &

Re: [packman] broadcom-wl-kmp and Kernel:stable

Hi Malcom, On Mon, 30 May 2016, 02:01:47 +0200, Malcolm wrote: > On Sun 29 May 2016 08:56:39 PM CDT, Manfred Hollstein wrote: > > >Hi there, > > > >I'm currently trying to install the most recent kernel from OBS > >Kernel:stable/standard on my systems

[packman] broadcom-wl-kmp and Kernel:stable

Hi there, I'm currently trying to install the most recent kernel from OBS Kernel:stable/standard on my systems, but get problems because one of the systems is using the broadcom-wl WLAN driver. I'd like to build it for those kernels, too, but I believe I'd need an account in the Packman build

Re: [packman] broadcom-wl-kmp and Kernel:stable

Hi Malcolm, On Mon, 30 May 2016, 17:04:43 +0200, Malcolm wrote: > Hi > I don't think pmbs has the spare build power...? yeah, that's what I was mostly worried about... > If you have an OBS account you could just build locally (with > osc) against HEAD, no need for the source to reside on

Re: [packman] broadcom-wl-kmp and Kernel:stable

Hi Olaf, On Mon, 30 May 2016, 22:37:45 +0200, Olaf Hering wrote: > On Mon, May 30, Manfred Hollstein wrote: > > > On Mon, 30 May 2016, 21:12:59 +0200, Olaf Hering wrote: > > > http://packman.inode.at/suse/Factory/Essentials/x86_64/broadcom-wl-kmp-default-6.30.223.248_k4.

Re: [packman] broadcom-wl-kmp and Kernel:stable

Hi Olaf, On Mon, 30 May 2016, 21:12:59 +0200, Olaf Hering wrote: > On Sun, May 29, Manfred Hollstein wrote: > > > I'm currently trying to install the most recent kernel from OBS > > Kernel:stable/standard on my systems, but get problems because one of > > the systems

[packman] Mirror setup laggy?

Hi there, I found the broadcom-wl-kmp-* rpms for openSUSE_13.2 via the search button on pmbs.linux2linux.org. According to the build log, they have been built for the latest security update kernel for openSUSE_13.2 on Mon Feb 22 07:58:35 UTC 2016, but it appears that no mirror has them. Even

[packman] All-clear: version kodi-15.2-6.5.x86_64 is OK again (was: Re: WARNING: Don't install kodi-15.2-6.3.x86_64! (was: Re: [kodi] ERROR: failed to load requested skin 'skin.confluence'))

Moin, I just updated again and package kodi-15.2-6.5.x86_64 seems to be OK again. Everything appears to work. Cheers. l8er manfred pgpIgmDWAdhow.pgp Description: PGP signature ___ Packman mailing list Packman@links2linux.de

[packman] [kodi] ERROR: failed to load requested skin 'skin.confluence'

Hi there, I just installed all available updates from packman, and now kodi does no longer start :( I see this in ~/.kodi/temp/kodi.log: ERROR: failed to load requested skin 'skin.confluence' ERROR: Previous line repeats 1 times. ERROR: Default skin 'skin.confluence' not found!

[packman] WARNING: Don't install kodi-15.2-6.3.x86_64! (was: Re: [kodi] ERROR: failed to load requested skin 'skin.confluence')

On Thu, 25 Feb 2016, 13:02:06 +0100, Manfred Hollstein wrote: > Moin, > > On Thu, 25 Feb 2016, 12:43:50 +0100, Manfred Hollstein wrote: > > Hi there, > > > > I just installed all available updates from packman, and now kodi does > > no longer start :( I

Re: [packman] [kodi] ERROR: failed to load requested skin 'skin.confluence'

Moin, On Thu, 25 Feb 2016, 12:43:50 +0100, Manfred Hollstein wrote: > Hi there, > > I just installed all available updates from packman, and now kodi does > no longer start :( I see this in ~/.kodi/temp/kodi.log: > > ERROR: failed to load requested skin 'skin.confluence' &

Re: [packman] fuse-exfat not working

On Mon, 07 Mar 2016, 11:17:39 +0100, Olaf Hering wrote: > On Sun, Mar 06, Manfred Hollstein wrote: > > > OBS:/repositories/filesystems gets sync'ed with Packman? > > I have created _link files for exfat-utils and fuse-exfat. Great, thanks! > Olaf Cheers. l8er ma

Re: [packman] fuse-exfat not working

Hi Philipp, long time no see... On Tue, 08 Mar 2016, 10:14:25 +0100, Philipp Thomas wrote: > Hi Manfred, > > * Manfred Hollstein (manfre...@gmx.net) [20160307 11:49]: > > > > > OBS:/repositories/filesystems gets sync'ed with Packman? > > How about hosting the no

[packman] fuse-exfat not working

Hi there, I just saw that my SDXC cards (exfat formatted) cannot be mounted using a file manager anymore; it also appears that mounting it from the command line (mount -t exfat /dev/sdf1 /mnt) also fails. According to this happens because

Re: [packman] broadcom-wl-kmp and Kernel:stable

Moin, On Tue, 31 May 2016, 07:49:34 +0200, Manfred Hollstein wrote: > Hi Olaf, > > On Mon, 30 May 2016, 22:37:45 +0200, Olaf Hering wrote: > > On Mon, May 30, Manfred Hollstein wrote: > > > > > On Mon, 30 May 2016, 21:12:59 +0200, Olaf Hering wrote: > > >

Re: [packman] kodi and handbrake (at least) fail to build on current Tumbleweed (was: What is the status of Packman for/on current Tumbleweed?)

On Mon, 01 Aug 2016, 13:32:57 +0200, Carlos E. R. wrote: > El 2016-07-31 a las 16:10 +0200, Manfred Hollstein escribió: > > On Sun, 31 Jul 2016, 15:58:21 +0200, Manfred Hollstein wrote: > > > This leads me back to my initial question: What is the current > > recommen

Re: [packman] kodi requires "libnfs", but that package doesn't exist anymore (was: What is the status of Packman for/on current Tumbleweed?)

Hi Olaf, On Mon, 01 Aug 2016, 08:19:50 +0200, Olaf Hering wrote: [...] > At the same time there was the switch to gcc6, which triggered some failures > as well. Kodi should be fixed by now. yes, thanks for adding the patch. There is however another problem because kodi and its plugins require

Re: [packman] kodi requires "libnfs", but that package doesn't exist anymore

On Mon, 01 Aug 2016, 15:40:33 +0200, Olaf Hering wrote: > Am 01.08.2016 um 14:46 schrieb Manfred Hollstein: > > There is however another problem > > because kodi and its plugins require "libnfs", but this is no longer > > provided on TW as the package has been rena

Re: [packman] kodi and handbrake (at least) fail to build on current Tumbleweed (was: What is the status of Packman for/on current Tumbleweed?)

On Sun, 31 Jul 2016, 14:52:08 +0200, Manfred Hollstein wrote: > Moin, > > On Sun, 31 Jul 2016, 14:39:56 +0200, Manfred Hollstein wrote: > > [...] but at least the libnfs package is not so easy to explain: > > > > # zypper in libnfs8 -libnfs > > Loading reposit

Re: [packman] What is the status of Packman for/on current Tumbleweed?

Moin, On Sun, 31 Jul 2016, 14:39:56 +0200, Manfred Hollstein wrote: > [...] but at least the libnfs package is not so easy to explain: > > # zypper in libnfs8 -libnfs > Loading repository data... > Reading installed packages... > Resolving package dependencies... > >

Re: [packman] What is the status of Packman for/on current Tumbleweed?

On Sun, 31 Jul 2016, 16:10:49 +0200, Carlos E. R. wrote: > > > El 2016-07-31 a las 15:43 +0200, Carlos E. R. escribió: > > El 2016-07-31 a las 15:33 +0200, Manfred Hollstein escribió: > >> On Sun, 31 Jul 2016, 15:14:16 +0200, Carlos E. R. wrote: > > > >&g

Re: [packman] kodi and handbrake (at least) fail to build on current Tumbleweed (was: What is the status of Packman for/on current Tumbleweed?)

On Sun, 31 Jul 2016, 15:58:21 +0200, Manfred Hollstein wrote: > On Sun, 31 Jul 2016, 14:52:08 +0200, Manfred Hollstein wrote: > > Moin, > > > > On Sun, 31 Jul 2016, 14:39:56 +0200, Manfred Hollstein wrote: > > > [...] but at least the libnfs pac

Re: [packman] What is the status of Packman for/on current Tumbleweed?

On Sun, 31 Jul 2016, 15:14:16 +0200, Carlos E. R. wrote: > Content-ID: <alpine.LSU.2.20.1607311513080.18210@zvanf-gvevgu.inyvabe> > > > El 2016-07-31 a las 14:39 +0200, Manfred Hollstein escribió: > > > Hi there, > > > > I'm not sure what I see is what it

Re: [packman] broadcom-wl-kmp and Kernel:stable

Hi Olaf, On Wed, 27 Jul 2016, 09:20:37 +0200, Olaf Hering wrote: > Am 27.07.2016 um 08:19 schrieb Manfred Hollstein: > > now that 4.7.0 is available in Kernel:stable for some days, the related > > packages for broadcom-wl-kmp-* are missing from the above directory. Can > >

[packman] Does Handbrake work for anybody on Tumbleweed?

Hi there, with reference to my former message(s) about the status of packman for Tumbleweed, I have now reached a state where most stuff works. However, Handbrake isn't able to convert almost anything. I used some digicam videos and some .ts files from an AV receiver, but Handbrake simply fails

Re: [packman] Does Handbrake work for anybody on Tumbleweed?

Hi Stefan, On Mon, 15 Aug 2016, 13:42:14 +0200, Stefan Seyfried wrote: > On 15.08.2016 13:12, Manfred Hollstein wrote: > > > My ultimate question really is, does Handbrake actually work for anyone? > > If so, which repos do you use? > > It looks like it does. I can co

Re: [packman] Does Handbrake work for anybody on Tumbleweed?

Hi Olaf, On Mon, 15 Aug 2016, 21:24:31 +0200, Olaf Hering wrote: > Today I changed handbrake to compile in TW and 42.2. > It will take some time until its published. I just wanted to confirm that the latest packages for handbrake (0.10.5-2.3) allow to remove all packages from multimedia:libs

Re: [packman] broadcom-* package (wl module) makes systemd-udev crazy breaking the ifnames

Moin, On Mon, 06 Feb 2017, 08:46:56 +0100, Olaf Hering wrote: > On Fri, Feb 03, Daniel Pecka wrote: > > > systemd ppl say it's problem of our suse systemd-udev, that we don't follow > > upstream defaults in order to keep inane backword compatibility and kernel > > guys says, it's clearly the

[packman] Package broadcom-wl gone?

Hi there, has the package been deleted? I cannot find it in its former repository Essentials. TIA, cheers. l8er manfred signature.asc Description: PGP signature ___ Packman mailing list Packman@links2linux.de

Re: [packman] Package broadcom-wl gone?

Hi Tomáš, On Wed, 22 Feb 2017, 10:34:25 +0100, Tomáš Chvátal wrote: > 2017-02-22 10:29 GMT+01:00 Manfred Hollstein <manfre...@gmx.net>: > > has the package been deleted? I cannot find it in its former repository > > Essentials. > > > Hello Manfred, > &

Re: [packman] Package broadcom-wl gone?

Moin, On Wed, 22 Feb 2017, 11:57:29 +0100, Manfred Hollstein wrote: > Hi Tomáš, > > On Wed, 22 Feb 2017, 10:34:25 +0100, Tomáš Chvátal wrote: > > 2017-02-22 10:29 GMT+01:00 Manfred Hollstein <manfre...@gmx.net>: > > > has the package been deleted? I cannot fi

Re: [packman] PMBS - quo vadis?

Hi there, first of all I'd like to heartfully thank you, Stefan, to start this discussion. It happened too often during the past months (actually since TW arrived), that software cannot be installed due to the reasons you explained very clearly. On Fri, 24 Feb 2017, 10:29:16 +0100, Stefan Botter

Re: [packman] PMBS - quo vadis?

Moin, On Fri, 24 Feb 2017, 11:36:11 +0100, Olaf Hering wrote: > Am Fri, 24 Feb 2017 11:09:42 +0100 > schrieb Manfred Hollstein <manfre...@gmx.net>: > > > Indeed! Another example why the current approach to rely on some > > packages being provided by Factory first is

Re: [packman] Kodi 16 but addons in 17

On Fri, 24 Feb 2017, 12:35:04 +0100, Sagi Ben-Akiva wrote: > kodi-17.0 and it's binary addons were published in packman repo. Thanks a lot, will try it as soon as they appear on the mirrors! > Sagi. Cheers. l8er manfred signature.asc Description: PGP signature

Re: [packman] PMBS - quo vadis?

On Fri, 24 Feb 2017, 14:48:14 +0100, Olaf Hering wrote: > Am Fri, 24 Feb 2017 11:45:42 +0100 > schrieb Manfred Hollstein <manfre...@gmx.net>: > > > What would be a proper replacement for full mplayer/mencoder > > functionality? > > I do not know the answer to

Re: [packman] Kodi 16 but addons in 17

Hi Stefan, On Thu, 23 Feb 2017, 14:29:38 +0100, Stefan Botter wrote: > On Thu, 23 Feb 2017 12:43:32 +0100 > Manfred Hollstein <manfre...@gmx.net> wrote: > > > Hi there, > > > > On Tue, 21 Feb 2017, 16:41:22 +0100, Andrei Dziahel wrote: > > > Hi, > &g

Re: [packman] Package broadcom-wl gone?

Hi Tomáš, On Wed, 22 Feb 2017, 15:09:43 +0100, Tomáš Chvátal wrote: > 2017-02-22 13:44 GMT+01:00 Manfred Hollstein <manfre...@gmx.net>: > [...] > dmesg says this: > > [    4.814315] b43-phy0: Broadcom 4352 WLAN found (core revision 42) > [    4.81469

Re: [packman] Package broadcom-wl gone?

Hi Tomáš, On Thu, 23 Feb 2017, 10:55:50 +0100, Tomáš Chvátal wrote: > It seems this card is indeed not supported by the open-source driver. Well > for time being I resurrected the broadcom-wl package and I will try to poke > up the kernel guys to figure out how to get rid of it. thanks for your

Re: [packman] Kodi 16 but addons in 17

Hi there, On Tue, 21 Feb 2017, 16:41:22 +0100, Andrei Dziahel wrote: > Hi, > > Kodi 17 depends on libcec 4.0+ which is on the way in Factory: > https://build.opensuse.org/request/show/459110 all kodi builds in pmbs are still in the status "unresolvable". When will there be an _installable_

[packman] openshot vs. openshot-qt

Hi there, it's me again. What is the purpose of providing openshot-1.4.1 and openshot-qt-2.2.0, both in the Multimedia repository? Version 2.2.0's .spec file contains this: Provides: openshot = %{version} Obsoletes:openshot < %{version} When one has openshot installed and then runs

Re: [packman] Publishing problems?

Moin, On Mon, 12 Sep 2016, 14:29:00 +0200, Stefan Botter wrote: [...] > I am doing so now ;-) > Since Friday the GPG key problems have been solved, Extra and Games are > publishing again. if I'm not mistaken, it appears that nothing gets published since quite some time now. For instance, the

Re: [packman] broadcom-wl vs. kernel-4.8

Moin, On Fri, 07 Oct 2016, 11:17:06 +0200, Manfred Hollstein wrote: > Hi there, > > apparently the function cfg80211_scan_done has changed in kernel 4.8. On > the Debian bugtracker there is a report with a proper patch to fix the > problem at > > <https://bugs.debian.o

[packman] broadcom-wl vs. kernel-4.8

Hi there, apparently the function cfg80211_scan_done has changed in kernel 4.8. On the Debian bugtracker there is a report with a proper patch to fix the problem at Can someone please take a look at it and apply it so we get a working

Re: [packman] broadcom-wl vs. kernel-4.8

Moin, On Fri, 07 Oct 2016, 11:44:26 +0200, Manfred Hollstein wrote: > Moin, > > On Fri, 07 Oct 2016, 11:17:06 +0200, Manfred Hollstein wrote: > > Hi there, > > > > apparently the function cfg80211_scan_done has changed in kernel 4.8. On > > the Debian bugtracke

Re: [packman] broadcom-wl vs. kernel-4.8

Hi Bruno, On Sun, 09 Oct 2016, 19:26:12 +0200, Bruno Friedmann wrote: > On vendredi, 7 octobre 2016 11.44:26 h CEST Manfred Hollstein wrote: > > Moin, > > > > On Fri, 07 Oct 2016, 11:17:06 +0200, Manfred Hollstein wrote: > > > Hi there, > > > > > >

[packman] Why is k3b _disabled_ in pmbs for openSUSE Leap 42.1?

Hi there, I just updated all my 42.1 systems to the latest state of packages available from the Packman mirrors. "zypper up" left two orphane packages "k3b" and "k3b-lang", which came from the Essential repo so far. Looking at pmbs shows that the package has been enabled for 42.2, but disabled

Re: [packman] mpv _disabled_ (amongst other packages) in pmbs for openSUSE_Leap_42.2

On Wed, 16 Nov 2016, 19:42:48 +0100, Olaf Hering wrote: > As long as multimedia:libs is in the repolist there will always be breakage. > Not sure why you have it enabled. I don't have it enabled. The initial problem was, that "mpv" would be pulled in from the Leap_42.2 installation media, and

Re: [packman] mpv _disabled_ (amongst other packages) in pmbs for openSUSE_Leap_42.2

Moin, update below. On Wed, 16 Nov 2016, 14:34:39 +0100, Manfred Hollstein wrote: > Hi there, > > I am currently starting to upgrade one of my Leap_42.1 systems to > Leap_42.2. It looks like several packages have been disabled for 42.2 > which were (and still are) ava

Re: [packman] mpv _disabled_ (amongst other packages) in pmbs for openSUSE_Leap_42.2

On Wed, 16 Nov 2016, 15:26:46 +0100, Olaf Hering wrote: > Am 16.11.2016 um 14:34 schrieb Manfred Hollstein: > > What is the status/intention with regard to such packages? Does anybody > > know and wants to explain it here? > > mpv is built in OBS/42.2, linked to the ffmpe

Re: [packman] mpv _disabled_ (amongst other packages) in pmbs for openSUSE_Leap_42.2

On Wed, 16 Nov 2016, 16:41:32 +0100, Olaf Hering wrote: > Am 16. November 2016 16:15:40 MEZ, schrieb Manfred Hollstein > <manfre...@gmx.net>: > >Is this what you have/had in mind? > > Why would the ordinary user have the devel project enabled? There are likely >

[packman] mpv _disabled_ (amongst other packages) in pmbs for openSUSE_Leap_42.2

Hi there, I am currently starting to upgrade one of my Leap_42.1 systems to Leap_42.2. It looks like several packages have been disabled for 42.2 which were (and still are) available for 42.1: # zypper -vv dup -D Verbosity: 2 Warning: You are about to do a distribution upgrade with all

Re: [packman] mpv _disabled_ (amongst other packages) in pmbs for openSUSE_Leap_42.2

On Wed, 16 Nov 2016, 18:24:04 +0100, Olaf Hering wrote: > Am 16.11.2016 um 17:18 schrieb Manfred Hollstein: > > If you believe, m:a is not needed, what's the suggested proposal then? > > multimedia:apps is a devel project for at least a few apps in Factory. > Its certainly o

Re: [packman] mpv _disabled_ (amongst other packages) in pmbs for openSUSE_Leap_42.2

Hi there, thanks to everyone who helped with my problem. I just wanted to confirm that changing the vendor from Packman to openSUSE (i.e. the original package from the Leap 42.2 distribution) for the various packages listed in my initial e-mail to this list resulted in a working system with a

Re: [packman] chromium and chromium-ffmpeg

On Wed, 14 Dec 2016, 14:27:15 +0100, Olaf Hering wrote: > [...] > It does not need to be, because it just links to the sources in the > Update repo. If there is a new chromium the ffmpeg subpackage will be > rebuild automatically. This did not happen for the latest update of chromium on Leap 42.1

[packman] Kodi+42.3+SMB - does it work for someone? repeatedly? reproducably?

Hi there, I believe I have some very strange phenomenon here. I upgraded my 42.2 boxes using "zypper dup --no-recommends; zypper dup --no-recommends --from packman.essentials --from packman.multimedia" to an up2date Leap 42.3 installation. From what I can tell, everything works as before, but

Re: [packman] Publish Leap 42.3

Moin, On Wed, 31 May 2017, 08:34:03 +0200, Bruno Friedmann wrote: > On mercredi, 24 mai 2017 16.58:11 h CEST Olaf Hering wrote: > > A few days ago a new repository for the upcoming Leap 42.3 was added. > > Please enable mirroring now, instead of waiting for the final release. > > > > > > Olaf >

Re: [packman] Publish Leap 42.3

Moin, On Wed, 24 May 2017, 16:58:11 +0200, Olaf Hering wrote: > A few days ago a new repository for the upcoming Leap 42.3 was added. > Please enable mirroring now, instead of waiting for the final release. it appears that the built packages are still not available on the mirrors. What needs to

Re: [packman] Publish Leap 42.3

Happy Pfingsten everyone, On Sun, 04 Jun 2017, 09:59:48 +0200, Manfred Hollstein wrote: > On Wed, 24 May 2017, 16:58:11 +0200, Olaf Hering wrote: > > A few days ago a new repository for the upcoming Leap 42.3 was added. > > Please enable mirroring now, instead of waiting for th

Re: [packman] Publish Leap 42.3

Hi Stefan, On Fri, 16 Jun 2017, 15:54:42 +0200, Stefan Botter wrote: > [...] > Publishing for openSUSE Leap 42.3 is enabled now. > Packages have already been pushed to the mirrors. great, packages are there now indeed ;) Thanks a lot! > Greetings, > > Stefan Cheers. l8er manfred

Re: [packman] is 42.1 archived anywhere?

Moin, On Sun, 18 Jun 2017, 21:54:17 +0200, Felix Miata wrote: > Trinity Desktop cannot be installed without Packman's libIlmImf package, and > maybe others, as well. Apparently packman.inode.at no longer has 42.1. I still get them from ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Leap_42.1/

Re: [packman] Publish Leap 42.3

Hi Stefan, On Tue, 06 Jun 2017, 14:38:57 +0200, Stefan Botter wrote: > Manfred Hollstein <manfre...@gmx.net> wrote: > > [...] > > I have now checked all (reasonably reachable) mirrors in my area, but > > none carries repositories for openSUSE_Leap_42.3. Do we have

Re: [packman] [PM] flash-player 27.0.0.130-1.5 (openSUSE Tumbleweed/x86_64)

Moin, On Mon, 16 Oct 2017, 19:53:57 +0200, Frank Krüger wrote: > Hi there > > Flash-player is still at version 27.0.0.130, while version 159 and > today's version 170 did not hit Packman repos. looks like everything is fresh in PMBS:

Re: [packman] Kodi 17.4 - any chance to submit it to Multimedia?

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

[packman] Kodi 17.4 - any chance to submit it to Multimedia?

Hi there, $SUBJECT says it all. TIA, cheers. l8er manfred signature.asc Description: PGP signature ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

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

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

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

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.

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

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

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

Hi Dave, On Mon, 02 Oct 2017, 13:16:40 +0200, Dave Plater wrote: > On 9/29/17, Manfred Hollstein <manfre...@gmx.net> wrote: > > [...] > > 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

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

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

Re: [packman] Kodi on openSUSE_Leap_42.2 and 42.3: Does the Youtube addon work for anyone?

Moin, On Mon, 23 Oct 2017, 19:41:41 +0200, Manfred Hollstein wrote: > On Sun, 22 Oct 2017, 12:54:49 +0200, Manfred Hollstein wrote: > > I just installed the Youtube addon in my kodi-17.4 installation. When I > > want to run it, it immediately errors out. The logs can be found bel

Re: [packman] Kodi on openSUSE_Leap_42.2 and 42.3: Does the Youtube addon work for anyone?

Moin, On Sun, 22 Oct 2017, 12:54:49 +0200, Manfred Hollstein wrote: > I just installed the Youtube addon in my kodi-17.4 installation. When I > want to run it, it immediately errors out. The logs can be found below. > > My question really is: does this addon work for anyone? I foun

[packman] kodi.binary-addons 17.5-1.2 (openSUSE_Leap_42.2/x86_64) needs kodi = 17.5 which does not exist

Hi there, $SUBJECT says it pretty much; kodi-17.5 doesn't build for openSUSE_Leap_42.2. Can someone please roll back kodi.binary-addons, or get the version from submitted to Multimedia? TIA, cheers. l8er manfred signature.asc

[packman] When will kodi-17.6 be available?

Hi there, $SUBJECT says it all. Kodi 17.6 had been released on November 15; I think it should be possible to release some packages built for openSUSE Leap 42.2 and 42.3, no? TIA, cheers. l8er manfred signature.asc Description: PGP signature ___

Re: [packman] When will kodi-17.6 be available?

On Mon, 18 Dec 2017, 18:47:50 +0100, Olaf Hering wrote: > On Mon, Dec 18, Manfred Hollstein wrote: > > > $SUBJECT says it all. Kodi 17.6 had been released on November 15; I > > think it should be possible to release some packages built for openSUSE > > Leap 42.2 and 42.

Re: [packman] kodi.binary-addons 17.5-1.2 (openSUSE_Leap_42.2/x86_64) needs kodi = 17.5 which does not exist

Hi Sagi, On Wed, 15 Nov 2017, 22:00:45 +0100, Sagi Ben-Akiva wrote: > I've rebuild kodi 17.5 for Leap 42.2 > Can you check again ? I have successfully tested the current version on both 42.2 and 42.3. > Sagi. Thx for your attention. Cheers. l8er manfred signature.asc Description: PGP

[packman] Kodi on openSUSE_Leap_42.2 and 42.3: Does the Youtube addon work for anyone?

Hi there, I just installed the Youtube addon in my kodi-17.4 installation. When I want to run it, it immediately errors out. The logs can be found below. My question really is: does this addon work for anyone? TIA, cheers. l8er manfred <<

[packman] [openSUSE_Leap_15.0@PMBS] Almost all Multimedia packages for x86_64 are "unresolvable"

Hi there, I don't know when $SUBJECT began, but when I tried to "zypper dup" do yesterday's Leap 15.0 snapshot (258.1), no packages could be retrieved from Packman. E.g. "kodi" is not available in Multimedia/x86_64 (it's shown as "(System Packages)" in "zypper se -s -i -x -t package kodi"). PMBS

Re: [packman] [openSUSE_Leap_15.0@PMBS] Almost all Multimedia packages for x86_64 are "unresolvable"

Hi Olaf, On Thu, 17 May 2018, 17:32:38 +0200, Olaf Hering wrote: > Am Thu, 17 May 2018 11:48:42 +0200 > schrieb Manfred Hollstein <manfre...@gmx.net>: > > > PMBS shows 319 packages in the state "unresolvable" for architecture > > "x86_64" <ht

Re: [packman] [PM] kodi 17.6-3.8 (openSUSE Tumbleweed/i586)

Hi Udo, On Tue, 22 May 2018, 11:02:36 +0200, Udo Lubich wrote: > Hi Packman-Team, > > is there a problem with Kodi on Leap 15.0 ? > I had installed on 15.04.2018 (17.6 Git:20171114-a9a7a20). > Now I wanted to install on a new Installation of Leap 15.0 and I found no > Kodi on the Repository for

Re: [packman] [openSUSE_Leap_15.0@PMBS] Almost all Multimedia packages for x86_64 are "unresolvable"

On Fri, 18 May 2018, 22:00:22 +0200, Manfred Hollstein wrote: > Moin, > > On Thu, 17 May 2018, 18:04:13 +0200, Manfred Hollstein wrote: > > Hi Olaf, > > > > On Thu, 17 May 2018, 17:32:38 +0200, Olaf Hering wrote: > > > Am Thu, 17 May 2018 11:48:42 +0200 >

Re: [packman] [openSUSE_Leap_15.0@PMBS] Almost all Multimedia packages for x86_64 are "unresolvable"

Moin, On Thu, 17 May 2018, 18:04:13 +0200, Manfred Hollstein wrote: > Hi Olaf, > > On Thu, 17 May 2018, 17:32:38 +0200, Olaf Hering wrote: > > Am Thu, 17 May 2018 11:48:42 +0200 > > schrieb Manfred Hollstein <manfre...@gmx.net>: > > > > > PMBS sho

Re: [packman] [openSUSE_Leap_15.0@PMBS] Almost all Multimedia packages for x86_64 are "unresolvable"

On Mon, 04 Jun 2018, 14:45:01 +0200, yahoo-pier_andreit wrote: > Almost all Multimedia packages for x86_64 are "unresolvable" > ...is this problem solved?? yes, it is. You could look at to find out yourself. > manythanks, ciao :-) Cheers.

Re: [packman] ffmpeg4

Moin, On Fri, 27 Jul 2018, 12:45:48 +0200, pack...@howorth.org.uk wrote: > On Fri, 27 Jul 2018 09:21:45 +0200 > Olaf Hering wrote: > > >Am Fri, 27 Jul 2018 07:40:16 +0200 > >schrieb Wolfgang Rosenauer : > > > >> Are there plan to add ffmpeg4 to the packman repo? > > > >It is already there. >

Re: [packman] ffmpeg4

Moin, On Fri, 27 Jul 2018, 09:21:45 +0200, Olaf Hering wrote: > Am Fri, 27 Jul 2018 07:40:16 +0200 > schrieb Wolfgang Rosenauer : > > > Are there plan to add ffmpeg4 to the packman repo? > > It is already there. > > Anyone who spots the typo will get an uncrippled version of it. For free. And

  1   2   3   4   >