Re: [packman] again LMMS
On 16 February 2015 at 10:01, Stephan Barth snba...@suse.de wrote: Hi Cristian, Am 15.02.2015 um 00:44 schrieb Cristian Morales Vega: I have not seen your SR. But apparently there is a big issue with 1.1.2 (https://github.com/LMMS/lmms/issues/1757), sorry. I have committed the real 1.1.0 version (Stephan, if you need help with git just ask, you may want to look at man git-archive), so hopefully the problem reported by Guus should get fixed. I noticed my mistake already and accidently found out how to fix it recently (git checkout stable-1.1 :) I just had no time to build and submit a new package. No, stable-1.1 is a branch. You want the tags. This is version 1.1.0: https://github.com/LMMS/lmms/commits/v1.1.0 This is version 1.1.2: https://github.com/LMMS/lmms/commits/v1.1.2 This is the stable-1.1 branch: https://github.com/LMMS/lmms/commits/stable-1.1 The stable-1.1 branch is already 3 commit over 1.1.2. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] again LMMS
If you used git clone https://github.com/LMMS/lmms.git -b stable-1.1 you are not using version 1.1.0, but the latest 1.1.x (maybe unreleased) version. I see that 2 days ago they released version 1.1.2 ( https://github.com/LMMS/lmms/releases). So probably that will fix the issues you found. Can somebody with more time than me please submit the update to multimedia:libs? Thanks. On 12 February 2015 at 00:00, guus guus.po...@upcmail.nl wrote: Hi Christian I am recompiling lmms, because I had to reinstall openSUSE. I used this command to clone the git. git clone https://github.com/LMMS/lmms.git -b stable-1.1 No idea if this is helping you, but I don't think it will harm either. friendly regards, Guus Op 09-02-15 om 20:42 schreef Cristian Morales Vega: On 5 February 2015 at 20:28, guus guus.po...@upcmail.nl wrote: The most important issue, I noticed with the latest version, midi recording is not working. There was another issue, were I cant mute a track. Can you show us how to reproduce this problems, keeping in mind that probably nobody here has ever actually used lmms? I am far from a Linux expert, I only managed to compile this program with help from two Linux forums. Did you do anything special? Packman's build is a standard 1.1.0 build (no master branch), built with a simple cmake followed by make. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] openSUSE 13.1 - Gmerlin Packages missing
On 11 May 2014 11:03, Stefan Botter j...@jsj.dyndns.org wrote: Hi Cristian, On Sun, 11 May 2014 10:37:48 +0100 Cristian Morales Vega reddw...@opensuse.org wrote: Stefan, there seems to be a problem with the mirroring of the packages. The packages are building but for example neither http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_13.1/Multimedia/i586/ http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_13.1/Multimedia/i586/ has gmerlin. Extra weird because ftp.gwdg.de has gmerlin-avdecoder but ftp.halifax.rwth-aachen.de doesn't. I know I am a little bit slow with giving updates about the PMBS healing progress. We currently still have a problem with packages from Multimedia. Our publishing process is not just the stock obs publishing task, we sync the packages to out packman.links2linux.de server, and there the packages will be checked for authenticity, re-signed with our GPG key, and then published. Since the bumpy update to obs 2.5.x not all packages on PMBS are signed with out PMBS signing key, but with some other key. There the authenticity check fails, and the offending package will not get published to the mirrors. As the only way out Marc and I will add the - now identified - other key to the authorized keys, and once this is implemented, we will start rebuilding Multimedia again - there are some additional workers there, as you may have noticed. This will then hopefully solve the problems with the missing packages, but will also take some hours. Once everything is resolved, I will notify the list again. Thanks. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] SLE 11
On 18 November 2013 13:54, Hendrik Vogelsang hvo...@hennevogel.de wrote: Let's build for the latest SP that is available, forget about the rest. Anybody has anything to say against this? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] moc package missing for openSUSE 13.1
On 29 November 2013 12:45, Flavio Castelli fla...@castelli.me wrote: Hello, I noticed the moc package is not being built for openSUSE 13.1 [1]. I installed the one for tumbleweed and everything works fine, but it would be definitely better to have this package built also for 13.1 The moc package shipped by the official openSUSE repositories does not have mp3 playback support. I am surprised somebody is actually still using it. But fixed... ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] SLE 11
On 17 November 2013 18:21, Christian ch...@computersalat.de wrote: SLE_11 is 'GA' and is obsolete. so you should at least use SLE_11_SP1 to build against. This has been announced somewhere? And just one question left: Why is 'obs' (b.o.o) offering three (SP1-3) to build against, when it would be enough to build just against 'GA' ??? Because some packages may not build against GA, or not with all the features. That's why I suggested disabling, and not deleting the other repos. AFAIK the different SLE_11 are NOT binary compatible. darix told me. It could be clearer. But my reference is http://lists.opensuse.org/opensuse-packaging/2010-02/msg00081.html ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Deleting Evergreen 11.1
https://bugs.links2linux.org/browse/PM-60 was open 1 year ago. And even at that point Evergreen 11.1 had been unmaintained for a while. So, if on the first of December nobody has complained, I will delete it. By the way, http://en.opensuse.org/openSUSE:Evergreen says Evergreen 11.2 support will end on Nov 2013. So it could also be deleted on the same day... ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] GStreamer on 13.1
On 15 November 2013 10:26, Olaf Hering o...@aepfle.de wrote: On Fri, Nov 15, Cristian Morales Vega wrote: A full install also includes all those libgst*-1_0-0-1.2* packages! Most probably you just miss them. Is the following good enough? zypper can tell you better. But yes, looks OK. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] GStreamer on 13.1
On 11 November 2013 15:24, Richard Brown rbrown...@opensuse.org wrote: On Mon, 2013-11-11 at 15:10 +, Cristian Morales Vega wrote: On 11 November 2013 15:02, Richard Brown rbrown...@opensuse.org wrote: I already *have* all the GStreamer 1.2 packages from Packman manually installed, but Totem/GStreamer+PackageKit clearly wants the 1.0 (from 13.1 oss repo) as well. I think Dominique/Dimstar is the openSUSE person who better understands it, you may ask him. But AFAIK Totem/GStreamer+PackageKit should not want the 1.0 as well. The 1.2 packages *are* enough, and it should be happy with them. Asking for the 1.0 one is IMHO a bug. At least that's the theory I'd like to pursue, unless there is an absolutely compelling reason why Packman must provide GStreamer 1.2 when 13.1 is released? Packman has a long tradition of providing the latest version. Whether that's a good idea or not is debatable, but long traditions are always difficult to change. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] GStreamer on 13.1
On 11 November 2013 15:53, Cristian Morales Vega cristian.morales.v...@gmail.com wrote: On 11 November 2013 15:24, Richard Brown rbrown...@opensuse.org wrote: On Mon, 2013-11-11 at 15:10 +, Cristian Morales Vega wrote: On 11 November 2013 15:02, Richard Brown rbrown...@opensuse.org wrote: I already *have* all the GStreamer 1.2 packages from Packman manually installed, but Totem/GStreamer+PackageKit clearly wants the 1.0 (from 13.1 oss repo) as well. I think Dominique/Dimstar is the openSUSE person who better understands it, you may ask him. But AFAIK Totem/GStreamer+PackageKit should not want the 1.0 as well. The 1.2 packages *are* enough, and it should be happy with them. Asking for the 1.0 one is IMHO a bug. I just checked in my 12.3, which is in *exactly* the same situation: Totem from openSUSE, compiled against GStreamer 1.0 from openSUSE, works just fine with GStreamer 1.2 from Packman. When I uninstall gstreamer-plugins-libav the video fails to play, but Totem doesn't ask me to install it. I guess there is something broken in 12.3 that was fixed in 13.1. Perhaps when fixing that a new problem appeared? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Repository layout clarification
On 14 November 2013 13:12, Tomáš Chvátal tomas.chva...@gmail.com wrote: As I was asked on irc I wrote bit update what I ment with my last mail about repo restructuralization. The gmail loves to mess up the formatting when I tried to paste it in so I uploaded it on webserver [1]. If you want to comment some section just copy it from the file into the reply and I will try to adjust and change the file as we proceed. Any suggestions for why is it bad idea or any other are welcome. Side benefit of this change is that we can not link some pacakges on purpose and use SR#s to include the changes into older distributions. Eg. keeping older ffmpeg in 13.1 repo over the Factory one because we know it is prone to be broken, etc. etc. Sorry, what? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] GStreamer on 13.1
On 11 November 2013 20:41, Cristian Morales Vega christian.morales.v...@gmail.com wrote: On 11 November 2013 15:53, Cristian Morales Vega cristian.morales.v...@gmail.com wrote: On 11 November 2013 15:24, Richard Brown rbrown...@opensuse.org wrote: On Mon, 2013-11-11 at 15:10 +, Cristian Morales Vega wrote: On 11 November 2013 15:02, Richard Brown rbrown...@opensuse.org wrote: I already *have* all the GStreamer 1.2 packages from Packman manually installed, but Totem/GStreamer+PackageKit clearly wants the 1.0 (from 13.1 oss repo) as well. I think Dominique/Dimstar is the openSUSE person who better understands it, you may ask him. But AFAIK Totem/GStreamer+PackageKit should not want the 1.0 as well. The 1.2 packages *are* enough, and it should be happy with them. Asking for the 1.0 one is IMHO a bug. I just checked in my 12.3, which is in *exactly* the same situation: Totem from openSUSE, compiled against GStreamer 1.0 from openSUSE, works just fine with GStreamer 1.2 from Packman. When I uninstall gstreamer-plugins-libav the video fails to play, but Totem doesn't ask me to install it. I guess there is something broken in 12.3 that was fixed in 13.1. Perhaps when fixing that a new problem appeared? And it also works in my new 13.1 installation. Something is broken in your system. You may want to run: rm -rf ~/.cache/gstreamer-1.0 ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Can't decode H.264 video after latest gstreamer update to 1.2.0
The problem is that some parts update automatically from the main OBS. Usually I would have took care of it. But my laptop died and now I am using a Frankenstein that is slowing me down. Looking into it now. Thanks for the report. On 8 November 2013 15:05, Holger Arnold holge...@gmail.com wrote: Hi, after Packman's latest update of the gstreamer 1.0 plugins to version 1.2.0, programs using gstreamer can no longer decode H.264 video files. I suspect this is because only gstreamer-base, gstreamer-plugins-good, and gstreamer-plugins-ugly have been updated to version 1.2, while gstreamer-plugins-bad and gstreamer-plugins-libav are still at 1.0. Wouldn't it be better to always update all gstreamer packages at the same time to avoid such version incompatibilities? Thanks, Holger ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] GStreamer on 13.1
On 11 November 2013 14:12, Richard Brown rbrown...@opensuse.org wrote: With the current Packman packages in your 13.1 repos, we seem to hit a problem which make your packages unusable - the userspace tools (eg. Totem) appear to be requiring gstreamer version 1.0.x, but as Packman provides 1.2.x, there’s currently no way to play proprietary media on 13.1 appear? If you try, you often just get the auto solver pop up, and then subsequently freak out when it tries to install both 1.0.x and 1.2.x and they conflict with each other You shouldn't try to install both, only 1.2. Can I see that auto solver pop up? Can we get all the packages for 13.1 set to gstreamer 1.0.x, or find out what's really going on? From http://gstreamer.freedesktop.org/news/ The GStreamer team is pleased to announce the first release of the stable 1.2 release series. The 1.2 release series is adding new features on top of the 1.0 series and is part of the API and ABI-stable 1.x release series of the GStreamer multimedia framework that contains new features. I didn't have time (or a proper computer) to check. But AFAIKT GStreamer 1.2 is 100% compatible with GStreamer 1.0. What's the problem? If the problem is that the Totem package is hardcoding a dependency to GStreamer == 1.0 then what must be fixed is the Totem package. But looking at https://build.opensuse.org/package/show/openSUSE:13.1/totem I can't see such a thing. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] GStreamer on 13.1
On 11 November 2013 15:02, Richard Brown rbrown...@opensuse.org wrote: On 11 November 2013 15:57, Cristian Morales Vega reddw...@opensuse.org wrote: You shouldn't try to install both, only 1.2. Can I see that auto solver pop up? Here it is: http://i2.minus.com/iVUjY1o1xdg4S.png I don't use Gnome, but that seems to be the GStreamer-PackageKit integration. It appears automatically when you try to play a video for which you don't have the decoder? If so, trying to install both 1.0 and 1.2 is a bug in the GStreamer-PackageKit integration. You should report it at https://bugzilla.novell.com/. If you assign it to the Gnome team I am sure you will get a reply soon. By the way, the fact that gstreamer-plugins-base-1.0.10-2.1.3 (64-bit) appears twice is clearly an indication that something is wrong there. Can we get all the packages for 13.1 set to gstreamer 1.0.x, or find out what's really going on? From http://gstreamer.freedesktop.org/news/ The GStreamer team is pleased to announce the first release of the stable 1.2 release series. The 1.2 release series is adding new features on top of the 1.0 series and is part of the API and ABI-stable 1.x release series of the GStreamer multimedia framework that contains new features. I didn't have time (or a proper computer) to check. But AFAIKT GStreamer 1.2 is 100% compatible with GStreamer 1.0. What's the problem? If the problem is that the Totem package is hardcoding a dependency to GStreamer == 1.0 then what must be fixed is the Totem package. But looking at https://build.opensuse.org/package/show/openSUSE:13.1/totem I can't see such a thing. I can understand where you're coming from, but if that was the case, then I shouldn't be having any problem playing media on my 13.1 laptop. Can you get it working fine? I don't have a 13.1 system yet. But you should be able to use zypper to install the GStreamer (1.2) packages from Packman manually and then the GStreamer-PackageKit integration will not be needed. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Can't decode H.264 video after latest gstreamer update to 1.2.0
From what I can see GStreamer 1.2 is compatible with GStreamer 1.0. In any case, I just tested a H.264 video with gst-launch-1.0 and at least now it's working fine. On 9 November 2013 16:55, Holger Arnold hol...@harnold.org wrote: The problem is that some parts update automatically from the main OBS. Maybe the gstreamer sub-packages should all require a particular major version of the gstreamer main package. This would prevent users from updating gstreamer to a new major version until all installed packages are actually available in the new version. Holger ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Disabling aRts
You removed the last line of my email. Are you fine with _with_arts being in the prjconf, or with me removing it? On 7 November 2013 12:05, Stefan Botter j...@jsj.dyndns.org wrote: On Thu, 7 Nov 2013 10:03:06 + Cristian Morales Vega reddw...@opensuse.org wrote: The latest MPlayer update wants to install aRts (and Qt3). It seems to be because we have %define _with_arts 1 %_with_arts 1 In the Essentials prjconf. Fine with me. Stefan -- Stefan Botter zu Hause Bremen ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] vlc-codecs cannot be installed because of missing dependency
On 11 September 2013 06:08, Christian Trippe ctri...@opensuse.org wrote: libva.so.1(VA_API_0.33.0)(64bit) You are using the Factory repo $ rpm -qRp http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_12.3/Essentials/x86_64/vlc-codecs-2.0.8a-158.2.x86_64.rpm | fgrep libva libva-x11.so.1()(64bit) libva.so.1()(64bit) $ rpm -qRp http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Factory/Essentials/x86_64/vlc-codecs-2.0.8a-158.2.x86_64.rpm | fgrep libva libva-x11.so.1()(64bit) libva.so.1()(64bit) libva.so.1(VA_API_0.33.0)(64bit) ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] audacious-plugins 3.2.4-1.4 (openSUSE 12.3/x86_64)
On 18 April 2013 07:46, Wolfgang Bauer e9325...@student.tuwien.ac.at wrote:
Am Mittwoch, 17. April 2013, 23:17:20 schrieb Mariusz Fik:
Dnia wtorek, 16 kwietnia 2013 22:23:52 Bob Goddard pisze:
Here we go again...
You are now building the latest version, 3.3.54 which is good.
HOWEVER
The weekly/fortnightly rebuilds do not build anything with those with
plugins in the name.
Meaning that all the plugins do not get rebuilt at the same time and as
there will be a mismatch in the build, Audacious will not start.
You mean plugins requires audacious in the same version-release?
Ie, if audacious is 3.3.4-1.6 and plugins are 3.3.4-1.2, then they won't
work, but if those pluginsa are the same, 3.3.4-1.6, then they will do
work? If so,
then we need to change in audacious-plugins.spec this line:
| BuildRequires: pkgconfig(audacious) = %{version}
to:
| BuildRequires: pkgconfig(audacious) = %{version}-%{release}
Thanks to this, audacious-plugins package will get rebuilding against
audacious in most current version. Am I right? Any opinions?
I don't think this is necessary!
It is not! You don't even need the same version. Audacious 3.3.4 is
compatible with the plugin APIs 40 and 41. The plugin API 40 was used
even before the final 3.3 version was released.
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] libcdio in Multimedia
Why do we have libcdio in Multimedia? I was surprised when zypper offered me to change the package in my openSUSE 12.3 installation. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] libcdio in Multimedia
On 15 April 2013 20:28, Cristian Morales Vega christian.morales.v...@gmail.com wrote: Why do we have libcdio in Multimedia? I was surprised when zypper offered me to change the package in my openSUSE 12.3 installation. If nobody disagrees I will substitute it for a link to openSUSE:Current and will disable the build for 12.3 and Factory. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Sox doesn't seem to support MP3 for OpenSUSE 12.3
On 18 March 2013 04:46, David Walker da...@walkerstreet.info wrote: I just upgraded to OpenSUSE 12.3, and the sox in Packman doesn't seem to have support for MP3 encoding/decoding. Is support still included in the package? Yes, support is still included in the package. Not the most verbose bug report ever. But I guess you installed sox from Packman and libsox2 from openSUSE. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] VLC media player
There was never a exhaustive set of rules written. And actually I am not sure they could be written. Answering your question. Why is VLC in Essentials? The answer perhaps is not a good one. But I would say it's just because when the split was done VLC was a very popular player (I guess it continues being it) and a single person decided to put it there. If it's so popular that everybody will add the Multimedia repo to have it what's the point of splitting Essentials from Multimedia? It is wrong? Perhaps: * True, it's a full multimedia application - Let's move it to Multimedia * But it's also a library (libvlc) that can be used to create other applications - Essentials * But in practice libvlc has never been as popular as GStreamer or libxine - Multimedia * It's not essential enough for openSUSE to package it as it does with libxine - Multimedia * That's probably just because nobody wants to do the hard and boring work of working through the legal problems of creating a cripped package. Otherwise it would be there. - Essentials * The Phonon backend depends on it. For sure Phonon backends are as low level/essential as anything could ever be for KDE - Essentials No easy answer. Let's just keep it in Essentials. On 2 March 2013 07:36, Alexey Svistunov sv...@svalx.net wrote: В Пт., 01/03/2013 в 13:46 +0100, todd rme пишет: On Mar 1, 2013 10:28 AM, Alexey Svistunov sv...@svalx.net wrote: Why VLC placed in Essentials Packman project but not Multimedia? It is a fully multimedia application. I think because it is a dependency of other packages. It is the same reason gstreamer is in Essentials. ___ I find https://bugs.links2linux.org/browse/PM-6 that define a clear policy about what should be in Essentials. But I still think VLC and Gstreamer must be in Multimedia. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] openSUSE 12.3
The build for openSUSE 12.3 is enabled. But will it appear in the FTPs or there is some extra configuration needed? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] gstreamer-0_10-plugins-bad-0.10.23-19.1 (openSUSE 12.2/i586)
I will look into it when I get time. But if you can verify
really-fix-h264-parsing.patch fixes the problem feel free to create a
submit request to multimedia:libs. Once it reaches Factory the fix
will also appear in Packman.
On 22 February 2013 13:58, Michal Vyskocil michal.vysko...@gmail.com wrote:
Hi packman team,
thanks a lot for making your great project. However after last update,
I've found that video in minitube does not work. After several
attempts including reinstallation of complete gstreamer stack I have
visited the minitube forum and realized there is a gstreamer bug
affecting some applications including minutube
See
http://flavio.tordini.org/forums/topic/gstreamer-bug-affecting-ubuntu-12-04-and-other-recent-linux-distributions
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad0.10/+bug/973014
What I can say is the recommended workaround
sudo mv /usr/lib/gstreamer-0.10/libgstvideoparsersbad.so{,.bak}
worked well on my system (stadard openSUSE + gstreamer from Packman)
--
best regards
Michal Vyskocil
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] jack in Essentials
Ping. On 6 January 2013 23:08, Cristian Morales Vega reddw...@opensuse.org wrote: 12 days ago jack was added to Essentials. What's the reason? It really needs to be built for Factory? Should we try to make it build for openSUSE = 12.1? Otherwise I guess it's better to explicitly disable it instead of leaving it in unresolvable state. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] gnome media player buttons
On 31 January 2013 14:47, Dutch Kind dutchk...@txoriaskea.org wrote: Hi, I have Gnome Media Player installed in Opensuse 12.2 64bits with KDE. Since a while I don't see the button icons anymore, just squares with a cross as if the image file is missing. I tried installing other icon themes, changed themes, etc, nothing helps. I first noticed while running the mediaplayer in firefox, I thought it was a firefox thing but then I saw the actual program did the same. I don't know if something is missing on my system or if it is a bug, but it would be nice if it could be fixed. Btw, when I installed Gnome Media Player, long ago, it was ok, so it must have been something from recent months which I didn't notice because I don't use it that often. Try with gtk-update-icon-cache /usr/share/icons/hicolor/ (as root) ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] XBMC 12.0 undefined symbol error
On 1 February 2013 00:54, Philipp Seiler p.sei...@linuxmail.org wrote: Hi Mariusz, On Thu, 31 Jan 2013 23:29:52 +0100 Mariusz Fik fisi...@jabster.pl wrote: Dnia czwartek, 31 stycznia 2013 22:11:44 Philipp Seiler pisze: philipp@newton ~ % xbmc /usr/lib64/xbmc/xbmc.bin: symbol lookup error: /usr/lib64/xbmc/xbmc.bin: undefined symbol: _ZTIN6TagLib5ID3v219Latin1StringHandlerE You have installed in Your system other version of taglib library then You build xbmc against. You're right ;) How did you found the wrong library? Look at _ZTIN6TagLib5ID3v219Latin1StringHandlerE for two minutes and you will see it in 3D. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] kdenlive 0.9.4-31.1
kdenlive 0.9.4 is not even available in Packman (will be once https://build.opensuse.org/request/show/150432 is accepted). It looks like a problem to report directly in http://www.kdenlive.org/bug-reports. But when reporting problems knowing where your packages come from would be nice. On 30 January 2013 14:20, Christoph Walzer christoph.wal...@wcr-edv.com wrote: Since last update (0.9.4-31.1) kdenlive does not show the white line indicating the gain level when applying the volume efffect to a piece of audio - oh wait it does but just when the audio piece is placed on first video track!? But then it is not really usable (no grabbing and dragging). So anyway: no gain level indicating line on audio tracks with volume effect enabled audio pieces. Regards ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] mlt/melt/kdenlive
On 28 January 2013 19:55, Dmitry Roshchin dmi...@roshchin.org wrote: On Monday 21 January 2013 22:44:00 Cristian Morales Vega wrote: The libmlt problem should be fixed with the update to 0.8.8. Can you push updates to multimedia:libs/libmlt ? We are in feature freeze. I am not supposed to put updates in there. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] mlt/melt/kdenlive
On 15 January 2013 21:37, Marcelo Borro marcelovbo...@gmail.com wrote: On kdenlive if I add an mp4 vídeo or an mp3 audio track, I have no sound from it. But if I convert the mp3 audio in wav with Audacity, then sound works. Yes, I can reproduce it. It's a bit suspicious that the problem has started now that libavresample just changed its soname. But I don't really have any real idea about where the problem is. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] jack in Essentials
12 days ago jack was added to Essentials. What's the reason? It really needs to be built for Factory? Should we try to make it build for openSUSE = 12.1? Otherwise I guess it's better to explicitly disable it instead of leaving it in unresolvable state. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] VLC missing dependency (pulseaudio)
On 20 November 2012 20:25, Jonathan Fischer Friberg odysso...@gmail.com wrote: So here's the deal: VLC (the package 'vlc') is missing the package 'vlc-aout-pulse' as dependency. https://bugs.links2linux.org/browse/PM-4 ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] VLC missing dependency (pulseaudio)
On 20 November 2012 21:11, Jonathan Fischer Friberg odysso...@gmail.com wrote: You must log in to access this page. It's not VLC, the whole Packman repository is broken. It has been for at least one year :-( ps. you should be able to register without problems. Even if probably read access should be public. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] VLC missing dependency (pulseaudio)
On 20 November 2012 21:26, Jonathan Fischer Friberg odysso...@gmail.com wrote: The whole of packman is broken? Wow, that sounds bad. How come it's broken? Register in the bug tracker and read the bug report for the details... Lack of man power, openSUSE specific extensions and a Debian server... ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Important GStreamer patch
On 19 November 2012 18:55, Martin Schlander martin.schlan...@gmail.com wrote: Hi One of the Phonon developers dropped by the #opensuse-kde IRC channel, saying that: This bug: https://bugs.kde.org/show_bug.cgi?id=302652 (When going from a mp3 track to an ogg track, Amarok stops playing) Is fixed by this GStreamer patch: http://cgit.freedesktop.org/gstreamer/gst- plugins-base/commit/?id=3880323 Since I'm personally hit by that issue, I'd be very happy if someone could apply that patch to the Packman GStreamer packages ;-) Even if you trigger it with MP3s the bug is not Packman specific. https://build.opensuse.org/request/show/141972 ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Important GStreamer patch
On 19 November 2012 21:34, Martin Schlander martin.schlan...@gmail.com wrote: Mandag den 19. november 2012 21:21:08 skrev Cristian Morales Vega: On 19 November 2012 18:55, Martin Schlander martin.schlan...@gmail.com wrote: Hi One of the Phonon developers dropped by the #opensuse-kde IRC channel, saying that: This bug: https://bugs.kde.org/show_bug.cgi?id=302652 (When going from a mp3 track to an ogg track, Amarok stops playing) Is fixed by this GStreamer patch: http://cgit.freedesktop.org/gstreamer/gst- plugins-base/commit/?id=3880323 Since I'm personally hit by that issue, I'd be very happy if someone could apply that patch to the Packman GStreamer packages ;-) Even if you trigger it with MP3s the bug is not Packman specific. https://build.opensuse.org/request/show/141972 Who said anything about Packman specific? Naturally it's upstream breakage. It's GStreamer afterall. Packman specific in contrast to openSUSE general. You reported this here, not in https://bugzilla.novell.com/. That's why I linked to a submit request in the main OBS. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] qmmp 0.6.3-3.14 (openSUSE 12.2 / i586)
On 1 November 2012 21:58, cup...@gmx.de wrote: thank you for creating qmmp package. Installation of package creates two menu entries, audio Player and video player but qmmp is not a video player. This entry should be removed. Linux packages have no menu entries. They have Categories and the Linux distribution automatically creates the menu entries from them. The categories in qmmp are AudioVideo;Player;Audio;Qt;. And the standard says that if Audio is included AudioVideo *must* also be included. I guess openSUSE is adding it to the video section because of AudioVideo. But that's a bug in openSUSE, no in the qmmp package. Please report it in http://bugzilla.novell.com/. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Video support in linphone package
On 12 October 2012 08:12, Cristian Morales Vega reddw...@opensuse.org wrote: On 12 October 2012 07:28, Vadim Kotelnikov vadimu...@gmail.com wrote: I don`t have a PMBS account. Can you post output here? I guess you want one anyway to package the plugins (http://www.linphone.org/eng/download/)? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] All builds are failing
No build log, no idea why. But every single build is failing. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] pmbs: libffmpeg-devel fails to find its dependencies
On 3 October 2012 12:58, Jürgen Weigert jnwei...@gmail.com wrote: Hey Packmen! I am re-building home:jnweiger/dvswitch and home:jnweiger/dvswitch-git and see the foolowing issues with its dependencies: openSUSE_12.1i586 succeeded openSUSE_12.1x86_64 succeeded openSUSE_12.2i586 unresolvable: nothing provides libavutil51 = 1.0 needed by libffmpeg-devel nothing provides libavutil51 = 1.0 needed by libavcodec54 nothing provides libavutil51 = 1.0 needed by libswresample0 nothing provides libavutil51 = 1.0 needed by libswscale2 nothing provides libavutil51 = 1.0 needed by libavformat54 nothing provides libavutil51 = 1.0 needed by libavdevice54 nothing provides libavutil51 = 1.0 needed by libavfilter3 nothing provides libavutil51 = 1.0 needed by libpostproc52 have choice for libidn.so.11 needed by libcurl4: libidn libidn11 have choice for libidn.so.11(LIBIDN_1.0) needed by libcurl4: libidn libidn11 I guess I can add Prefer: libidn11 to my prjconf to help with the 'have choice' issue; but I am not sure what to do about the 'nothing provides libavutil51 = 1.0' thing. Any ideas? I don't think you want that Factory there: repository name=openSUSE_12.2 path repository=standard project=openSUSE.org:openSUSE:12.2/ path repository=Factory project=Essentials/ archi586/arch archx86_64/arch /repository ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] mlt for opensuse 12.1
On 3 October 2012 12:20, Werner Franke w...@arcor.de wrote: Hello Packman Team, I'm not sure you understand german... No, I don't. I'm using openSuse 12.1 and have it installed from scratch. The installed MLT version is 0.7.8+0.7.9_78_g14c5abc-3.1 and it is from packman (said YAST2). But currently there is no known repository known for MLT. Do you habe any idea what's happen ? Latest version is 0.8.2. Is well possible that you still have an old version installed with the old soname... Shouldn't be a problem since all programs will be using the new version, just uninstall it. There is actually any problem? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Packman status
On 1 October 2012 10:44, richard -rw- weinberger richard.weinber...@gmail.com wrote: On Mon, Oct 1, 2012 at 9:57 AM, Marc Schiffbauer m...@links2linux.de wrote: I'd like to ask all maintainers who have no longer the time to maintain their packages to mark them as orphaned, than we can try to move them to the OBS. Why move? That way you will make packman die. So what? Do you want to have orphaned packages in packman? He didn't complain about the first part (mark them as orphaned), only about the second part (move). He clearly wants to have those packages maintained... in Packman. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] lmms 0.4.13-24.1 (openSUSE 12.1/x86_64)
On 15 September 2012 03:20, Cameron Rapp khy...@gmail.com wrote: Thank you, Zynaddsubfx is working now. Im now investigating why vestige is missing. I added lines to the spec file following these steps, but vestige still diddnt get built. http://nickhumphreyit.blogspot.com/2012/01/how-to-compile-and-install-vestige.html Could you check this out when you have a chance please? To easily support it on x86-64 a change needed to be done in the wine package. That change was done for 12.2. The vestige plug-in is build for all versions in i586, but only for openSUSE = 12.2 in x86-64. You could build it for = 12.1 using an updated wine package. But IMHO it's easier just to update to 12.2. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] lmms 0.4.13-24.1 (openSUSE 12.1/x86_64)
On 11 September 2012 22:15, Cristian Morales Vega reddw...@opensuse.org wrote: Until I get time to fix it. Run Fixed. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] lmms 0.4.13-24.1 (openSUSE 12.1/x86_64)
Until I get time to fix it. Run sudo chmod +x /usr/lib64/lmms/RemoteZynAddSubFx And run lmms as LD_LIBRARY_PATH=/usr/lib64/lmms/ lmms On 10 September 2012 21:03, Cameron Rapp khy...@gmail.com wrote: Hello lmms crashes when i push the Show Gui button in the zynaddsubfx plugin. minimal bt since i dont have the debug packages, let me know if i should mention this upstream. #0 0x748828dd in nanosleep () from /lib64/libc.so.6 #1 0x748ae0d4 in usleep () from /lib64/libc.so.6 #2 0x00580b12 in RemotePluginBase::receiveMessage() () #3 0x0058105e in RemotePluginBase::waitForMessage(RemotePluginBase::message const, bool) () #4 0x7fffea02045d in ZynAddSubFxInstrument::initPlugin() () from /usr/lib64/lmms/libzynaddsubfx.so #5 0x7fffea020d4c in ZynAddSubFxInstrument::reloadPlugin() () from /usr/lib64/lmms/libzynaddsubfx.so #6 0x7fffea020dd5 in ZynAddSubFxView::toggleUI() () from /usr/lib64/lmms/libzynaddsubfx.so #7 0x7fffea020e60 in ZynAddSubFxView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/lmms/libzynaddsubfx.so #8 0x769bb5aa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #9 0x7775ae12 in QAbstractButton::toggled(bool) () from /usr/lib64/libQtGui.so.4 #10 0x774a3c0e in QAbstractButton::setChecked(bool) () from /usr/lib64/libQtGui.so.4 #11 0x774a38aa in ?? () from /usr/lib64/libQtGui.so.4 #12 0x774a3b5c in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4 #13 0x77140306 in QWidget::event(QEvent*) () -- Signed thoughtfully by Cameron Rapp. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Approval ***PLEASE***
On 5 September 2012 19:00, Philipp Thomas p...@suse.de wrote: Thanks! Can you also tell me what to use as API URL in .oscrc? I don't like working in the web ui if I can avoid it. https://pmbs-api.links2linux.org You will need ca-certificates-cacert to verify the certificate. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Approval ***PLEASE***
On 5 September 2012 10:37, Philipp Thomas p...@suse.de wrote: I'm now waiting for approval of my registration for three days. Is there nobody that can do the approval? Probably just Pascal and... not sure anybody else. And I didn't know from him for some time. Probably on holidays. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] openshot 12.1 64 bits
2012/8/15 jdd j...@dodin.org: Le 14/08/2012 22:56, Cristian Morales Vega a écrit : On 14 August 2012 17:20, jdd j...@dodin.org wrote: packman 1 click install gives errors (no instruction for this distribution) for 12.1, 1 clic: Le fichier ou le lien d'installation ouvert ne contient pas d'instructions pour cette version d'openSUSE. Open a bug report in https://bugs.links2linux.org/ Solution 2: Les actions suivantes seront exécutées: désinstallation de libavcodec53-0.10.3-1.1.x86_64 désinstallation de libavdevice53-0.10.3-1.1.x86_64 installation d'une version moins récente de libmlt5-modules-0.8.0-15.1.x86_64 vers libmlt5-modules-0.8.0-6.1.x86_64 installer libmlt5-modules-0.8.0-6.1.x86_64 (avec changement de fournisseur) obs://build.opensuse.org/multimedia:libs -- http://packman.links2linux.de installation d'une version moins récente de amarok-2.5.0-19.3.x86_64 vers amarok-2.5.0-6.3.x86_64 installation d'une version moins récente de libquicktime0-1.2.4-66.4.x86_64 vers libquicktime0-1.2.4-56.2.x86_64 installation d'une version moins récente de libsox2-14.4.0-34.1.x86_64 vers libsox2-14.4.0-30.2.x86_64 désinstallation de mlt-0.7.8+0.7.9_78_g14c5abc-2.4.x86_64 Next time, please, add a LANG=C before the command. I speak three languages but none of them is French and I could be missing something. I don't see the problem with solution 2. Just apply it. See http://forums.opensuse.org/english/get-technical-help-here/how-faq-forums/unreviewed-how-faq/474523-software-management-dist-upgrade-way.html. Funny enough the installation d'une version moins récente de libquicktime0-1.2.4-66.4.x86_64 vers libquicktime0-1.2.4-56.2.x86_64 is exactly the example I put there to show the problem. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] openshot 12.1 64 bits
On 14 August 2012 17:20, jdd j...@dodin.org wrote: Hello, since 10 days, I can no more run openshot. I can neither update it with yast, always ask for not satisfied dependencies sudo zypper up openshot output? packman 1 click install gives errors (no instruction for this distribution) and there are much too many rpm to install them (any of them ask for an other one) Again, copy paste of the output. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Can't install kdenlive
On 13 August 2012 13:31, Eric Schirra e...@schirra.net wrote: Am 12.08.2012 22:47, schrieb Eric Schirra: Am 12.08.2012 11:15, schrieb Cristian Morales Vega: And i must rename libmltjackrack.so, so it does not crash. I can't reproduce that problem. When I use the libmlt5-modules-package from packman kdenlive crashes. When I use the libmlt5-modules from packman, and rename libmltjackrack, then kdenlive runs. When i use die libmlt5-modules from opensuse:KR49 kdenlive runs too and i must not rename libmltjackrack. New Info after tests. With mlt from opensuse i can not open mpg-files. So i switch back to libmlt5 from packman. Now it crashes. I rename libmltjackrack.so kdenlive from packman starts and i can open mpg's. It's now running well. Can I see the output of zypper se -s -i mlt kdenlive? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Bug tracker down
On 13 August 2012 13:50, Marc Schiffbauer m...@links2linux.de wrote: Am Freitag, 10. August 2012, 23:37:28 schrieb Cristian Morales Vega: Just in case you still didn't know, the bug tracker is down. Its up again! Thanks. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Can't install kdenlive
On 12 August 2012 09:28, Eric Schirra e...@schirra.net wrote: Am 11.08.2012 13:50, schrieb Dmitriy Perlow: Eric Schirra e...@schirra.net писал(а) в своём письме Sat, 11 Aug 2012 13:56:47 +0300: Hello. Seems to be broken because of libmlt only existance. Hello, i wan't install kdenlive on openSUSE 12.1 64bit, but it is not possible. Yast says: mlt needs, but no repository offer it. Can someone please correct this? Thank you for your fast help. But why does it now work? I look in your BuildServer and it seams the spec-files is the same, or not? I changed it after reading this mail. I have some things too. I must manuell install libmlt5-data and libmlt5-modules. Yast does it not automatically. It's bug PM-4. Packman repository metadata is incomplete. And i must rename libmltjackrack.so, so it does not crash. I can't reproduce that problem. And i must change mlt to mlt-5 at first start from kdenlive in the path for profiles. Fixing... And kdenlive is not found over search in KDE-Menu. It is in my openSUSE 12.2 RC2 install. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Bug tracker down
Just in case you still didn't know, the bug tracker is down. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] openshot in opensuse 12.2 fails to run
The problem is with MLT (or swig or g++, let's see...). Please open a bug report at bugzilla.novell.com so I don't forget. On 4 August 2012 08:31, Dutch Kind dutchk...@txoriaskea.org wrote: In opensuse 12.2 (both RC1 and RC2) I tried to run openshot from the packman repo. It fails to start and haven't been able to find the reason. The openshot website also gives some ideas but none work. In opensuse 12.2 openshot worked without a problem, and when I upgraded this install to 12.2 openshot would not start anymore. On another computer same thing, so it doesn't seem related to just one installation. openshot - ERROR 1 -- Failed to import 'from openshot import main' Error Message: cannot import name main ** (process:6417): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags' ** (process:6417): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags' ** (process:6417): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags' OpenShot (version 1.4.2) Process no longer exists: 6390. Creating new pid lock file. LONG LIST OF FILTERS (omitted for clarity) ... state saved Segmentatiefout ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] openshot in opensuse 12.2 fails to run
On 4 August 2012 18:23, Cristian Morales Vega reddw...@opensuse.org wrote: The problem is with MLT (or swig or g++, let's see...). Please open a bug report at bugzilla.novell.com so I don't forget. Ignore that. The problem is openshot crashes if the libmltavformat.so plugin is not available. I will make a Packman build with the plugin... ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] Is the x86-64 scheduler down?
Is the x86-64 scheduler down? It doesn;t seem to be building the pending packages. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] aMule 2.3.1-1.4 (openSUSE 12.1/src)
On 2 August 2012 10:03, Осипов Женя zeni...@yandex.ru wrote:
Hello.
I found a mistake in SRPM of aMule when tried to build it in openSUSE 11.4.
Before build I install wxWidgets from Factory because of aMule 2.3.1 needs
wxWidgets 2.8.12, not less. openSUSE 11.4 has wxWidgets 2.8.11.
1). BuildRequires: wxWidgets-wxcontainer-devel. In
http://en.opensuse.org/openSUSE:Packaging_wxWidgets I read that wxcontainer
is deprecated, and all applications need be compiled with stl
(wxWidgets-devel). I don't know, is it possible to run application build with
deprecated wxcontainer with not deprecated stl, but I think, no.
A possible ways to fix:
a).
-BuildRequires: wxWidgets-wxcontainer-devel
+BuildRequires: wxWidgets-devel
b).
%if %{version} 2.3.1
BuildRequires: wxWidgets-wxcontainer-devel
%else
BuildRequires: wxWidgets-devel
%endif
A the latest aMule is able to build with the STL wxWidgets would
have been enough ;-)
2). %if %suse_version = 1130 in spec file. But openSUSE 11.3 has an old
version of wxWidgets. Is it time to remove the outdated condition, which is
probably used to compile aMule 2.2.6? Or if not, change the condition to
compile in openSUSE 11.3, add a condition for 11.4, which makes checking for
wxWingets 2.8.12 and later.
Done.
3). Forgotten RPM-macros debug_info which leads to 248.5 Mb of builded RPM.
openSUSE has not used %debug_info at least since we started to use the OBS.
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] live vs live555 and redland-bindings-1.0.14
On 2 June 2012 14:40, Greg Kroah-Hartman gre...@linux.com wrote: On Thu, Apr 26, 2012 at 07:27:06PM +0100, Cristian Morales Vega wrote: On 18 April 2012 01:16, Greg Kroah-Hartman gre...@linux.com wrote: Ok, but where did the version of redland-bindings come from? Shouldn't I just link in the X11:common:Factory versions of redland AND redland-bindings into Tumbleweed, instead of using the version of redland from KDE-4.8? Sure. Now done. No, you didn't. $ osc cat -u openSUSE:Tumbleweed redland _link link package=redland project=KDE:Release:48 rev=f6ced863225677c1d17fbf3e4f05dcf3 ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] live vs live555 and redland-bindings-1.0.14
On 25 July 2012 15:44, Greg Kroah-Hartman gre...@linux.com wrote: On Wed, Jul 25, 2012 at 02:54:19PM +0100, Cristian Morales Vega wrote: On 2 June 2012 14:40, Greg Kroah-Hartman gre...@linux.com wrote: On Thu, Apr 26, 2012 at 07:27:06PM +0100, Cristian Morales Vega wrote: On 18 April 2012 01:16, Greg Kroah-Hartman gre...@linux.com wrote: Ok, but where did the version of redland-bindings come from? Shouldn't I just link in the X11:common:Factory versions of redland AND redland-bindings into Tumbleweed, instead of using the version of redland from KDE-4.8? Sure. Now done. No, you didn't. $ osc cat -u openSUSE:Tumbleweed redland _link link package=redland project=KDE:Release:48 rev=f6ced863225677c1d17fbf3e4f05dcf3 $ ./check_package X11:common:Factory/redland # redland is up to date. They are up to date. And I'm going to delete the package from Packman since that fixes the problem. But that doesn't mean you are linking Tumbleweed's redland to X11:common:Factory as you said you did. If you have any good reason to link to KDE:Release:48 and that wasn't just a mistake great, I am not discussing that decision. Just informing. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] live vs live555 and redland-bindings-1.0.14
On 25 July 2012 16:27, Greg Kroah-Hartman gre...@linux.com wrote: On Wed, Jul 25, 2012 at 03:56:12PM +0100, Cristian Morales Vega wrote: On 25 July 2012 15:44, Greg Kroah-Hartman gre...@linux.com wrote: On Wed, Jul 25, 2012 at 02:54:19PM +0100, Cristian Morales Vega wrote: On 2 June 2012 14:40, Greg Kroah-Hartman gre...@linux.com wrote: On Thu, Apr 26, 2012 at 07:27:06PM +0100, Cristian Morales Vega wrote: On 18 April 2012 01:16, Greg Kroah-Hartman gre...@linux.com wrote: Ok, but where did the version of redland-bindings come from? Shouldn't I just link in the X11:common:Factory versions of redland AND redland-bindings into Tumbleweed, instead of using the version of redland from KDE-4.8? Sure. Now done. No, you didn't. $ osc cat -u openSUSE:Tumbleweed redland _link link package=redland project=KDE:Release:48 rev=f6ced863225677c1d17fbf3e4f05dcf3 $ ./check_package X11:common:Factory/redland # redland is up to date. They are up to date. And I'm going to delete the package from Packman since that fixes the problem. But that doesn't mean you are linking Tumbleweed's redland to X11:common:Factory as you said you did. Well, my scripts, as shown above, sure think that it is linked properly :) If you have any good reason to link to KDE:Release:48 and that wasn't just a mistake great, I am not discussing that decision. Just informing. That's because it is the same exact package: $ osc cat -u KDE:Release:48 redland _link link package=redland project=KDE:Distro:Factory rev=1 vrev=1 patches /patches /link $ osc cat -u KDE:Distro:Factory redland _link link project=X11:common:Factory baserev=3f8fba80afab3f422aba84faaa247f71 patches branch/ /patches /link So we are linking in the correct package into openSUSE:Tumbleweed, it just so happens that is the same package that is in KDE:Release:48 at the moment. So all is well, right? Yes. Really, I just told you in case you though you were directly linking to X11:common:Factory. If you know you aren't and are happy with that I don't see any problem. I don't know if your scripts will help you detect problems if at some point KDE:Release:48/redland starts to be different from X11:common:Factory/redland, but that's up to you to handle. But just in case your scripts depend on the output of those commands: - KDE:Release:48 is linking to a specific revision of KDE:Distro:Factory, when you do osc cat -u KDE:Distro:Factory redland _link you are looking at the latest one. - The output of osc cat -u KDE:Distro:Factory redland _link only says the package was branched from X11:common:Factory at some specific revision. It doesn't say if there are any differences between the version in KDE:Distro:Factory and the version in X11:common:Factory. So those commands don't shown the packages are exactly the same. But since in this case they actually are the same, no problem. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 248 Essentials/lame
On 21 July 2012 09:34, Pascal Bleser pascal.ble...@opensuse.org wrote: Sorry again, and thanks for the changes. No need to apologize. I am only worried about having a system where people wants to collaborate and regulars have no problems noticing when people is trying to collaborate. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 248 Essentials/lame
On 21 July 2012 09:34, Pascal Bleser pascal.ble...@opensuse.org wrote: I re-merged the funky patching that's needed on 12.2 to disable outdated automake/autoconf features though. Do you mean http://pmbs.links2linux.org/package/rdiff?commit=9linkrev=basepackage=lameproject=Essentials? What's that supposed to do? Change configure.in and Makefile.am that, since autoreconf is not used, shouldn't make any difference. Add -lm to LIBS even if it build without it. Define CFLAGS with something that %configure already defines. And re-adding options that to the best of my knowledge configure ignores?? I got loss with that one. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 248 Essentials/lame
On 15 July 2012 14:46, PMBS p...@links2linux.org wrote: New submit request 248 on lame by RedDwarf https://pmbs.links2linux.org/request/show/248 - update to 3.99.5 Given that two days later a different patch was committed and this SR was not even rejected it seems we still have a problem with #PM-9 and making people aware of SRs. Anyway. About the committed version: - The license seems to be LGPL-2.0+, no LGPL-2.1+ - lame-tgetstr.patch is kept, forcing a autoreconf call that makes the build fail in old distributions, even if I don't think it's needed. I don't know a lot about curses, but: When libtinfo was splitted it wasn't done in the best way, but soon after a linker script was used to avoid the need of patching other packages. In my SR I didn't use it and the only difference in the result is that in 12.2 I linked against libncurses instead of libncursesw... but since in = 12.2 only libtinfo is used I don't think it really matters. SR#248 has other changes that are less important, but those two IMHO should be fixed. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] When to add 12.2?
We should wait: - to save build power We should add it right now: - because we will have more time to fix any problems that happen with 12.2 (but not in 12.1 or Factory) - users will be happier to test 12.2 RC1 (and we want them to test it) if they have Packman available ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] build-compare in Factory
On 13 July 2012 00:23, Kyrill Detinov lazy.k...@opensuse.org wrote: On Thu, 12 Jul 2012 23:35:59 +0100 Cristian Morales Vega wrote: What is the difference? ./gCue2tracks-appdata.xml is new And why is it new? No files are changed. Support: brp-extract-appdata wasn't in the prjconf in the previous build. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 245 Multimedia/libquvi
Would not make more sense to: a) Only build it for 11.4 since the other distributions already provide quvi in the default repos b) Link to openSUSE:Current for the 11.4 version ? On 8 July 2012 11:59, PMBS p...@links2linux.org wrote: New submit request 245 on libquvi by dnh https://pmbs.links2linux.org/request/show/245 libquvi/libquvi-scripts were split from quvi ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 236 Essentials/npapi-vlc
On 27 June 2012 22:31, Cristian Morales Vega reddw...@opensuse.org wrote: On 27 June 2012 22:23, Cristian Rodríguez crrodrig...@opensuse.org wrote: El 27/06/12 14:14, Cristian Morales Vega escribió: Meaning update to unreleased git version. Why? On 27 June 2012 18:38, PMBS p...@links2linux.org wrote: New submit request 236 on npapi-vlc by crrodriguez https://pmbs.links2linux.org/request/show/236 - Update to version 2.0.2 is there a problem with it ? No that I know of. But when a stable version is changed by a development one usually there is a good reason. There is one here? I would not feel as a good maintainer of the package if I would not know why the actual tarball is the one it is. I just need to know that, *why* the tarball was updated? There was a problem with the old version? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [opensuse-factory] Fwd: commit libavutil for openSUSE:Factory
On 27 June 2012 08:58, Dave Plater davejpla...@gmail.com wrote: When I discovered that the future xine-lib had a hard dependancy on libavutil and that libavutil wasn't encumbered by patent problems (August last year) I decided on a static lib built with xine due to libavutil being part of ffmpeg. The only safe way that I can see with a dynamic libavutil in factory is for packman to also separate libavutil and build a linked package otherwise it will be a problem to keep them in sync. The Packman ffmpeg maintainer will need to maintain openSUSE libavutil as well. I normally run multimedia:apps with libxine-codecs from Packman. Ffmpeg tends to change frequently and may cause unforseen problems if libavutil gets out of sync. libxine2 itself needs libavutil the rest of the ffmpeg libs are used by plugin builds. IMHO the xine-lib developers should include a static libavutil. Have a look at Debian and Fedora for clues. This is far from a specific case. And AFAIK Debian packages the full libav and Fedora doesn't package libxine 1.2, what clues should I look for there? I guess the basic question is: why is this different to the libxine case? Packman doesn't make any effort to keep it in sync with openSUSE version. And it even packages a binary incompatible version. What's more, Packman already packages two binary incompatible versions of libavutil! ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 236 Essentials/npapi-vlc
Meaning update to unreleased git version. Why? On 27 June 2012 18:38, PMBS p...@links2linux.org wrote: New submit request 236 on npapi-vlc by crrodriguez https://pmbs.links2linux.org/request/show/236 - Update to version 2.0.2 ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 236 Essentials/npapi-vlc
On 27 June 2012 22:23, Cristian Rodríguez crrodrig...@opensuse.org wrote: El 27/06/12 14:14, Cristian Morales Vega escribió: Meaning update to unreleased git version. Why? On 27 June 2012 18:38, PMBS p...@links2linux.org wrote: New submit request 236 on npapi-vlc by crrodriguez https://pmbs.links2linux.org/request/show/236 - Update to version 2.0.2 is there a problem with it ? No that I know of. But when a stable version is changed by a development one usually there is a good reason. There is one here? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [opensuse-factory] Fwd: commit libavutil for openSUSE:Factory
If xine is going to be the only library that uses libavutil a static version could make sense. But there is no reason to think that's going to be the case. And then... really, I fail to see the problem here. Could you please show a specific case where using a dynamic version of libavutil there is a problem that isn't there when using a static one? On 24 June 2012 13:47, Dave Plater davejpla...@gmail.com wrote: I have been working on a static build of libavutil included in the hg version of xine-lib but was having difficulty getting that version of xine-lib to build. Unfortunately I'm computerless atm but this would certainly solve the problem. Dave On 6/15/12, Cristian Morales Vega reddw...@opensuse.org wrote: On 15 June 2012 18:25, Dominique Leuenberger a.k.a DimStar dims...@opensuse.org wrote: Has this be well planned Since xine 1.2.x depends on libavutil unconditionally (https://bugzilla.novell.com/show_bug.cgi?id=762784) it's basically the only solution. But I don't see any real problem here. Can you put an specific combination of circumstances that would be problematic? It would be safer and easier if libavutil versioned symbols in a more detailed way instead of just to avoid using symbols from a library with a different soname, but that problem happens with lots of libraries that don't even version symbols at all. xine is the only package from openSUSE that will link against it. And the most common case is for users to use both xine and libavutil from Packman. So this seems 100% safe to me. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Manual dependencies on ffmpeg: not good
On 17 June 2012 14:25, Jan Engelhardt jeng...@inai.de wrote: On Sunday 2012-06-17 14:39, Manfred Tremmel wrote: Am Dienstag, 12. Juni 2012, 18:01:39 schrieb Jan Engelhardt: My openSUSE_12.1 system currently has ffmpeg-0.9.1-1.1[packman], but ffmpeg 0.9.1 has been replaced in January, you realy should update to the latest version. zypper does not want to update to ffmpeg-0.11[packman], because of some whacky manual dependencies that someone had added. Drilled down (minimal testcase), in rpm lingo,: make a zypper dup, this should resolve. I do not consider that an ideal solution, because it replaces all packages by random vendors, depending on which repositories are enabled. I agree with you in the general problem (http://lists.links2linux.de/pipermail/packman/2012-May/011142.html). But dist-upgrade behavior isn't random - http://forums.opensuse.org/english/get-technical-help-here/how-faq-forums/unreviewed-how-faq/474523-software-management-dist-upgrade-way.html ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [opensuse-factory] Fwd: commit libavutil for openSUSE:Factory
On 15 June 2012 18:25, Dominique Leuenberger a.k.a DimStar dims...@opensuse.org wrote: Has this be well planned Since xine 1.2.x depends on libavutil unconditionally (https://bugzilla.novell.com/show_bug.cgi?id=762784) it's basically the only solution. But I don't see any real problem here. Can you put an specific combination of circumstances that would be problematic? It would be safer and easier if libavutil versioned symbols in a more detailed way instead of just to avoid using symbols from a library with a different soname, but that problem happens with lots of libraries that don't even version symbols at all. xine is the only package from openSUSE that will link against it. And the most common case is for users to use both xine and libavutil from Packman. So this seems 100% safe to me. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 230 Multimedia/qmmp
The problem only happened with Factory, true? Anyway I fixed it in https://build.opensuse.org/package/rdiff?linkrev=basepackage=qmmpproject=openSUSE%3AFactoryrev=2 Anybody against https://bugs.links2linux.org/browse/PM-18? On 31 May 2012 20:42, PMBS p...@links2linux.org wrote: New submit request 230 on qmmp by crrodriguez https://pmbs.links2linux.org/request/show/230 - exclude libcdaudio plugin temporarily, fix build there is a mess in the required libraries that will be fixed later. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 227 Essentials/ffmpeg
On 29 May 2012 22:09, Manfred Tremmel manf...@links2linux.de wrote:
Am Dienstag, 29. Mai 2012, 20:49:51 schrieb Cristian Morales Vega:
In the past all libs where included in libffmpeg and later in
libffmpeg0.
The point is that libavcodec54 doesn't obsolete any of them.
Ok, maybe we can remove it complete, then the provides should also
removed. It's so long ago we had libffmpeg and libffmpeg0, so it
shouldn't matter.
I didn't remove the provides because I saw a tendency in Packman
packages to directly BuildRequire the libraries and not just the
-devel packages, and I didn't want to break something. But indeed the
provides could also be deleted.
And the problem is that libavcodec53 provided libffmpeg0. If
libavcodec54 obsoletes libffmpeg0, it obsoletes libavcodec53.
Since
Right, but even if I remove it, it's impossible to keep
libavcodec53, it depends on libavutil2 = %{version} like
libavcodec54 dose.
I didn't notice that... Probably a good moment to change it to
libavutil2 = %{version}. It will avoid the problem in the future
and if ffmpeg guys keep the promise of binary compatibility (no cause
to thing otherwise) it must work.
I had big problmes in the past between incompatible ffmpeg libs with the
same so number. And it's realy hard to find such a problems, because I
don't know the exact version of the lib, the user uses (and even if I
know, I don't have to reproduce). That's the reason I've added all this
dependencies.
The problem was with a higher version? Problems are normal if an user
updated libavcodec without updating libavutil (the soname only
warranties forward compatibility), but I would be surprised if ffmpeg
actually didn't keep it's promise of ABI compatibility. After all they
are doing all the work of maintaining... six? ABI versions.
But if Carl Eugen Hoyos doesn't complain about this it's OK with me ;-)
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] k3b-codecs issue
On 28 May 2012 10:24, Manfred Tremmel manf...@links2linux.de wrote: Am Montag, 28. Mai 2012, 05:55:35 schrieb Carl Fletcher: 12.1 Can't install k3b-codecs YaST2 conflicts list - generated 2012-05-28 05:50:49 nothing provides libavformat.so.53()(64bit) needed by k3b-codecs-2.0.2-14.1.x86_64 [ ] break k3b-codecs by ignoring some of its dependencies [ ] do not install k3b-codecs-2.0.2-14.1.x86_64 Please wait until your mirror is up to date, I've updated ffmpeg to 0.11 and there are a lot of packages that don't build against this. I'm still on fixing it (about 15 packages to do). The fix for k3b has been checked in 14 hours ago and two hours ago the results have been put to our ftp server. Are you talking care of gstreamer010-ffmpeg and its URLProtocol - AVIOContext? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 227 Essentials/ffmpeg
On 29 May 2012 19:14, Manfred Tremmel manf...@links2linux.de wrote: Am Montag, 28. Mai 2012, 23:24:25 schrieb PMBS: New submit request 227 on ffmpeg by RedDwarf https://pmbs.links2linux.org/request/show/227 - Remove incorrect obsoletes What's wrong with this obsoletes entries? I've inserted both some time ago, after renaiming and splitting the ffmpeg package to get rid of old package and prevent from conflicts. Just after the renaming they were OK. But when the package was named libffmpeg0 it provided... what? libavcodec36? Now it's false that libavcodec54 obsoletes libavcodec36 since you may need both (for programs compiled against one or the other). Just because of this they are wrong. And the problem is that libavcodec53 provided libffmpeg0. If libavcodec54 obsoletes libffmpeg0, it obsoletes libavcodec53. Since there were some packages already compiled against libavcodec54 and others failed to build (but the old versions were still available in the repo compiled against libavcodec53)... users needed libavcodec53 and libavcodec54 installed at the same time. The Obsoletes didn't allow that since installing libavcodec54 triggered the uninstall of libavcodec53. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PMBS] SR 227 Essentials/ffmpeg
On 29 May 2012 20:42, Manfred Tremmel manf...@links2linux.de wrote:
Am Dienstag, 29. Mai 2012, 19:57:34 schrieben Sie:
On 29 May 2012 19:14, Manfred Tremmel manf...@links2linux.de wrote:
Am Montag, 28. Mai 2012, 23:24:25 schrieb PMBS:
New submit request 227 on ffmpeg by RedDwarf
https://pmbs.links2linux.org/request/show/227
- Remove incorrect obsoletes
What's wrong with this obsoletes entries? I've inserted both some
time ago, after renaiming and splitting the ffmpeg package to get
rid of old package and prevent from conflicts.
Just after the renaming they were OK. But when the package was named
libffmpeg0 it provided... what? libavcodec36? Now it's false that
libavcodec54 obsoletes libavcodec36 since you may need both (for
programs compiled against one or the other). Just because of this they
are wrong.
In the past all libs where included in libffmpeg and later in
libffmpeg0.
The point is that libavcodec54 doesn't obsolete any of them.
And the problem is that libavcodec53 provided libffmpeg0. If
libavcodec54 obsoletes libffmpeg0, it obsoletes libavcodec53. Since
Right, but even if I remove it, it's impossible to keep libavcodec53, it
depends on libavutil2 = %{version} like libavcodec54 dose.
I didn't notice that... Probably a good moment to change it to
libavutil2 = %{version}. It will avoid the problem in the future
and if ffmpeg guys keep the promise of binary compatibility (no cause
to thing otherwise) it must work.
there were some packages already compiled against libavcodec54 and
others failed to build (but the old versions were still available in
the repo compiled against libavcodec53)... users needed libavcodec53
and libavcodec54 installed at the same time. The Obsoletes didn't
allow that since installing libavcodec54 triggered the uninstall of
libavcodec53.
I work on porting the missing packages. Give me a view days.
No problem.
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] k3b-codecs issue
On 28 May 2012 10:24, Manfred Tremmel manf...@links2linux.de wrote: Am Montag, 28. Mai 2012, 05:55:35 schrieb Carl Fletcher: 12.1 Can't install k3b-codecs YaST2 conflicts list - generated 2012-05-28 05:50:49 nothing provides libavformat.so.53()(64bit) needed by k3b-codecs-2.0.2-14.1.x86_64 [ ] break k3b-codecs by ignoring some of its dependencies [ ] do not install k3b-codecs-2.0.2-14.1.x86_64 Please wait until your mirror is up to date, I've updated ffmpeg to 0.11 and there are a lot of packages that don't build against this. I'm still on fixing it (about 15 packages to do). The fix for k3b has been checked in 14 hours ago and two hours ago the results have been put to our ftp server. Anyway part of the problem is that libavcodec53 can not be installed at the same time than libavcodec54. I created SR#227 that removes some obsoletes that not really apply (I don't know when it was called libffmpeg or libffmpeg0, but for sure it wasn't binary compatible with libavcodec54). ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] kdemultimedia4 4.7.2-3.1.7 (openSUSE 12.1/x86_64)
On 9 May 2012 20:33, Mathias Homann ad...@eregion.de wrote: please update this package to the one from KDE 4.8.3... kmix 4.7.2 has several old bugs relating to pulseaudio that have been fixed by now. Just not install it from Packman. It is there just because of https://bugs.links2linux.org/browse/PM-3 ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Package update workflow?
On 8 May 2012 15:43, Stefan Seyfried se...@s3e.de wrote: Am 08.05.2012 15:39, schrieb Cristian Morales Vega: So... any +1/-1 about adding these rpm packages to Essentials? Again, the idea is to allow multimedia:libs/multimedia:apps maintainers play with the new rpm features. We can link them and will still build in the old distros that we support and they don't. IMHO: go ahead and add them. But don't publish them, just keep Use for Build checked. So people cannot fsck up their SLES with these rpm packages (and to use the built packages, they should not need the patched RPM). Done for 11.1 and SLE 11 SP2. I would need the sources of the RPM from SLE 11 GM (4.4.2.3-37.8) to finish it. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Package update workflow?
On 4 May 2012 18:52, Cristian Morales Vega reddw...@opensuse.org wrote: On 4 May 2012 16:48, Pascal Bleser pascal.ble...@opensuse.org wrote: discussing it on the list first: there are many issues with the way the maintainers of multimedia:libs and multimedia:apps on build.o.o handle their packages, I've mentioned that in the past (they don't care about older distros, replace foo-devel with pkgconfig(foo) which doesn't work on SLE or Evergreen, they carelessly rename packages which breaks a lot of other things (e.g. taglib - libtag), etc..., and generally speaking they don't see their packages are linked in Packman, hence they don't see the side effects of changes to their packages, and that doesn't work too well) I could try to create the packages - rpm-Evergreen_11.1 - rpm-Evergreen_11.2 - rpm-SLE-11 - rpm-SLE-11-SP2 branching from its original packages but adding - a default definition of build root - a definition of the make_install macro (With some luck it would be just a matter of putting the definitions in /usr/lib/rpm/macros) Then, when someone finds a problem with a pkgconfig() buildrequire, please don't patch it but add a Substitute entry in the Essentials prjconf. I think we could have the packages from multimedia:libs/multimedia:apps with these things building without problems quite easily. To say the truth I first thought about this months ago. But I never tried only because it could easily happen that something breaks in the first tries... Just another case of in order to not step on anyone's toes... we don't do the work. mjpegtools with pkgconfig() BuildRequires, %make_install and no BuildRoot tag is building in home:RedDwarf for Evergreen 11.1 and 11.2. If someone can say me where to get the SRPMs for SLE the same thing could be done for them. The %make_install is a no-brainer. But the buildroot part required a little patch to the code. Again, something could broke... Anybody against putting these patched RPMs in Essentials? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Package update workflow?
On 4 May 2012 22:49, Manfred Tremmel manf...@links2linux.de wrote: Am Freitag, 4. Mai 2012, 18:36:26 schrieb Cristian Morales Vega: transcode is dead, let's accept it. And I see 11 packages that require it. Either the dependencies are wrong or those packages should have already started to move to something else. Those packages are usually DVD related... we are in 2012!!! DVDs??? Who uses those any more? I maintaine some packages which are not updated for years, but used by other packages, like transcode. What's the alternate to DVD's on linux? Blue-Ray Disks with HDCP, AACS and BD+ or Video On Demand over Internet with DRM and no Linux clients? DVDs are well supported and CSS is no real problem, so it simply works with linux. As long as I can manage transcode to build with new gcc versions and new library versions from e.g. ffmpeg and no security problems are known, why should we drop it? My alternative to DVDs are just Matroska files. But if somebody actually cares for transcode there is no cause to drop it, sure. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Package update workflow?
On 4 May 2012 15:39, Stefan Seyfried stefan.seyfr...@googlemail.com wrote: Hi all, a small question wrt. the workflow in pmbs -- in order to not step on anyone's toes :-) In order to update clipgrab to the latest version, I have linked it into home:seife and updated it there. It builds fine. The question is: what to do now? Submitrequest and self-accept? Submitrequest and wait for somebody else to accept? Should I commit directly to Extra next time? (I wouldn't like that because I usually want to test if it really builds and works... :-) Good question. In my first commit I was said to never again create a branch because the build power was too limited. Then people complained because of committing directly. Once I got a submit request I didn't like accepted by somebody else. I saw people in this mailing list discussing different ways to fix something and never getting an answer (and the problem remained unfixed). Now I created a bug (PM-15) and a submit request (#192) for a fix that for me is so obvious that shouldn't require any discussion. And for a package that I don't think has any real active maintainer any more (I guess Pascal will be the one to accept it). So... there is no clear policy. And if you trust the maintainer/bugowner tags in the package metadata it's easy to be worried about stepping on the toes of somebody that isn't there. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Package update workflow?
On 4 May 2012 16:48, Pascal Bleser pascal.ble...@opensuse.org wrote: On 2012-05-04 15:58:33 (+0100), Cristian Morales Vega reddw...@opensuse.org wrote: That's why a lot of packages don't really have much of a maintainer and why, instead, I'm jumping from one package to another like a fire fighter. If someone feels like wanting to own packages in Packman, be my guest, please do so ;) A solution is to just lower the workload. I think a problem is that nobody wants to drop packages. If we had download statistics probably we would find packages with *zero* downloads! Usually packages that have been abandoned upstream and are therefore the ones that take more time to make them build in the latest versions. transcode is dead, let's accept it. And I see 11 packages that require it. Either the dependencies are wrong or those packages should have already started to move to something else. Those packages are usually DVD related... we are in 2012!!! DVDs??? Who uses those any more? There a few packages I just don't feel motivated to fix because I don't think any user really cares. If you look at the Packman build service the situation looks bad. But we don't have so many users complaining here. Perhaps it's just that no user cares about those packages any more. And it could be argued that we could drop Evergreen and SLE targets from Essentials to also lower the workload. But if interested people can accept its current state I guess it's not such a problem. So... there is no clear policy. And if you trust the maintainer/bugowner tags in the package metadata it's easy to be worried about stepping on the toes of somebody that isn't there. How do you mean? Just that, that I don't know who disappeared and who is just in a two weeks holiday. I don't do something expecting the maintainer to do it (searching for some other package broken...) or send an email to him... Just to find he is not there any more. But more important. I somebody sees in the metadata that a package has a maintainer (even if that maintainer is not available any more) he is not going to offer himself to be the new maintainer. Do you want new maintainers? Publish here a list of packages without maintainer and interested people will appear. But... there is a list of packages without a maintainer? Can it be created reliably at all? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Package update workflow?
On 4 May 2012 16:48, Pascal Bleser pascal.ble...@opensuse.org wrote: discussing it on the list first: there are many issues with the way the maintainers of multimedia:libs and multimedia:apps on build.o.o handle their packages, I've mentioned that in the past (they don't care about older distros, replace foo-devel with pkgconfig(foo) which doesn't work on SLE or Evergreen, they carelessly rename packages which breaks a lot of other things (e.g. taglib - libtag), etc..., and generally speaking they don't see their packages are linked in Packman, hence they don't see the side effects of changes to their packages, and that doesn't work too well) I could try to create the packages - rpm-Evergreen_11.1 - rpm-Evergreen_11.2 - rpm-SLE-11 - rpm-SLE-11-SP2 branching from its original packages but adding - a default definition of build root - a definition of the make_install macro (With some luck it would be just a matter of putting the definitions in /usr/lib/rpm/macros) Then, when someone finds a problem with a pkgconfig() buildrequire, please don't patch it but add a Substitute entry in the Essentials prjconf. I think we could have the packages from multimedia:libs/multimedia:apps with these things building without problems quite easily. To say the truth I first thought about this months ago. But I never tried only because it could easily happen that something breaks in the first tries... Just another case of in order to not step on anyone's toes... we don't do the work. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Maintainers speak up (was: Package update workflow?)
On 4 May 2012 19:14, Pascal Bleser pascal.ble...@opensuse.org wrote: Well, the situation, right now, as I see it: * Manfred takes good care of a few packages that need some experience with them, most prominently ffmpeg and xine * I'm staying on top of mixxx, MPlayer, smplayer and some jack related packages (because I use them all the time) * almost everything else: has no maintainer and I'm jumping in because no one else does Manfred, do you have other packages that you'd like to remain the sole maintainer of ? Or anyone else ? Please speak up so we can draw a map of what's actually maintained (and where maintainers would like to stay in charge). Everything else is up for takes. I tried to keep the maintainer/bugowner up to date. I really maintain these (even if I don't use some of them so much) $ osc -A pm my -U RedDwarf pkg Essentials/amarok Essentials/gmtk Essentials/kdemultimedia4 Essentials/kdemultimedia4-12.1 Essentials/kdemultimedia4-Tumbleweed Essentials/mp4v2 Essentials/npapi-vlc Essentials/opencv Essentials/opencv-12.1 Essentials/strigi Essentials/vo-aacenc Essentials/vo-amrwbenc Games/libdevil Games/love Games/scummvm Games/scummvm-tools Multimedia/aegisub Multimedia/moc I keep distribution specific versions of opencv because it's tendency to break binary compatibility. And from kdemultimedia4 just because I don't know what would happen if you mix latest ones with older KDEs. You are set as the maintainer of gnome-mplayer/gecko-mediaplayer. If you don't want them I will take them to complement gmtk. I am used to the OBS informing me of upstream updates. How do you manage it? Any scripts? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Maintainers speak up (was: Package update workflow?)
On 4 May 2012 20:05, Cristian Morales Vega reddw...@opensuse.org wrote: On 4 May 2012 19:14, Pascal Bleser pascal.ble...@opensuse.org wrote: Well, the situation, right now, as I see it: * Manfred takes good care of a few packages that need some experience with them, most prominently ffmpeg and xine * I'm staying on top of mixxx, MPlayer, smplayer and some jack related packages (because I use them all the time) * almost everything else: has no maintainer and I'm jumping in because no one else does Manfred, do you have other packages that you'd like to remain the sole maintainer of ? Or anyone else ? Please speak up so we can draw a map of what's actually maintained (and where maintainers would like to stay in charge). Everything else is up for takes. I tried to keep the maintainer/bugowner up to date. I really maintain these (even if I don't use some of them so much) $ osc -A pm my -U RedDwarf pkg Essentials/amarok Essentials/gmtk Essentials/kdemultimedia4 Essentials/kdemultimedia4-12.1 Essentials/kdemultimedia4-Tumbleweed Essentials/mp4v2 Essentials/npapi-vlc Essentials/opencv Essentials/opencv-12.1 Essentials/strigi Essentials/vo-aacenc Essentials/vo-amrwbenc Games/libdevil Games/love Games/scummvm Games/scummvm-tools Multimedia/aegisub Multimedia/moc I keep distribution specific versions of opencv because it's tendency to break binary compatibility. And from kdemultimedia4 just because I don't know what would happen if you mix latest ones with older KDEs. You are set as the maintainer of gnome-mplayer/gecko-mediaplayer. If you don't want them I will take them to complement gmtk. I am used to the OBS informing me of upstream updates. How do you manage it? Any scripts? I can also take ownership of the gstreamer things (the latest ones, those gstreamer-0.10.4 and gstreamer010-plugins-good-0.10.24 can be kept as a community effort). I don't mind taking care of the relationship with multimedia:libs, fixing problems here. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] nautilus-gnome-mplayer-properties-page package missing important dependency
On 26 April 2012 12:46, Adam Bolte abo...@systemsaviour.com wrote: Unfortunately, gnome-mplayer somehow got uninstalled and appears to be a requirement for nautilus-gnome-mplayer-properties-page (and hence Nautilus) to run. Specifically, nautilus-gnome-mplayer-properties-page seems to depend on one or more of these gnome-mplayer files: /usr/share/glib-2.0/schemas/apps.gecko-mediaplayer.preferences.gschema.xml /usr/share/glib-2.0/schemas/apps.gnome-mplayer.preferences.enums.xml /usr/share/glib-2.0/schemas/apps.gnome-mplayer.preferences.gschema.xml In summary, nautilus-gnome-mplayer-properties-page should have gnome-mplayer as a dependency to prevent others from having this issue. Requires /usr/share/glib-2.0/schemas/apps.gnome-mplayer.preferences.gschema.xml just to enable or disable it... I will add the requires now. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] live vs live555 and redland-bindings-1.0.14
On 18 April 2012 01:16, Greg Kroah-Hartman gre...@linux.com wrote: Ok, but where did the version of redland-bindings come from? Shouldn't I just link in the X11:common:Factory versions of redland AND redland-bindings into Tumbleweed, instead of using the version of redland from KDE-4.8? Sure. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] [PM] vlc 2.0.1-8.3 (openSUSE 12.1/x86_64)
On 19 April 2012 22:06, Quentin Denis quentin.de...@gmail.com wrote: Just noticed you updated the phonon-backend-vlc. package. Thanks for it. VLC 2.0 seems not to have any mozilla plugin. Is it a compilation error or is the new generation of VLC coming without that plugin? The package is named npapi-vlc. Should subtitute automatically any vlc-mozillaplugin install automatically once it appears in the repos. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] live vs live555 and redland-bindings-1.0.14
Are not live and live555 the same package? Why we have it twice? And what the purpose of redland-bindings-1.0.14 for Tumbleweed?? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] live vs live555 and redland-bindings-1.0.14
On 17 April 2012 13:48, Pascal Bleser pascal.ble...@opensuse.org wrote: And what the purpose of redland-bindings-1.0.14 for Tumbleweed?? Fixes the broken python-redland that is currently in Tumbleweed, and which prevented the build of some packages (most notably OpenOctaveMidi) because it was pulled in as some transitive dependency. I see, redland-bindings should be included in Tumbleweed. Does Greg know? ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] more dependecy breakage while doing zypper dup
On 15 April 2012 10:39, Pascal Bleser pascal.ble...@opensuse.org wrote: Actually, the package does have a baselibs.conf, but it is not up-to-date and does not match any of the packages. SR #184 should fix the problem in the future. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
[packman] List of 12.1 packages that are available in both Packman and openSUSE without without providing anything new in Packman
I got this list from the output of zypper. It does not include packages with different names in openSUSE and Packman, but... Any idea about why they are in Packman? libmms is there because the 32bit package is needed by gstreamer-0_10-plugins-bad-32bit. The others, no idea... google-perftools google-perftools-devel libetpan-devel libmms0 libmms-devel libqwt5 libwavpack1 libwavpack1-32bit licq licq-devel licq-kde4-gui licq-qt4-gui licq-qt4-gui-data linphone linphone-applet linphone-devel perl-AnyEvent perl-Class-Factory-Util perl-Class-Singleton perl-Config-Tiny perl-DateTime perl-DateTime-Format-Builder perl-DateTime-Format-Strptime perl-DateTime-Locale perl-Devel-Cycle perl-Digest-CRC perl-File-Find-Rule perl-JSON-XS perl-libintl-perl perl-Number-Compare perl-PadWalker perl-Switch perl-Test-Fatal perl-Test-Memory-Cycle perl-Test-Simple perl-Text-Glob perl-Try-Tiny portaudio-devel python-distribute python-pyparsing python-pyparsing-doc python-Sphinx python-Sphinx-doc python-xdg qwt-designer qwt-devel qwt-devel-doc qwt-examples ripit wavpack wavpack-devel xine-ui ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] VLC 2.0
On 10 April 2012 05:39, rlee rleev...@gmail.com wrote: My question is it possible to repackage VLC2.0 so that when one updates they'll get the vlc-aout-pulse along with it instead of having to do this separately? The package is fine. It's the repo that's broken: http://lists.links2linux.de/pipermail/packman/2011-November/010441.html ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] XBMC 11.0
On 9 April 2012 21:44, Mariusz Fik fisi...@jabster.pl wrote:
Please wait for update that will fix this issue. Proper requirement should
call libbluray1. For this moment You can ignore dependency by taking 2nd
solution ;)
Instead of hardcoding library sonames in .spec's Requires one could
just use something like:
Requires: %(rpm -qf $(readlink -e %{_libdir}/libbluray.so) --qf '%{NAME}')
And these problems would disappear in the future.
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] Gamin conflicts
On 8 April 2012 14:50, RGB ES rgb.m...@gmail.com wrote: I'm on openSUSE 11.4, 64 bits. Since a couple of days, when trying to update the system I get a package conflict with gamin: it seems that gamin-server, gamin-devel and related packages on the server were updated to version 0.1.10-16-1, but gamin package itself just disappeared: there is nothing to update the gamin 0.1.10-6.3 package installed on my system, hence the conflict. This comes from a weird situation in the main OBS where two packages were developed in parallel. It could be fixed, but I still don't know why Packman is offering gamin to start with... libgmerlin-avdecoder-devel requires gamin-devel. It's already quite suspicious that an avdecoder requires a File Alteration Monitor system... but if you look at the non devel packages you see they don't have any gamin requirement. Unless it's dlopen()ed it's just not needed. (IMHO those million -devel hardcoded Requires in some -devel packages are just crazy, impossible to maintain and only produce problems like this one). And something similar happens with gstreamer-0_10-buzztard-devel. That's it, nothing else in my Packman 12.1 repository requires gamin. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Re: [packman] vlc 2.0
On 5 April 2012 08:16, Pascal Bleser pascal.ble...@opensuse.org wrote: Hence I had to package a few things only for SLE_11, SLE-11-SP2, and sometimes for Evergreen_11.1 or 11.2 in order to have all the dependencies (those packages are named libxxx-for-sle or libxxx-for-older-than-11.4, etc... in Essentials). libmatroska-for-older-than-11.4, libebml-for-older-than-11.4, lash-for-sle and fluidsynth-for-sle were building against *every* version. I disabled the build to what I understood the name meant (older-than-11.4 includes both SLE_11 and SLE-11-SP2?) and wiped the binaries. Unrelated... why are we building against both SLE_11 and SLE-11-SP2? Every binary compiled against SLE_11 should work with SLE-11-SP2. ___ Packman mailing list Packman@links2linux.de http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
