October 2009 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] query - compiling package wflogs.
by doiggl＠velocitynet.com.au 07 Apr '10

07 Apr '10

Hello I am trying to compile project called wflogs. Project -> https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl Last log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=wflog… spec file -> https://build.opensuse.org/package/view_file?file=wflogs.spec&package=wflog… I have a link to another project called wfnetobjs too (no wfnetobjs rpm installed yet) Last set of wflog errors: configure: error: wfnetobjs-incdir: no directory found, use configure option error: Bad exit status from /var/tmp/rpm-tmp.w8AYXU (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.w8AYXU (%build) System halted. Can someone assist me to compile this package please. 1. I think Ive got to install wfnetobjs rpm but dont know to set that in the spec file. 2. Also I got to do the configure bit with a call like (but unsure how to set in the spec file) # ./configure --with-wfnetobjs-libdir=/usr/include/wallfire/ 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

5 13

[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] Convert existing changelog from .spec file to .changes file
by Cristian Morales Vega 05 Nov '09

05 Nov '09

Sometimes I find a package with a long changelog that has always lived directly in the .spec file. I would like to continue the changelog in a .changes file... but how should I convert all the existing entries? Thanks. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

14 22

[opensuse-packaging] Docuement not found
by Sascha 'saigkill' Manns 02 Nov '09

02 Nov '09

Hello Mates, i have the following: Source1: README.SUSE %install install -m644 %{SOURCE1} README.SUSE %doc README.SUSE. But after running the %doc Macro comes: Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.rCoBO7 + umask 022 + cd /usr/src/packages/BUILD + cd openemr-3.1.0 + DOCDIR=/usr/src/packages/BUILDROOT/openemr-3.1.0-1.x86_64/usr/share/doc/packages/openemr + export DOCDIR + rm -rf /usr/src/packages/BUILDROOT/openemr-3.1.0-1.x86_64/usr/share/doc/packages/openemr + /bin/mkdir -p /usr/src/packages/BUILDROOT/openemr-3.1.0-1.x86_64/usr/share/doc/packages/openemr + cp -pr README.SUSE /usr/src/packages/BUILDROOT/openemr-3.1.0-1.x86_64/usr/share/doc/packages/openemr cp: cannot stat `README.SUSE': No such file or directory Anyone know what is false? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] commands to go into a .specfile
by doiggl＠velocitynet.com.au 29 Oct '09

29 Oct '09

Hello, I am trying to compile the cricket from source code. I am using this a guide to try and get it going:- http://cricket.sourceforge.net/support/doc/beginner.html I need to put the following commands into the spec file 1. Setup cricket userid and group [done] %pre id cricket >/dev/null 2>&1 if [ $? -ne 0 ]; then /usr/sbin/groupadd cricket /usr/sbin/useradd -r -d %{_libdir}/%{name} -c "Cricket SNMP Monitor" cricket fi step 2. How do I unpack the cricket-1.0.5.tar.gz into the cricket account that has just been created, what commands do I use to do this ? The next steps from 2 onwards needs to go into the .specfile. Question: What section do they go under ? step 3. /bin/su - cricket step 4. /bin/ln -s cricket-1.0.5 cricket step 5. /bin/cp -rv cricket/sample-config cricket-config step 6. cd ~cricket step 7. cd cricket step 8. /bin/cp -v cricket-conf.pl.sample cricket-conf.pl Another question:- Q. How do I install the following Perl modules ?, what commands do I add to the .specfile ? You need to install the following Perl modules for Cricket to work correctly. Module From -------------------------------------------------------------------- MD5 CPAN: by-authors/id/GAAS/Digest-MD5-*.tar.gz LWP CPAN: by-authors/id/GAAS/libwww-perl-*.tar.gz DB_File CPAN: by-authors/id/PMQS/DB_File-*.tar.gz Date::Parse CPAN: by-authors/id/GBARR/TimeDate-*.tar.gz Time::HiRes CPAN: by-authors/id/DEWEG/Time-HiRes-*.tar.gz SNMP_Session http://www.switch.ch/misc/leinen/snmp/perl RRD http://ee-staff.ethz.ch/~oetiker/webtools/rrdtool Project -> https://build.opensuse.org/package/show?package=cricket-1-0-5&project=home%… Thanks for your answers and time on this Glenn. -- 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] How can I get usable debugsource packages?
by Dave Plater 28 Oct '09

28 Oct '09

Hi, I've googled and searched other package's spec files and build logs but I cant seem to get usable debugsource rpms for my home:plater rosegarden-qt4 package. I've written : <debuginfo> <enable/> </debuginfo> into my project meta but I still get empty debugsource packages : |Preparing packages for installation... rosegarden-qt4-debuginfo-10.02-60.1 rosegarden-qt4-debugsource-10.02-60.1 rosegarden-qt4-10.02-60.1 ... running 01-check-debuginfo ... testing for empty debuginfo packages ! ! rosegarden-qt4-debugsource-10.02-60.1.x86_64.rpm: no debug sources, deleting package ! rosegarden-qt4-debuginfo-10.02-60.1.x86_64.rpm: WARNING: this probably means the debug information is invalid What am I missing? Thanks Dave P Apologies for possible double posting but I have had a nightmare with emails to the list for the last couple of weeks. 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 2

Re: [opensuse-packaging] How can I get usable debugsource packages?
by Dave Plater 27 Oct '09

27 Oct '09

On 10/27/2009 02:30 PM, Andreas Jaeger wrote: > On Tuesday 27 October 2009 13:18:37 Dave Plater wrote: > >> On 10/27/2009 12:49 PM, Andreas Jaeger wrote: >> >>>> On Tuesday 27 October 2009 11:47:38 Dave Plater wrote: >>>> >>>>>> Hi, I've googled and searched other package's spec files and build >>>>>> logs but I cant seem to get usable debugsource rpms for my >>>>>> home:plater rosegarden-qt4 package. I've written : >>>>>> <debuginfo> >>>>>> <enable/> >>>>>> </debuginfo> >>>>>> >>>>>> into my project meta but I still get empty debugsource packages : >>>>>> |Preparing packages for installation... >>>>>> >>>>>> rosegarden-qt4-debuginfo-10.02-60.1 >>>>>> rosegarden-qt4-debugsource-10.02-60.1 >>>>>> rosegarden-qt4-10.02-60.1 >>>>>> ... running 01-check-debuginfo >>>>>> ... testing for empty debuginfo packages >>>>>> ! >>>>>> ! rosegarden-qt4-debugsource-10.02-60.1.x86_64.rpm: no debug sources, >>>>>> deleting package >>>>>> ! rosegarden-qt4-debuginfo-10.02-60.1.x86_64.rpm: WARNING: this >>>>>> probably means the debug information is invalid >>>>>> >>>>>> What am I missing? >>>>>> >>>> Are you using $RPM_OPT_FLAGS which includes "-g" to produce debug >>>> output? Or do you remove the debug output somewhere using "strip"? >>>> >>>> Andreas >>>> >> I saw -g mentioned in my searches but couldn't quite understand where it >> was used. I inserted my own C and CXXFLAGS in an attempt to get >> -fno-strict-aliasing flag to work but my other projects use >> $RPM_OPT_FLAGS and also build empty debugsource packages. I've changed >> back to plain $RPM_OPT_FLAGS and still no joy. >> $RPM_OPT_FLAGS expand to :- >> + export 'CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 >> -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' >> + CFLAGS='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 >> -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' >> + export 'CXXFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 >> -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' >> + CXXFLAGS='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 >> -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' >> which seems to have a -g at the end and there's no sign of strip >> anywhere in the spec file. The project is home:plater rosegarden-qt4 if >> you want to take a look. >> > Looking here: > https://build.opensuse.org/package/live_build_log?arch=x86_64&package=roseg… > qt4&project=home%3Aplater&repository=openSUSE_11.2 > > I see that it uses "-g0" which means no debuginfo. So, CXXFLAGS gets ignored > due to the make files somehow. > > Andreas > I restored my CFLAGS string again and added -g and -ggdb to the end of it and the package still had -g0 when it compiled so I appended --enable-debug to %configure in the spec file and now it builds with DEBUG and the debugsource packages aren't empty. This still doesn't explain why other packages don't build debugsource properly but I don't need them anyway. The only explanation are the lines in configure.ac for release packages that says :- ------>RELEASEFLAGS="$RELEASEFLAGS -g0 -O2 -Wall -pipe" <------>MINIMAL_CFLAGS="$MINIMAL_CFLAGS -g0 -O0" Thanks Dave P -- 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] BuildRequires query
by doiggl＠velocitynet.com.au 27 Oct '09

27 Oct '09

Hello On a package I need to ensure Apache and MySQL are installed as prerequsites. Are these items valid for a .specfile ?, if not what should the names be for Apache and MySQL. BuildRequires: Apache BuildRequires: MySQL Thanks Glenn -- 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] Call for Participation: New Project - openSUSE Medical
by Sascha 'saigkill' Manns 27 Oct '09

27 Oct '09

Abstract: I'm pleased to announce an new Subproject from openSUSE: openSUSE_Medical. This new Project tries to package more Software for doctors's practice or clinical needs. With our work we try to bridge a gap in the market. Logistic: For better logistic we have opened an new OBS Project called "medical". You can use it as Repo http://download.opensuse.org/repositories/medical/. Our new Wikisite is placed under: http://en.opensuse.org/OpenSUSE-Medical. There you find our new Mailinglist for our Project. What is to do? We try to package more Software. I've found this List [1] about Free Medical Software. we thought, that we can try to build one Software each purpose. If this is done, we can try to package more Software. But it is important to package not too much. This is an Joy- Project. What we need: First of all we need Packager. and one who updates the wikipage and make status updates. This Project is for packaging Beginners to Specialists. We have stuff for everyone. If you want to join our Team, just send a Message to: saigkill(a)opensuse.org [1] http://en.wikipedia.org/wiki/List_of_open_source_healthcare_software -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4

Re: [opensuse-packaging] How can I get usable debugsource packages?
by Dave Plater 27 Oct '09

27 Oct '09

On 10/27/2009 12:49 PM, Andreas Jaeger wrote: > > On Tuesday 27 October 2009 11:47:38 Dave Plater wrote: > > >> >> Hi, I've googled and searched other package's spec files and build logs >> >> but I cant seem to get usable debugsource rpms for my home:plater >> >> rosegarden-qt4 package. I've written : >> >> <debuginfo> >> >> <enable/> >> >> </debuginfo> >> >> >> >> into my project meta but I still get empty debugsource packages : >> >> |Preparing packages for installation... >> >> >> >> rosegarden-qt4-debuginfo-10.02-60.1 >> >> rosegarden-qt4-debugsource-10.02-60.1 >> >> rosegarden-qt4-10.02-60.1 >> >> ... running 01-check-debuginfo >> >> ... testing for empty debuginfo packages >> >> ! >> >> ! rosegarden-qt4-debugsource-10.02-60.1.x86_64.rpm: no debug sources, >> >> deleting package >> >> ! rosegarden-qt4-debuginfo-10.02-60.1.x86_64.rpm: WARNING: this probably >> >> means the debug information is invalid >> >> >> >> What am I missing? >> >> > > Are you using $RPM_OPT_FLAGS which includes "-g" to produce debug output? Or > > do you remove the debug output somewhere using "strip"? > > > > Andreas > > I saw -g mentioned in my searches but couldn't quite understand where it was used. I inserted my own C and CXXFLAGS in an attempt to get -fno-strict-aliasing flag to work but my other projects use $RPM_OPT_FLAGS and also build empty debugsource packages. I've changed back to plain $RPM_OPT_FLAGS and still no joy. $RPM_OPT_FLAGS expand to :- + export 'CFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' + CFLAGS='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' + export 'CXXFLAGS=-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' + CXXFLAGS='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g' which seems to have a -g at the end and there's no sign of strip anywhere in the spec file. The project is home:plater rosegarden-qt4 if you want to take a look. Thanks Dave P -- 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] Query about commands you can use in .spec files
by doiggl＠velocitynet.com.au 27 Oct '09

27 Oct '09

Hello I would like to learn about some of the commands you can use in .spec files. Question: Do you have a script to do the following ? 1. Download all the .spec files from the openSUSE Build Service {for all packages in all projects} to your pc. The reason I ask is so I can at least grep for the command I am looking for in those spec files and get some idea on how something is done. Thanks Glenn -- 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] RPM changelog aggregator?
by Martin Vidner 26 Oct '09

26 Oct '09

Hi, for a certain project(*) I would like to aggregate the changelogs of multiple packages, in chronological order, like for example here: http://download.opensuse.org/factory/repo/non-oss/ChangeLog Where can find a tool to do that? Ideally it should work with installed RPMs, RPMs on disk or whole repos. -- Martin Vidner, YaST developer (*) http://lists.opensuse.org/yast-devel/2009-10/msg00154.html Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 1

[opensuse-packaging] freemed: htaccess problem
by Sascha 'saigkill' Manns 25 Oct '09

25 Oct '09

Hello Mates, atm i'm packaging freemed. And i'm getting: freemed.noarch: W: htaccess-file /usr/share/freemed/data/fax/unfiled/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/lib/acl/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/scripts/fax_import/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/lib/template/default/htmlarea/plugins/SpellChecker/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/data/config/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/scripts/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/data/fax/unread/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/data/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/lib/perl/.htaccess freemed.noarch: W: htaccess-file /usr/share/freemed/img/store/.htaccess You have individual apache configuration .htaccess file(s) in your package. Replace them by a central configuration file in /etc/, according to the web application packaging policy for your distribution. Does anyone know how can to fix this? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] [gspcav1-20071224] - error: asm/semaphore.h: No such file or directory'
by doiggl＠velocitynet.com.au 22 Oct '09

22 Oct '09

Hello, In the following log I see the line '/usr/src/packages/BUILD/gspcav1-20071224/obj/debug/gspca_core.c:54:27: error: asm/semaphore.h: No such file or directory' What else is needed in the in the specfile to resolve this error and some others near the end of the log ? Am I missing anything else so this can build ? Full log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=gspca… Spec file -> https://build.opensuse.org/package/view_file?file=gspcav1-kmp.spec&package=… Project -> https://build.opensuse.org/package/show?package=gspcav1-20071224&project=ho… Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 3

[opensuse-packaging] poppler maintenance
by Vincent Untz 22 Oct '09

22 Oct '09

Hi, I'm a bit worried about the fact that poppler bugs and security issues get assigned to me. And, hrm, as far as I can tell, I'm not even marked as maintainer of the package in the build service ;-) (it's Stephan Binner) This is probably because, before the opening of factory development, the GNOME team was marked as maintainer of poppler, which is, I think, purely historical (it was probably first needed by evince). This could also be because I'm the one who updated the package lately, but I was probably just the fastest to do it... It's quite some work for me since I don't know poppler that well and there might be other people who know the code better than I do (or as well as I do). I certainly don't want to leave poppler unmaintained, and so the situation won't get worse, but having help from other people would be quite great :-) So, is there anybody else interested in becoming co-maintainer of poppler? 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

4 7

[opensuse-packaging] Looking for volunteers to fix package dependencies
by Stephan Kulow 21 Oct '09

21 Oct '09

Hi, For the ISOs I make sure there is only software on it that can be installed, but for the factory tree there is no such autocheck, so I have to check this manually from time to time. Now I got a little suprise: tons of problems. So I need people to look through the list and either file deleterequests, or bugs. Greetings, Stephan can't install antivir-gui-2.1.10.15-86.2.i586: nothing provides antivir needed by antivir-gui-2.1.10.15-86.2.i586 can't install compiz-devel-0.7.8-40.1.i586: nothing provides kdebase3-devel needed by compiz-devel-0.7.8-40.1.i586 can't install compiz-fusion-plugins-extra-devel-0.7.8-4.20.i586: package compiz-fusion-plugins-extra-devel-0.7.8-4.20.i586 requires compiz-fusion-plugins-main-devel, but none of the providers can be installed package compiz-fusion-plugins-main-devel-0.7.8-12.3.i586 requires compiz-devel, but none of the providers can be installed nothing provides kdebase3-devel needed by compiz-devel-0.7.8-40.1.i586 can't install compiz-fusion-plugins-main-devel-0.7.8-12.3.i586: package compiz-fusion-plugins-main-devel-0.7.8-12.3.i586 requires compiz-devel, but none of the providers can be installed nothing provides kdebase3-devel needed by compiz-devel-0.7.8-40.1.i586 can't install geeqie-1.0beta2.svn20090730-1.6.i586: nothing provides exiftran needed by geeqie-1.0beta2.svn20090730-1.6.i586 can't install git-arch-1.6.4.2-1.6.i586: nothing provides tla needed by git-arch-1.6.4.2-1.6.i586 can't install kdebase3-beagle-3.5.10-26.25.i586: nothing provides kdebase3-workspace = 3.5.10 needed by kdebase3-beagle-3.5.10-26.25.i586 can't install libcompizconfig-devel-0.7.8-7.2.i586: package libcompizconfig-devel-0.7.8-7.2.i586 requires compiz-devel, but none of the providers can be installed nothing provides kdebase3-devel needed by compiz-devel-0.7.8-40.1.i586 can't install obs-api-1.5-6.14.i586: nothing provides rubygem-rails = 2.0.5 needed by obs-api-1.5-6.14.i586 (we have rubygem-rails-2_3-2.3.2-2.5.i586) (we have rubygem-rails-2.3.2-1.5.noarch) can't install ocfs2-tools-1.4.1-23.30.i586: nothing provides ocfs2-kmp needed by ocfs2-tools-1.4.1-23.30.i586 can't install ocfs2-tools-devel-1.4.1-23.30.i586: package ocfs2-tools-devel-1.4.1-23.30.i586 requires ocfs2-tools = 1.4.1, but none of the providers can be installed nothing provides ocfs2-kmp needed by ocfs2-tools-1.4.1-23.30.i586 can't install ocfs2-tools-o2cb-1.4.1-23.30.i586: package ocfs2-tools-o2cb-1.4.1-23.30.i586 requires ocfs2-tools = 1.4.1, but none of the providers can be installed nothing provides ocfs2-kmp needed by ocfs2-tools-1.4.1-23.30.i586 can't install ocfs2console-1.4.1-23.30.i586: package ocfs2console-1.4.1-23.30.i586 requires ocfs2-tools = 1.4.1, but none of the providers can be installed nothing provides ocfs2-kmp needed by ocfs2-tools-1.4.1-23.30.i586 can't install phoronix-test-suite-1.8.1-1.4.i586: nothing provides php5-gtk needed by phoronix-test-suite-1.8.1-1.4.i586 can't install privoxy-doc-3.0.13.90.1-2.4.i586: nothing provides privoxy = 3.0.14 needed by privoxy-doc-3.0.13.90.1-2.4.i586 (we have privoxy-3.0.13.90.1-2.4.i586) can't install python-libbtctl-0.11.1-3.18.i586: nothing provides libbtctl4 = 0.11.1 needed by python-libbtctl-0.11.1-3.18.i586 can't install python-wxGTK-examples-2.8.10.1-1.2.i586: nothing provides python-numeric needed by python-wxGTK-examples-2.8.10.1-1.2.i586 can't install pythoncad-DS1_R36-193.2.i586: nothing provides python-numeric needed by pythoncad-DS1_R36-193.2.i586 can't install rembrand-1.2-113.1.i586: nothing provides librpm-4.4.so needed by rembrand-1.2-113.1.i586 can't install sysbench-0.4.8-99.3.i586: nothing provides mysql-shared needed by sysbench-0.4.8-99.3.i586 can't install sysbench-ctcs2-glue-0.4.8-99.3.i586: nothing provides ctcs2 >= 0.1.6 needed by sysbench-ctcs2-glue-0.4.8-99.3.i586 can't install tin-1.8.3-51.24.i586: nothing provides urlview needed by tin-1.8.3-51.24.i586 can't install vm-dump-metrics-devel-0.2-5.7.i586: nothing provides vhostmd-vm-dump-metrics* = 0.2 needed by vm-dump-metrics-devel-0.2-5.7.i586 can't install xrdp-0.4.1-33.8.i586: nothing provides xorg-x11-server-dmx needed by xrdp-0.4.1-33.8.i586 can't install excalibur-fortress-bean-1.3.1-2.38.noarch: package excalibur-fortress-bean-1.3.1-2.38.noarch requires excalibur-fortress-container-impl = 1.3.1, but none of the providers can be installed package excalibur-fortress-container-impl-1.3.1-2.38.noarch requires excalibur-sourceresolve = 2.2.1, but none of the providers can be installed nothing provides jakarta-commons-httpclient2 needed by excalibur-sourceresolve-2.2.1-2.38.noarch can't install excalibur-fortress-container-impl-1.3.1-2.38.noarch: package excalibur-fortress-container-impl-1.3.1-2.38.noarch requires excalibur-sourceresolve = 2.2.1, but none of the providers can be installed nothing provides jakarta-commons-httpclient2 needed by excalibur-sourceresolve-2.2.1-2.38.noarch can't install excalibur-fortress-examples-1.3.1-2.38.noarch: package excalibur-fortress-examples-1.3.1-2.38.noarch requires excalibur-fortress-container-impl = 1.3.1, but none of the providers can be installed package excalibur-fortress-container-impl-1.3.1-2.38.noarch requires excalibur-sourceresolve = 2.2.1, but none of the providers can be installed nothing provides jakarta-commons-httpclient2 needed by excalibur-sourceresolve-2.2.1-2.38.noarch can't install excalibur-fortress-migration-1.3.1-2.38.noarch: package excalibur-fortress-migration-1.3.1-2.38.noarch requires excalibur-fortress-container-impl = 1.3.1, but none of the providers can be installed package excalibur-fortress-container-impl-1.3.1-2.38.noarch requires excalibur-sourceresolve = 2.2.1, but none of the providers can be installed nothing provides jakarta-commons-httpclient2 needed by excalibur-sourceresolve-2.2.1-2.38.noarch can't install excalibur-fortress-platform-1.3.1-2.38.noarch: nothing provides tanukiwrapper needed by excalibur-fortress-platform-1.3.1-2.38.noarch can't install excalibur-fortress-testcase-1.3.1-2.38.noarch: package excalibur-fortress-testcase-1.3.1-2.38.noarch requires excalibur-fortress-container-impl = 1.3.1, but none of the providers can be installed package excalibur-fortress-container-impl-1.3.1-2.38.noarch requires excalibur-sourceresolve = 2.2.1, but none of the providers can be installed nothing provides jakarta-commons-httpclient2 needed by excalibur-sourceresolve-2.2.1-2.38.noarch can't install excalibur-monitor-2.2.1-2.38.noarch: package excalibur-monitor-2.2.1-2.38.noarch requires excalibur-sourceresolve = 2.2.1, but none of the providers can be installed nothing provides jakarta-commons-httpclient2 needed by excalibur-sourceresolve-2.2.1-2.38.noarch can't install excalibur-sourceresolve-2.2.1-2.38.noarch: nothing provides jakarta-commons-httpclient2 needed by excalibur-sourceresolve-2.2.1-2.38.noarch can't install excalibur-xmlutil-2.2.1-2.38.noarch: package excalibur-xmlutil-2.2.1-2.38.noarch requires excalibur-sourceresolve = 2.2.1, but none of the providers can be installed nothing provides jakarta-commons-httpclient2 needed by excalibur-sourceresolve-2.2.1-2.38.noarch can't install lesspipe-1.60-1.5.noarch: nothing provides dvi2tty needed by lesspipe-1.60-1.5.noarch can't install lucene-contrib-benchmark-2.4.1-2.32.noarch: nothing provides xml-commons-jaxp-1.3-apis needed by lucene-contrib-benchmark-2.4.1-2.32.noarch can't install mockobjects-alt-httpclient-0.09-1.6.noarch: nothing provides jakarta-commons-httpclient needed by mockobjects-alt-httpclient-0.09-1.6.noarch can't install mockobjects-httpclient-0.09-1.6.noarch: nothing provides jakarta-commons-httpclient needed by mockobjects-httpclient-0.09-1.6.noarch can't install setroubleshoot-plugins-2.0.16-2.3.noarch: nothing provides setroubleshoot-server >= 2.0.4 needed by setroubleshoot-plugins-2.0.16-2.3.noarch can't install susedoc-4.2_20090924-1.1.noarch: nothing provides mplus-fonts needed by susedoc-4.2_20090924-1.1.noarch -- 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] skrooge: QTestEventList' has no member named 'addKeyClicks'
by Sascha 'saigkill' Manns 20 Oct '09

20 Oct '09

Hello Mates, The compiling Process for skrooge goes to 84%. No he breaks with that Error, who we can see in the Subject. I've pasted the BuildLog in http://pastebin.ca/1629203. Does anyone know, how to fix it? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] New developer releases for osc, OBS and Junior Jobs
by Adrian Schröter 19 Oct '09

19 Oct '09

Hello, some updates from our OBS development front: * osc 0.123 release candidate * obs-server 1.7 Alpha 1 candidate * Updated Junior Jobs osc 0.123 RC 1 ============== There is a new osc 0.123 RC 1 package inside of the openSUSE:Tools:Unstable project. Beside some important bugfixes, it contains new support for SSL handshake library python-m2crypto. This lib is validating the server certificates now and protects you for a man-in-the-middle attack. An update is therefore recommended, but it needs the new python-m2crypto package. It builds on almost all platforms, just not yet for Ubuntu. If someone knows how to get a secure python SSL layer on Ubuntu, I would be happy about a mail, patch or submit request :) http://software.opensuse.org/search?baseproject=openSUSE%3ATools%3AUnstable… I will release this one as stable as soon as I heard enough positive feedback. Please try it and report thanks ! (downgrade to the 0.122 one from openSUSE:Tools is easy in case of problems) obs-server 1.7.0 Alpha 1 release candidate ========================================== openSUSE:Tools:Unstable contains also new packages for our OBS server itself. Biggest changes are the SAT based scheduler (which made opensuse.org so much faster) and SLP support in the init scripts. This means the workers should find the server themselfs without configuration. I hope to be able to build a appliance based on this packages soon for easier deployment. Updated Junior Jobs =================== Some updates happened in our wiki page for OBS junior jobs, since some people are even implementing some of these :) Become an OBS developer today by looking here: http://en.opensuse.org/Build_Service/Junior_Projects have fun 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

1 0

[opensuse-packaging] skrooge: QTestEventList' has no member named 'addKeyClicks'
by Sascha 'saigkill' Manns 19 Oct '09

19 Oct '09

Hello Mates, The compiling Process for skrooge goes to 84%. No he breaks with that Error, who we can see in the Subject. I've pasted the BuildLog in http://pastebin.ca/1629203. Does anyone know, how to fix it? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] skrooge: devel-file-in-non-devel-package
by Sascha 'saigkill' Manns 19 Oct '09

19 Oct '09

Hello Mates, that RPMLint error i know. But it looks, that i can't fix this error. I've pasted that into: http://pastebin.ca/1627701. Does anyone know more? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] dep for suse-release broken ?
by Christian 18 Oct '09

18 Oct '09

Hi, I tried to define dep for suse-release. It is working for any {suse_version} but SLE_10. I did not get it work. I looked into sles-release-10 spec file Provides: distribution-release Provides: %{name}-10 %{name}-10-sp1 %{name}-10-sp2 and tested them all without success. %if 0%{?sles_version} == 10 BuildRequires: distribution-release %endif buildinfo is broken... it says: expansion error: nothing provides distribution-release Is this worth for a bug ? Regards Chris -- 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] Skrooge: No %description skrooge-lang
by Dominique Leuenberger 17 Oct '09

17 Oct '09

Hi Sascha, >>> "Sascha 'saigkill' Manns" <samannsml(a)directbox.com> 10/17/09 8:48 PM >>> >Hi Mates, > >does anyone know why the Spec not respect my %description? Yes :) > http://pastebin.ca/1625585 (Specfile) A syntax error in this line (87) Obsoletes: %{name}-lang < %{version]-%{release} the version tag is not closed, as such %description is not getting defined at any point in the spec file. Hope this helps. Dominique -- 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] osc rq decline 22540 ...
by Boyd Lynn Gerber 17 Oct '09

17 Oct '09

When I looked at it, there were not any builds scheduled. I just looked again an now a couple builds have succedded. I think this rq should be re-submmited once everything has built. Not before. I wanted to make sure it was clear that at the time I reviewed the rq it did not have any builds even scheduled. That is why I rejected it. Maybe in a day or so all the build will have had a chance to build. I think there should be a policy that the project the rq is being done agains at least pass the builds on the OBS. Thanks, -- Boyd Gerber <gerberb(a)zenez.com> 801 849-0213 ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- 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] 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] Skrooge: No %description skrooge-lang
by Sascha 'saigkill' Manns 17 Oct '09

17 Oct '09

Hi Mates, does anyone know why the Spec not respect my %description? http://pastebin.ca/1625585 (Specfile) -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] *.desktop run as user
by Sascha 'saigkill' Manns 17 Oct '09

17 Oct '09

Hello Mates, i have written an *.desktop Files, and i would like to run this as root. In the KMenu i can specify an User. But how can i add this in the File directly? I have searched there: http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html But don't find the Key, Has anyone an Idea? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] Building KMP openSUSE 11.2 i586
by Matwey V. Kornilov 17 Oct '09

17 Oct '09

Hi, Adrian advised me to write here. I have the problem with building my KMP at i586 with Factory repository using OBS. Building for other platforms is successful. I checked building the rpm with opensuse 11.2 i586 livecd and It was successful. Full error message: + make -C /usr/src/linux-obj/i586/debug modules M=/usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel LDDINC=/usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/include make: Entering directory `/usr/src/linux-2.6.31.3-1-obj/i386/debug' make -C ../../../linux-2.6.31.3-1 O=/usr/src/linux-2.6.31.3-1- obj/i386/debug/. modules CC [M] /usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel/lpt.o CC [M] /usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel/rs485_irq.o make[3]: execvp: /bin/sh: Argument list too long make[3]: *** [/usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel/rs485_tools.o] Error 127 make[2]: *** [_module_/usr/src/packages/BUILD/rs485-5.1.2/obj/debug/lpt/kernel] Error 2 make[1]: *** [sub-make] Error 2 I am sure that my Makefiles are valid. The problem appears only with OBS Factory i586. -- 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] openSUSE 11.2 setup in OBS
by Adrian Schröter 17 Oct '09

17 Oct '09

Hi, (and sorry for the cross post, please answer only on one ml with me in CC) The openSUSE Build Service is now building 11.2 in the openSUSE 11.2 project. openSUSE:Factory is de-prefered atm (building only, if really nothing else is there). The build-compare stuff is disabled for now (to ensure that all packages get the new tags and that all packages have chronical build times). We will enable it again after GA (when openSUSE:11.2 project is frozen). Happy Weekend. 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

1 0

[opensuse-packaging] skrooge 0.5.2
by Sascha 'saigkill' Manns 16 Oct '09

16 Oct '09

Hello Mates, while building skrooge i'm getting an Error. -> http://pastebin.ca/1623972 Anyone know how to fix it? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] 11.2 is done, long lives 11.2
by Stephan Kulow 16 Oct '09

16 Oct '09

Hi, As you may have heard, 11.2 RC1 was released. This means, development of it has ended, from now on we will only fix bugs that we would have fixed as maintenance update too. So everything you submit to openSUSE:Factory will not automatically go into 11.2, but I will hand pick. As this has to be done with care, factory checkins will be very slow the the next weeks. And openSUSE:Factory will get a lower priority than 11.2, but if you build against the snapshot this shouldn't be a problem for you. But again: for now you submit your fixes to openSUSE:Factory and just make sure your changelog makes clear it's a bug fix and we look up the bug report to decide if we want to take the risk and for those I do not feel worth it, will end up in openSUSE:Factory only. Greetings, Stephan -- 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] Why devel projects for openSUSE:Factory?
by Andreas Jaeger 15 Oct '09

15 Oct '09

I've been asked why we have devel projects and why a package should use one. Looking around I found not directly a good answer - and only these two pages: http://en.opensuse.org/Build_Service/Concepts/Upstream_Project http://news.opensuse.org/2009/06/18/opensuse-factory-is-now-open/ Do we have anything better? If not: Anybody interested in writing something up? Andreas -- Andreas Jaeger, Program Manager openSUSE, 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

2 1

[opensuse-packaging] boinc client: shared-lib-calls-exit
by Sascha 'saigkill' Manns 13 Oct '09

13 Oct '09

Hello Mates, i'm packaging boinc client 6.6.40 and i'm getting: boinc-client.x86_64: W: shared-lib-calls-exit /usr/lib64/libboinc_graphics2.so.6.6.40 exit(a)GLIBC_2.2.5 boinc-client.x86_64: W: shared-lib-calls-exit /usr/lib64/libboinc_api.so.6.6.40 exit(a)GLIBC_2.2.5 This library package calls exit() or _exit(), probably in a non-fork() context. Doing so from a library is strongly discouraged - when a library function calls exit(), it prevents the calling program from handling the error, reporting it to the user, closing files properly, and cleaning up any state that the program has. It is preferred for the library to return an actual error code and let the calling program decide how to handle the situation Does anyone knows how to fix it? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill -- 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] cmake and %_libdir
by Cristian Morales Vega 13 Oct '09

13 Oct '09

Trying to package OpenCV 2.0 I found this line in the CMakeLists.txt file: set(CMAKE_LIB_DIRS_CONFIGCMAKE "${CMAKE_INSTALL_PREFIX}/lib") that ends specifying the libraries install dir. It should be fixed... but doesn't seems to be a standard variable in cmake to specify the libdir. The only thing I have found is this thread from 2007 (http://lists.opensuse.org/opensuse-buildservice/2007-08/msg00332.html) but as pointed by Andreas LIB_SUFFIX isn't an standard variable. Looking at the Fedora %cmake macro (https://fedoraproject.org/wiki/PackagingDrafts/cmake) this doesn't looks any better. So... two years after cmake still hasn't a way to specify the libraries install directory? I can't submit upstream a patch with a non standard variable. I'm supposed to use LIB_SUFFIX and maintain the patch forever? -- 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] Junior Jobs
by Michal Hrusecky 13 Oct '09

13 Oct '09

Hi, lately we formulated concept of openSUSE Junior Jobs[1]. Maintainers of openSUSE packages can choose some of theirs easy bugs and mark them as Junior Jobs. Then anybody from community can volunteer and fix these issues. These tasks will be easily fixable and their purpose is to let people learn how to contribute and to create some easy task so anybody can join and start participating. [1] http://en.opensuse.org/Junior_Jobs -- Michal HRUSECKY SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz

1 0

[opensuse-packaging] [python] fixing "no module named" (and packaging modules properly)
by Jan Matejek 08 Oct '09

08 Oct '09

Dear fellow packagers, since our switch to noarch-capable python, a number of bugs for arch-dependent python module packages have popped up, where some module can't be imported even though it seems to be installed properly. Root cause of those bugs is common to all of them: half of the files are installed in platform-independent /usr/lib dir, while the other half goes into /usr/lib64 (on 64bits only, of course), causing all sorts of confusion. That is Bad Style (tm). Don't do it. in short: Fix your package so that it goes either into /usr/lib (in which case it should be noarch too), or into /usr/lib64. The bug will then go away. long version: In Python, the arch-independence is on a per-module level. Either the whole module is arch-independent, then it belongs to %python_sitelib, or some of it is arch-dependent and then the whole module belongs to %python_sitearch. Historically, sitelib and sitearch were in the same directory. Now that they are separate, two classes of problems have arisen. One, many python modules depend on being installed within a single directory. Sometimes explicitly and sometimes they make the assumption in some not-really-trivial way. There is even a feature called "relative imports" that relies on the fact that a whole module is installed in a single directory. Two, sometimes modules are not installed on python search path. Python doesn't search subdirectories automatically, so modules from e.g. %python_sitearch/gtk-2.0 can't be imported, even though modules from %python_sitearch itself can. For that reason, such module often installs a file.pth pointing to its directory. When python finds something.pth on its search path, it appends all directories listed in that file to the search path. Some packages install into two different locations but use only one pth file pointing into only one of them. Why is that a problem is left as an exercise for the reader. Distutils know all this and do the right thing, unless your upstream is extremely clever and installs two separate modules (wxGTK) or beats distutils into submission (egenix-mx-base). Also, prusnak volunteered and checked all packages in d:l:py that don't use --record-rpm, and they are all OK. hope this helps regards m. -- 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] query - opensuse equavilant of elfutils-libelf, elfutils-devel, beecrypt-devel, bzip2-devel, perl-devel
by doiggl＠velocitynet.com.au 08 Oct '09

08 Oct '09

I got an expansion error for a project. nothing provides elfutils-libelf, elfutils-devel, beecrypt-devel, bzip2-devel, perl-devel Question: Is there any equivalent opensuse modules to these ones ? project -> https://build.opensuse.org/package/show?package=rpm5&project=home%3Adoiggl Thanks Glenn -- 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] What is the correct way for a maintainer to submit to factory?
by Dave Plater 08 Oct '09

08 Oct '09

Hi, I'm trying to work out if it was me or something else that caused the devel project tarball to fail to arrive in factory along with all the other files. 1) Should I disable building before making a submit request? 2) Should the link to the factory package disappear when the submit request is accepted? 3) Does the link need to be present for a new submit request? Thanks Dave P -- 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] Question about KDE >= 4.2. Building in openSUSE 11.1
by Sascha 'saigkill' Manns 07 Oct '09

07 Oct '09

Hello Mates, i have an big Problem (for me) with building skrooge for 11.1. Since the 0.5.x Tags skrooge uses Functions from KDE 4.2. So i have declared the BuildRequires libkde4 >= 4.2. But 11.1 comes without KDE 4.2. So the Build only runs only for Factory. So i have tried to Link the kdelibs4 Package to my home:saigkill Repository But that linked Package don't builds, because osc finds unpackaged Files. But it builds just for Factory. Has anyone an Idea? I'm happy for every Proposal, i have tried all my thoughts. As Attachement i'm adding the Spec. Maybe i have an Error there. -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill

1 0

[opensuse-packaging] removing gecko-sharp2
by Andrew Jorgensen 07 Oct '09

07 Oct '09

gecko-sharp2 has not been maintained in a long while and, as far as I can tell, is not required by anything that can't be compiled without it. In fact PDB seems to think that nothing requires it except a package called jscall-sharp which is supposed to be a JS-C# bridge. The maintainer of that source says it should be dropped as he's been recommending for years that people adopt the source if they actually need it. What's the process for removing a package? We should do this before 11.2 is released if possible as one of the goals for 11.2 seems to be removing xulrunner 1.9.0 and older and gecko-sharp will not likely work w/ 1.9.1. -- 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] Projekt rename: Subversion related packages now in devel:tools:scm:svn
by Dirk Müller 07 Oct '09

07 Oct '09

Hi, The subversion related packages in the buildservice project "Subversion" are now being maintained in devel:tools:scm:svn. The duplicates in devel:tools:scm will be removed as soon as the develproject changerequests are being approved by the build team. the packages have been removed from Subversion and publishing has been disabled. Please change your repo entries to the new location. The old Subversion project will be completely removed by October 16th. Thanks a lot for your understanding. Greetings, Dirk -- 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] RPM Summit Summary
by yersinia 07 Oct '09

07 Oct '09

> On Tue, Oct 6, 2009 at 6:14 PM, Pavol Rusnak <prusnak(a)suse.cz> wrote: >> >> Hi! >> >> I've written a short summary[1] about RPM Summit that was part of this >> year's openSUSE Conference. The changes are not affecting us at the >> moment, but they will, once they are implemented in upstream and we >> adopt the new RPM version in our distribution. >> > The new rpm version that you quote is http://www.rpm.org, with a bunch a opensuselocal patch - not sharp criticism,just a matter of fact. So,tell that you follow "upstream" is not so true. Other version of rpm, everyone know that exists and who is the maintainer, were not considered : there are good reasons for this, I suppose. I just hope this are technical not political reason. > > Regards > >> [1] >> http://stick.gk2.sk/blog/2009/10/rpm-summit-at-the-opensuse-conference-2009/ >> >> -- >> Best Regards / S pozdravom, >> >> Pavol RUSNAK SUSE LINUX, s.r.o >> openSUSE Boosters Team Lihovarska 1060/12 >> PGP 0xA6917144 19000 Praha 9, CR >> prusnak[at]suse.cz 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 >> > -- 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] Fwd: Ebuild of Dooble Web Browser
by Max 07 Oct '09

07 Oct '09

---------- Forwarded message ---------- From: Ian Whyman <v00d00(a)v00d00.net> Date: Wed, Oct 7, 2009 at 1:38 AM I managed to create an ebuild if anyone wants to try this. It seems to be nothing special currently but please do try it as the ebuild took a while to get right and I would be unhappy if no one used it. ebuild: http://gitweb.sabayon.org/?p=overlay.git;a=commit;h=7fd998de110ebb6d9ed6890… Can I have a cookie now?? lol Ian -- 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] Dooble Web Browser needs RPM packaging
by Max 06 Oct '09

06 Oct '09

Hello, new Web Browser Dooble http://dooble.sf.net is out Is anyone able to make a rpm Suse Build? then we can link it on the homepage Thanks for a feedback Max ---------- Forwarded message ---------- Date: Tue, Oct 6, 2009 at 8:57 PM Subject: New Armel & Ubuntu Builds SVN 874 of Dooble Web Browser https://launchpad.net/ubuntu/karmic/+source/dooble/0.0+svn874-0ubuntu1 lpia build of dooble 0.0+svn874-0ubuntu1 in ubuntu karmic RELEASE https://launchpad.net/ubuntu/+source/dooble/0.0+svn874-0ubuntu1/+build/1278… armel build of dooble 0.0+svn874-0ubuntu1 in ubuntu karmic RELEASE debhttps://launchpad.net/ubuntu/+source/dooble/0.0+svn874-0ubuntu1/+build/1…. see the releases soon on the homepage: http://dooble.sf.net -- 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] Lack of information
by Andreas Schneider 06 Oct '09

06 Oct '09

Hi, what I really miss sometimes is the information which toolkit or desktop environment an application is for. Qt, GTK, CLI Sometimes I want to know if it is a compiled application or just a script. Binary, Python, Perl, Ruby It would be nice if such things would be in the description or some extra fields. Maybe the software portal or zypper is able to get the information from the requires. The software portal could show little icons and zypper could print it in the deatailed view. Just some wild thoughts... -- andreas

3 2

[opensuse-packaging] RPM Summit Summary
by Pavol Rusnak 06 Oct '09

06 Oct '09

Hi! I've written a short summary[1] about RPM Summit that was part of this year's openSUSE Conference. The changes are not affecting us at the moment, but they will, once they are implemented in upstream and we adopt the new RPM version in our distribution. [1] http://stick.gk2.sk/blog/2009/10/rpm-summit-at-the-opensuse-conference-2009/ -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz 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] [bwgraph] - Need help with error *** No rule to make target `install'
by doiggl＠velocitynet.com.au 06 Oct '09

06 Oct '09

Hello I'm using an existing make file in building this package. The make file is as follows it just has one line in it. all: bw The package error log shows the following: + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/bwgraph-1-2.1.x86_64 ++ dirname /usr/src/packages/BUILDROOT/bwgraph-1-2.1.x86_64 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/bwgraph-1-2.1.x86_64 + cd bwgraph + test -x ./configure + make cc bw.c -o bw + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.SC1SKd + umask 022 + cd /usr/src/packages/BUILD + cd bwgraph + make DESTDIR=/usr/src/packages/BUILDROOT/bwgraph-1-2.1.x86_64 install make: *** No rule to make target `install'. Stop. error: Bad exit status from /var/tmp/rpm-tmp.SC1SKd (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.SC1SKd (%install) System halted. - Question: What other entries do i need in the make file to do the compile ? The package has four files in total. Makefile 8 README 727 bw.c 8.5K bwbar 273 project -> https://build.opensuse.org/package/show?package=bwgraph&project=home%3Adoig… Last build log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=bwgra… spec file -> https://build.opensuse.org/package/view_file?file=bwgraph.spec&package=bwgr… Thanks for the assistance. Glenn. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 7

[opensuse-packaging] How to get a patch applied.
by doiggl＠velocitynet.com.au 06 Oct '09

06 Oct '09

Hello What needs to be altered in the .spec file so this patch gets applies properly ? Error messages listed --------------------- + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + echo 'Patch (rpm5-add-5-suffix.patch):' Patch (rpm5-add-5-suffix.patch): + /bin/cat /usr/src/packages/SOURCES/rpm5-add-5-suffix.patch + /usr/bin/patch -s -p1 --fuzz=2 3 out of 3 hunks FAILED -- saving rejects to file Makefile.am.rej 1 out of 1 hunk FAILED -- saving rejects to file popt/Makefile.am.rej 3 out of 5 hunks FAILED -- saving rejects to file rpmdb/Makefile.am.rej 1 out of 1 hunk FAILED -- saving rejects to file scripts/Makefile.am.rej 1 out of 1 hunk FAILED -- saving rejects to file file/magic/Makefile.am.rej 1 out of 1 hunk FAILED -- saving rejects to file file/magic/Makefile.in.rej error: Bad exit status from /var/tmp/rpm-tmp.djsLR1 (%prep) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.djsLR1 (%prep) System halted. specfile -> https://build.opensuse.org/package/view_file?file=rpm5.spec&package=rpm5&pr… Project -> https://build.opensuse.org/package/show?package=rpm5&project=home%3Adoiggl Last log -> https://build.opensuse.org/package/live_build_log?arch=x86_64&package=rpm5&… Thanks Glenn -- 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] skrooge: Problems with skgbankpluginwidget
by Sascha 'saigkill' Manns 05 Oct '09

05 Oct '09

Hello Mates, ATM i'm getting: In file included from /usr/src/packages/BUILD/skrooge-0.5.1/skrooge_bank/skgbankpluginwidget.h:24, from /usr/src/packages/BUILD/skrooge-0.5.1/skrooge_bank/skgbankplugin.cpp:23: /usr/src/packages/BUILD/skrooge-0.5.1/skrooge_bank/ui_skgbankpluginwidget_base.h:45: error: ISO C++ forbids declaration of 'KFilterProxySearchLine' with no type /usr/src/packages/BUILD/skrooge-0.5.1/skrooge_bank/ui_skgbankpluginwidget_base.h:45: error: expected ';' before '*' token /usr/src/packages/BUILD/skrooge-0.5.1/skrooge_bank/ui_skgbankpluginwidget_base.h: In member function 'void Ui_skgbankplugin_base::setupUi(QWidget*)': /usr/src/packages/BUILD/skrooge-0.5.1/skrooge_bank/ui_skgbankpluginwidget_base.h:107: error: 'kFilterEdit' was not declared in this scope /usr/src/packages/BUILD/skrooge-0.5.1/skrooge_bank/ui_skgbankpluginwidget_base.h:107: error: expected type-specifier before 'KFilterProxySearchLine' /usr/src/packages/BUILD/skrooge-0.5.1/skrooge_bank/ui_skgbankpluginwidget_base.h:107: error: expected `;' before 'KFilterProxySearchLine' make[2]: *** [skrooge_bank/CMakeFiles/skrooge_bank.dir/skgbankplugin.o] Error1 Anyone know what happens? -- Sincerely yours Sascha Manns openSUSE Member openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Blog: http://saigkill.wordpress.com ClaimID: http://claimid.com/saigkill

2 2

[opensuse-packaging] One step back with devel projects
by Stephan Kulow 05 Oct '09

05 Oct '09

Hi, There is one big problem with the devel projects: some just don't work as it was hoped they would. I expressed the problems before, but basically some projects are just too artificial to create any kind of group feeling for the group of packages. Fortunately some jump into the gap, but I feel we need to discuss some change here. Some of us talked about the problem briefly and the idea that formed out of it is basically this: * We create openSUSE:Factory:Devel as a pool of packages with single maintainers, maintainers can move their packages their if they do not feel they belong in any specific group. In there you only maintain your package, not the rest. * Projects have the choice to move factory packages without maintainer into it up to grab. (I don't think we should leave the TODO project around). I will be maintainer (hopefully with the help of others) of that project to be the interface for new maintainers - avoiding the current "whom to ask of these 100 maintainers" confusion. I don't feel any need to do this before 11.2, but I would like you to give me your ideas about it now so we can implement it shortly after. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

8 14

[opensuse-packaging] 'openSUSE Webclient Error' when using the 'Create package using spec file wizard'
by doiggl＠velocitynet.com.au 03 Oct '09

03 Oct '09

Things are really busy today with obs, I got 'openSUSE Webclient Error:' when using the 'Create package using spec file wizard' I tried it a few times. Regards Glenn Error Details: Errorcode: unknown Message: execution expired Exception from Webclient: Timeout::Error: execution expired Stack Trace: /usr/lib64/ruby/1.8/timeout.rb:60:in `rbuf_fill' /usr/lib64/ruby/1.8/net/protocol.rb:134:in `rbuf_fill' /usr/lib64/ruby/1.8/net/protocol.rb:116:in `readuntil' /usr/lib64/ruby/1.8/net/protocol.rb:126:in `readline' /usr/lib64/ruby/1.8/net/http.rb:2020:in `read_status_line' /usr/lib64/ruby/1.8/net/http.rb:2009:in `read_new' /usr/lib64/ruby/1.8/net/http.rb:1050:in `request' /usr/lib64/ruby/1.8/net/http.rb:772:in `get' /srv/www/vhosts/opensuse.org/common/current/lib/activexml/transport.rb:507:in `http_do' /srv/www/vhosts/opensuse.org/common/current/lib/activexml/transport.rb:346:in `find' /srv/www/vhosts/opensuse.org/common/current/lib/activexml/base.rb:69:in `find' /srv/www/vhosts/opensuse.org/webclient/releases/svn/app/controllers/package_controller.rb:203:in `wizard' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:1166:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:1166:in `perform_action_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:579:in `call_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:572:in `perform_action_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/rescue.rb:201:in `perform_action' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in `process_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:568:in `process_without_session_management_support' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/session_management.rb:130:in `process' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:389:in `process' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:149:in `handle_request' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:107:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:35:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:103:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:153:in `with_signal_handler' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:101:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:78:in `process_each_request' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:77:in `process_each_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `catch' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `process_each_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:50:in `process!' /usr/lib64/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:24:in `process!' /srv/www/vhosts/opensuse.org/webclient/current/public/dispatch.fcgi:24 -- 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] audit 2.0 packaging question
by Tony Jones 02 Oct '09

02 Oct '09

[I'm not suggesting any of this for OpenSUSE 11.2 ;-)] audit 2.0 has been released. Removal of dead/broken apis with the result that libaudit.so is now bumped to .1 A while ago it was deemed necessary for audit to be split into two spec files, audit.spec and audit-secondary.spec to move python dependancies to prevent huge build system dependancies. Not sure if this is still needed?? If not it would be nice to go back to just one spec as it makes updates a bit easier. To the more important question .... I can osc build v2.0 of audit.spec which produces libaudit.so.1 but when I try to build audit-secondary using previous as the preferred rpms the buildsystem fails to init because su, pam, others require that something provides libaudit.so.0. I have the changes checked into: https://build.opensuse.org/package/show?package=audit-secondary&project=hom… I briefly talked to Marcus on IRC about whether we needed to provide a compat library and he didn't think it was necessary as most/all users of audit-libs are suse system rpms but Adrian seemed to be of the opinion that it was essential for things to build inside the Factory buildservice. Right now my interest is just getting the above location building for test purposes. Not sure if there is an easy way? I can force load the resultant new audit-libs.rpm over an existing system for testing but I'd like to test the -secondary stuff also. Tony -- 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] enabling services while installing a package
by Stefan Schubert 02 Oct '09

02 Oct '09

Hi, we have a WebYaST plugin called "status" which will be installed via an own RPM (yast2-webservice-status). This plugin requires a running service collectd (package collectd). So how is the correct way to enable and start collectd while installing yast2-webservice-status. My first assumption was: File: yast2-webservice-status.spec: PreReq: collectd %post # # enable and start collectd # insserv -f collectd /etc/init.d/collectd start Is this the correct way, or not ? Thank you and greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- 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

2 1

[opensuse-packaging] BuildRequires rpms from other repos
by aledr 02 Oct '09

02 Oct '09

Good day! I need to provide python-protobuf (from protobuf in devel:tools:building) and python-ReportLab (dropped from openSUSE:Factory but availabe in openSUSE:Factory:Contrib) as BuildRequires for two packages in devel:languages:python. Should I just link these packages into devel:languages:python or add its entire repo under Build Repositories? Seems that first makes more sense to me. Regards. -- [ ]'s Aledr - Alexandre "OpenSource Solutions for SmallBusiness Problems" -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 7