August 2009 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] renaming for nagios-nrpe
by Christian 06 Mar '10

06 Mar '10

Hi, I am not very happy with naming of nrpe and its sub-pkg. we have nagios-nrpe-client, nagios-nrpe-server While seeing the client pkg I'll be misled to install this pkg on the remote box and vice versa. But the "client" pkg has to be installed on the nagios box. That's why I am thinking of: - nagios-nrpe it is the package to be installed on the remote box. - nagios-nrpe-plugin or nagios-plugins-nrpe just the name will let you associate to install this pkg on the nagios box. What do you think ? Any recommendations are welcome Kind Regards Chris -- 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] Re: --as-needed and pthread
by Michael Matz 17 Oct '09

17 Oct '09

Hi, [including some random mailing list, so that the text isn't lost :) ] On Thu, 18 Jun 2009, Cristian Rodríguez wrote: > > there are some packages that fail to build because they miss phtread > > symbols. I have always have the doubt about why there is the > > "-pthread" gcc flag... somewhere I read that's the correct thing to > > do, that using -lpthread is wrong, but without explanations. What > > should I use in these cases? I suppose use -lpthread would be the > > equivalent to what they did without --as-needed... but perhaps the > > behavior without --as-needed was already wrong. > > matz is the right person to answer your question, as far as I know, the > right way is using -lpthread instead of -pthread , is that correct ? Nope, -pthread is better than -lpthread (see below). It's completely possible that something is broken with as-needed vs. pthreads. Those cases have to be identified and then worked around (export SUSE_AS_NEEDED=0), or better, analyzed for the root cause. I didn't get the complete thread, only this forward, so I don't know what the nature of the breakage is, so I can give only speculations: I would think that if something with pthread and as-needed breaks it doesn't get exposed as missing symbols or the like (so that apps don't even start) but rather mysterious breakages related to non-thread-aware functions being used even though -pthread was given as compile and link flag. [background] Regarding the explanation of -pthread/-lpthread: Unfortunately the initial threading support for UNIX was a bit like bolted onto the existing (non thread-aware) libc. For various reasons it was decided that users that aren't interested in threading are not supposed to pay the cost of _potential_ thread safety. This cost is mostly associated with locking some shared data structures for libc and the process output (e.g. output of printf() ). Now, given this criteria, there's not much choice. Basically the user has to announce to the system if or if not the application is thread aware, so that it (the system) can chose between thread-aware or non thread-aware functions. This announcement is done by the -pthread flag. The difference to the -lpthread flag is that it is not only a link time flag (saying that the libpthread library has to be put into the dependence libraries) but also a compile time flag. So for compiling .c to .o files for a thread aware program it's necessary to include -pthread into the compile flags. The effect of that option is system dependend. Usually it will result in the compiler defining some preprocessor symbols (_REENTRANT) so that system headers can choose between different implementations of various posix functions (where the API doesn't make a difference between thread-safe and -unsafe functions) and internal data structures. So, for memoizing the difference: -lpthread is a link time only flag, simply telling the linker to include libpthread into the application. -pthread (without the "l") is a link time _and compile time flag_. Because sometimes different code has to be emitted (for the runtime system including libc) for programs supposed to be thread-safe, this can't be announced only at the link phase, the compiler has to know about this. [more magic] Now, for linux there's a bit magic involved. To make the cost for non thread-safe programs really low some routines in libc _are not thread-safe_. That's fine, those programs aren't linked against libpthread, so they have announced to be not interested in threads. libpthread.so provides thread-aware variants of some functions that are also provided by libc itself. For instance open() and friends is such function. The libpthread variant includes some locking for shared data structures. (Apart from these overriding functions it also includes the usual pthread functions, pthread_*, e.g. pthread_spin_lock). How this all works is because ELF symbols resolution rules say so. If an application calls "open" and is linked against libpthread and libc (which both provide a version of "open", one thread-aware the other not) then the dynamic linker will chose the first it finds. Other things (gcc .spec files) make sure that libpthread is linked in _before_ libc when -pthread is given. This can't be ensured for -lpthread, the latter being simply a request for a random other library, as far as the system knows. So only -pthread, not -lpthread, makes really sure that libpthread is linked at the right place vs. libc, so that it can override the non thread-aware functions of it. [less magic] Having said all this, it usually is just fine to simply link against libpthread (via -lpthread) with linux, as long as you don't mention -lc before. This is because most headers don't care about the _REENTRANT preprocessor define, i.e. they don't change their content depending on the flag, and because ELF rules will still make the functions from libpthread be preferred. But for cross-platform compatibility it's important to use -pthread, _not_ -lpthread. And as it's important for others, and at least good under linux, you can just as well use it always if you need. Ciao, Michael.

5 15

[opensuse-packaging] Supplements package with a required version
by Lubos Lunak 08 Sep '09

08 Sep '09

Hello, I have package mozilla-xulrunner191, which can make use of package mozilla-xulrunner191-kde4, but only of a specific version. How do I express that using rpm dependencies? Currently the -kde4 package has "Supplements: packageand(mozilla-xulrunner191:kdebase4-workspace)" to be pulled in when both the main package and the KDE desktop are installed. I however don't know how to express the version dependency, since the -kde4 package does not care what the version of the main package is, but the main package has a version requirement on the -kde4 package, if it is installed. I cannot use Requires in the main package, since -kde4 is optional. If I use Recommends in the main package, I don't know how to recommend the -kde4 package only if KDE is also installed. Is there a way? -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak(a)suse.cz , l.lunak(a)kde.org Lihovarska 1060/12 tel: +420 284 028 972 190 00 Prague 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

2 2

[opensuse-packaging] Skrooge 0.5.0/brp-symlink Build fails
by Sascha 'saigkill' Manns 02 Sep '09

02 Sep '09

Hello Mates, atm i'm getting the following Error. Does anyone know how to fix it? + /usr/lib/rpm/brp-symlink ERROR: link target doesn't exist (neither in build root nor in installed system): /usr/share/doc/kde/HTML/uk/skrooge/common -> /usr/share/doc/kde/HTML/uk/common Add the package providing the target to neededforbuild and Requires INFO: relinking /usr/share/doc/kde/HTML/uk/skrooge/common -> ../common (was /usr/share/doc/kde/HTML/uk//common) ERROR: link target doesn't exist (neither in build root nor in installed system): /usr/share/doc/kde/HTML/sv/skrooge/common -> /usr/share/doc/kde/HTML/sv/common Add the package providing the target to neededforbuild and Requires INFO: relinking /usr/share/doc/kde/HTML/sv/skrooge/common -> ../common (was /usr/share/doc/kde/HTML/sv//common) INFO: relinking /usr/share/doc/kde/HTML/en/doc/common -> ../common (was /usr/share/doc/kde/HTML/en/common) INFO: relinking /usr/share/icons/oxygen/128x128/apps/skrooge.png -> .../../../../pixmaps/skrooge.png (was /usr/share/pixmaps/skrooge.png) INFO: relinking /usr/share/kde4/apps/skrooge/images/logo/l10n/en_US/list_bank.txt -> .../en/list_bank.txt (was /usr/share/kde4/apps/skrooge/images/logo/l10n/en/list_bank.txt) INFO: relinking /usr/lib64/libskgbasegui.so.0.5.0 -> kde4/plugins/designer/libskgbasegui.so.0.5.0 (was /usr/lib64/kde4/plugins/designer/libskgbasegui.so.0.5.0) INFO: relinking /usr/lib64/libskgbankgui.so.0.5.0 -> kde4/plugins/designer/libskgbankgui.so.0.5.0 (was /usr/lib64/kde4/plugins/designer/libskgbankgui.so.0.5.0) error: Bad exit status from /var/tmp/rpm-tmp.7525 (%install) -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- 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] query - Linking in another project.
by doiggl＠velocitynet.com.au 01 Sep '09

01 Sep '09

Hello, I am trying to build the wflogs rpm and have gotten the result back It says - checking for shl_load in -ldld... no configure: error: wfnetobjs-incdir: no directory found, use configure option error: Bad exit status from /var/tmp/rpm-tmp.36404 (%build) References: project -> https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl spec file -> https://build.opensuse.org/package/view_file?file=wflogs.spec&package=wflog… logs -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=wflog… I know I need to include or depend on Package wfnetobjs. It is located in another persons project -> https://build.opensuse.org/package/show?package=wfnetobjs&project=home%3Ael… Ouestions. ========= 1. How do I link in wfnetobjs to my wflogs project so it can compile. 2. There are possible parameters I can use Parameter switches e.g --with-wfnetobjs-incdir --with-wfnetobjs-library --with-wfnetobjs-libdir An example I have seen in the past is ./configure --with-wfnetobjs-libdir=/usr/include/wallfire/ 3. Where in the spec file does the line go, if so which section ? Any help appreciated Cheers Glenn. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 10

[opensuse-packaging] Rebuilding in OBS
by Magnus Boman 28 Aug '09

28 Aug '09

Hello, For the past months it's been really difficult to contribute to package updates since I only have time to help out on weekends. This boils down to commits going in to oS:F, and my pet project (GNOME:Factory) is basically always blocked waiting for oS:F to build. Trying to build a package locally, is not all that easy, as recently, osc tells me, more often than not, that it can't find a package on a mirror nor in OBS so the local build is aborted. Now, I understand that we want to rebuild packages etc, and I also understand that weekends are the most appropriate time to this. The way OBS rebuilds packages seems a little bit paranoid to me though and I would like to ask the question if we can do it better. So, this is the workflow (AFAIK): 1. I branch a package from G:F, it ends up in my home and basically the content of it is a _link (since I have not changed anything yet) 2. I update the package and commit (now, I have a project.diff) 3. I submit the package to G:F 4. The package is accepted into G:F (G:F will now contain _link and project.diff, while the package in my home is back to being a _link) 5. The package is submitted from G:F to oS:F (and lets say accepted into oS:F). G:F will now be _link, and the package in my home is _link. In oS:F, it's all the files this package contains of Now, what will happen is: * When I do 1, OBS wants to build the package in my home * In step 4 (when package have been accepted), OBS will want to build the package in both my home and in G:F * In step 5, OBS will want to build the package in oS:F, G:F and my home My thinking: In this scenario, my home, G:F and oS:F all use the same build dependencies, so when a package is a _link, can't OBS just copy the content from the linked package instead of having to rebuild it completely in all these different places? Cheers, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 14

[opensuse-packaging] RE: Adobe Reader 9 (Was: Re: [opensuse-factory] Queries about M6)
by Dominique Leuenberger 28 Aug '09

28 Aug '09

>>> On 8/28/2009 at 7:06, Rastislav Krupanský<rastislav.krupansky(a)gmail.com> >> Installed i586 fine and it works, but Acroread icon missing in SLAB´s >> Aplication Browser. Via Traditional Main Menu is available. Executed in >> terminal without error, described above. > > It´s already there. After log out and log in, icon has appeared in SLAB´s > Aplication Browsare also. (X-posting to -packaging. Those people probably have more knowledge in this domain). Anybody having the trick for me to avoid this glitch in the package? There must be a macro to be executed in the %post section. any help is appreciated. Dominique -- 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] Import of Fedora Packaging Guidelines
by Michal Vyskocil 28 Aug '09

28 Aug '09

Hi all, as you know I wrote a post about Fedora Packaging Guidelines [1]. I was working on it during last three weeks (but a little, so it takes a long time :)) and nowadays I'm ready to import a Fedora's content to en.opensuse.org wiki. Now it is on pack.suse.cz [2]. I also checked that none of that page conflicts with an existing content on openSUSE wiki, so it can be imported easily. Tom Callaway [3] from RedHat confirms me that a Guidelines are under Open Publication License [4] and we can use it for SUSE without restrictions. He was also interested on future collaboration and offers some meeting on LinuxTag - it would be nice if anyone from SUSE will be ready to start a discussion. Before import I'd like to ask: Which pages should be excluded for openSUSE? Some pages seems that they are not interesting for SUSE (like Packaging:OldJPackagePolicy [5], Packaging:SugarActivities [6]). Import it, or don't? Second one is how to edit the text and adapt it for SUSE? Change the existing text or leave it and add a SUSE specifics to the beginning or end of page (as suggests Vladimir)? The second way should help us with synchronizing of changes. After that I'll add a warning [7] on the beginning of every page to prevent that some users will use those guidelines and ask for help with editing ;-) [1] http://lists.opensuse.org/opensuse-packaging/2009-02/msg00043.html [2] http://pack.suse.cz/mvyskocil/fedora-packaging-guidelines/ [3] https://fedoraproject.org/wiki/TomCallaway [4] http://fedoraproject.org/wiki/Legal/Licenses/OPL [5] http://fedoraproject.org/wiki/Packaging:OldJPackagePolicy [6] http://fedoraproject.org/wiki/Packaging:SugarActivityGuidelines [7] http://en.opensuse.org/Template:Warning1 Best regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 26

[opensuse-packaging] URGENT: please review your project.diffs
by Stephan Kulow 27 Aug '09

27 Aug '09

Hi, On http://www.suse.de/~coolo/factory-status.html I try to collect all problematic packages. While it defaults to show only packages currently failing, you can switch to show all problems in the first line. And there a lot of packages where someone accepted it to the devel project reviewing and then didn't submit it for inclusion to the distribution. This is a problem as we're nearing already the 2nd milestone after version freeze and I see tons of such packages ;( Take e.g. python-cairo, a prime example ;( <collection> <request id="15026"> <action type="submit"> <source project="home:lmedinas:branches:GNOME:Factory" package="python- cairo" rev="2" /> <target project="GNOME:Factory" package="python-cairo" /> </action> <state name="accepted" who="vuntz" when="2009-07-21T13:55:05"> <comment></comment> </state> <history name="new" who="lmedinas" when="2009-07-21T13:49:04" /> <description>Update to 1.8.6</description> </request> <request id="16898"> <action type="submit"> <source project="GNOME:Factory" package="python-cairo" rev="9" /> <target project="devel:languages:python" package="python-cairo" /> </action> <state name="accepted" who="poeml" when="2009-08-06T14:44:30"> <comment>reviewed ok.</comment> </state> <history name="new" who="vuntz" when="2009-08-06T00:07:38" /> <description>New upstream version</description> </request> </collection> lmedinas, vuntz, poeml - 3 people worked on this package and still it isn't in 11.2 ;( I understand the problem very well and IMO the work flow just _asks_ for that trouble, but it is as it is - and _everyone_ needs to be aware of it and help others in looking at factory-status.html for packages he worked on and expected them to end in 11.2 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 6

[opensuse-packaging] another little build service tip
by Stephan Kulow 27 Aug '09

27 Aug '09

Hi, Often I'm asked "what happend to my submit request"? All I do to answer that question (most often the answer is "what submit request?") is: curl -n "https://api.opensuse.org/search/request?match=action/target/@package='bash'" It returns XML format, but it tells you what when where - for all projects where a "bash" package exists. 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

[opensuse-packaging] Patch0 versus %patch
by Michael Schroeder 26 Aug '09

26 Aug '09

Hi packaging folks, FYI: rpm-4.7 complains if the Patch tag doesn't match the %patch call, i.e. if you use Patch0/%patch or Patch/%patch0. I've fixed and submitted all Factory packages where this was a problem. So don't be alarmed ;-) Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- 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] ANNOUNCE: changing the role of pre_checkin.sh
by Stephan Kulow 25 Aug '09

25 Aug '09

Hi, We just had a little discussion about one little detail of our checkins and I would like to announce the result: - we will no longer call pre_checkin.sh while accepting, it has to be called by the packager _before_ submit (pre checkin basically :) This has two reasons: 1. be less suprising if accepting changes spec file texts - especially for people new to packaing this proved to be a factor 2. avoid one more risk of our infrastructure by malformed scripts (the more important reason) - osc commit will (later) call the script before transfering to the server, so you also have more freedom in what you call in that script, it only has to be on your computer [as long as you can live without co-maintainers] Unrelated to this I would like to remind everyone that every extra script and data file needs to be listed as Source in the .spec file. The change is not yet active, but please stop relying on others calling pre_checkin.sh now. Thanks, Stephan -- 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] Libs Dev?
by Sascha 'saigkill' Manns 25 Aug '09

25 Aug '09

Hello Mates, i'm trying to port an Program to openSUSE: Have we an Place similar to /usr/share/libs/dev? I don't heard that place before... -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4

[opensuse-packaging] need help with bugzilla 3.4.1 .spec file
by doiggl＠velocitynet.com.au 25 Aug '09

25 Aug '09

Hello, I am trying to compile the bugzilla 3.4.1x series The last compile attempt shows these errors. warning: group apache does not exist - using root ... running 01-check-debuginfo ... testing for empty debuginfo packages ... running 02-check-gcc-output ... testing for serious compiler warnings (using /usr/lib/build/checks-data/check_gcc_output) (using //.build.log) ... running 03-check-binary-kernel-log ... running 04-check-filelist ... checking filelist bugzilla-doc-build-3.4.1-24.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs bugzilla-doc-3.4.1-24.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs bugzilla: "/etc/httpd/conf.d/bugzilla.conf" is not allowed anymore in SuSE Linux. bugzilla-3.4.1-24.1.noarch.rpm: directories not owned by a package: - /etc/httpd - /etc/httpd/conf.d - /usr/share/bugzilla/extensions - /usr/share/bugzilla/lib System halted. So far I added in to the specfile 1. Fix warning 'warning: group apache does not exist - using root' BuildRequires: pwdutils , apache2-devel Requires: apache2 %{apache_mmn} %pre id apache >/dev/null 2>&1 if [ $? -ne 0 ]; then /usr/sbin/groupadd apache /usr/sbin/useradd -r -d %{_libdir}/%{name} -c "apache id" apache fi 2. set ownership as directories not owned by a package /usr/share/bugzilla/extensions /usr/share/bugzilla/lib /usr/share/bugzilla/docs Set to in %files section. Question: Is this the correct syntax to use ? %{buildroot}/usr/share/bugzilla/extensions %{buildroot}/usr/share/bugzilla/lib %{buildroot}/usr/share/bugzilla/docs 3. What should be done with these entries as they are directories not owned by a package ? - /etc/httpd - /etc/httpd/conf.d 4. How can this line be fixed, where should the file be moved to ? bugzilla: "/etc/httpd/conf.d/bugzilla.conf" is not allowed anymore in SuSE Linux Specfile -> https://build.opensuse.org/package/view_file?file=bugzilla.spec&package=Bug… Last log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=Bugzi… Any help appreciated. Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 8

[opensuse-packaging] new package: python-psycopg2
by Jon Nelson 25 Aug '09

25 Aug '09

I have in my home:jnelson-suse project a ready-to-go package: python-psycopg2 I'd like to get it in to Factory, but the first step is to use submitreq. I'm not sure which devel project to submit it to, however, therefore I would like some suggestions, please! -- Jon -- 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] Status update on Action Item: Screencast about the collaboration features of the BS
by Andreas Jaeger 24 Aug '09

24 Aug '09

Quite some time ago during one of the openSUSE project meetings, an AI was created to do a screencast about the collaboration features of the BuildService (https://bugzilla.novell.com/show_bug.cgi?id=397053). Those people that wanted to do it, did not have time - and I have not found any other volunteer. So, I've marked this now as WONTFIX - but on the other hand, this is something that I still think makes sense. We do need good documentation on how to build packages together and get them into factory. If anybody is interested to work on such documentation, I would appreciate it and I'll promise to review anything and get questions answered. Anybody interested? Andreas -- Andreas Jaeger, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 3

[opensuse-packaging] spec-cleaner script
by Vincent Untz 21 Aug '09

21 Aug '09

Hi all, I wrote a spec-cleaner script yesterday, with the goal to, hrm, well, clean spec files ;-) My main goal was mainly to have something that I could use to make it easier to review the moblin packages, but I think it can be useful for other people. You can find it at http://gitorious.org/opensuse/spec-cleaner It's certainly broken in many interesting ways, but for packages that are not too complex, it should work relatively well. Note that it uses some "spec style" that is close to what we use in the GNOME team. So feel free to play with it and report any issue you find! 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

2 3

[opensuse-packaging] Packages that need a new maintainer
by Stefan Seyfried 21 Aug '09

21 Aug '09

Hi, some of my packages are urgently in need o fa loving hand. Some already have found a new home, but those probably also can benefit from a helpful co-maintainer. Some are not very useful IMHO and good candidates for dropping, but maybe someone thinks differently and wants to maintain them. Here we go: Package | drop? |Notes -------------|----------|------------------------------------------------ acpid | probably | low maintenance effort brlemu | no | very low effort comgt | yes | not really useful anymore cpufrequtils | yes | not really needed libdaemon | no | ifplugd needs this. low effort ifplugd | no | network without NM needs this, low effort kqemu-kmp | yes | everybody has VT capable processors anyway ;) laptop-mode-tools | no | leafnode | yes | anybody using this? not me. Low effort, though libebml | yes | needed by mkvtoolnix libmatroska | yes | needed by mkvtoolnix mkvtoolnix | yes | easy to maintain, but I don't use it libsynaptics | yes libx86 | no | needed by suspend and vbetool mailsync | yes | anybody using this? ozerocdoff | yes | the kernel now should do this AFAIK pm-utils | no | need some amount of love to sync with upstream radeontool | yes | nobody should use it anyway rovclock | yes | see radeontool suspend | no | needed for s2ram, s2disk tuxcursors | yes | but I'll keep them in my home project ;) umtsmon | no | should be obsoleted by NM since years usb_modeswitch | yes | see ozerocdoff vbetool | yes | see radeontool Those have already found new maintainers, but surely could benefit from active co-maintainership: (maintained by Vladimir Botka, vbotka): bluez | no | active upstream, but easy to maintain bluez-firmware | no | see bluez bluez-hcidump | no | see bluez-firmware (maintained by Matthias Hopf, mopf) lablgtk2 | no | needed by unison, needs some packaging cleanup unison | no | useful, not too much effort Thanks, seife -- Stefan Seyfried R&D Preload Department | "Any ideas, John?" SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out." This footer brought to you by insane German lawmakers: 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

5 14

[opensuse-packaging] Development of .spec files
by doiggl＠velocitynet.com.au 21 Aug '09

21 Aug '09

Hello, Would this tool assist people on the creation of .spec files ?. http://wiki.eclipse.org/Linux_Tools_Project/SpecfileEditor/User_Guide The Specfile Editor plug-in provides a wizard for creating new .spec files too. Cheers Glenn -- 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] Packagers Section in Weekly News
by Sascha 'saigkill' Manns 20 Aug '09

20 Aug '09

Hello Mates, today i got an interesting Idea in our Weekly News Survey. An User asks for an own Packaging Section. He mean that that is an place for Packagers to announce fixed Packages (with an Bugzilla Reference). So the Weekly News Format is maybe: * Bugzilla-Number and Summary * Package and Version * Date and Packager * Free Text: What is changed. (Short Issue). Exists interesting about that Idea? Would Packager like to announce through the Weekly News? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 5

[opensuse-packaging] need help with .spec file
by doiggl＠velocitynet.com.au 19 Aug '09

19 Aug '09

Hello, I am interested in getting the following package into the opensuse build service (obs). It is called Cricket. Home page: http://cricket.sourceforge.net/ So far I have started to create a project, extracted the files and uploaded them. Currently the build fails. Can someone have a look at the cricket.spec for me and let me know what needs changing/adding/removing please. Project -> https://build.opensuse.org/package/show?package=cricket&project=home%3Adoig… Specfile -> https://api.opensuse.org/source/home:doiggl/cricket/cricket.spec Last Logfile -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=crick… Any assistance welcome Cheers Glenn -- 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] Automatic Dependencies of libraries
by Dominique Leuenberger 19 Aug '09

19 Aug '09

Hi everybody, some mails just earlier made me check some of my packages (vlc from the vlc repo). I've seen one thing that puzzles me a bit and which I consider a source for possible problems at this moment. Just some simple output to 'show' my case: dle3ams@3120-2914:/usr/lib64/vlc/access> ldd libvcdx_plugin.so | grep iso9660 libiso9660.so.7 => /usr/lib64/libiso9660.so.7 (0x00007f5bf6709000) dle3ams@3120-2914:/usr/lib64/vlc/access> rpm -qf libvcdx_plugin.so vlc-noX-1.0.1-2.1 dle3ams@3120-2914:/usr/lib64/vlc/access> rpm -q --requires vlc-noX | grep iso9660 dle3ams@3120-2914:/usr/lib64/vlc/access> So in human words: the package vlc-noX contains a libvcdx access plugin which itself depends on libiso9660.so.7. The package vlc-noX OTOH does not have this requirement in it's table. So if somebody installs this package, there is at least this dependency not being pulled in automatically. How can this happen and even more important: how can we avoid it? (well I see one option, but that's rather surprising to me: the same file also depends on libvcdinfo.so.0, which in turn itself has a dependency on libiso9660.so.7. Is this already enough to consider not to list this dependency? This in return would break if there was any other implementation of libvcdinfo.so.0 that would not depend on libiso9660.so.7 (statically linked or whatever the cause would be). At the moment I'm just puzzled... and I'm eager to hear explanations that are able to take away my fear of things like this breaking around us. Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 9

[opensuse-packaging] Is Xvid allowed in factory?
by Dave Plater 18 Aug '09

18 Aug '09

Hi, I'm packaging blender-2.49a as an upgrade for eventual submission to factory. The original source package contained xvidcore and I was advised to remove it. I am surprised as it contained a gnu v2 license and http://www.xvid.org claims it is an open source alternative to mpeg-4. Further googling finds this statement " /XviD/ is an ISO MPEG-4 compliant video codec." but brings up no trace of legal battles or such. I have honored the instruction to remove it but I just wondered if anyone knows why? Regards Dave P -- 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] Communication problem within packagers
by Sebastian Siebert 18 Aug '09

18 Aug '09

Hello, At first I'm a maintainer of PokerTH for packaging on openSUSE systems. I want to discuss with you a simple problem. Unfortunately I see a problem with a bad consultation between you and me as packager with dependet package in OBS. In my case the package PokerTH needs boost package. Any time the boost package was updated from 1.38 to 1.39. The Upstream from PokerTH know about a established problem in boost 1.39, so the new library let crash the PokerTH-Server. For my case I have to consult the boost packager for patching the boost package. The patching is a least problem. The biggest problem is the nonconsultation with all of packager of dependet packages before any update of the dependet packages. The maintainer of package (e.g. boost) is completely blind to me as packager (PokerTH), but backwards I know which package depend on other sub-packages. This communication order isn't a problem e.g.: Package PokerTH -> Package boost -> Package glibc Package Wesnoth -> Package boost -> Package glibc In this case all packages are completely blind afterwards e.g.: Package glibc -> Package boost -> Package PokerTH Package glibc -> Package boost -> Package Wesnoth This example isn't only for boost, but also other dependet packages. I think, all other packagers have the same problem. On this note we need a simple communication platform for packager like Wiki-pages or something like that. On this platform every packager see which package depends with other package and can easily consulte the other packager or inform of a upcoming update of sub-package. In this case we have a chance to discuss about potential bugs, incompatiblity and so on. I wish more communication with packager from dependet packages. What do you think about this situation? How we can change this situation? Regards, Sebastian -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 6

[opensuse-packaging] More cyclic dependencies ...
by Jan-Simon Möller 17 Aug '09

17 Aug '09

Hi! cannadic: it buildrequires canna, which requires cannadic emacs: buildrequires m17n-lib-devel, this buildrequires anthy-devel which buildrequires emacs-x11 xemacs-package: BuildRequires xemacs-el, but this requires xemacs-package-el and nothing provides xemacs-packages needed by xemacs libgnome and gnome-vfs2 <-> desktop-file-utils Best, Jan-Simon -- 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] server:database target of PHP packages will be removed
by Cristian Rodríguez 16 Aug '09

16 Aug '09

Hi: All PHP packages built against the server:database repository will be removed in a couple of hours, the reason for this is that PHP will no longer use mysql libraries, but a native driver called mysqlnd. You can read what mysqlnd is about at the following URL: http://forge.mysql.com/wiki/PHP_MYSQLND server_database_apache_* users should use server_apache_* repositories server_database_ users should use standard repositories. If you find any problem, please open a bug report. -- 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] Bootstrap broken, cyclic dependencies in factory
by Jan-Simon Möller 13 Aug '09

13 Aug '09

Hi ! I've discovered bootstrap-cycles in Factory 1) ConsoleKit buildrequire polkit which requires ConsoleKit 2) libffi buildrequires gtk2-devel which buildrequires pango which buildrequires gobject-introspection which buildrequires libffi 3) possibly also: ConsoleKit <-> PolicyKit Can we get these resolved ? Best, Jan-Simon -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 5

[opensuse-packaging] Reminder: milestone6 next week
by Stephan Kulow 12 Aug '09

12 Aug '09

Hi, Just reminding everyone that next week is one of the more important releases: milestone6 aka "all packages have their final version" milestone. Also next monday is crypto freeze, so please don't act suprised if we reject your packages. To make sure we can release M6 really next week, I won't check packages next week that are risky or trigger a lot of packages, so please make friday for such stuff. And remember, that M6 is not the end of 11.2 development, so don't rush things in that won't work, but talk to me about a delay. I'm really a nice guy when people are nice to me ;) Greetings, Stephan -- 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] python modules as noarch - for real this time
by Jan Matejek 12 Aug '09

12 Aug '09

Fellow python packagers, Now it is time to review your packages and find out whether they can be built noarch. (hint: if you see "no-binary" warning in rpmlint output, you can switch to noarch) I'm currently going through d:l:py repository and switching as necessary, but not everything pythonic is in there, and sometimes i'm not sure whether the package needs to be submitted to factory or not. If you need to maintain compatibility with older distros, you can use this expression i've devised: %if %{?suse_version: %{suse_version} > 1110} %{!?suse_version:1} BuildArch: noarch %endif in earthspeak: IF (suse_version is defined AND bigger than 1110) OR (suse_version is undefined) THEN build noarch (both mandriva and fedora seem to have python packages noarch'd) if you keep your own filelists and need the new macros, just add an %else branch with the definitions you need: %if %{?suse_version: %{suse_version} > 1110} %{!?suse_version:1} BuildArch: noarch %else %{!?python_sitelib: %global python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")} %{!?python_sitearch: %global python_sitearch %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib(True)")} %endif as mentioned in the old thread, it might happen that we define those macros in project configs. but maybe not. with kind regards m. -- 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] adding with sed?
by Sascha 'saigkill' Manns 12 Aug '09

12 Aug '09

Hello Mates, i would like to add this in the End of libs/toolkit/objects/tkSettings.cpp: if (QDir("/usr/lib64/qt4/plugins").exists()) d->m_Enum_Path.insert( QtPlugInsPath,"/usr/lib64/qt4/plugins" ) ); else if (QDir("/usr/lib/qt4/plugins").exists()) d->m_Enum_Path.insert( QtPlugInsPath,"/usr/lib/qt4/plugins" ) ); Can i do this with sed? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

Re: [opensuse-packaging] New packages for factory
by Stephan Kulow 12 Aug '09

12 Aug '09

Am Montag 10 August 2009 schrieb Andrew Beekhof: > Since you seem to be the contact person then, can you please give me > an update for the two packages I submitted? There are no problems with them. I don't plan to post daily updates for all submitted packages, if there is a problem I'll notify the packager. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

17 38

[opensuse-packaging] python modules as noarch
by Jan Matejek 11 Aug '09

11 Aug '09

Fellow python packagers, here's something i've been working on during and post-hackweek, and that is adopting some of Fedora's modifications so that we can build pure python modules as noarch. At the moment, this is enabled in OBS project devel:languages:python:Factory (and the corresponding "bleeding_edge_python" repositories in devel:languages:python) and used successfully in python-setuptools package. I'll be submitting to Factory shortly and i'd love to have this feature in 11.2. But be aware, this might (and will) break things. == Short how-to == is now in Python Packaging guidelines on the wiki: http://en.opensuse.org/Packaging/Python#Noarch_modules Please review your python modules. In many cases, it's enough to put "BuildArch: noarch" into the spec file. (Of course, don't do that now. Once the modified python is accepted into Factory, i'll post another mail.) == Technical details == The modified python now keeps "purelib" at /usr/lib/python2.6, and "platlib" at /usr/lib(64)/python2.6. So this modification is only meaningful on 64bits anyway, 32bits are not affected at all. In addition to this, /usr/lib/python2.6{,/site-packages} is now created and owned by python-base, regardless of platform, and added to python's search path automagically. Platform-dependent search path comes up first, so in case you installed the 32bit and 64bit versions of the same C module, the 64bit version is found and used first. == Troubleshooting / Possible breakage == 32bit side is completely unaffected, all the paths are the same. Platform-dependent modules are not affected too. They still install everything into /usr/lib64 on 64bits. So let's discuss pure python modules on 64bits, shall we? Packages using --record-rpm for keeping filelist should be (and are) working fine with the new python. They will just install into /usr/lib on all platforms. If not changed to noarch, it will make installing 32bit and 64bit versions alongside each other impossible - but on the other hand, you don't need to do it anyway. Packages keeping their own filelists in spec files will break - distutils/setuptools will install into purelib directory, but %py_sitelib macro is pointing into platlib. Such packages need to be changed - either by using --record-rpm, or if that is not possible, using the new macros adopted from Fedora. %python_sitelib points to /usr/lib/python2.6/site-packages %python_sitearch is /usr/lib64/python2.6/site-packages (same thing as %py_sitelib, actually). I'm not aware of any other possible problems besides the file list issue. (apart from the obvious "there's no guarantee that byte-compiled files will stay platform-independent") regards m. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 14

[opensuse-packaging] libatlas3
by Sascha 'saigkill' Manns 11 Aug '09

11 Aug '09

Project: home:saigkill Package: libatlas3 Hello Mates, maybe anyone can help me. ATM the build are broken, but i couldn't find an Errormessage in the BuildLog. Has anyone an Idea? ----cut--- STAGE 2-1-5: GEMV TUNE make -f Makefile INSTALL_LOG/dMVRES pre=d 2>&1 | ./xatlas_tee INSTALL_LOG/dMVTUNE.LOG gemvN : chose routine 3:ATL_gemvN_1x1_1a.c written by R. Clint Whaley Yunroll=32, Xunroll=1, using 100 percent of L1 Performance = 621.65 ( 8.03 of copy matmul, 26.91 of clock) gemvT : chose routine 105:ATL_gemvT_2x16_1.c written by R. Clint Whaley Yunroll=2, Xunroll=16, using 100 percent of L1 Performance = 569.85 ( 7.36 of copy matmul, 24.67 of clock) STAGE 2-1-6: GER TUNE make -f Makefile INSTALL_LOG/dR1SUMM pre=d 2>&1 | ./xatlas_tee INSTALL_LOG/dR1TUNE.LOG make[1]: *** [build] Error 255 make[1]: Leaving directory `/usr/src/packages/BUILD/ATLAS/x86_64_base' make: *** [build] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.32621 (%build) ---cut--- -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- 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] RFC: Banning system library paths from .pc files
by Philipp Thomas 11 Aug '09

11 Aug '09

https://bugzilla.novell.com/show_bug.cgi?id=529921 shows why encoding system library paths like /usr/lib and /usr/lib64 in pkgconfig files is a very bad idea indeed. I'd propose to add a brp script that checks for -L%{libdir} in .pc files and fails the package if found. That way maintainers of a package that comes with .pc files would be forced to fix their packages. I'd even volunteer to write said brp script. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

7 9

[opensuse-packaging] setuid
by Philippe Makowski 08 Aug '09

08 Aug '09

Hi, how can I avoid this : E: permissions-file-setuid-bit (Badness: 10000) I have to put (06550) on a file, these is correct setting for the program -- 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] Question about Preload
by Sascha 'saigkill' Manns 07 Aug '09

07 Aug '09

Hello Mates, i try to make Preload Rules for my Program. I've checked http://en.opensuse.org/Preload but it is not clear for me. What is the right Way? * prepare_preload -s -p FreeMedForms * strace FreeMedforms | prepare_preload -s -p or another Way? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com

2 3

[opensuse-packaging] Using other repos without rebuilding them
by Hans-Peter Jansen 07 Aug '09

07 Aug '09

Hi, given that the build system is "under fire" ATM(*), I'm looking for a way to build - say 11.1 packages, but with Qt from KDE:Qt - without rebuilding Qt. Sure I can link them, but that would rebuild them, and would occupy disk space for all those chunky 111 MB qt archives needlessly. This feature would union the 11.1 and KDE:Qt packages and give the build target a new name. Is anything like this available? Thanks, Pete (*): How many kernels do you build today? -- 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] package build in faild state, although rpms build successfully
by Hans-Peter Jansen 07 Aug '09

07 Aug '09

Hi, I've build python-qt4 in BS (again), and now I found them in failed state although the build was successful, and rpms are generated. The only issue, rpmlint complains about is: python-qt4-devel-4.5.4-43.1.i586.rpm: directories not owned by a package: - /usr/share/qt4/qsci - /usr/share/qt4/qsci/api - /usr/share/qt4/qsci/api/python Should I %dir those? These directories are usually owned by qscintilla, but I refrained from pulling qscintilla as another build dependency (just for it's existence), should I? Instead, I'm using python-qt4's configure.py switch --qsci-api to always install the api file, not only if qscintilla is found. You can look yourself: home:frispete:branches:KDE:Qt home:frispete:branches:KDE:KDE4:Factory:Desktop Could somebody give me an advise, what's wrong here? Thanks, Pete -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 6

[opensuse-packaging] New packages for factory
by Stephan Kulow 05 Aug '09

05 Aug '09

Hi, I would like to point out something that seems not obvious to everyone: Everyone can maintain packages in factory now There is no limitation anymore on who can maintain packages, _BUT_: - the package has to be submitted and reviewed into an _existant_ devel project - it has to build successfully against factory - the devel project has set a bugowner and maintainer for the package - preferably someone else from the devel project submits it to factory, but this is not a strict requirement - the submitrequest contains a note with informations about the package. Preferably you introduce the package to a mailing list (either topic or opensuse-factory) and point to that introduction in your submitrequest. The information we need are things like this: - who is the bugowner (has to be set in the package)? - how long has it been around? - how well has it been tested? - what is the upstream project? - does it have a track record of security issues? - what is the purpose of having it in the distribution? - what are its users? - what is the license (has to be set in the package)? The main purpose of requiring this informations in the submitrequest is that you think about such things before you write a script that dumps all of freshmeat into factory. I don't want to stop anyone from maintaining a package in our distribution, but I want every package to be maintained, not to be packaged - I hope you understand the difference. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 10

[opensuse-packaging] unstripped binary warning
by Tony Jones 03 Aug '09

03 Aug '09

Can anyone explain why I'm getting this warning in devel:tools/perf perf.i586: W: unstripped-binary-or-object /usr/bin/perf Log: https://build.opensuse.org/package/live_build_log?arch=i586&package=perf&pr… I'm obeying RPM_OPT_FLAGS for the build so no -g (confirmed with V=1) and debuginfo generation is disabled for this package. Tony -- 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] Source Services 0.0.1, no more writing SPEC files ?
by Adrian Schröter 03 Aug '09

03 Aug '09

Just a heads up ... and a call for help of course ;) http://lizards.opensuse.org/2009/08/03/source-services-001-no-more-writing- spec-files/ I would be really happy if packagers with dedicated areas, like perl moduls, java packages and so on join the attempt to write spec file code generators. As you can read there is some groundwork, like mapping link libraries to package names which can be reused. thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] Doc files and shared library packaging (Re: /mounts/work_src_done/STABLE/libwebkit not checked in)
by Vincent Untz 03 Aug '09

03 Aug '09

Hi, Sending this to opensuse-packaging because I'm not sure about the policy... Le vendredi 31 juillet 2009, à 20:06 +0200, lrupp(a)suse.de a écrit : > Script 'mail_helper' called by lrupp > > Hi vuntz(a)novell.com, > /mounts/work_src_done/STABLE/libwebkit was not checked in by lrupp for the following reasons: > > Packaging documentation in library packages is not allowed: > http://en.opensuse.org/Packaging/Shared_Library_Packaging_Policy#Package_Co… (note that the doc files in question are only license files + NEWS, not API documentation, or "how to use this library" documentation) I made the change, but I consider the policy broken here: if libwebkit11 is LGPLv2 and libwebkit12 is LGPLv3, then I can only have one libwebkit-devel, and therefore one of those two packages won't have the right license installed. Can someone clarify if I'm right or wrong, and if we need to adapt a bit the policy? :-) Thanks, 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

3 2

[opensuse-packaging] freemedforms
by Sascha 'saigkill' Manns 02 Aug '09

02 Aug '09

Hello Mates, my build for freemedforms failed with: ---cut--- objects/tkGlobal.cpp:97: error: no matching function for call to 'QString::arg()' /usr/include/QtCore/qstring.h:133: note: candidates are: QString QString::arg(qlonglong, int, int, const QChar&) const /usr/include/QtCore/qstring.h:135: note: QString QString::arg(qulonglong, int, int, const QChar&) const /usr/include/QtCore/qstring.h:733: note: QString QString::arg(long int, int, int, const QChar&) const /usr/include/QtCore/qstring.h:735: note: QString QString::arg(ulong, int, int, const QChar&) const /usr/include/QtCore/qstring.h:729: note: QString QString::arg(int, int, int, const QChar&) const /usr/include/QtCore/qstring.h:731: note: QString QString::arg(uint, int, int, const QChar&) const /usr/include/QtCore/qstring.h:737: note: QString QString::arg(short int, int, int, const QChar&) const /usr/include/QtCore/qstring.h:739: note: QString QString::arg(ushort, int, int, const QChar&) const /usr/include/QtCore/qstring.h:149: note: QString QString::arg(double, int, char, int, const QChar&) const /usr/include/QtCore/qstring.h:151: note: QString QString::arg(char, int, const QChar&) const /usr/include/QtCore/qstring.h:153: note: QString QString::arg(QChar, int, const QChar&) const /usr/include/QtCore/qstring.h:155: note: QString QString::arg(const QString&, int, const QChar&) const /usr/include/QtCore/qstring.h:741: note: QString QString::arg(const QString&, const QString&) const /usr/include/QtCore/qstring.h:743: note: QString QString::arg(const QString&, const QString&, const QString&) const /usr/include/QtCore/qstring.h:745: note: QString QString::arg(const QString&, const QString&, const QString&, const QString&) const /usr/include/QtCore/qstring.h:748: note: QString QString::arg(const QString&, const QString&, const QString&, const QString&, const QString&) const /usr/include/QtCore/qstring.h:751: note: QString QString::arg(const QString&, const QString&, const QString&, const QString&, const QString&, const QString&) const /usr/include/QtCore/qstring.h:754: note: QString QString::arg(const QString&, const QString&, const QString&, const QString&, const QString&, const QString&, const QString&) const /usr/include/QtCore/qstring.h:758: note: QString QString::arg(const QString&, const QString&, const QString&, const QString&, const QString&, const QString&, const QString&, const QString&) const /usr/include/QtCore/qstring.h:762: note: QString QString::arg(const QString&, const QString&, const QString&, const QString&, const QString&, const QString&, const QString&, const QString&, const QString&) const make[1]: *** [../../build/toolkit/.obj/unix/tkGlobal.o] Error 1 make[1]: Leaving directory `/usr/src/packages/BUILD/freemedforms-read- only/libs/toolkit' make: *** [sub-libs-toolkit-make_default-ordered] Error 2 ---cut--- What can i do? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com

2 2

[opensuse-packaging] Question about spec
by Sascha 'saigkill' Manns 01 Aug '09

01 Aug '09

Hello Mates, short Question: What is the differemce between: * make * %__make * %make? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com

2 1

[opensuse-packaging] What happens with packages that depend on packman or videolan packages?
by Dave Plater 01 Aug '09

01 Aug '09

Hi, as a learning exercise I am trying to package blender-2.49a for factory (see https://bugzilla.novell.com/show_bug.cgi?id=525298 ) and my first obstacle is a dependency on ffmpeg which is a packman / videolan package. What do I do in this case? Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 5