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

[Manfred Hollstein]

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

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

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

[Manfred Hollstein]

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 the RPM's version number be 0.7.0 instead of the current 0.6.0 ?

In case this wasn't clear from my initial message, apt-get now wants to
DOWNGRADE libgpod3 because the currently installed version from Packman
is libgpod3-0.6.0-100.pm.8

Cheers.

l8er
manfred

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

Re: [packman] Packman repo und Versionsrückschritt

[Manfred Hollstein]

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
apt-get wird das auch entsprechend gemeldet, ganz im Gegensatz zu einem
zypper lu (aber das ist ein ganz anderes Thema...).

Man kann dann ja gezielt die neueren Version installieren, aber, was
aktuell ziemlich nervt, ist, dass manchmal die aelteren Versionen (die
mit der hoeheren Versionsnummer) trotzdem im Repository enthalten
bleiben (aktuell zumindest bei k3b im 11.1/i586 Verzeichnis):

4240 -rw-rw-r-- 1 manfred users 4339413 Nov 26 16:00 
11.1/i586/k3b-1.0.5-1.pm.1.5.i586.rpm
4240 -rw-rw-r-- 1 manfred users 4340037 Sep  1 19:08 
11.1/i586/k3b-1.0.5-1.pm.19.2.i586.rpm
  20 -rw-rw-r-- 1 manfred users   18985 Nov 26 16:00 
11.1/i586/k3b-arts-1.0.5-1.pm.1.5.i586.rpm
  20 -rw-rw-r-- 1 manfred users   18992 Sep  1 19:08 
11.1/i586/k3b-arts-1.0.5-1.pm.19.2.i586.rpm
  64 -rw-rw-r-- 1 manfred users   63200 Nov 26 16:00 
11.1/i586/k3b-codecs-1.0.5-1.pm.1.5.i586.rpm
  64 -rw-rw-r-- 1 manfred users   63183 Sep  1 19:08 
11.1/i586/k3b-codecs-1.0.5-1.pm.19.2.i586.rpm
 104 -rw-rw-r-- 1 manfred users  104825 Nov 26 16:00 
11.1/i586/k3b-devel-1.0.5-1.pm.1.5.i586.rpm
 104 -rw-rw-r-- 1 manfred users  104875 Sep  1 19:08 
11.1/i586/k3b-devel-1.0.5-1.pm.19.2.i586.rpm
5312 -rw-rw-r-- 1 manfred users 5438434 Nov 26 16:00 
11.1/i586/k3b-lang-1.0.5-1.pm.1.5.i586.rpm
5312 -rw-rw-r-- 1 manfred users 5438422 Sep  1 19:08 
11.1/i586/k3b-lang-1.0.5-1.pm.19.2.i586.rpm
4256 -rw-rw-r-- 1 manfred users 4356690 Nov 26 18:00 
11.1/x86_64/k3b-1.0.5-1.pm.1.5.x86_64.rpm
  20 -rw-rw-r-- 1 manfred users   19141 Nov 26 18:00 
11.1/x86_64/k3b-arts-1.0.5-1.pm.1.5.x86_64.rpm
  64 -rw-rw-r-- 1 manfred users   64251 Nov 26 18:00 
11.1/x86_64/k3b-codecs-1.0.5-1.pm.1.5.x86_64.rpm
 104 -rw-rw-r-- 1 manfred users  104801 Nov 26 18:00 
11.1/x86_64/k3b-devel-1.0.5-1.pm.1.5.x86_64.rpm
5312 -rw-rw-r-- 1 manfred users 5438616 Nov 26 18:00 
11.1/x86_64/k3b-lang-1.0.5-1.pm.1.5.x86_64.rpm

Ob das noch bei anderen Paketen so ist, habe ich nicht geprueft. Es ist
aber haesslich, dass bei einem erneuten zypper up oder apt-get
upgrade immer wieder k3b als Update installiert werden soll, obwohl das
ja eigentlich ein Rueckschritt ist. Koennt ihr mal im Repository
aufraeumen und solche mehrfachen Versionen wegloeschen?

TIA, cheers.

l8er
manfred

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

Re: [packman] Packman repo und Versionsrückschritt

[Manfred Hollstein]

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 Monaten
 aufgefallen, dass solche Version-Rueckschritte stattgefunden haben; dank
 apt-get wird das auch entsprechend gemeldet, ganz im Gegensatz zu einem
 zypper lu (aber das ist ein ganz anderes Thema...).
 
 Man kann dann ja gezielt die neueren Version installieren, aber, was
 aktuell ziemlich nervt, ist, dass manchmal die aelteren Versionen (die
 mit der hoeheren Versionsnummer) trotzdem im Repository enthalten
 bleiben (aktuell zumindest bei k3b im 11.1/i586 Verzeichnis):
 
 4240 -rw-rw-r-- 1 manfred users 4339413 Nov 26 16:00 
 11.1/i586/k3b-1.0.5-1.pm.1.5.i586.rpm
 4240 -rw-rw-r-- 1 manfred users 4340037 Sep  1 19:08 
 11.1/i586/k3b-1.0.5-1.pm.19.2.i586.rpm
   20 -rw-rw-r-- 1 manfred users   18985 Nov 26 16:00 
 11.1/i586/k3b-arts-1.0.5-1.pm.1.5.i586.rpm
   20 -rw-rw-r-- 1 manfred users   18992 Sep  1 19:08 
 11.1/i586/k3b-arts-1.0.5-1.pm.19.2.i586.rpm
   64 -rw-rw-r-- 1 manfred users   63200 Nov 26 16:00 
 11.1/i586/k3b-codecs-1.0.5-1.pm.1.5.i586.rpm
   64 -rw-rw-r-- 1 manfred users   63183 Sep  1 19:08 
 11.1/i586/k3b-codecs-1.0.5-1.pm.19.2.i586.rpm
  104 -rw-rw-r-- 1 manfred users  104825 Nov 26 16:00 
 11.1/i586/k3b-devel-1.0.5-1.pm.1.5.i586.rpm
  104 -rw-rw-r-- 1 manfred users  104875 Sep  1 19:08 
 11.1/i586/k3b-devel-1.0.5-1.pm.19.2.i586.rpm
 5312 -rw-rw-r-- 1 manfred users 5438434 Nov 26 16:00 
 11.1/i586/k3b-lang-1.0.5-1.pm.1.5.i586.rpm
 5312 -rw-rw-r-- 1 manfred users 5438422 Sep  1 19:08 
 11.1/i586/k3b-lang-1.0.5-1.pm.19.2.i586.rpm
 4256 -rw-rw-r-- 1 manfred users 4356690 Nov 26 18:00 
 11.1/x86_64/k3b-1.0.5-1.pm.1.5.x86_64.rpm
   20 -rw-rw-r-- 1 manfred users   19141 Nov 26 18:00 
 11.1/x86_64/k3b-arts-1.0.5-1.pm.1.5.x86_64.rpm
   64 -rw-rw-r-- 1 manfred users   64251 Nov 26 18:00 
 11.1/x86_64/k3b-codecs-1.0.5-1.pm.1.5.x86_64.rpm
  104 -rw-rw-r-- 1 manfred users  104801 Nov 26 18:00 
 11.1/x86_64/k3b-devel-1.0.5-1.pm.1.5.x86_64.rpm
 5312 -rw-rw-r-- 1 manfred users 5438616 Nov 26 18:00 
 11.1/x86_64/k3b-lang-1.0.5-1.pm.1.5.x86_64.rpm
 
 Ob das noch bei anderen Paketen so ist, habe ich nicht geprueft. ...

Ich habe jetzt mal die 11.1 Sub-Directories untersucht und dabei so
einige Pakete gefunden, die mehrfach enthalten sind. Ob die auch das
Problem haben, dass neuere Versionen eine niedrigere Versionsnummer
haben (und damit das gleiche Problem wie bei k3b auftritt) kann ich
allerdings nicht sagen. Drei Listen haengen an von den Paketen mit
mehrfachen Versionen jeweils aus 11.1/i586, 11.1/noarch und 11.1/x86_64

HTH, cheers.

l8er
manfred
AssaultCube
FreeCAD
FreeCAD-devel
KDoodle
SubdiverSVN
SubdiverSVN-konqueror
SubdiverSVN-lang
SubdiverSVN-nautilus
SubdiverSVN-thunar
Vuze-libswt3-gtk2
bpmdj
broadcom-wl-kmp-debug
broadcom-wl-kmp-default
broadcom-wl-kmp-pae
broadcom-wl-kmp-trace
broadcom-wl-kmp-vmi
broadcom-wl-kmp-xen
clam-annotator
clam-annotator-examples
clam-networkeditor
clam-networkeditor-examples
clam-smstools
clam-smstools-examples
faust2pd
ffmpeg
fmodex-designerapi
gamin
gamin-devel
gamin-server
gephex
gmerlin-avdecoder
gmerlin-avdecoder-plugins
gnonlin
gnonlin-doc
gstreamer-0_10-plugins-base
gstreamer-0_10-plugins-base-devel
gstreamer-0_10-plugins-base-doc
gstreamer-0_10-plugins-base-lang
jdic
jdic-demo
jdic-javadoc
k3b
k3b-arts
k3b-codecs
k3b-devel
k3b-lang
kde4-diff-ext
kde4-partitionmanager
kde4-partitionmanager-lang
kde4-skrooge
kde4-skrooge-lang
kmm_kbanking
kmm_kbanking-lang
libavcodec52
libavdevice52
libavformat52
libclam-devel
libclam13
libclam13-doc
libcrypto++0
libcrypto++0-devel
libdc-devel
libdc-devel
libdc5
libffmpeg-devel
libffmpeg0
libgmerlin-avdecoder-devel
libgmerlin_avdec1
libgpod-devel
libgpod-devel-static
libgpod-doc
libgpod-python
libgpod-tools
libgpod4
libgstinterfaces-0_10-0
libifp-devel
libifp-tools
libifp4
libmlt++3
libmlt2
libmodplug-devel
libmodplug0
libmowgli-devel
libmyth-0_22
libmyth-0_22-devel
libosgGtk0
libosgGtkmm0
libossim-devel
libossim1
libossimPlanetQt1
libossimQt1
libpostproc51
libpqe
libquicktime-devel
libquicktime-tools
libquicktime0
libschroedinger-1_0-0
libschroedinger-devel
libskgbankgui1
libskgbankmodeler1
libskgbasegui1
libskgbasemodeler1
libsquish-devel
libsquish1
libswscale0
libtorrent-devel
libtorrent-devel
libtorrent11
libtunepimp
libtunepimp-devel
libtunepimp5
libtunepimp5-mad
libtunepimp5-mp4
libwms
libwms-devel
libwms-tools
libxine-devel
libxine1
libxine1-aa
libxine1-arts
libxine1-codecs
libxine1-directfb
libxine1-esd
libxine1-gnome-vfs
libxine1-jack
libxine1-pulse
libxine1-sdl
lv2-vcf
mesk
mixxx
mixxx-skin-Collusion
mixxx-skin-hercules
mixxx-skin-nCut
mixxx-skin-outline
mixxx-skin-outlineClose
mixxx-skin-outlineMini
mixxx-skin-outlineNetbook
mixxx-skin-traditional
mlt++-devel
mlt++-devel
mlt
mlt-devel
mythtv-0_22-backend
mythtv-0_22

Re: [packman] openSUSE 11.1 x86_64 Repo inconsistent?

[Manfred Hollstein]

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 version of libfaac so it was switched off. The
   discussion was about ffmpeg. You'll find it under that subject in the
   archives, the date for the thread was around Nov 16.
  
  thanks for the reply. I've now looked at the thread and fully understand
  that the package has been pulled and appreciate re-configuring/-building
  packages like ffmpeg to not rely on libfaac, but, as MPlayer and avidemux,
  at least, also require libfaac.so.0, I hope similar tidying will be
  done for such packages, too. Does anybody know, if so and when?
 
 Which mirror are you using for the Packman repository ?

I tried various mirrors (packman.jacobs-university.de, ftp.gwdg.de), but
all have the same problem. If you go to the faac page on the packman
site at

  http://packman.links2linux.de/package/faac/192959

and click on 1.28-2.pm.5.1 openSUSE 11.1   x86_64 you'll see that
there's only

  libfaac0-32bit-1.28-2.pm.5.1.x86_64.rpm   Mi 17.11.2010 (vor 7 Tagen) 

while for the other distribution/architecure combinations all packages
are there. It seems that the build for openSUSE 11.1 on x86_64 somehow
failed.

 As rlee pointed out, faac support has indeed been removed from ffmpeg,
 but the faac/libfaac packages are still built and published.
 
 I just checked on our primary server and the RPM packages are there
 indeed.

Yeah, but not for just this combination.

 Smells like something is fishy with the mirror (or the repository
 metadata).
 
 cheers
 -- 
   -o) Pascal Bleser pascal.ble...@opensuse.org

Cheers.

l8er
manfred

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

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

[Manfred Hollstein]

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 which I have installed, but which are no longer
available anywhere:

  DVDStyler-1.8.1-3.pm.5.12
  avidemux-2.5.3-4.pm.5.1
  avidemux-gtk-2.5.3-4.pm.5.1
  libaften0-0.08-4.pm.4.2
  libx264-88-0.0svn20100227-1.pm.2.2

(I've just included the version numbers in case someone needs them). I
understand that GUI programs like DVDStyler and/or avidemux are
difficult to maintain over time, so I looked for an alternative for
DVDStyler (because it does no longer work due to the recent updates for
the libav* packages). My attempt to install kdvdauth from the openSUSE
buildservice (KDE:/KDE3/SLE_11 repo) however fails, as it requires
transcode which is not available anywhere (for SLE_11/Evergreen/11.1).

Is it possible to get some packages back into the set of packages which
are still built for SLE_11/Evergreen? Or, can transcode be added?

FWIW, here's the error message from invoking dvdstyler and trying to
create an ISO from an MPG file:

  Output #0, dvd, to '/nobackup/tmp/dvd-tmp/menu1-0.mpg_bg.mpg':
  Stream #0.0: Video: mpeg2video, yuv420p, 720x576 [PAR 64:45 DAR 16:9], 
q=2-31, 6000 kb/s, 90k tbn, 25 tbc
  Stream #0.1: Audio: mp2, 48000 Hz, 2 channels, 64 kb/s
  [mp2 @ 0xbe41b0] Specified sample_fmt is not supported.
  [mpeg2video @ 0xbcbbd0] rc buffer underflow

TIA, cheers.

l8er
manfred

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

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

[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 repositories for openSUSE 12.2

Has this been an oversight, or (when) will the required package become
available?

TIA, cheers.

l8er
manfred

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

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

[Manfred Hollstein]

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 repositories for openSUSE 12.2
  
  Has this been an oversight, or (when) will the required package become
  available?
 
 Should be fixed inbetween.

Yep, after the latest round of updates all packages now install cleanly
here, thx!

Cheers.

l8er
manfred

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

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

[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
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 the
avidemux package be rebuilt?

TIA, cheers.

l8er
manfred

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

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

[Manfred Hollstein]

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
  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 the
  avidemux package be rebuilt?
 
 avidemux has built against libx264.so.129 since March 2nd:
 
 +++ /tmp/tmp.FPbG7B4KrL2013-03-02 20:50:14.872011171 +
 @@ -167,7 +167,7 @@
  libstdc++.so.6(GLIBCXX_3.4.9)(64bit) 16384
  libvorbis.so.0()(64bit) 16384
  libvorbisenc.so.2()(64bit) 16384
 -libx264.so.128()(64bit) 16384
 +libx264.so.129()(64bit) 16384
  libxml2.so.2()(64bit) 16384
 
 Maybe publishing from the buildservice does not work or your mirror is
 out of date?

I just ran rsync against ftp.halifax.rwth-aachen.de, but it didn't show
any files to resync; hence, avidemux is still out of date here. Using
packman.jacobs-university.de shows the same. So it seems that publishing
the buildservice doesn't work, at least not for openSUSE_12.1

Cheers.

l8er
manfred

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

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

[Manfred Hollstein]

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 MPlayer-1.1.1+r36500-1.2.x86_64

zypper in MPlayer-1.1.1+r36500-1.2 would of course pull in any needed
packages, but, to be honest, I'd rather stay away from having this arts
stuff back on my systems... Also, arts will pull in qt3... This doesn't
look proper to me.

Another thing I saw is that zypper believes that my currently installed
version of MPlayer 1.1+35127-4.1 has a higher version number than the
newer one:

  $ zypper in MPlayer-1.1.1+r36500-1.2
  Loading repository data...
  Reading installed packages...
  The selected package 'MPlayer-1.1.1+r36500-1.2.x86_64' from repository 
'packman' has lower version than the installed one. Use 'zypper install 
--oldpackage MPlayer-1.1.1+r36500-1.2.x86_64' to force installation of the 
package.
  Resolving package dependencies...

  Nothing to do.

From what I can tell, 1.1.1+r36500-1.2 looks larger/higher to me  than
1.1+35127-4.1


Looking at the package's ChangeLog shows interesting stuff:

  $ rpm -qp 
/nobackup/update-mirror/packman/suse/12.3/Essentials/x86_64/MPlayer-1.1.1+r36500-1.2.x86_64.rpm
 --changelog
  * Tue Nov 05 2013 joerg.loren...@ki.tng.de
  - update to version 1.1.1+r36500
* build against external libx264
* build internal ffmpeg-2.1 (build against external ffmpeg also possible)
* update Blue to version 1.8
* update Clearlooks to version 1.5
* added several patches from distro Mageia
* (nearly) complete rewrite of specfile

The (nearly) complete rewrite of specfile looks quite suspicious to
me; could it be the source for suddenly require'ing libartsc again, as
my current version of MPlayer 1.1+35127-4.1 did not require it.

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 built
as x86_64 packages, while the 1.4.* version do exist as x86_64 packages
(up until openSUSE_12.2) -- Factory and Tumbleweed are special, as they
have x86_64 packages only(!) for 1.4.* and i586 packages only(!) for
1.5.* ...

 Is this on purpose or has it just been forgotten? Can the 64-bit x86_64
 version be built as a regular package?

FWIW, I've just succeeded to build the 12.3 based src.rpm in a local
build environment, so it should work out of the box.

Cheers.

l8er
manfred

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

Re: [packman] Strange repositories for openshot

[Manfred Hollstein]

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 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 based distros, but
> >x86_64 is explicitly disabled
> > 
> > Does anyone know the logic behind this?
> 
> Yes, that was an easy pick :-)
> Since openshot is a noarch package, there is no need to build it for
> both i586 and x86_64, so x86_64 had been disabled completely.
> I now have enabled building for x86_64 and disabled the i586
> scheduling, so it will build for Leap 42.1, and be available on a mirror
> near you hopefully later today.

great, thanks a lot!

> Greetings,
> 
> Stefan

Cheers.

l8er
manfred


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

[packman] Strange repositories for openshot

[Manfred Hollstein]

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 based distros, but
   x86_64 is explicitly disabled

Does anyone know the logic behind this?

TIA, cheers.

l8er
manfred


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

Re: [packman] kodi vs. pulseaudio-7

[Manfred Hollstein]

Und ein letztes Mal Moin (fuer dieses Thema zumindest ;) )

normalerweise mache ich kein Top-Posting, aber in diesem Fall mache ich
mal eine Ausnahme, denn ich muss (leider) feststellen, dass nicht
Pulseaudio Schuld war, insofern der direkte Kontext nicht mehr stimmt...

Ich weiss nicht wie, aber irgendwie muss mein ~/.kodi einen Schuss
bekommen haben, denn auf einem anderen Rechner (HTPC-Rolle und dort Gott
sei Dank ohne PA und noch auf openSUSE-13.2) lief immer noch alles wie
gewohnt.  Nach einem beherzten "rsync -avHPSEAXOJ --delete
theotherhost:.kodi/ .kodi/" laeuft's jetzt 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 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,
> > weswegen ich PA schon mal vor einiger Zeit verbannt hatte. Wenn Kodi
> > startet, steht der Lautstaerkeregler auf 0; man kann dann zwar im
> > pavucontrol die Lautstaerke auf normal ziehen, aber sobald ein neues
> > Signal in Kodi anliegt (also z.B. Wechsel zwischen Musik (mp3) und Video
> > (mkv)), hoert man wieder nichts mehr und auch pavucontrol zeigt wieder 0
> > fuer Kodi an.
> > 
> > Da andere Programme (rhythmbox z.B.) keine Probleme damit haben, vermute
> > ich mal, dass die PA Doedels wieder mal etwas schnittstellen-inkompatibel 
> > geaendert haben... :( Ach ja, Kodi zeigt auch permanent oben rechts
> > einen roten, durchgestrichenen Lautsprecher an, selbst dann, wenn man in
> > pavucontrol wieder hochgeregelt hat.
> > 
> > Kennt einer dieses Verhalten oder hat sogar einen Fix dafuer?
> 
> da es gerade in einem anderen Thread erwaehnt wurde:
> 
>   <https://bugzilla.opensuse.org/show_bug.cgi?id=950487>
> 
> mein konkretes Problem hat nichts mit den KDE Problemen mit Pulseaudio
> zu tun, denn ich nutze hier XFCE (tatsaechlich habe ich den in
> <https://bugzilla.opensuse.org/show_bug.cgi?id=950487#c12> genannten
> Workaround installiert, allerdings ohne Auswirkung). Es ist tatsaechlich
> nur Kodi, das dieses merkwuerdige Verhalten an den Tag legt...
> 
> Cheers.
> 
> l8er
> manfred
> 
> > Systemrelevante Daten:
> > 
> > PRETTY_NAME="openSUSE Tumbleweed (20151012) (x86_64)"
> > kernel-desktop-4.2.1-1.4.x86_64
> > kodi-15.1-1.14.x86_64
> > pulseaudio-7.0-1.1.x86_64


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

[packman] kodi vs. pulseaudio-7

[Manfred Hollstein]

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 der Lautstaerkeregler auf 0; man kann dann zwar im
pavucontrol die Lautstaerke auf normal ziehen, aber sobald ein neues
Signal in Kodi anliegt (also z.B. Wechsel zwischen Musik (mp3) und Video
(mkv)), hoert man wieder nichts mehr und auch pavucontrol zeigt wieder 0
fuer Kodi an.

Da andere Programme (rhythmbox z.B.) keine Probleme damit haben, vermute
ich mal, dass die PA Doedels wieder mal etwas schnittstellen-inkompatibel 
geaendert haben... :( Ach ja, Kodi zeigt auch permanent oben rechts
einen roten, durchgestrichenen Lautsprecher an, selbst dann, wenn man in
pavucontrol wieder hochgeregelt hat.

Kennt einer dieses Verhalten oder hat sogar einen Fix dafuer?

TIA, cheers.

l8er
manfred

Systemrelevante Daten:

PRETTY_NAME="openSUSE Tumbleweed (20151012) (x86_64)"
kernel-desktop-4.2.1-1.4.x86_64
kodi-15.1-1.14.x86_64
pulseaudio-7.0-1.1.x86_64


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

Re: [packman] kodi vs. pulseaudio-7

[Manfred Hollstein]

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,
> weswegen ich PA schon mal vor einiger Zeit verbannt hatte. Wenn Kodi
> startet, steht der Lautstaerkeregler auf 0; man kann dann zwar im
> pavucontrol die Lautstaerke auf normal ziehen, aber sobald ein neues
> Signal in Kodi anliegt (also z.B. Wechsel zwischen Musik (mp3) und Video
> (mkv)), hoert man wieder nichts mehr und auch pavucontrol zeigt wieder 0
> fuer Kodi an.
> 
> Da andere Programme (rhythmbox z.B.) keine Probleme damit haben, vermute
> ich mal, dass die PA Doedels wieder mal etwas schnittstellen-inkompatibel 
> geaendert haben... :( Ach ja, Kodi zeigt auch permanent oben rechts
> einen roten, durchgestrichenen Lautsprecher an, selbst dann, wenn man in
> pavucontrol wieder hochgeregelt hat.
> 
> Kennt einer dieses Verhalten oder hat sogar einen Fix dafuer?

da es gerade in einem anderen Thread erwaehnt wurde:

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

mein konkretes Problem hat nichts mit den KDE Problemen mit Pulseaudio
zu tun, denn ich nutze hier XFCE (tatsaechlich habe ich den in
<https://bugzilla.opensuse.org/show_bug.cgi?id=950487#c12> genannten
Workaround installiert, allerdings ohne Auswirkung). Es ist tatsaechlich
nur Kodi, das dieses merkwuerdige Verhalten an den Tag legt...

Cheers.

l8er
manfred

> Systemrelevante Daten:
> 
> PRETTY_NAME="openSUSE Tumbleweed (20151012) (x86_64)"
> kernel-desktop-4.2.1-1.4.x86_64
> kodi-15.1-1.14.x86_64
> pulseaudio-7.0-1.1.x86_64


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

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

[Manfred Hollstein]

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, 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 service for that. Can I get that, please?
> >
> >E-Mail: manfre...@gmx.net
> >
> >I tried to sign up on pmbs.link2linux.org, but failed because
> >"password must not contain invalid characters". However, I failed to
> >find out what characters are allowed, so I thought I'd ask here ;)
> >
> >TIA, cheers.
> >
> >l8er
> >manfred
> >
> Hi
> Just grab the src rpm and build locally as your user, then install the
> built packages with root user.
> 
> rpmbuild --rebuild 

yeah, I know and that's exactly how I do it atm. My goal was to get this
automatted somehow, though ;)

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 service for that. Can I get that, please?

E-Mail: manfre...@gmx.net

I tried to sign up on pmbs.link2linux.org, but failed because
"password must not contain invalid characters". However, I failed to
find out what characters are allowed, so I thought I'd ask here ;)

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 OBS...?
> 
> You don't even need the repo present, just use --alternative-project
> option.

Sounds great, I'll try how/if that works. Thanks for the hint!

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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.5.4_1-8.53.x86_64.rpm
> > 
> > yes, this is the current Tumbleweed kernel, but Kernel:stable is way
> > ahead at 4.6.0-4.g2a4d959 atm. I need the newer kernel for better
> > support for current Skylake chipsets.
> 
> Try again in a few minutes/hours, Factory builds now against
> Kernel:stable.

indeed, it's there. Thanks a lot for your help!

> Olaf

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 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 service for that. Can I get that, please?
> 
> It depends what Kernel:stable really is. Its kernel-source likely close
> to openSUSE:Factory. So it should be possible to grab the kmp from the
> PMBS Factory repo. Right now its this pkg:
> 
> http://packman.inode.at/suse/Factory/Essentials/x86_64/broadcom-wl-kmp-default-6.30.223.248_k4.5.4_1-8.53.x86_64.rpm

yes, this is the current Tumbleweed kernel, but Kernel:stable is way
ahead at 4.6.0-4.g2a4d959 atm. I need the newer kernel for better
support for current Skylake chipsets.

> If all else fails we can swith the Factory repo from 
> 
> to
> 
> 
> Not sure if this would also inherit the 'rebuild="local" block="local"'
> knobs from OBS. But since Factory is a compile-test-only repo anyway it
> would not matter much for PMBS.

That would be great from my point of view, others may have a different
opinion, though.

> Olaf

Cheers.

l8er
manfred


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

[packman] Mirror setup laggy?

[Manfred Hollstein]

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 mirror.karneval.cz which, according to
, runs mirrors at a 1hourly
interval, still does not have them.

Could it be that some outgoing configuration for mirrors is wrong at the
Packman build service?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

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

[Manfred Hollstein]

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

This happens with an existing profile and also after moving ~/.kodi to
~/.kodi.save

The directory /usr/share/kodi/addons/skin.confluence/ exists. Do others
see similar problems? How can I debug this?

Here are some package versions on my openSUSE_13.2 system:

  kodi-15.2-6.3.x86_64
  kodi-pvr.addons-15.2-6.3.x86_64

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 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! Terminating..
> > 
> > This happens with an existing profile and also after moving ~/.kodi to
> > ~/.kodi.save
> > 
> > The directory /usr/share/kodi/addons/skin.confluence/ exists. Do others
> > see similar problems? How can I debug this?
> 
> when looking at the files in /usr/share/kodi/addons/skin.confluence/, it
> reveals that they are not readable for normal users:
> 
> [root@saturn (0) skin.confluence]# ll
> total 44
>  0 drwxr-xr-x  8 root root   154 Feb 25 12:08 .
>  4 drwxr-xr-x 76 root root  4096 Feb 22 13:25 ..
> 12 drwxr-xr-x  2 root root  8192 Feb 25 12:08 720p
>  0 -rw---  1 root root 0 Feb 22 13:25 addon.xml
>  0 drwxr-xr-x  2 root root84 Feb 25 12:08 backgrounds
>  0 -rw---  1 root root 0 Feb 22 13:25 build.bat
>  0 -rw---  1 root root 0 Feb 22 13:25 changelog.txt
>  0 drwxr-xr-x  2 root root25 Feb 25 12:08 colors
>  0 drwxr-xr-x  2 root root88 Feb 25 12:08 fonts
>  0 -rw---  1 root root 0 Feb 22 13:25 icon.png
> 12 drwxr-xr-x 76 root root  8192 Feb 22 13:25 language
> 16 drwxr-xr-x  7 root root 12288 Feb 25 12:08 media
> 
> Seems to be seriously broken, no?

Indeed, the package contains lots (426) unreadable files of which almost
all are 0 length only. This package ought to be removed/downgraded!

HTH, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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'
>   ERROR: Previous line repeats 1 times.
>   ERROR: Default skin 'skin.confluence' not found! Terminating..
> 
> This happens with an existing profile and also after moving ~/.kodi to
> ~/.kodi.save
> 
> The directory /usr/share/kodi/addons/skin.confluence/ exists. Do others
> see similar problems? How can I debug this?

when looking at the files in /usr/share/kodi/addons/skin.confluence/, it
reveals that they are not readable for normal users:

[root@saturn (0) skin.confluence]# ll
total 44
 0 drwxr-xr-x  8 root root   154 Feb 25 12:08 .
 4 drwxr-xr-x 76 root root  4096 Feb 22 13:25 ..
12 drwxr-xr-x  2 root root  8192 Feb 25 12:08 720p
 0 -rw---  1 root root 0 Feb 22 13:25 addon.xml
 0 drwxr-xr-x  2 root root84 Feb 25 12:08 backgrounds
 0 -rw---  1 root root 0 Feb 22 13:25 build.bat
 0 -rw---  1 root root 0 Feb 22 13:25 changelog.txt
 0 drwxr-xr-x  2 root root25 Feb 25 12:08 colors
 0 drwxr-xr-x  2 root root88 Feb 25 12:08 fonts
 0 -rw---  1 root root 0 Feb 22 13:25 icon.png
12 drwxr-xr-x 76 root root  8192 Feb 22 13:25 language
16 drwxr-xr-x  7 root root 12288 Feb 25 12:08 media

Seems to be seriously broken, no?

Cheers.

l8er
manfred


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

Re: [packman] fuse-exfat not working

[Manfred Hollstein]

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
manfred


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

Re: [packman] fuse-exfat not working

[Manfred Hollstein]

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 non-fuse exfat driver on Packman? openSUSE can't host
> it because its license isn't clear. If yes, I'll move the package over.

I'm clearly not a lawyer, and I don't run anything here at Packman - I'm
a plain user. Someone who has control over Packman, including the legal
aspects, should comment on this one.

> cu
> Philipp

Cheers.

l8er
manfred


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

[packman] fuse-exfat not working

[Manfred Hollstein]

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 the symbolic links in /sbin are missing. Can
someone please ensure that the package from
OBS:/repositories/filesystems gets sync'ed with Packman?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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:
> > > > http://packman.inode.at/suse/Factory/Essentials/x86_64/broadcom-wl-kmp-default-6.30.223.248_k4.5.4_1-8.53.x86_64.rpm
> > > 
> > > yes, this is the current Tumbleweed kernel, but Kernel:stable is way
> > > ahead at 4.6.0-4.g2a4d959 atm. I need the newer kernel for better
> > > support for current Skylake chipsets.
> > 
> > Try again in a few minutes/hours, Factory builds now against
> > Kernel:stable.
> 
> indeed, it's there. Thanks a lot for your help!

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
someone please check if it's still setup to be built against
Kernel:stable ?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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
> > recommendation for using Packman on Tumbleweed - now extended by "and
> > not having to add openSUSE:multimedia:libs"?
> 
> In that situation you need two packman repos with different policies. 
> One that keeps synced with TW official versions, and another that 
> follows the old policy of having the most recent version of anything 
> (the traditional packman policy). Perhaps in sync with 
> openSUSE:multimedia, I don't know.
> 
> Or choose one of the two policies.

This is what I did on my systems:

1. Accept vendor change for all packages no longer provided by Packman,
   i.e. take the version coming with TW itself
2. Switch to the packages from oS:m:l for all orphaned packages,
   i.e.  libavcodec57, libavdevice57, libavfilter6, libavformat57,
   libavresample3, libavutil55, libpostproc54, libswresample2, libswscale4
3. The oS:m:l repositories priority is set to 100

I tried to run some programs to see if they still work, especially
encoding/decoding the proprietary stuff, and they do run. So, this works
for me.

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 "libnfs", but this is no longer
provided on TW as the package has been renamed to "libnfs8" there.
Can someone please modify the spec files correspondigly?

> In general I think it is wrong to force a fixed ffmpeg version, unless its 
> the 2.8 or ffpmeg_oldapi API.
> 
> Olaf 

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 renamed to "libnfs8" there.
> > Can someone please modify the spec files correspondigly?
> 
> I think no changes are needed for kodi. A newer libnfs is on its way
> which also provides "libnfs" in the utils subpackage.

that's even better ;) Thx. FWIW, I worked around this issue with the
installed kodi packages for the moment by creating a wrapper RPM which
provides: libnfs and requires: libnfs8...

> Olaf

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 repository data...
> > Reading installed packages...
> > Resolving package dependencies...
> > 
> > Problem: kodi-16.1-1.9.x86_64 requires libnfs, but this requirement cannot 
> > be provided
> >   deleted providers: libnfs-1.10.0-1.7.x86_64
> >  Solution 1: Following actions will be done:
> >   deinstallation of kodi-16.1-1.9.x86_64
> >   deinstallation of kodi.binary-addons-pvr.vuplus-16.1-1.22.x86_64
> >  Solution 2: keep libnfs-1.10.0-1.7.x86_64
> >  Solution 3: break kodi-16.1-1.9.x86_64 by ignoring some of its dependencies
> > 
> > Choose from above solutions by number or cancel [1/2/3/c] (c): 
> > 
> > So, kodi (at least) hasn't be rebuilt against current Tumbleweed for
> > quite some time, has it?
> 
> hmm, looking at kodi's build results in pmbs shows that there are issues
> caused by switching to gcc6. There is a patch for this available at
> 
>   <https://github.com/xbmc/xbmc/pull/9703>
> 
> Can someone please add this to the package in Multimedia?

hmm, and package "handbrake" appears to depend on the various libav* and
related packages apparently coming from ffmpeg-3.1 which is no longer
provided by Packman but now reuses old ffmpeg-2.8 from oS:multimedia:libs
Looking at "handbrake"'s build results shows "unresolvable".

I'm afraid, moving back/using packages like ffmpeg etc. to oS is not
actually working in the current state.

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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...
> 
> Problem: kodi-16.1-1.9.x86_64 requires libnfs, but this requirement cannot be 
> provided
>   deleted providers: libnfs-1.10.0-1.7.x86_64
>  Solution 1: Following actions will be done:
>   deinstallation of kodi-16.1-1.9.x86_64
>   deinstallation of kodi.binary-addons-pvr.vuplus-16.1-1.22.x86_64
>  Solution 2: keep libnfs-1.10.0-1.7.x86_64
>  Solution 3: break kodi-16.1-1.9.x86_64 by ignoring some of its dependencies
> 
> Choose from above solutions by number or cancel [1/2/3/c] (c): 
> 
> So, kodi (at least) hasn't be rebuilt against current Tumbleweed for
> quite some time, has it?

hmm, looking at kodi's build results in pmbs shows that there are issues
caused by switching to gcc6. There is a patch for this available at

  <https://github.com/xbmc/xbmc/pull/9703>

Can someone please add this to the package in Multimedia?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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:
> >
> >>> zypper dup --no-allow-vendor-change
> >> 
> >> Thanks, Carlos, I use that since shortly after you described it ;)
> >> 
> >> The actual reason is kodi is now failing to build using gcc6.
> >
> > Oh, I see.
> 
> I have a doubt. With this option, I thought that zypper would not change 
> the packman packages to the oss ones if there are no update path within 
> packman :-?

It appears that a *lot* packages are no longer available from Packman.
E.g. gstreamer, only the bad and ugly plugins are there at the moment.
Also, ffmpeg-3.1 does no longer exist in Packman.

So it looks like (a) packages permanently moved to oS:m:l and one would
have to use oS:m:l in addition the repos we used to have, or (b)
something is really broken in Packman for Tumbleweed.

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 package is not so easy to explain:
> > > 
> > > # zypper in libnfs8 -libnfs
> > > Loading repository data...
> > > Reading installed packages...
> > > Resolving package dependencies...
> > > 
> > > Problem: kodi-16.1-1.9.x86_64 requires libnfs, but this requirement 
> > > cannot be provided
> > >   deleted providers: libnfs-1.10.0-1.7.x86_64
> > >  Solution 1: Following actions will be done:
> > >   deinstallation of kodi-16.1-1.9.x86_64
> > >   deinstallation of kodi.binary-addons-pvr.vuplus-16.1-1.22.x86_64
> > >  Solution 2: keep libnfs-1.10.0-1.7.x86_64
> > >  Solution 3: break kodi-16.1-1.9.x86_64 by ignoring some of its 
> > > dependencies
> > > 
> > > Choose from above solutions by number or cancel [1/2/3/c] (c): 
> > > 
> > > So, kodi (at least) hasn't be rebuilt against current Tumbleweed for
> > > quite some time, has it?
> > 
> > hmm, looking at kodi's build results in pmbs shows that there are issues
> > caused by switching to gcc6. There is a patch for this available at
> > 
> >   <https://github.com/xbmc/xbmc/pull/9703>
> > 
> > Can someone please add this to the package in Multimedia?
> 
> hmm, and package "handbrake" appears to depend on the various libav* and
> related packages apparently coming from ffmpeg-3.1 which is no longer
> provided by Packman but now reuses old ffmpeg-2.8 from oS:multimedia:libs
> Looking at "handbrake"'s build results shows "unresolvable".
> 
> I'm afraid, moving back/using packages like ffmpeg etc. to oS is not
> actually working in the current state.

Adding openSUSE:multimedia:libs to my current system also doesn't really
look promising:

  # zypper dup -D --from multimedia:libs.obs
  Loading repository data...
  Reading installed packages...
  Computing distribution upgrade...
  219 Problems:
  ...

It looks like it would be really replacing everything from former
Packman and those packages actually coming from Tumbleweed itself.
Filtering out those package from Tumbleweed to keep instead of m:l looks
a bit teadious to me. To be honest, the previous situation where one
would install plain Tumbleweed and then adds Packman's repositories for
the most relevant packages is much more appealing. I'd really prefer to
have a _usable_ basic OS installation with a Packman dropin to provide
everything for all those bad codecs looked compared to what we have
now, no?

This leads me back to my initial question: What is the current
recommendation for using Packman on Tumbleweed - now extended by "and
not having to add openSUSE:multimedia:libs"?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 should be...
> >
> > My last Tumbleweed installation was based on "openSUSE Tumbleweed
> > (20160710) (x86_64)". Last time I tried to "zypper dup" to a newer
> > snapshot was around 2 weeks ago. As a result I saw similar stuff like I
> > see now when I ran "zypper dup" again today (TW 20160728)... which is:
> >
> > # zypper dup
> 
> Idea. Try instead:
> 
> 
> export SOLVER_FLAG_DUP_ALLOW_VENDORCHANGE=0
> zypper dup
> 
> or perhaps
> 
> zypper dup --no-allow-vendor-change

Thanks, Carlos, I use that since shortly after you described it ;)

The actual reason is kodi is now failing to build using gcc6.

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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
> > someone please check if it's still setup to be built against
> > Kernel:stable ?
> 
> The API changed and the kmp fails to compile.
> Did anyone already look at the fallout?

I just saw that you added a 4.7 specific patch and the .rpm is available
at the build service. It just loads fine here on my system, thanks a
lot!

> Olaf

Cheers.

l8er
manfred


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

[packman] Does Handbrake work for anybody on Tumbleweed?

[Manfred Hollstein]

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 to properly scan them in and/or detect anything.

Here is what I did:

1. zypper dup --allow-vendor-change --from multimedia:libs.obs
2. zypper dup --allow-vendor-change --from packman-essentials --from 
packman-multimedia

[multimedia:libs.obs] 
http://download.opensuse.org/repositories/multimedia:/libs/openSUSE_Tumbleweed/
[packman-essentials] rsync copy from 
packman.inode.at::packman/suse/openSUSE_Tumbleweed/
[packman-multimedia] rsync copy from 
packman.inode.at::packman/suse/openSUSE_Tumbleweed/

I have also ensured that ffmpeg from packman is used because the version from
multimedia:libs.obs produces "unknown parameter" messages with winff.

My ultimate question really is, does Handbrake actually work for anyone?
If so, which repos do you use?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 convert TS recordings from VDR, containing
> h264 / AC3 sound:

Thanks very much for your response. I have some comments/remarks, please
read on.

> seife@susi:/local/video> HandBrakeCLI -Z "Android Tablet" -O -i
> /mounts/server2/capture/vdr/Irgendwie_und_Sowieso/2016-08-08.22.00.80-0.rec/1.ts
> -o Irgendwie_und_sowieso_9.mp4 -a 3 -E copy:ac3
> [13:33:34] hb_init: starting libhb thread
> HandBrake 0.10.5 (2016022000) - Linux x86_64 - https://handbrake.fr
> 2 CPUs detected
> Opening
> /mounts/server2/capture/vdr/Irgendwie_und_Sowieso/2016-08-08.22.00.80-0.rec/1.ts...
> [13:33:34] CPU: Intel(R) Core(TM)2 Duo CPU L9400  @ 1.86GHz
> [13:33:34]  - logical processor count: 2
> [13:33:34] OpenCL: library not available
> [13:33:34] hb_scan:
> path=/mounts/server2/capture/vdr/Irgendwie_und_Sowieso/2016-08-08.22.00.80-0.rec/1.ts,
> title_index=1
> udfread ERROR: ECMA 167 Volume Recognition failed
> disc.c:274: failed opening UDF image
> /mounts/server2/capture/vdr/Irgendwie_und_Sowieso/2016-08-08.22.00.80-0.rec/1.ts
> disc.c:352: error opening file BDMV/index.bdmv
> disc.c:352: error opening file BDMV/BACKUP/index.bdmv
> [13:33:34] bd: not a bd - trying as a stream/file instead
> libdvdnav: Using dvdnav version 5.0.3
> libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.IFO failed
> libdvdread:DVDOpenFileUDF:UDFFindFile /VIDEO_TS/VIDEO_TS.BUP failed
> libdvdread: Can't open file VIDEO_TS.IFO.
> libdvdnav: vm: failed to read VIDEO_TS.IFO
> [13:33:34] dvd: not a dvd - trying as a stream/file instead
> [13:33:34] file is MPEG Transport Stream with 188 byte packets offset 0
> bytes
> [13:33:34] Found the following PIDS
> [13:33:34] Video PIDS :
> [13:33:34]   0x1451 type H.264 (0x1b) (PCR)
> [13:33:34] Audio PIDS :
> [13:33:34]   0x1452 type MPEG1 (0x3)
> [13:33:34]   0x1453 type MPEG1 (0x3)
> [13:33:34]   0x1456 type AC3 (0x81)
> [13:33:34] Subtitle PIDS :
> [13:33:34] Other PIDS :
> [13:33:34]   0x1455 type DVB Subtitling (0x0)
> [13:33:34] stream id 0x1452 (type 0x3 substream 0x0) audio 0x1452
> [13:33:34] stream id 0x1453 (type 0x3 substream 0x0) audio 0x1453
> [13:33:34] stream id 0x1456 (type 0x81 substream 0x0) audio 0x1456
> [13:34:07] stream doesn't seem to have video IDR frames
> [13:34:07] scan: decoding previews for title 1
> Scanning title 1 of 1, preview 1, 0.00 %[13:34:07] file is MPEG
> Transport Stream with 188 byte packets offset 0 bytes

I get very similar output for my files up to here, but then I see lots
of messages similar to this:

  [16:11:46] decavcodecvInit: failed to find codec for id (28)
  [16:11:46] decavcodecvWork: failed to find codec for id (28)
  [16:11:46] decavcodecvWork: failed to find codec for id (28)
  [16:11:46] decavcodecvWork: failed to find codec for id (28)
  [16:11:46] no info on audio type 131072/0x15000 for id 0x1339
  [16:11:46] no info on audio type 131072/0x15000 for id 0x133a
  [16:11:46] decavcodecvWork: failed to find codec for id (28)
  [16:11:46] decavcodecvWork: failed to find codec for id (28)
  [16:11:46] no info on audio type 2048/0x15003 for id 0x133c
  [16:11:46] no info on audio type 131072/0x15029 for id 0x133e

I used a similar command line like you did, but deliberately left out
any audio related option to rely on using the first audio track found
(according to "HandBrakeCLI --help"):

  $ HandBrakeCLI -Z "Android Tablet" -O -i Dreambox/20160813\ 2010\ -\ 
ServusTV\ HD\ Deutschland\ -\ The\ Score.ts -o foo.mp4

> [13:34:07] scan: audio 0x1453: mp2, rate=48000Hz, bitrate=128000 Unknown
[...]

> I have never added anything from multimedia:libs, only packman and factory

Hmm, where did you get your libavcodec57 from then? Could it be that you
are still using the old version provided by Packman before most of such
packages got removed from Packman? Which repository is shown for it when
you run the following command:

  # zypper se -s -i libavcodec57

Mine is from multimedia:libs.obs, yours probably is '(System Packages)',
isn't it?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 and to
fall back to the libav* packages from Packman, but, the best thing is,
it actually works again ;) Thanks a lot!

> There is currently no ffmpeg3 for TW.

I'm not sure if the winff package in Packman is able at all to work with
ffmpeg3, so there's no real need atm (at least from my point of view).

> Not sure if the is an easy way to default to ffmpeg2
> if no specific version is in BuildRequires.

When there are multiple versions in one tree, I guess we'd need
something like:

BuildRequires: ffmpeg < 3.0

??

> Olaf

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 problem of wl module forcefully binding to eth0
> > (shall be - and always was wlan0)
> 
> You are the first one who reports this. Looks like an upstream bug.

I saw that, too, and worked around it by creating a file in
/etc/systemd/network:

  $ cat /etc/systemd/network/10-wlan0.link
  [Match]
  MACAddress=AA:BB:CC:DD:EE:FE

  [Link]
  Name=wlan0

> src/wl/sys/wl_linux.c:218:#define BRCM_WLAN_IFNAME eth%d

Never looked at the sources myself, but this appears an obvious error,
thx!

> I wonder what will break if this gets changed to wlan%d.

I'm not sure many have seen the wrong behaviour so far, but we'll see.

> Olaf

Thanks for analyzing and fixing this, Olaf!

Cheers.

l8er
manfred


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

[packman] Package broadcom-wl gone?

[Manfred Hollstein]

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
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] Package broadcom-wl gone?

[Manfred Hollstein]

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,
> 
> Yes the broadcom-wl is gone from the repository.
> 
> I had a review meeting with our kernel guys and we discovered it was not
> updated in couple of years while its device scanning ment it was loaded and
> attempted to be loaded on almost all broadcom cards errornously.
> 
> What the labs people said is that the driver that is at the moment in
> kernel should work more reliably and they are more than willing to receive
> bugs if something is still not behaving well with the broadcom chipsets
> that were before covered by this package.

thanks for your feedback. Does that mean that I should use one of the
kernel provided drivers (e.g. bcma) from openSUSE_Leap_42.1/2, or would
it be necessary to run a more recent kernel like Kernel:stable?

> HTH
> 
> Tom

TIA, cheers.

l8er
manfred


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

Re: [packman] Package broadcom-wl gone?

[Manfred Hollstein]

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 find it in its former repository
> > > Essentials.
> > >
> > Hello Manfred,
> > 
> > Yes the broadcom-wl is gone from the repository.
> > 
> > I had a review meeting with our kernel guys and we discovered it was not
> > updated in couple of years while its device scanning ment it was loaded and
> > attempted to be loaded on almost all broadcom cards errornously.
> > 
> > What the labs people said is that the driver that is at the moment in
> > kernel should work more reliably and they are more than willing to receive
> > bugs if something is still not behaving well with the broadcom chipsets
> > that were before covered by this package.
> 
> thanks for your feedback. Does that mean that I should use one of the
> kernel provided drivers (e.g. bcma) from openSUSE_Leap_42.1/2, or would
> it be necessary to run a more recent kernel like Kernel:stable?

too bad! I just tried to get wlan0 (Broadcom 4352 WLAN core revision 42)
to work, but it fails on both kernels I have here on my openSUSE_Leap_42.1
system:

  kernel-default-4.1.38-47.1
  kernel-default-4.9.11-1.1

dmesg says this:

[4.814315] b43-phy0: Broadcom 4352 WLAN found (core revision 42)
[4.814698] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), 
Revision 1)
[4.815499] b43: probe of bcma0:1 failed with error -95
[4.815524] Broadcom 43xx driver loaded [ Features: PNLS ]

Neither NetworkManager nor wicked can see any related device; this means
networking is no longer possible for a wide range of devices (from Dell
and ASrock and possibly many others). Do we have a backup of the former
driver which worked properly, at least for me.

Thx, cheers.

l8er
manfred


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

Re: [packman] PMBS - quo vadis?

[Manfred Hollstein]

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 wrote:
> Hi Tomáš, (and of course all other list subscribers),
> 
> thank you for your reply.
> 
> On Thu, 23 Feb 2017 22:03:28 +0100
> Tomáš Chvátal  wrote:
> > [...]
> > With the cleanups of Essentials now happening only actual packages
> > that were cut without main openSUSE repository providing them are
> > items depending on ffmpeg-0.x which contains at least 40CVE's and
> > some remote executions among them (yes there were packages depending
> > on that which were removed, but frankly I would rather have
> > non-exploitable system, and I don't mind recreating those packages if
> > someone patches them to build with new ffmpeg). Other removals were
> > mostly based around stack that was supposed to be removed ages ago by
> > simply replacing with renamed libraries libraries. The end result
> > will simply be almost identical for end user like the current state.
> 
> It is a good idea to streamline packages, and I am happy to see more
> people engaging in packaging on PMBS. On the other hand, it would have
> been a good idea to announce this major change on the mailing list and
> wait for objections.

Exactly, this is really no way to work with a community. Especially when
functionality (or support for specific hardware in this case) gets
silently removed without announcing it first. Yes, I'm talking about the
broadcom-wl driver which got removed without any announcement. I agree
you re-added the package pretty fast when I asked if/why the package had
been removed, but this is just an example for bad communication. I would
have sent a message indicating that the in-kernel driver should support
all/most of the NICs out there, and that everybody using the
out-of-kernel package should check if the in-kernel driver actually
works for them. Only when there is consensus that that is the case, the
package can be removed. But this is just my opninion.

> >  We are grateful for the infrastructure
> > itself but simply put the growing amount of complains about the state
> > of Packman was quite dishearting for us on openSUSE side. As you say
> > Richard already raised these points 8 moths back and without seeing
> > much improvement of stability in meantime I decided to try to do
> > something about it.
> 
> As I hinted yesterday, Richard expressed the opinion, that Packman is
> merely an extension of openSUSE to do the dirty work of publishing
> software, which openSUSE does not dare to publish itself. This seems to
> be a common opinion among openSUSE supporters, as I can read from the
> real quick answers to request made by more inexperienced users in
> mailing lists or the openSUSE forum.
> "Go include Packman repo, do zypper dup and everything is working.".
> Good idea, and it worked real well a few years back, when there was no
> Tumbleweed (TW), but just the regular openSUSE releases. It took us some
> days, but then the functionality was provided.

Indeed! Another example why the current approach to rely on some
packages being provided by Factory first is kodi-17. It got build by
some fellow packager here in PMBS with an libcec version that appears to
be required kodi-17, but which wasn't available neither in PMBS nor in
OBS. So, he created his version of libcec >= 4.0, and everything was OK
for his home: project. But, when the package got moved to the Multimedia
repository, kodi-17 didn't build because the current policy appears to
dictate that libcec >= 4.0 must go through Factory first and only then
can be linked from there. We're still waiting for it to finally show up.
As a result, the corresponding kodi-17 plugins/addons, which don't need
libcec, are now being made available in a version which doesn't fit to
kodi-16, which every user still has installed. Users who currently want
to upgrade their systems from openSUSE_Leap_42.1 (or even openSUSE_13.2)
to openSUSE_Leap_42.2 get into trouble, while those users who want to
install new systems with kodi included and who happen to need one of the
addons for their e.g. DVB-C/T/S receivers, cannot install it anymore...
To be honest, since nothing in the distribution or on OBS so far
required libcec >= 4.0, I really cannot understand why we couldn't
simply put it into Packman, as it used to be done a long time before,
and it used to work then!

> And not only this, but as especially multimedia packages are moving
> forwards rapidly, Packman provided the things and versions openSUSE was
> to slow or inflexible to provide. There are still packages in the
> repos, which are there in the way they are for a reason.
> 
> Richards objected to the way Packman selected its packages, with
> respect to TW. Packman either used package sources hosted 

Re: [packman] PMBS - quo vadis?

[Manfred Hollstein]

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 kodi-17.
> 
> This is more an issue with the workflow.
> 
> Using 'osc bco Multimedia kodi' would have shown the issue right away.
> There is no need to rush anything in. If a required library comes from
> OBS or PMBS does not matter much. It has to be decided on a
> case-by-case base how to satisfy the requirements. In case of libcec we
> should just have waited until it appears in TW. In case of the recent
> ABI change in libbluray it was clear that certain changes can not be
> done globally.

agreed, this has nothing to do with the "way forward" discussion.

> > And when packages get removed, again, this needs some way of
> > communication, potentially with reasons included and hints what should
> > be used instead - this can be currently seen on openSUSE_Leap_42.1
> > where several gstreamer related packages (0_10 version) either would
> > need to get downgraded to those versions from OBS, or they don't even
> > exist anymore (like libaudio2 or libslv2), but are still required by
> > other packages (like MPlayer2).
> 
> I think MPlayer2 was dropped. Installed but orphaned packages are hard
> to handle.

Nope, I just looked at one of the mirrors, and it's still there for
42.1:

ncftp ...42.1/Essentials/x86_64 > dir -rw-rw-r--1 1003 1003  
2896873 Feb 23 21:28 MPlayer-1.2.r37916-4.2.x86_64.rpm

What would be a proper replacement for full mplayer/mencoder
functionality?

> [...]
> Also it would be helpful if the email setup would work properly. Only a
> subset of the submit_request emails are sent.
> 
> And perhaps each mail should be mirrored to this list to reach a wider
> audience. But that may create too much noise for the "ordinary" lurker.

I wouldn't mind receiving such stuff, and everybody else could just
filter them away.

> Olaf

Cheers.

l8er
manfred


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

Re: [packman] Kodi 16 but addons in 17

[Manfred Hollstein]

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
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Re: [packman] PMBS - quo vadis?

[Manfred Hollstein]

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 that.
> Not sure what the benefit of MPlayer is today.

it's more its encoding/grabbing stuff I use from time to time. For
instance, extracting music titles in mp3 from a music video dvd. Other
than that, handbrake, mpv, vlc etc. cover everything else MPlayer was
famous for.

> Olaf

Cheers.

l8er
manfred


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

Re: [packman] Kodi 16 but addons in 17

[Manfred Hollstein]

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,
> > > 
> > > 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_ version of Kodi 17 available? And, how
> > are non Factory/Tumbleweed users supposed to get libcec 4.0+ for their
> > distribution (openSUSE Leap 42.1 and/or 42.2)?
> > 
> > The current situation with incompatible kodi-16 and
> > kodi.binary-addons-pvr.*-17 packages is not really usefull for
> > installing new systems or upgrading older ones...
> 
> There will be a libcec version 4 for all currently built openSUSE
> versions in Packman, once the submit request of the libcec 4 in
> openSUSE.org's Factory will be accepted.
> Out libcec is a link to factory (appartently since a week or so, rather
> than a own-supplied version). 

thanks for you explanation! I just added a comment to tbe OBS request
asking when we can expect the request to be accepted. I'd urge everybody
interested in kodi-17 here to add a similar comment ;)

> These dependencies are unfortunate, and obviously the prize for "moving
> everything to OBS" and have Packman be merely a detached build host and
> distribution place for packages Suse does not dare to provide
> themselves.

Yes, it's always the good old ways (tm) ;)

> Greetings,
> 
> Stefan

Cheers (and greetings to Bremen - I lived there myself quite some time
ago).

l8er
manfred


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

Re: [packman] Package broadcom-wl gone?

[Manfred Hollstein]

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.814698] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11
> (AC), Revision 1)
> [    4.815499] b43: probe of bcma0:1 failed with error -95
> [    4.815524] Broadcom 43xx driver loaded [ Features: PNLS ]
> 
> Neither NetworkManager nor wicked can see any related device; this means
> networking is no longer possible for a wide range of devices (from Dell
> and ASrock and possibly many others). Do we have a backup of the former
> driver which worked properly, at least for me.
> 
> This says the driver was not properly loaded indeed.
> 
> Could you please check which exact chipset you have?
> "lspci -nn -d 14e4:"

02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)

> Btw most of the cards are described on the wiki here:
> <https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211#to_be_done_for_fullmac_driver>
> 
> Cheers
> 
> Tom

Cheers.

l8er
manfred


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

Re: [packman] Package broadcom-wl gone?

[Manfred Hollstein]

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 help! FWIW, I have created my own package in OBS to
ensure I always have a working driver ;)

> Tom

Cheers.

l8er
manfred


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

Re: [packman] Kodi 16 but addons in 17

[Manfred Hollstein]

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_ version of Kodi 17 available? And, how
are non Factory/Tumbleweed users supposed to get libcec 4.0+ for their
distribution (openSUSE Leap 42.1 and/or 42.2)?

The current situation with incompatible kodi-16 and
kodi.binary-addons-pvr.*-17 packages is not really usefull for
installing new systems or upgrading older ones...

Thx, cheers.

l8er
manfred


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

[packman] openshot vs. openshot-qt

[Manfred Hollstein]

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 "zypper up", openshot gets
obsoleted and replaced by openshot-qt. Without adding a lock, there is
no chance to keep openshot installed. Is this the purpos? Or should
version 1.4 be deleted?

Cheers.

l8er
manfred


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

Re: [packman] Publishing problems?

[Manfred Hollstein]

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 twenty latest packages according to
 are now five days old... And, no new
packages appear to be(come) available on any mirror.

Do you have an update on the situation?

> Greetings,
> 
> Stefan

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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.org/cgi-bin/bugreport.cgi?bug=839629>
> 
> Can someone please take a look at it and apply it so we get a working
> module again for Factory's kernel?

FWIW, I have created a patch which applies cleanly to the latest src rpm
from the Factory tree. It's attached to this e-mail.

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] broadcom-wl vs. kernel-4.8

[Manfred Hollstein]

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
module again for Factory's kernel?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 bugtracker there is a report with a proper patch to fix the
> > problem at
> > 
> >   <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839629>
> > 
> > Can someone please take a look at it and apply it so we get a working
> > module again for Factory's kernel?
> 
> FWIW, I have created a patch which applies cleanly to the latest src rpm
> from the Factory tree. It's attached to this e-mail.

hmm, something scrubbed the attachment from my last e-mail, so here it
is inline:

### begin of patch:
diff -rup broadcom-wl-6.30.223.248.orig/src/wl/sys/wl_cfg80211_hybrid.c 
broadcom-wl-6.30.223.248/src/wl/sys/wl_cfg80211_hybrid.c
--- broadcom-wl-6.30.223.248.orig/src/wl/sys/wl_cfg80211_hybrid.c   
2016-10-07 11:38:57.857206380 +0200
+++ broadcom-wl-6.30.223.248/src/wl/sys/wl_cfg80211_hybrid.c2016-10-07 
11:41:41.561802881 +0200
@@ -2383,8 +2383,15 @@ wl_bss_connect_done(struct wl_cfg80211_p
s32 err = 0;
 
if (wl->scan_request) {
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 8, 0)
+   struct cfg80211_scan_info info = {
+   .aborted = true
+   };
WL_DBG(("%s: Aborting scan\n", __FUNCTION__));
-   cfg80211_scan_done(wl->scan_request, true); 
+   cfg80211_scan_done(wl->scan_request, );
+#else
+   cfg80211_scan_done(wl->scan_request, true);
+#endif
wl->scan_request = NULL;
}
 
@@ -2485,7 +2492,14 @@ wl_notify_scan_status(struct wl_cfg80211
 
 scan_done_out:
if (wl->scan_request) {
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 8, 0)
+   struct cfg80211_scan_info info = {
+   .aborted = false
+   };
+   cfg80211_scan_done(wl->scan_request, );
+#else
cfg80211_scan_done(wl->scan_request, false);
+#endif
wl->scan_request = NULL;
}
rtnl_unlock();
@@ -2912,7 +2926,14 @@ s32 wl_cfg80211_down(struct net_device *
s32 err = 0;
 
if (wl->scan_request) {
-   cfg80211_scan_done(wl->scan_request, true); 
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 8, 0)
+   struct cfg80211_scan_info info = {
+   .aborted = true
+   };
+   cfg80211_scan_done(wl->scan_request, );
+#else
+   cfg80211_scan_done(wl->scan_request, true);
+#endif
wl->scan_request = NULL;
}
 
### end of patch.

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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,
> > > 
> > > 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.org/cgi-bin/bugreport.cgi?bug=839629>
> > > 
> > > Can someone please take a look at it and apply it so we get a working
> > > module again for Factory's kernel?
> > 
> > FWIW, I have created a patch which applies cleanly to the latest src rpm
> > from the Factory tree. It's attached to this e-mail.
> > 
> > TIA, cheers.
> > 
> > l8er
> > manfred
> 
> Sorry Manfred the attachement was cleaned by some process.

yeah, I realized that myself when I received the e-mail from the mailing
list. I sent an inline patch to the list afterwards and I can see it in
the archives, so it should be available for further inspection.

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 for 42.1. It is my understanding that 42.2 is not yet
officially released, so we should be able to keep up to date with the
current 42.1 installations, shouldn't we? Can the package be re-enabled
again, please?

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 last time I tried
it, it failed to play my .ts files. Are you saying, Leap_42.2's original
"mpv" is capable to play the same files Packman's did?

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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) available for 42.1:
> 
>   # zypper -vv dup -D
>   Verbosity: 2
>   Warning: You are about to do a distribution upgrade with all enabled 
> repositories. Make sure these repositories are compatible before you 
> continue. See 'man zypper' for more information about this command.
>   Initializing Target
>   Checking whether to refresh metadata for Kernel:stable.local
>   Checking whether to refresh metadata for Skype
>   Checking whether to refresh metadata for Virtualization:containers.local
>   Checking whether to refresh metadata for home:mhnovell.obs
>   Checking whether to refresh metadata for mh
>   Checking whether to refresh metadata for mozilla.local
>   Checking whether to refresh metadata for non-oss.local
>   Checking whether to refresh metadata for oss.local
>   Checking whether to refresh metadata for packman-multimedia.local
>   Checking whether to refresh metadata for packman.local
>   Checking whether to refresh metadata for printing.local
>   Checking whether to refresh metadata for update-non-oss.local
>   Checking whether to refresh metadata for update.local
>   Checking whether to refresh metadata for virtualbox.local
>   Checking whether to refresh metadata for virtualbox.org
>   Loading repository data...
>   Reading installed packages...
>   Computing distribution upgrade...
>   Force resolution: No
>   Computing upgrade...
>   39 Problems:
>   Problem: problem with installed package fdupes-1.51-3.2.x86_64
>   Problem: problem with installed package gstreamer-1.8.3-77.4.x86_64
>   Problem: problem with installed package gstreamer-0_10-0.10.36-22.3.x86_64
>   Problem: problem with installed package 
> gstreamer-0_10-lang-0.10.36-22.3.noarch
>   Problem: problem with installed package 
> gstreamer-0_10-plugins-base-0.10.36-18.2.x86_64
>   Problem: problem with installed package 
> gstreamer-0_10-plugins-base-lang-0.10.36-18.2.noarch
>   Problem: problem with installed package 
> gstreamer-0_10-plugins-good-0.10.31-92.1.x86_64
>   Problem: problem with installed package 
> gstreamer-0_10-plugins-good-extra-0.10.31-92.1.x86_64
>   Problem: problem with installed package 
> gstreamer-0_10-plugins-good-lang-0.10.31-92.1.noarch
>   Problem: problem with installed package gstreamer-lang-1.8.3-77.4.noarch
>   Problem: problem with installed package 
> gstreamer-plugins-base-1.8.3-74.5.x86_64
>   Problem: problem with installed package 
> gstreamer-plugins-base-lang-1.8.3-74.5.noarch
>   Problem: problem with installed package 
> gstreamer-plugins-good-1.8.3-86.1.x86_64
>   Problem: problem with installed package 
> gstreamer-plugins-good-extra-1.8.3-86.1.x86_64
>   Problem: problem with installed package 
> gstreamer-plugins-good-lang-1.8.3-86.1.noarch
>   Problem: problem with installed package libchromaprint1-1.3.1-33.3.x86_64
>   Problem: problem with installed package 
> libgstallocators-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libgstapp-0_10-0-0.10.36-18.2.x86_64
>   Problem: problem with installed package libgstapp-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libgstaudio-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libgstfft-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package 
> libgstinterfaces-0_10-0-0.10.36-18.2.x86_64
>   Problem: problem with installed package 
> libgstpbutils-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package 
> libgstreamer-0_10-0-0.10.36-22.3.x86_64
>   Problem: problem with installed package libgstreamer-1_0-0-1.8.3-77.4.x86_64
>   Problem: problem with installed package libgstriff-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libgstrtp-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libgstrtsp-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libgstsdp-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libgsttag-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libgstvideo-1_0-0-1.8.3-74.5.x86_64
>   Problem: problem with installed package libnfs-1.10.0-1.2.x86_64
>   Problem: problem with installed package libopencv3_1-3.1.0-91.43.x86_64
>   Problem: problem with installed package mpv-0.21.0-66.1.x86_64
>   Problem: problem with installed package 
> typelib-1_0-Gst-1_0-1.8.3-77.4.x86_64
>   Problem: problem with installed package 
> typelib-1_0-GstAudio-1_0-1.8.3-74.5.x86_64
>   Problem: problem with installed package 
> typelib-1_0-Gs

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

[Manfred Hollstein]

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 ffmpeg version in OBS/42.2.
> ffmpeg, as rebuilt in PMBS, links to OBS/42.2.
> 
> The intention is that there has to be some consistency between the
> packages in OBS and PMBS. Back in the days when ffmpeg was not in OBS
> everything came from PMBS. Since Leap ffmpeg used also in OBS by many
> packages. The result is that PMBS should not simply build ffmpeg from
> the OBS devel project, because that will break SONAMEs, instead the
> exact source version for the given release is rebuilt. This is
> implemented for TW and 42.2, it will not be implemented for 42.1, 13.x
> and SLE_12.
> 
> I'm sure the suggested vendor change when upgrading from 42.1 to 42.2
> will not cause issues.

Hmm, what would be the suggested recipe then?

1. zypper dup   # accept all vendor changes packman -> 
obs
2. zypper dup --from multimedia:apps# accept all vendor changes
3. zypper dup --from packman/Essentials \
--from packman/Multimedia   # accept all vendor changes

If Multimedia works afterwards, ok, but, what I really hate (to be
honest) is the to be expected amount of "xxx packages will not be
updated" messages when running "zypper up" on a daily basis, with "xxx"
being packages available both in multimedia:apps and Packman...

Is this what you have/had in mind?

> Olaf

Thx, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 
> pkgs which are not in Leap or PMBS. But there is no way around it if the 
> repos have overlapping packages. 

hmm, which devel project? If multimedia:apps (maybe multimedia:libs is
sufficient, but a current version of "mpv" is only available in :apps)
is a devel project, then I think (not proven yet), it's still necessary
for a lot of applications from Packman. Last time I faced this issue in
Tumbleweed, at least, Handbrake, winff and probabably others were
affected.

If you believe, m:a is not needed, what's the suggested proposal then?

> Olaf 

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 enabled 
repositories. Make sure these repositories are compatible before you continue. 
See 'man zypper' for more information about this command.
  Initializing Target
  Checking whether to refresh metadata for Kernel:stable.local
  Checking whether to refresh metadata for Skype
  Checking whether to refresh metadata for Virtualization:containers.local
  Checking whether to refresh metadata for home:mhnovell.obs
  Checking whether to refresh metadata for mh
  Checking whether to refresh metadata for mozilla.local
  Checking whether to refresh metadata for non-oss.local
  Checking whether to refresh metadata for oss.local
  Checking whether to refresh metadata for packman-multimedia.local
  Checking whether to refresh metadata for packman.local
  Checking whether to refresh metadata for printing.local
  Checking whether to refresh metadata for update-non-oss.local
  Checking whether to refresh metadata for update.local
  Checking whether to refresh metadata for virtualbox.local
  Checking whether to refresh metadata for virtualbox.org
  Loading repository data...
  Reading installed packages...
  Computing distribution upgrade...
  Force resolution: No
  Computing upgrade...
  39 Problems:
  Problem: problem with installed package fdupes-1.51-3.2.x86_64
  Problem: problem with installed package gstreamer-1.8.3-77.4.x86_64
  Problem: problem with installed package gstreamer-0_10-0.10.36-22.3.x86_64
  Problem: problem with installed package 
gstreamer-0_10-lang-0.10.36-22.3.noarch
  Problem: problem with installed package 
gstreamer-0_10-plugins-base-0.10.36-18.2.x86_64
  Problem: problem with installed package 
gstreamer-0_10-plugins-base-lang-0.10.36-18.2.noarch
  Problem: problem with installed package 
gstreamer-0_10-plugins-good-0.10.31-92.1.x86_64
  Problem: problem with installed package 
gstreamer-0_10-plugins-good-extra-0.10.31-92.1.x86_64
  Problem: problem with installed package 
gstreamer-0_10-plugins-good-lang-0.10.31-92.1.noarch
  Problem: problem with installed package gstreamer-lang-1.8.3-77.4.noarch
  Problem: problem with installed package 
gstreamer-plugins-base-1.8.3-74.5.x86_64
  Problem: problem with installed package 
gstreamer-plugins-base-lang-1.8.3-74.5.noarch
  Problem: problem with installed package 
gstreamer-plugins-good-1.8.3-86.1.x86_64
  Problem: problem with installed package 
gstreamer-plugins-good-extra-1.8.3-86.1.x86_64
  Problem: problem with installed package 
gstreamer-plugins-good-lang-1.8.3-86.1.noarch
  Problem: problem with installed package libchromaprint1-1.3.1-33.3.x86_64
  Problem: problem with installed package 
libgstallocators-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libgstapp-0_10-0-0.10.36-18.2.x86_64
  Problem: problem with installed package libgstapp-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libgstaudio-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libgstfft-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package 
libgstinterfaces-0_10-0-0.10.36-18.2.x86_64
  Problem: problem with installed package libgstpbutils-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package 
libgstreamer-0_10-0-0.10.36-22.3.x86_64
  Problem: problem with installed package libgstreamer-1_0-0-1.8.3-77.4.x86_64
  Problem: problem with installed package libgstriff-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libgstrtp-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libgstrtsp-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libgstsdp-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libgsttag-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libgstvideo-1_0-0-1.8.3-74.5.x86_64
  Problem: problem with installed package libnfs-1.10.0-1.2.x86_64
  Problem: problem with installed package libopencv3_1-3.1.0-91.43.x86_64
  Problem: problem with installed package mpv-0.21.0-66.1.x86_64
  Problem: problem with installed package typelib-1_0-Gst-1_0-1.8.3-77.4.x86_64
  Problem: problem with installed package 
typelib-1_0-GstAudio-1_0-1.8.3-74.5.x86_64
  Problem: problem with installed package 
typelib-1_0-GstPbutils-1_0-1.8.3-74.5.x86_64
  Problem: problem with installed package 
typelib-1_0-GstTag-1_0-1.8.3-74.5.x86_64
  Problem: problem with installed package 
typelib-1_0-GstVideo-1_0-1.8.3-74.5.x86_64
  
  Problem: problem with installed package fdupes-1.51-3.2.x86_64
   Solution 1: install fdupes-1.50-8.57.x86_64 (with vendor change)
http://packman.links2linux.de  -->  openSUSE
  
  Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c):
  ...

To be honest, I don't care about the various *gst* 

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

[Manfred Hollstein]

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 ok to have its Leap repo enabled. But the downside is that
> multimedia:apps builds against multimedia:libs, which in turn is also
> a devel project. Soon it will happen that ffmpeg gets new SONAMEs and
> mpv will stop working because it links against OBS.
> 
> There will be always some conflict between "having the latest" and
> "having a consistent system". The idea was to provide updates via the
> 42.2:Update project. In the case of mpv itself it might be ok to build
> it unconditionally in PMBS for all repos. A few packages have
> Requires: mpv (Essentials/baka-mplayer, Essentials/smplayer,
> Multimedia/selene, Multimedia/xt7-player-mpv).
> 
> So what should be done with mpv? Provide always the variant from
> multimedia:apps via PMBS (linked against the given ffmpeg from PMBS),
> or should mpv be updated as needed via the Update channel?

I'm not sure what others think, but I believe "mpv" is a must to have on
a current desktop system, so I'd be OK with it provided via the normal OBS
update channel - but it ought to pick up all those libav* packages
provided by Packman to ensure it actually works with today's multimedia
files (such as the .ts file I had problems with when streaming it from
the Dreambox). I'm definitely not deep enough into the features which
are/are not available when packages come from m:a vs. m:l vs. OBS vs.
Packman.  In my experience, the mixture of packages such as "mpv" and
"handbrake" resulted in an unresolvable situation when I last tried it
on Tumbleweed. I'm afraid, with current 42.2 we are in a similar shape.

> Olaf

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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
fully functional "mpv" program! Handbrake also works properly! So, this
bucket can be closed... ;)

There's another one remaining, though, "winff" is disabled in Packman
for openSUSE_Leap_42.2. My daughters are using it regularly on their
systems, so they would be missing it a lot. Can the package be enabled
for 42.2, please?

TIA, cheers.

l8er
manfred


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

Re: [packman] chromium and chromium-ffmpeg

[Manfred Hollstein]

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 and
42.2. Interestingly the package for 13.2 got rebuilt! I just looked at
the PMBS monitor and it shows a lot of idle workers, so a build of
chromium-ffmpeg for Leap 42.1 and 42.2 could potentially run without
any problems. Can someone please trigger the build manually?

> Olaf

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] Kodi+42.3+SMB - does it work for someone? repeatedly? reproducably?

[Manfred Hollstein]

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
Kodi _most_ of the times is having problems to access my
Picture/Music/Video shares imported from some of my internal servers.
All internal PCs use the same class-C network, and this class-C network
is added to FW_TRUSTED_NETS, so I _think_ that all internal traffic
should just go through - this is how it used to work on 42.2, 42.1,
13.2, 13.1, ...

However, when I start Kodi on any of the new machines, it happens in
_most_ cases, that access to those pre-defined shares just hangs the
program. I ran "tcpdump" from another not-involved computer to just
track the traffic between the client and the host, but I cannot see any
difference to what happens on 42.2. Disabling the SuSEfirewall2 and
rebooting the client makes it work, like it did before. I checked all
potential settings of SF2 regarding broadcasts, trusted nets, netbios
etc., but nothing has a persistent benefit. What's worse it, sometime it
starts and works well once, but when the program gets restarted it hangs
again. In the meantime I made a copy of a _working_ ~/.kodi directory,
and comparing its content with the one that fails, only shows binary
diffs in the usual media DB files. FWIW, rebooting into 42.2 or 42.1 and
starting Kodi with the exact same ~/.kodi directory simply works without
any trouble.

Does accessing SMB shares over the internal net (host and client may
even reside on the same host) work repeatedly and consistently for
others on a configuration similar to the following one?

  - Leap 42.3 x86_64 with or without PulseAudio (I actually have one
dedicated installation for DTS and the like without PA)
  - all packages dup'ed from Packman.Essentials and Packman.Multimedia
  - kodi-17.3-2.1.x86_64
  - SF2 enabled
  - Samba shares enabled

FWIW2, clicking on the "Add source->Windows (SMB)" goes into an endless
loop with one core running at 100% utilization.

I am completely uncertain whether this is a Kodi bug or something is
wrong with SF2; but, as all other Multimedia programs using SMB (such as
Rhythmbox) simply work OK as before, I thought I'd ask for other
experiences.

TIA, cheers.

l8er
manfred


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

Re: [packman] Publish Leap 42.3

[Manfred Hollstein]

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
> 
> It seems that the repository is still not visible and thus remove the 
> possibility to check builded packages.
> 
> https://packman.inode.at/suse/openSUSE_Leap_42.3/
> 
> It would be awesome to have it.

I fully agree here! When will we get packman packages for 42.3? This
would dramatically help testing the upcoming Leap 42.3 release and
ensure no (or not too many) unknowns will arise when we'll be forced
(again) to upgrade from 42.2 to 42.3... ;) .

TIA, cheers.

l8er
manfred


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

Re: [packman] Publish Leap 42.3

[Manfred Hollstein]

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 be done to change that?

> Olaf

TIA, cheers.

l8er
manfred


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

Re: [packman] Publish Leap 42.3

[Manfred Hollstein]

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 the final release.
> 
> it appears that the built packages are still not available on the
> mirrors. What needs to be done to change that?

I have now checked all (reasonably reachable) mirrors in my area, but
none carries repositories for openSUSE_Leap_42.3. Do we have to ask all
maintainers of the mirrors to _please_ add openSUSE_Leap_42.3 to their
mirrors? Or is is that releasing the built packages has to be enabled at
a central location first?

> > Olaf

TIA, cheers.

l8er
manfred


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

Re: [packman] Publish Leap 42.3

[Manfred Hollstein]

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


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

Re: [packman] is 42.1 archived anywhere?

[Manfred Hollstein]

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/

HTH, cheers.

l8er
manfred


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

Re: [packman] Publish Leap 42.3

[Manfred Hollstein]

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 to ask
> > all maintainers of the mirrors to _please_ add openSUSE_Leap_42.3 to
> > their mirrors? Or is is that releasing the built packages has to be
> > enabled at a central location first?
> 
> No, you do not need to ask everyone.
> I have to enable publishing on PMBS to the staging server. For that to
> work I have to change certain settings on the staging server and test
> these.
> 
> All this takes time, of with I have very few at the moment.
> 
> Please be patient.

thanks for the update message!

> Greetings,
> 
> Stefan

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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:

  

> Does this mean that it is no longer maintained?
> 
> Regards Frank

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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

  

helps with your problem, too.

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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

[Manfred Hollstein]

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.


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

[Manfred Hollstein]

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.

:

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


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

[Manfred Hollstein]

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


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

[Manfred Hollstein]

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

Again, thanks a lot for your effort! Olaf, Sagi: can you please ensure
that Dave's patches get merged and fed into Kodi 17.4? I don't have an
account on PMBS, so we rely on you (as usual) ;)

> Dave

TIA, cheers.

l8er
manfred


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

[Manfred Hollstein]

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


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

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

[Manfred Hollstein]

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 below.
> > 
> > My question really is: does this addon work for anyone?
> 
> I found the reason; the version of the python-pyOpenssl package is
> apparently too old. Interestingly Kodi+Youtube run even without the
> package being installed. But, since it is required by package
> xorg-x11-Xvnc (which is installed on my systems - need to check if I
> actually need it), I worked around it by creating a fake package
> pretending it provides all the pyOpenssl related symbols, and now the
> Youtube plugin works in Kodi.

it turns out that I don't actually need xorg-x11-Xvnc, so I removed the
package and all of its dependencies. No need for python-pyOpenssl
anymore, and Kodi and Youtube still work OK ;)

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 found the reason; the version of the python-pyOpenssl package is
apparently too old. Interestingly Kodi+Youtube run even without the
package being installed. But, since it is required by package
xorg-x11-Xvnc (which is installed on my systems - need to check if I
actually need it), I worked around it by creating a fake package
pretending it provides all the pyOpenssl related symbols, and now the
Youtube plugin works in Kodi.

HTH, cheers.

l8er
manfred

> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~/.kodi/temp/kodi.log: 
> >>>>>>>>>>>>>>>>>>>>>>>>>
> 12:46:41.236 T:140175436674816  NOTICE: [plugin.video.youtube] Startup: 
> detected Krypton (Kodi-17.4), setting DASH_SUPPORT_BUILTIN = False, 
> DASH_SUPPORT_ADDON = True
> 12:47:07.183 T:140175961847552 WARNING: [plugin.video.youtube] Switching API 
> key set from  to 1
> 12:47:07.198 T:140175961847552  NOTICE: [plugin.video.youtube] Running: 
> YouTube (5.4.5) on Krypton (Kodi-17.4) with Python 2.7.13
> 12:47:12.911 T:140175961847552  NOTICE: Previous line repeats 2 times.
> 12:47:12.911 T:140175961847552   ERROR: EXCEPTION Thrown 
> (PythonToCppException) : -->Python callback/script returned the following 
> error<--
>  - NOTE: IGNORING THIS CAN LEAD 
> TO MEMORY LEAKS!
> Error Type:  'requests.exceptions.SSLError'>
> Error Contents: ('bad handshake: 
> SysCallError(0, None)',)
> Traceback (most recent call last):
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/default.py", 
> line 7, in 
> runner.run(__provider__)
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/kodion/runner.py",
>  line 40, in run
> __RUNNER__.run(provider, 
> context)
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/kodion/impl/xbmc/xbmc_runner.py",
>  line 23, in run
> results = 
> provider.navigate(context)
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/kodion/abstract_provider.py",
>  line 83, in navigate
> self._process_wizard(context)
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/kodion/abstract_provider.py",
>  line 73, in _process_wizard
> 
> wizard_step[0](*wizard_step[1])
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/youtube/helper/yt_setup_wizard.py",
>  line 58, in process
> _process_language(provider, 
> context)
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/youtube/helper/yt_setup_wizard.py",
>  line 16, in _process_language
> json_data = 
> client.get_supported_languages(kodi_language)
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/youtube/client/youtube.py",
>  line 104, in get_supported_languages
> return 
> self._perform_v3_request(method='GET', path='i18nLanguages', params=params)
>   File 
> "/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/youtube/client/youtube.py",
>  line 636, in _perform_v3_request
> result = requests.get(_url, 
> params=_params, headers=_headers, verify=self._verify, 
> allow_redirects=allow_redirects)
>

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

[Manfred Hollstein]

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
Description: PGP signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

[packman] When will kodi-17.6 be available?

[Manfred Hollstein]

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
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

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

[Manfred Hollstein]

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.3, no?
> 
> Which change in 17.6 is a must-have?
> 
> https://github.com/xbmc/xbmc/compare/17.5-Krypton...17.6-Krypton

dunno, but I keep getting error messages for the auto-update feature of
various plugins/extensions; looks like some checks refuse to install
updates (audio and video scrapers for instance).

> I assume the maintainer will find some time to upgrade the pkg at some point.
> 
> Olaf

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 signature
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

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

[Manfred Hollstein]

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


<< ~/.kodi/temp/kodi.log: 
>
12:46:41.236 T:140175436674816  NOTICE: [plugin.video.youtube] Startup: 
detected Krypton (Kodi-17.4), setting DASH_SUPPORT_BUILTIN = False, 
DASH_SUPPORT_ADDON = True
12:47:07.183 T:140175961847552 WARNING: [plugin.video.youtube] Switching API 
key set from  to 1
12:47:07.198 T:140175961847552  NOTICE: [plugin.video.youtube] Running: YouTube 
(5.4.5) on Krypton (Kodi-17.4) with Python 2.7.13
12:47:12.911 T:140175961847552  NOTICE: Previous line repeats 2 times.
12:47:12.911 T:140175961847552   ERROR: EXCEPTION Thrown (PythonToCppException) 
: -->Python callback/script returned the following error<--
 - NOTE: IGNORING THIS CAN LEAD TO 
MEMORY LEAKS!
Error Type: 
Error Contents: ('bad handshake: 
SysCallError(0, None)',)
Traceback (most recent call last):
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/default.py", 
line 7, in 
runner.run(__provider__)
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/kodion/runner.py",
 line 40, in run
__RUNNER__.run(provider, 
context)
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/kodion/impl/xbmc/xbmc_runner.py",
 line 23, in run
results = 
provider.navigate(context)
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/kodion/abstract_provider.py",
 line 83, in navigate
self._process_wizard(context)
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/kodion/abstract_provider.py",
 line 73, in _process_wizard
wizard_step[0](*wizard_step[1])
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/youtube/helper/yt_setup_wizard.py",
 line 58, in process
_process_language(provider, 
context)
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/youtube/helper/yt_setup_wizard.py",
 line 16, in _process_language
json_data = 
client.get_supported_languages(kodi_language)
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/youtube/client/youtube.py",
 line 104, in get_supported_languages
return 
self._perform_v3_request(method='GET', path='i18nLanguages', params=params)
  File 
"/home/manfred/.kodi/addons/plugin.video.youtube/resources/lib/youtube_plugin/youtube/client/youtube.py",
 line 636, in _perform_v3_request
result = requests.get(_url, 
params=_params, headers=_headers, verify=self._verify, 
allow_redirects=allow_redirects)
  File 
"/home/manfred/.kodi/addons/script.module.requests/lib/requests/api.py", line 
70, in get
return request('get', url, 
params=params, **kwargs)
  File 
"/home/manfred/.kodi/addons/script.module.requests/lib/requests/api.py", line 
56, in request
return 
session.request(method=method, url=url, **kwargs)
  File 
"/home/manfred/.kodi/addons/script.module.requests/lib/requests/sessions.py", 
line 488, in request
resp = self.send(prep, 
**send_kwargs)
  File 
"/home/manfred/.kodi/addons/script.module.requests/lib/requests/sessions.py", 
line 609, in send
r = adapter.send(request, 
**kwargs)
  File 
"/home/manfred/.kodi/addons/script.module.requests/lib/requests/adapters.py", 
line 497, in send
raise SSLError(e, 
request=request)

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

[Manfred Hollstein]

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 shows 319 packages in the state "unresolvable" for architecture
"x86_64" .
I'm not sure if we just need to wait, but since "aarch64" doesn't have
this problem, I thought I'd just ask...

TIA, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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" <https://pmbs.links2linux.org/project/show/Multimedia>.
> 
> Known bugs in OBS:
> 
> https://lists.opensuse.org/opensuse-factory/2018-05/msg00141.html
> https://lists.opensuse.org/opensuse-factory/2018-05/msg00149.html

now I see... I have just asked the _project maintainer_ to make the
necessary changes to the project config. Will see what'll happen.

> Olaf

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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

there's a problem in the OBS setup of Leap 15.0 resulting in any project
using Leap 15.0 as a base not being able to resolve any packages any
more. There are more details in the following threads:

  
  
  

> Greetings
> Udo Lubich

HTH, cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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
> > > schrieb Manfred Hollstein <manfre...@gmx.net>:
> > > 
> > > > PMBS shows 319 packages in the state "unresolvable" for architecture
> > > > "x86_64" <https://pmbs.links2linux.org/project/show/Multimedia>.
> > > 
> > > Known bugs in OBS:
> > > 
> > > https://lists.opensuse.org/opensuse-factory/2018-05/msg00141.html
> > > https://lists.opensuse.org/opensuse-factory/2018-05/msg00149.html
> > 
> > now I see... I have just asked the _project maintainer_ to make the
> > necessary changes to the project config. Will see what'll happen.
> 
> In <https://lists.opensuse.org/opensuse-factory/2018-05/msg00232.html>
> Richard Brown indicates that the Packman _project maintainer_ has to
> change the project config. Do you know _what_ must be changed?

Scratch this. Jim Berry just showed in another e-mail in that thread
that the problem is caused on the openSUSE OBS side.

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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 shows 319 packages in the state "unresolvable" for architecture
> > > "x86_64" <https://pmbs.links2linux.org/project/show/Multimedia>.
> > 
> > Known bugs in OBS:
> > 
> > https://lists.opensuse.org/opensuse-factory/2018-05/msg00141.html
> > https://lists.opensuse.org/opensuse-factory/2018-05/msg00149.html
> 
> now I see... I have just asked the _project maintainer_ to make the
> necessary changes to the project config. Will see what'll happen.

In <https://lists.opensuse.org/opensuse-factory/2018-05/msg00232.html>
Richard Brown indicates that the Packman _project maintainer_ has to
change the project config. Do you know _what_ must be changed?

> > Olaf

Cheers.

l8er
manfred


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

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

[Manfred Hollstein]

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.

l8er
manfred

> On 2018-05-22 08:42, Olaf Hering wrote:
> > Am Sun, 20 May 2018 17:07:51 -0500
> > schrieb Jimmy Berry :
> > 
> > > For now this can be worked around by dropping ports from project
> > > config on packman. Once fixed on OBS it can be re-added.
> > 
> > This would wipe all aarc64 packages. Not an option.
> > 
> > Olaf


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

Re: [packman] ffmpeg4

[Manfred Hollstein]

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.
> 
> Maybe I'm being dumb, but YaST still wants to install the openSUSE
> version of libavformat58 when I ask it to upgrade chromium?

see below.

> >Anyone who spots the typo will get an uncrippled version of it. For
> >free. And automatically.
> 
> Huh? ;)

It's probably related to Olaf's commit message:

  link to 'openSUSE.org:openSUSE:Leap:42.2:Update' package='ffmpeg2'

(please notice the 42.2 thing...). Looking at the ffmpeg-4 build for
15.0 and 42.3 shows:

  15.0: succeeded for x86_64 (so, wait for an update of your mirror)
  42.3: unresolvable: nothing provides libmysofa-devel, nothing provides
pkgconfig(libopenmpt), nothing provides pkgconfig(srt),
nothing provides pkgconfig(ffnvcodec)

> >Olaf

Hmm...

Cheers.

l8er
manfred


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

Re: [packman] ffmpeg4

[Manfred Hollstein]

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

while there is a package for openSUSE_Leap_42.3 (presumably
"A_42.3-ffmpeg-4"), it sits there and cannot be built due to several
unresolved requirements:

  nothing provides libmysofa-devel,
  nothing provides pkgconfig(libopenmpt),
  nothing provides pkgconfig(srt),
  nothing provides pkgconfig(ffnvcodec)

For instance, the "mysofa" stuff is conditionalized using

  %if 0%{?suse_version} > 1500
  %bcond_without mysofa
  ...
  %else
  %bcond_with mysofa
  %endif

  %if %{with mysofa}
  BuildRequires:libmysofa-devel
  %endif

This can't be right as on openSUSE_Leap_42.3 %suse_version is defined as
1315, so all comparisons of "%suse_version" with 1500 don't work as
probably expected.

Can someone please take a look? Thx.

> Olaf

Cheers.

l8er
manfred


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