openSUSE Packaging October 2009

packaging@lists.opensuse.org

46 participants
53 discussions

[opensuse-packaging] query - compiling package wflogs.

by doiggl＠velocitynet.com.au

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

12 years, 1 month

[opensuse-packaging] renaming for nagios-nrpe

by Christian

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

12 years, 2 months

[opensuse-packaging] Convert existing changelog from .spec file to .changes file

by Cristian Morales Vega

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

12 years, 6 months

[opensuse-packaging] Docuement not found

by Sascha 'saigkill' Manns

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

12 years, 6 months

[opensuse-packaging] commands to go into a .specfile

by doiggl＠velocitynet.com.au

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

12 years, 6 months

[opensuse-packaging] How can I get usable debugsource packages?

by Dave Plater

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

12 years, 6 months

Re: [opensuse-packaging] How can I get usable debugsource packages?

by Dave Plater

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

12 years, 6 months

[opensuse-packaging] BuildRequires query

by doiggl＠velocitynet.com.au

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

12 years, 6 months

[opensuse-packaging] Call for Participation: New Project - openSUSE Medical

by Sascha 'saigkill' Manns

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

12 years, 6 months

Re: [opensuse-packaging] How can I get usable debugsource packages?

by Dave Plater

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

12 years, 6 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging October 2009