- openSUSE Packaging

[opensuse-packaging] insserving services
by Jan Engelhardt 28 Oct '07

28 Oct '07

Hi, some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 8

[opensuse-packaging] Multiple KMP modules
by Andreas Schneider 28 Oct '07

28 Oct '07

Hi, I'm currently updating VirtualBox and building all the kernel modules now. https://build.opensuse.org/project/show?project=Virtualization%3AVirtualBox VirtualBox needs a kernel module (vboxdrv) loaded to work. But it has two additional kernel modules for installed guest (vboxadd, vboxvfs). Is it possible to add several KMP modules in one spec file or do I need an additional spec file? So hat I have virtualbox-kmp-default and virtualbox-kmp-guest-additions-default. -- andreas -- http://www.cynapses.org/ - cybernetic synapses

1 0

[opensuse-packaging] RPM packageing is too much like folklore.
by Paul Elliott 28 Oct '07

28 Oct '07

Folklore, like every village has its own version of the story, slightly different from every other village's version. There is plenty of documentation on writing a .spec file on the net, but is scattered across 1000 different web sites and mailing list archives. A lot of the documentation is obsolete in places. You can not go to one place and learn RPM packaging, instead you have to go prospecting like an anthropologist to find all the information that seems to be relevant to your problem. Every distro does it approximately the same, with enough differences to drive one mad! Will Linux Standard base or some big documentation writer ever come to save the day and bring order to this chaos? -- Paul Elliott 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

3 2

[opensuse-packaging] how to convert pkg-config checks to BuildRequires (was: Re: openSUSE GNOME meeting (2007/10/25))
by Stanislav Brabec 26 Oct '07

26 Oct '07

Rodrigo Moya wrote: > - Stanislav had a tool to analyze pkg-config checks for automatically update > BuildRequires It's still unfinished and might be broken... I made my proof of concept public: http://pack.suse.cz/sbrabec/pkg-buildrequires/ Technical background and problems: - It's not easy to get package dependency data from configure.in. m4 expansion may occur and shell expansion may occur as well. Finally it's not easy to guess, which branch of code is actully active => The simplest way is modifying or wrapping of pkg-config itself. Solved. - RPM offers no way how to get data collected by %build back to the spec file preamble. We need a simple but enforcing way to perform this step manually. Still needs proper solution. Proposed usage: BuildRequires: pkg-buildrequires and replace %configure by %pkg_buildrequires_configure -- 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 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 1

[opensuse-packaging] rpm5.org
by Pascal Bleser 25 Oct '07

25 Oct '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I look at the "Team" presented on http://rpm5.org I notice several people involved in QA for several distributions, but no one for openSUSE/SLE*. Lack of time, lack of interest, technical reasons ? Thanks for enlightening me :) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHH9iwr3NMWliFcXcRAtYqAJ4x9fkJ1Jb2nT0nTpyLAF3aLPemRQCgkH9I M3dXLk3Xuo0uVBNAUyT+074= =l3v5 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 17

[opensuse-packaging] Suggests/Enhances HOWTO?
by Nikolay Derkach 25 Oct '07

25 Oct '07

Hi, Is there any howto/guide on how to use these RPM tags? I couldn't find any, moreover I never saw a single package using them. Nevertheless, I recall there was an announcement on the list that these instructions were implemented [*]. So, could someone please clarify the situation? PS: are these patches included into the upstream RPM? [*] http://lists4.opensuse.org/opensuse-packaging/2005-12/msg00068.html -- Regards, Nikolay Derkach --------------------------------------------------------------------- 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] 2nd reminder to fix your packages for compiling with GCC 4.3
by Richard Guenther 23 Oct '07

23 Oct '07

[BCCed to devel, labs as not all people seem to be subscribed to opensuse-packagers] Hi, this is a reminder for you to have a look at your packages that fail in the BETA distribution (which has GCC 4.3 as its compiler). If you think that the compiler is at fault feel free to report these issues back to me or file a bugzilla for them. Builds with a slightly newer version of GCC for x86_64 and i586 are also available in the home:rguenther:playground build service project. Thanks, Richard. -- Richard Guenther <rguenther(a)suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 7

[opensuse-packaging] Re: [Research] Re: [devel] 2nd reminder to fix your packages for compiling with GCC 4.3
by Ruediger Oertel 22 Oct '07

22 Oct '07

On Mon, 22 Oct 2007, Miklos Szeredi wrote: > On Mon, 2007-10-22 at 15:08 +0200, Richard Guenther wrote: > > > this is a reminder for you to have a look at your packages that fail > > in the BETA distribution (which has GCC 4.3 as its compiler). If you > > think that the compiler is at fault feel free to report these issues > > back to me or file a bugzilla for them. > > A couple of my packages (and >100 others it seems) are failing with > > error: 'foo' was not declared in this scope > > I'm rather clueless about C++ issues, so I don't have a clear idea if > this is indeed a bug in all these programs or if it's a gcc problem. no these are really missing include files in your sources. What I've seen up to now were roughly 90% of either missing "#include <cstring>" or "#include <cstdlib>". > But even if these are bugs, wouldn't it have been prudent to make this a > warning, for couple of releases, before turning it into an error? well, "function not declared" has been an error in C++ before. What changed is that some files are not any longer pulled in automatically by others to get closer to the standard (please correct me here if I'm wrong). Unfortunately I don't see how a compiler should do something like "include this header but prefix all declared functions with a warning" ... -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux Fatou 2.6.22.9-0.4-default #1 SMP 2007/10/05 21:32:04 UTC x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

1 0

[opensuse-packaging] Re: [Research] Re: [devel] 2nd reminder to fix your packages for compiling with GCC 4.3
by Stephan Kulow 22 Oct '07

22 Oct '07

Am Montag 22 Oktober 2007 schrieb Miklos Szeredi: > On Mon, 2007-10-22 at 15:08 +0200, Richard Guenther wrote: > > this is a reminder for you to have a look at your packages that fail > > in the BETA distribution (which has GCC 4.3 as its compiler). If you > > think that the compiler is at fault feel free to report these issues > > back to me or file a bugzilla for them. > > A couple of my packages (and >100 others it seems) are failing with > > error: 'foo' was not declared in this scope > > I'm rather clueless about C++ issues, so I don't have a clear idea if > this is indeed a bug in all these programs or if it's a gcc problem. > > But even if these are bugs, wouldn't it have been prudent to make this a > warning, for couple of releases, before turning it into an error? As in "Warning: you obviously did not include all header files you need, but I invented some for you"? I don't think that would work. If 'foo' needs foo.h, you need to include it. If bar.h of gcc 4.1 happend to include it, there is no guarantee whatsoever that it will continue so. Greetings, Stephan --------------------------------------------------------------------- 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] Reminder to fix your packages for compiling with GCC 4.3
by Richard Guenther 18 Oct '07

18 Oct '07

On Wed, 17 Oct 2007, Holger Macht wrote: > On Wed 17. Oct - 17:53:53, Richard Guenther wrote: > > On Wed, 17 Oct 2007, Richard Guenther wrote: > > > > > On Wed, 17 Oct 2007, Holger Macht wrote: > > > > > > > On Wed 17. Oct - 13:09:30, Marcus Rueckert wrote: > > > > > On 2007-10-17 12:56:51 +0200, Holger Macht wrote: > > > > > > What would result in > > > > > > > > > > > > char *prop = (char*)"laptop_panel.num_levels"; > > > > > const char *prop = "laptop_panel.num_levels"; > > > > > > > > > > should fix it too no? > > > > > > > > Of course it does. > > > > > > > > I also have to change everything like: > > > > > > > > void testfunc(char *str); > > > > testfunc("foo"); > > > > to > > > > testfunc((char*)"foo"); > > > > > > No, the correct fix is to make testfunc take a const char *. > > > > So what about functions which modify their arguments and thus can't take a > const? For those it would be even more wrong to pass a constant string literal, the function would simply segfault in that case. For those you need to use char tmp[] = "foo"; bar (tmp); which constructs a stack temporary string with the contents "foo" and thus allows writing into it. Richard. -- Richard Guenther <rguenther(a)suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0