openSUSE Packaging December 2007

packaging@lists.opensuse.org

29 participants
19 discussions

[opensuse-packaging] problem with spec file for kdepim3

by Rajko M.

I tried to build source package for kdepim and rpmbuild complained on missing dependencies. # rpmbuild -bs kdepim3.spec error: Failed build dependencies: pilot-link-devel is needed by kdepim3-3.5.7.enterprise.0.20070904.708012-9.i586 gpgme-devel is needed by kdepim3-3.5.7.enterprise.0.20070904.708012-9.i586 # zypper in pilot-link-devel gpgme-devel package 'pilot-link-devel' not found package 'gpgme-devel' not found I found replacements using YaST search for what provides them and installed them. After that source package was built without complains. # rpm -q --whatprovides pilot-link-devel gpgme-devel libpisock-devel-0.12.2-26 libgpgme-devel-1.1.5-31 I changed kdepim3.spec replacing nonexistant files with above 2. This is the 'diff -u' output: --- kdepim3.spec 2007-09-25 16:59:15.000000000 -0500 +++ kdepim3.spec-new 2007-12-31 14:51:35.000000000 -0600 @@ -18,10 +18,10 @@ BuildRequires: gnokii-devel %endif %if %suse_version > 1010 -BuildRequires: libopensync-devel pilot-link-devel +BuildRequires: libopensync-devel libpisock-devel %endif %if %suse_version > 1000 -BuildRequires: gpgme-devel +BuildRequires: libgpgme-devel %else BuildRequires: gpgme libgpg-error-devel %endif I hope this was correct way to change spec file. -- Regards, Rajko --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 1 month

[opensuse-packaging] Packaging of efltk

by Vincenzo Barranco

Hi, I've to do the rpms of ede for X11:windowmanagers and I'm building on my home project (home:barravince112) I'm doing some build tests. During the building the obs said in the window: Installing shared libraries... cp: cannot create regular file `/usr/local/lib/libefltk.so.2.0': Permission denied make[1]: *** [install_shared] Error 1 make[1]: Leaving directory `/usr/src/packages/BUILD/efltk-2.0.7/src' make: *** [install] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.15095 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.15095 (%build) mount: can't find / in /etc/fstab or /etc/mtab md: stopping all md devices. xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping System halted. What can it be? I've another question: why in the x86_64 package obs don't find the package gcc42-c++ ? Best Regards Vincenzo --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

[opensuse-packaging] Publishing to non-oss repository?

by Jasem Mutlaq

Hello, After the build service, what's the procedure to submit and publish the packages on openSUSE official non-oss repository? Anyone specific to contact? Regards, Jasem --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

[opensuse-packaging] Version Update for Webproxy: Privoxy, can't build a source-rpm myself

by Michael Foerster

Hello, dear maintainers For the Webproxy: Privoxy there's been a 3.0.7-BETA release. My trouble with it is: I'm simply not able to make an working Source-RPM out of it. SourceRpms I can handle (compile and install). My Question is: Could please somebody of the more knowlegeable make an Source-RPM out of it, and make it available on opensuse.org? (I'll have to test it on 'older' SuSE-Dists too, so the SRPM is the most needed.) Info: no easy change from 3.0.6 to 3.0.7! Many internals have changed and the config-files reflect this. Sources: on sourceforge.net Files-Listing: * http://sourceforge.net/project/showfiles.php?group_id=11118 Tar-Ball(1.8MB): * http://downloads.sourceforge.net/ijbswa/privoxy-3.0.7-beta-src.tar.gz Thanks -- Giving up HOPE is giving up LIFE E-Mail: foerstermichael(a)gmx.de or: foerster(a)lisas.de . Logical: A bus station is where a bus stops. A train station is where train stops. On my desk, I have a work station... ...what more can I say.........? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

[opensuse-packaging] Version Update for Webproxy: Privoxy, can't build a source-rpm myself

by Michael Foerster

Hello, dear maintainers For the Webproxy: Privoxy there's been a 3.0.7-BETA release. My trouble with it is: I'm simply not able to make an working Source-RPM out of it. SourceRpms I can handle (compile and install). My Question is: Could please somebody of the more knowlegeable make an Source-RPM out of it, and make it available on opensuse.org? (I'll have to test it on 'older' SuSE-Dists too, so the SRPM is the most needed.) Info: no easy change from 3.0.6 to 3.0.7! Many internals have changed and the config-files reflect this. Thanks. -- Logical: A bus station is where a bus stops. A train station is where train stops. On my desk, I have a work station... ...what more can I say.........? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

[opensuse-packaging] package not name after its SONAME

by Michael Skibbe

Hi, i want to package libeXosip2 but i get following error message and i have no clue how to fix this problem: libeXosip2.i586: E: shlib-policy-name-error (Badness: 10000) libeXosip2-4 Your package contains a single shared library but is not named after its SONAME. the soname is: SONAME libeXosip2.so.4 i named the package libeXosip2-4 but build give me the same error. i also named the package liblibeXosip2-4 but nothing helps. how should i call my package? greetz Michael -- Michael Skibbe <mskibbe(a)suse.de> Core Services SUSE Linux Products GmbH GF: Markus Rex Nuernberg, Germany HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

[opensuse-packaging] Automatically generate a file list for an rpm - from a known good directory hierarchy

by Dan Stromberg

I have a 3 tar archives that I want to package up as rpm's. Actually, they're already getting packaged up as rpm's, but it's kind of a pain, because the files to include vary from one release to the next. I want to get this more automated. Wait! Before you fire off a message saying that this part shouldn't be automated, continue reading please :) The tar archives are not full of source code; they're full of binary results and shell scripts. It would be perfectly acceptable to package up every file in each of the tar archives into a distinct rpm, so long as they have the right permissions, owners, %config's, %attr's, etc. What's the sweet spot of ease vs effectiveness for automatically generating an rpm from such a tar archive? Can I stuff things like %config and %attr into the %files -f filename, or do these keywords have to go into the %files section of the spec file, beneath the %files token? I googled about this, but it's hard to get useful hits on things like "%files" and "-f". :) The search terms are too generic. Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

[opensuse-packaging] "cd" commands for generating Makefiles render them invalid

by Hans-Peter Jansen

Hi, from time to time, some of my rpmbuilds bail out during "make" run, which boil down to Makefiles created on the fly with commands containing "cd", because that echos the new path into the generated Makefile, rendering it invalid. E.g.: (excerpt from hylafax/man/Makefile.in) cman.apps/Makefile: ${DEPTH}/defs cman.apps ${MANCAPP} ${RM} -f cman.apps/Makefile (${ECHO} '#!smake'; \ ${ECHO} 'DEPTH=../..'; \ ${ECHO} '@MAKEINCLUDE@ @MAKELQUOTE@$${DEPTH}/defs@MAKERQUOTE@';\ ${ECHO} 'install:'; \ (cd cman.apps; for i in *.1; do \ f=${MANCAPPNAME}; \ ${ECHO} ' $${INSTALL} -m 444 -root $${INSTALLROOT} -F $${MAN}/$${MANAPPS} \ -idb $${PRODUCT}.man.client -src' "$$i" '-O' "$$f"; \ done); \ ${ECHO}; \ ${ECHO} 'uninstall:'; \ (cd cman.apps; for i in *.1; do \ f=${MANCAPPNAME}; \ ${ECHO} ' $${RM} -f $${MAN}/$${MANAPPS}/'"$$f"; \ done) \ )>cman.apps/Makefile Since similar sequences can be found in the other packages as well. I wonder, why I suffer from this occasionally, but most of you seemingly not. Before I start digging into the bash source, I thought, I try to get some expert advice. Does that issue rings a bell for anybody? TIA, Pete [openSUSE 10.2, bash environment tweaked, but it's still bash] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

[opensuse-packaging] available java-1_5_0-sun package for Fedora/Mandrake

by Denny Beyer

Hi guy's i have been building a java program for openSUSE within the BS and now tried to expand to Fedora/Mandrake ... but unpacking fails due to missing dependancies of java-1_5_0-sun package. A search also in projects/packages did not show any available packages. Anyone and idea how to get these? cheers, denny --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

[opensuse-packaging] Requiring library deprecated by the build system

by Karl Eichwalder

The build system wants me to stop requiring libxslt in the xmlto spec file. Because xmlto needs xsltproc and xmllint at runtime, I added /usr/bin/xsltproc and /usr/bin/xmllint as "Requires:". But the build system does not seem to honor those statements and opensp-doc fails: > config.status: executing po-directories commands > config.status: creating po/POTFILES > config.status: creating po/Makefile > + make -C docsrc > make: Entering directory `/usr/src/packages/BUILD/OpenSP-1.5.2/docsrc' > /usr/bin/xmlto man onsgmls.xml > /usr/bin/xmlto: line 366: xsltproc: command not found > make: *** [onsgmls.1] Error 1 Shall I continue requiring libxslt for now? Shall we split libxml2 and libxslt into the libraries and the tools? -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

13 years, 2 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging December 2007