March 2008 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Some notes from your friendly autobuild team
by Marcus Rueckert 14 Apr '08

14 Apr '08

hi, 1. good ways of doing library policy compatible packages Since quite some time we have some policy for packaging shared libraries. [1] We all had lots of fun and work with it already. There is some way to save some work for all of us. I will use libetpan as an example here. in the current factory package we have libetpan11 and libetpan-devel. and in the queue there is an update that would bump the soname to libetpan.so.13. now it would be renaming a package in autobuild, rename the spec, rename the changes file and check in the new package. To save us all a bit work we slightly change the packaging: we rename the package back to libetpan and let the spec generate an empty main package. Additionally we have 2 subpackages (libetpan13 and libetpan-devel). Of course you should add a provides to the libetpan13 package: Provides: %{name} = %{version} 2. Renaming a package Just a short not how the proper provides/obsoletes should look like in the usual case -> [2] with kind regards darix [1] http://en.opensuse.org/Packaging/Shared_Library_Packaging_Policy [2] http://en.opensuse.org/Upgrade_Dependencies#Renaming_a_package -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 6

[opensuse-packaging] [RFC] Proposal: Distribution Branding (RC3)
by Stanislav Brabec 31 Mar '08

31 Mar '08

Hallo. RC3 of Distribution branding proposal was just released on the Wiki: http://en.opensuse.org/SUSE_Package_Conventions/Branding It is intended as addition to the SUSE Package Conventions Feel free to fix minor issues and discuss major problems or missing issues. Important changes since RC2: - "opensuse" is now consistently "openSUSE" - Self conflict added to branding packages to ensure conflict of one branding with each another (proposed by coolo) - New sections regarding Branding and themes - New sections regarding GNOME packages branding - Branding virtual package specification -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Next openSUSE milestone: crypto/base freeze
by Stephan Kulow 31 Mar '08

31 Mar '08

Hi, Just a small reminder - this is the last week to submit changes for the base system and do version updates for crypto related routines. From http://en.opensuse.org/Roadmap/11.0: Mon, Apr 7 Component freeze for beta1, crypto freeze Milestone: We have settled for a KDE branch to go for Milestone: Feature and version freeze for the base system Milestone: Kernel and install works on most targeted machines. Milestone: Packages containing cryptographic routines are frozen (ECR) Preliminary Authoring Deadline for localized doc files (ADL loc prelim) 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

1 0

[opensuse-packaging] rpm/lzma upgrade issue
by JP Rosevear 29 Mar '08

29 Mar '08

Trying to upgrade to the latest internal rpm this morning (rev 181) from a factory box that hadn't been updated in a couple weeks I received the following error: rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by rpm-4.4.2-181.x86_64 Presumably because the older rpm could not update itself because of the new payload requirements. Updating to the intermediate rev 179 that was available in the public channel worked around the problem. There are two potential issues: 1) People using zypp to upgrade factory may be halted from upgrades and the more critical: 2) People on older distros may be unable to upgrade to 11.0 when it comes out. Coolo suggested we might need to define some core packages that don't use the new payload system so upgrades work, but it seems like it yast potentially we'd have to upgrade rpm first and then upgrade the packages even if we fix that. -JP -- JP Rosevear <jpr(a)novell.com> Novell, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 12

[opensuse-packaging] Re: commit mozilla-nspr
by Wolfgang Rosenauer 28 Mar '08

28 Mar '08

Hi, h_root wrote: > +- Split out a shared library subpackage. > +Source1: README.SuSE > Patch1: prdtoa.patch > Patch3: pkgconfig.patch > BuildRoot: %{_tmppath}/%{name}-%{version}-build > +Requires: libnspr4 = %{version} > > %description > NSPR provides platform independence for non-GUI operating system > @@ -52,8 +56,26 @@ > -------- > Mozilla Foundation <drivers(a)mozilla.org> > > +%package -n libnspr4 > +Summary: Netscape Portable Runtime > +Group: System/Libraries > +Requires: %{name} >= %{version} I'm wondering about that "split". I understand and support the shared library policy for most cases but I don't support it in this case. The package now consists of mozilla-nspr libnspr4 subpackages where mozilla-nspr only contains README.SuSE (which I have yet to see) and libnspr4 which contains three shared libraries with different names and without SO-versioning. If it's really mandatory that the package name is libnspr4 (while libnspr4.so is only one of the three libs) then please just do a package rename. So to summarize that looks like a split which effectively only is a package rename with some overhead and is only done for the sake of the rename. Personally I think keeping the consistency with older distributions in that special case outweighs the value of that change. Please tell me if I'm wrong and what I don't see. Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 4

[opensuse-packaging] Review Request: themonospot - Avi parser and content descriptor
by hman 27 Mar '08

27 Mar '08

Hi, i dev a cross platform open source (GPLv2) application to scan and edit avi file: http://www.integrazioneweb.com/themonospot dev in C# using MONO and GTK i used OpenSUSE Build Service to build tarball for openSUSE 10.3 and Factory https://build.opensuse.org/project/show?project=home:hmandevteam:themonospot repo: http://download.opensuse.org/repositories/home:/hmandevteam:/themonospot/ i would like to publish it in openSUSE repository. Could you help me ? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Changes in the desktop menu part of the package conventions
by Vincent Untz 20 Mar '08

20 Mar '08

Hi, Starting a new thread with a clear title so everybody reads it :-) I've updated the desktop menu part of the package conventions [1] to fix some errors. See [2] for the discussion. Here's the detail of the changes: + GenericName is not the key used for the tooltip. It's the Comment key. Fixed the examples accordingly. + Make the examples valid .desktop files. Also use StartupNotify and StartupWMClass instead of old KDE-specific keys. + the Encoding key is deprecated, so I removed any mention of it. + Fix the description of the Icon key. The value can be an absolute path. Also link to the icon theme specification to explain where icons should be installed. Thanks, Vincent [1] http://en.opensuse.org/Packaging/SUSE_Package_Conventions/Desktop_Menu [2] http://lists.opensuse.org/opensuse-packaging/2008-03/msg00102.html -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Fixing package conventions
by Vincent Untz 20 Mar '08

20 Mar '08

Hi, I found several errors on http://en.opensuse.org/SUSE_Package_Conventions/Desktop_Menu What is the process to fix them? I guess it's a bit more complex than just editing the wiki page? Here are the errors: + the xboard example has this line: "Categories=Game;BoardGame" It's missing a ; at the end of the line + Encoding explicitly defines the encoding used in the desktop file. The value “UTF-8” should be used. => the Encoding key is deprecated now, and shouldn't be used any more. The files are always UTF-8 encoded. + Icon defines the icon connected with the application. The value is an icon name without a suffix. Only the .png and .xpm icons are supported. They must be installed either below /usr/share/pixmaps/ or below /opt/gnome/share/pixmaps/. => the value can also be a path to an icon. The icon should be installed according to the guidelines defined in the icon theme specification if possible. + GenericName defines a comment that can be shown in a tool tip. It was defined by the key Comment in old desktop files. => that's wrong. The tooltip is still defined by the Comment key according to the spec. + the emacs.desktop example is not valid: Terminal=0 should be Terminal=false Also, X-KDE-StartupNotify=true should probably be StartupNotify=true and X-KDE-WMClass should be StartupWMClass + I'm confused by the list of categories. Some of them are not defined in the menus spec and shouldn't be used. It's not clear whether the small text above the categories implies that they should be prefixed with "X-SuSE-"? Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 7

[opensuse-packaging] RPM condition
by Bernhard Walle 19 Mar '08

19 Mar '08

Hello, can somebody help me in writing %if %{undefined rhel_version} && %{undefined centos_version} # code %else # code %endif in a way that the build in the OBS / SUSE_Linux_10.0 succeeds? I currently get a parser error. Thanks for your help. Bernhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 6

[opensuse-packaging] Naming of developer snapshot packages
by Ludwig Nussel 18 Mar '08

18 Mar '08

Hi, Suppose I have a package 'foo' for the stable release of that software but also want to package developer snapshots of e.g. the svn repo. I wonder how such a package should be named. Names such as foo-unstable foo-snapshot foo-devx foo-beta foo-experimental come into mind. Is there any established practice for the naming of developer snapshot packages? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

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

[opensuse-packaging] deprecated %run_ldconfig
by Stephan Binner 11 Mar '08

11 Mar '08

Hello, obviously some autobuild team member is currently in a mood to reject the checkin of packages which contain %run_ldconfig calls. Can we please make this a build failure instead of a warning before this policy is enforced? Bye, Steve --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 9

[opensuse-packaging] Reminder: openSUSE 11.0 Alpha3 deadline this week
by Stephan Kulow 10 Mar '08

10 Mar '08

Hi, To avoid conflicts with RC1 of SLE SP2, we will have the Alpha3 builds earlier (publish date 18th). This means to everyone developing and packaging: your package has to be ready not later than friday, 14th. 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

1 0

[opensuse-packaging] Call for test: open-vm-tools in OBS (and on the lookout for a co-maintainer)
by Dominique Leuenberger 08 Mar '08

08 Mar '08

Hello! Recently, somebody (Sunny) requested some RPMs offering the open-vm-tools in our nice distribution [0]. I opted to create some packages and have a look into this. So here I am, just a few days later with a working (as for me, my house did not burn down) example of those packages. They can be found at http://download.opensuse.org/repositories/home:/dimstar and are currently built for: openSUSE 10.3 stock openSUSE 10.3 updated openSUSE Factory (for factory, i586 fails to compile because of inconsistency within BS... for the moment, the kernel-source matching the kernel-syms can not be found but that will solve itself I guess.. it's just busy). There are two things to be installed in your VM: vmware-kmp-<kernelflavour> and open-vm-tools The KMP contains 5 kernel modules: vmblock vmhgfs mvmemctl vmsync vmxnet open-vm-tools installs the service vmware-guest (get's automatically activated) and the toolbox. In my tests, the mouse was after installation freely going in and out the VM (normally one of the easiest indices that the VM tools work), I could mount a shared host (mount.vmhgfs .host:/test /mnt) and access it and the clipboard was shared between host and guest... so now I have to ask you fellows to help me improve it, to make it undergo a lot of testing so we can convince coolo that he wants to include this package in the upcoming alphas and betas and finals of openSUSE (ups... we still don't have the procedures in place for community maintained packages). so for now that's it from my side... any sort of comment is highly appreciated. A short discussion with coolo revealed that, if there is an internal co-maintainer willing to work with me on this, we could possibly push it inside the Distribution... the time would be great, we did not reach feature freeze yet. Anybody willing to go down this road together with me? Have a good time, Dominique [0] http://lists.opensuse.org/opensuse-factory/2008-03/msg00068.html --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Use of icedtea in 11?
by Michal Vyskocil 08 Mar '08

08 Mar '08

Hi, I'm currently working on update of some java packages from OBS project Java:jpackage-1.7 to stable. So I'm also trying to build some of these packages with icedtea. Some of them should be builded (like adaptx) with small patches, some of them currently not (like hsqldb). But the switch to icedtea is not an automated process anymore, so if the autobuild team switches the compiler, majority of java packages will not be builded and needs to do some patches or revert back to the non free compiler. I can update a package and try to build it by icedtea, so I'm be able to switch the BuildRequire to java-1_7_0-icedtea-devel, if it works. The problem is, that the icedtea is only for i386 and a x86_64 available. On ppc or s390 we are using an IBM's compiler only. But a majority of a java packages is noarch, because a Java bytecode is architecture indepentent. I'm not sure, if I should use something like %ifarch %ix86 x86_64 BuildRequires: java-1_7_0-icedtea-devel %else BuildRequires: java-devel %endif in a spec file for noarch packages. May I try to build the most of java packages using icedtea? And if yes, how to do that? Use of the %ifarch in spec? Regards Michal Vyskocil --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5

[opensuse-packaging] Installation: lightweight VNC server
by Lukas Ocilka 07 Mar '08

07 Mar '08

[ This mail has been originally sent to opensuse-FACTORY] Hi, I just went through the new installation images searching for any huge binaries or libraries (or any other big files). I've found that we use Xvnc server (for remote installation). Only the binary takes 3.8 MB (of course, installation image is compressed). I'm asking here because FACTORY users have often broad knowledge of several alternatives [package maintainers too ;), of course]. Don't you know any 'better' and smaller (binary size, memory consumptions, less libraries) than the current Xvnc? Ideally we have it in build service... Of course, it has to cover the same range of features we currently use. Some hints: * FreeNX http://freenx.berlios.de/ * TightVNC http://myprogs.net/program/44ec3a0569499cc480f1fafabb8aebbb/TightVNC * any other? http://nixbit.com/search/vnc-server/ Any ideas, opinions, experience? Thanks and Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

5 6