March 2008 - openSUSE Packaging - openSUSE Mailing Lists

Re: [opensuse-packaging] PySoulSeek and Nicotine
by Jan Matejek 17 Mar '08

17 Mar '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pascal Bleser napsal(a): | Christian Morales Vega wrote: | | 2008/3/14, Jan Matejek: | | Nicotine is also dead, nicotine-plus is the project currently alive. | | Pascal Bleser mantains it in Packman (because of legal problems?): | | | | http://packman.links2linux.org/package/nicotine-plus | | Yep. DHT is considered risky by Novell's legal dept. | | I also build ktorrent with DHT on Packman. The ktorrent packages that | ship with openSUSE + the ones in the Build Service repositories are | without DHT (it can be disabled at build time). | | cheers Thanks for the info. Question remains, though: Does Nicotine+ contain DHT or some other technology that is considered risky, AND that is different from original PySoulSeek? ~From what I understood, the SoulSeek protocol has a central server and therefore is "safe". I'd be happy to include Nicotine+ if that's the case. regards, m. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFH3pWnjBrWA+AvBr8RAiDHAJ9XyhlUVneJhuv7kZayB/hVF66IjwCbBlAg swwEitKz96I7NhFAvsS/tFQ= =QqU+ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

Re: [opensuse-packaging] New rpm in beta
by Stephan Kulow 17 Mar '08

17 Mar '08

Am Freitag, 14. März 2008 schrieb Stephan Kulow: > Am Donnerstag 13 März 2008 schrieb Stephan Kulow: > > Hi, > > > > If you see build failures in beta, then this is due me trying to > > program C - i.e. support lzma payload in rpm. It's only in BETA. > > OK, beta is through (after several adoptions in build system for that > new payload) and this is a tar of the packages on the current kde cd > built with bzip -9 payload and lzma -2 payload: > > -rw-r--r-- 1 coolo suse 547M 14. Mär 10:44 bzip.tar > -rw-r--r-- 1 coolo suse 491M 14. Mär 10:47 lzma.tar -rw-r--r-- 1 coolo suse 447M 16. Mär 10:13 lzma5.tar lzma -2 compresses 11% better than bzip -9, lzma -5 even 18% And at a pretty impressive price: 2008-03-12 20:41:28: built kernel-source in 4 + 43 + 182 s 2008-03-13 22:03:23: built kernel-source in 5 + 43 + 195 s -> switching from lzma -2 to lzma -5 2008-03-15 05:32:50: built kernel-source in 14 + 50 + 469 s 2008-03-15 18:35:51: built kernel-source in 7 + 42 + 465 s Could be bad luck too of course - especially as the setup times increased too, which is very weired taking my previous measurements with lzma - perhaps the host (the same all the time) was busy. Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] PySoulSeek and Nicotine
by Jan Matejek 15 Mar '08

15 Mar '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello, there was a mention of Nicotine (a soulseek client, successor to PySoulSeek, http://nicotine.thegraveyard.org/ ) on opensuse mailinglist. I am maintainer of PySoulSeek and would like to drop it in favor of Nicotine. However, contrary to the mention on the opensuse list, it appears that we do not have Nicotine package (yet). Is this true, or was I searching for a wrong name? If we don't have the package, why? Are there some licensing issues i'm not aware of (something along the lines of bittorrent's DHT technology problem), and if yes, how come we can have PySoulSeek (package pyslsk) and not Nicotine? Or is it just that nobody packaged Nicotine yet? regards jan matejek -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFH2rjAjBrWA+AvBr8RAkbMAJ4x1BDnT3hsNJCZBYE7KBTd7B4EVgCePDoW 6vWkWGHK7Gg7QAwbK9VvnhI= =Xoh1 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] NetworkManager in alpha 3
by Tambet Ingo 15 Mar '08

15 Mar '08

Hey, There was a pretty frequent crasher in the package I submitted to NetworkManager yesterday. Now, after deadline for alpha 3 packages, I submitted a fix for it. Is it possible to get it to alpha3 still somehow? Tambet --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Framewave binaries
by Rohit Garg 14 Mar '08

14 Mar '08

Hi, Please provide packages for Framewave library from the oss repos. I really need it. The license is Apache, so that should be no problem. It can be found at http;//framewave.sourceforge.net It's already in the science wishlist. -- Rohit Garg Junior Undergraduate Department of Physics IIT Bombay --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 5

[opensuse-packaging] New rpm in beta
by Stephan Kulow 14 Mar '08

14 Mar '08

Hi, If you see build failures in beta, then this is due me trying to program C - i.e. support lzma payload in rpm. It's only in BETA. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

[opensuse-packaging] Request for Co_Maintainer (open-vm-tools)
by Dominique Leuenberger 14 Mar '08

14 Mar '08

Hi everybody (this timeespecially @novell/@suse) I'm on the lookout for a co-maintainer of one of my packages in OBS. The goal actually would be to get the package in the base distribution, out of OBS. As Stephan Kulow told me, this would not be difficult (for him / the project), if some internal packager agrees to co-maintain the package with me. I would say I make the packages in OBS and once ready, you can check them in to your system, if you agree. Any errors in the packages you're welcome to report directly to me (via bugzilla and assign to me or by mail). I'm talking about the open-vm-tools, they can currently be found in home:dimstar project (and were requested by users to be included). I just upgraded (together with an internal dev from vmware, they are quiet supportive) the bundle to support kernel 2.6.25 (tested with rc5). It just does not build for i586 in OBS for the moment (expansion errors on kernel-syms, but that's a Factory owb problem, not of 'my' package). so the question in short: is there anybody that would be willing / ready to work with me on this package, to have it included in openSUSE 11.0? We're still in time before feature freeze and I guess it should be possible to have it integrated. Thank you veyr much for your help! I'm sure the tools would be a great addition to be installed by default on openSUSE on every VMWare installation. We can only support our users with it. Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

Re: [opensuse-packaging] PulseAudio plans for suse 11.0
by Jan Matejek 13 Mar '08

13 Mar '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Morales Vega napsal(a): > 2008/3/11, Wade Berrier <wberrier(a)novell.com>: >> Hello, >> >> >> On Tue, 2008-03-11 at 23:19 +0100, Adrian Schröter wrote: >> > On Tuesday 11 March 2008 19:17:47 wrote Wade Berrier: >> > > Hi, >> > > >> > > I know that PulseAudio is going to be the default sound server for >> > > Gnome. Will it also be for KDE (or better yet, is it going to be a >> > > distribution wide sound server?) >> > >> > I can not tell what is planned, but we were happy to get rid of any extra >> > server process some years ago, because it can hurt sometimes and is not >> > needed anymore, what means it is just overhead (because either alsa does >> > mixing or hardware itself). >> > >> > > The reason I ask is because it would be great if all packages in the >> > > distro were pre-configured to work against pulseaudio. That way no >> > > matter what desktop environment you're using, sound will just work for >> > > all apps. >> > >> > well, it should be no problem if some apps use direct alsa and if some other >> > app gets started later what uses pulseaudio. At least as long pulseaudio >> > daemon gets started automatically (I see no reason why it should run always) >> > and pulseaudio itself is using alsa as well. >> >> >> The idea would be to have pulseaudio go stright to hw:0, and not use >> dmix for either pulseaudio, or anything else. That way the dmix issues >> can be avoided, and all the cool features of pulse can be used. >> Currently, I must stop pulseaudio to run this app, reconfigure alsa to >> run that app, etc... >> > What issues dmix has? You don't need to configure it manually anymore, > and the classic "mixing should be done in kernel" complain isn't > "solved" by PulseAudio. > > Also, would be good to know exactly what are the cool features of > PulseAudio that ALSA hasn't. > - Network transparency? Yes, it's cool, but will not be so much used. > - Per application volumen control? Isn't Phonon going to give us the same? > - ? phonon - um, not really? a) isn't phonon somehow limited to KDE4-based stuff? b) how about legacy applications? (pulse has pulse-oss or whatever it's called) - - how about "every soundcard plays all the sound" ? or precise control of sources/sinks in GUI *and* real-time - let's say i want music to run through my high-end audiophiliac soundcard and stupid icq notification sounds through the built-in piece-of-crud AC97 into tiny speakers in my display? or something (yes, phonon is supposed to do that as well, see above) regards, m. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFH1/k0jBrWA+AvBr8RAh9YAKCz3vuokiyv+F4tidxqYGFAc8s0/gCfZWbi 580D0pXd+IJxCqHM/t5S0E4= =ivpo -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 17

[opensuse-packaging] PulseAudio plans for suse 11.0
by Wade Berrier 12 Mar '08

12 Mar '08

Hi, I know that PulseAudio is going to be the default sound server for Gnome. Will it also be for KDE (or better yet, is it going to be a distribution wide sound server?) The reason I ask is because it would be great if all packages in the distro were pre-configured to work against pulseaudio. That way no matter what desktop environment you're using, sound will just work for all apps. Lennart posted a nice guide of how to package apps so they will work with pulseaudio: https://www.redhat.com/archives/fedora-devel-list/2007-August/msg01196.html Wade

4 5

[opensuse-packaging] PAM_SCRIPT
by James Tremblay 12 Mar '08

12 Mar '08

Hey guys, I was wondering about getting pam_script into the default pam_modules RPM what is the reason it isn't already there? Can we include it in openSUSE version? It would certainly help make this solution easier to configure and possibly help write an automated solution around it. http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId… If someone could write an installer for the above solution it would be a huge thing. -- James Tremblay Director of Technology Newmarket School District Newmarket NH 03857 "let's make a difference" http://en.opensuse.org/education --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 3