openSUSE Packaging February 2006

packaging@lists.opensuse.org

12 participants
10 discussions

Re: [opensuse] Horde and its apps in SL 10.1

by Pascal Bleser

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christoph Thiel wrote: > On Mon, 27 Feb 2006, Leang Chumsoben wrote: > >> maybe I'm wrong but I cannot see any Horde applications (IMP, Turba...) >> on SL 10.0 CDs. I can see only Horde 3.0.5-4. What's about SL 10.1? Is >> there any plan to include those applications? > > Open your eyes ;) > > I was at least able to find those packages in the current Factory tree: > > ./suse/src/horde-3.0.9-5.src.rpm > ./suse/noarch/horde-3.0.9-5.noarch.rpm > ./suse/src/imp-4.0.4-5.src.rpm > ./suse/noarch/imp-4.0.4-5.noarch.rpm > > No, those packages aren't on the CDs/DVD. (But they might be on the DVD9, > that shipps with the retail version.) I guess that Leang meant all the other applications that plug onto the horde framework. IMP is just one of them (webmail UI), but there's also a calendaring part, one to manage notes and tasks, etc... Leang, I'm afraid there's "only" Horde and IMP shipped with SUSE Linux 10.0, but it's already a good starting point ;) If I didn't already maintain RPMs for around 700 projects, I would have said I'd have a look at it ;) Any other packager interested ? (I'll cross-forward this mail to the opensuse-packaging mailing-list as well - maybe someone over there is interested in maintaining RPMs for those Horde add-ons) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEBKSzr3NMWliFcXcRAhVgAJ43MPjjvQiomoUJUk5crtQ6feW36wCeP4Lq TX4GjUee6J3/+feEwEX099w= =N0Fv -----END PGP SIGNATURE-----

14 years, 12 months

How to make Con's kernel

by giulio alfano

Hi everyone! My "problem" is this, I have volunteered make con's kernel rpm for opensuse. I would like to know: - how to make the rpm, it's enough to apply the patch, and type make rpms in opensuse kernel dir? - how to make the srpm - how to know when new kernel are made - is there a place to put the rpm? I would like to have only one installation to make x86, x86_64 for stable and non stable version of opensuse. Suggestion on how to set up the installation? Of course I would appreciate a detailed step by step tutorial..... or a lot of least some pointer to documentation :)) Many, thanks.

14 years, 12 months

[SLE] [suse-programming-e] Problem with Digi rpmbuild --rebuild 40002347_B.src.rpm

by Boyd Lynn Gerber

Hello, I want to create a rpm for this and put it on my ftp site for others to use with SUSE Linux 10.0 retail version. I need some assistance. I may be too tired but I can not seem to figure out this problem. I am trying to get the Digi PC/Xem board working on SUSE Linux 10.0 retail version. I have done the following... 1. cd /usr/src/linux-2.6.13-15.8 2. make mrproper 3. make oldconfig Then... 4. # rpmbuild --rebuild 40002347_B.src.rpm ... + '[' /var/tmp/dgap-buildroot = / ']' + CFLAGS='-O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2' + export CFLAGS + CXXFLAGS='-O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2' + export CXXFLAGS + FFLAGS='-O2 -g -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2' + export FFLAGS + ./configure --host=i686-suse-linux --build=i686-suse-linux --target=i586-suse-linux --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info ... (cd driver; make all) make[1]: Entering directory `/usr/src/packages/BUILD/dgap-1.2/driver' make -C /lib/modules/2.6.13-15.8-smp/build SUBDIRS=$PWD modules MYPWD=/usr/src/packages/BUILD/dgap-1.2/driver make[2]: Entering directory `/usr/src/linux-2.6.13-15.8-obj/i386/smp' make -C ../../../linux-2.6.13-15.8 O=../linux-2.6.13-15.8-obj/i386/smp modules CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_driver.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_fep5.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_mgmt.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_parse.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_proc.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_trace.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_tty.o CC [M] /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.o /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:183: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:200: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:228: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:245: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:262: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:279: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:296: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:313: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:330: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:347: warning: initialization from incompatible pointer type /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c: In function ‘dgap_tty_class_init’: /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:387: error: implicit declaration of function ‘class_simple_create’ /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:387: warning: assignment makes pointer from integer without a cast /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c: In function ‘dgap_tty_class_destroy’: /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:400: error: implicit declaration of function ‘class_simple_destroy’ /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c: In function ‘dgap_tty_register_device’: /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:571: error: implicit declaration of function ‘class_simple_device_add’ /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:573: warning: assignment makes pointer from integer without a cast /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:582: warning: assignment makes pointer from integer without a cast /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c: In function ‘dgap_tty_unregister_device’: /usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.c:605: error: implicit declaration of function ‘class_simple_device_remove’ make[5]: *** [/usr/src/packages/BUILD/dgap-1.2/driver/dgap_sysfs.o] Error 1 make[4]: *** [_module_/usr/src/packages/BUILD/dgap-1.2/driver] Error 2 make[3]: *** [modules] Error 2 make[2]: *** [modules] Error 2 make[2]: Leaving directory `/usr/src/linux-2.6.13-15.8-obj/i386/smp' make[1]: *** [build] Error 2 make[1]: Leaving directory `/usr/src/packages/BUILD/dgap-1.2/driver' make: *** [build] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.23324 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.23324 (%build) Can someone shed some light on what to do to fix this? Thanks, -- Boyd Gerber <gerberb(a)zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

15 years

Translation of package summaries and descriptions

by Krzysztof Lichota

Hello! I am not a packager, but a translator. Maybe my problem is already solved, but I have never heard of anything like this. If so, point me into the right direction :) My main problem is that Suse (and any other Linux distribution) cannot be fully used by person not knowing English, because package summaries and descriptions are in English. So, I would like to draw your attention to incorporating translation into process of creating and building packages. How I imagine it: 1. Translators are used to using .po (gettext-style) files. There are many tools for updating such files, translation, automated checking, etc. These files contain text to translate (in English) and corresponding translated text. 2. rpm has ability to specify translated summary and description in .spec file and tools (such as Yast package manager) can extract it from binary RPM file and show it to user. The main problem is how to update the spec file with translation (while allowing updates of summaries/descriptions and updates of translations). This is why it has to be done during creating packages (I don't know of any tool which would allow updating translation in already built RPM file, but maybe it could be created). 3. There are already tools in KDE which allow extracting text to translate from .desktop files (into .po files) and update back .desktop files with translation. I think it could be also done with .spec files (I can even volunteer to write a script to do that). So the process would be .spec -> .po -> translator updates translation -> .spec -> build package. 4. Now the main problem is creating infrastructure to do this - some kind of repository of .po files for packages which can be accessed by translators, and which will be used when building packages. 5. I also see other problems - when Yast package manager fetches information about packages from packages source, it shouldn't fetch descriptions in all languages but in one (to save bandwidth). So maybe translations should not be incorporated in RPM files but distributed separately? I am not sure my proposal is the best (putting translations in RPM files), so maybe you come up with something better :) Anyway, I would like to start the discussion on this matter as I think it is very important for average users :) Regards Krzysztof Lichota (Polish KDE translation team)

15 years

apache2-mod-tidy for OpenSUSE/SUSE Linux 10.1

by Sierk Bornemann

Hallo! Mit Erstaunen stelle ich fest, dass weder unter ftp://ftp.gwdg.de/pub/linux/suse/projects/apache/ noch unter ftp://ftp.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source/suse/i586 irgendwelche Pakete von mod_tidy (apache2-mod_tidy) zu finden sind. Hat das einen speziellen Grund? Zumindest bis Dezember 2005 war mod_tidy noch unter ftp://ftp.gwdg.de/pub/linux/suse/projects/apache/ eingepflegt (wenn auch in einer nicht mehr ganz aktuellen Version). Mit einem Mal jedoch leider nicht mehr. Warum? Aktuelle Suse-RPMs von mod_tidy (mod_tidy-0.5.5) stehen unter http://mod-tidy.sourceforge.net/release/0.5.5/linux/opensuse/ bzw. http://sourceforge.net/project/showfiles.php?group_id=142791 zur Verfügung. Das RPM-Binary der Version 0.5.5 kann ich leider nur für Apache 2.2 bereitstellen, da ich mein Build-System auf Apache2.2 umgestellt habe und nicht weiß, wie ich für Apache 2.0 und Apache 2.2 gleichzeitig compilieren kann (für hilfreiche Hinweise und Tipps, wie ich es dennoch bewerkstelligen kann, wäre ich dankbar). Alle von mir erstellten Suse-Pakete und Sources von mod_tidy sind wie gehabt ebenfalls unter http://sierkbornemann.de/pub/tools/mod_tidy/ zu finden. Ich bin sehr daran interessiert, dass die anstehende Linux-Distribution 10.1 aktuelle mod_tidy-Pakete enthält. Was ist da schief gelaufen, dass die Pakete nirgendwo mehr in einem Tree von SUSE/OpenSUSE zu finden sind? Für einen Hinweis und eine schnelle Antwort wäre ich sehr dankbar. Mit freundlichem Gruß, Sierk Bornemann Sierk Bornemann | Hannover | Germany e-mail: sierkb(a)gmx.de URL: http://sierkbornemann.de/

15 years

W3C Markup Validator for OpenSUSE?

by Sierk Bornemann

Is there any interest in the OpenSUSE community or SUSE itself to take RPMs of http://validator.w3.org/ into its tree? Installing the validator offline on a local host or a local net will have several benefits especially for web developers and web agencies. With the next release 0.7.2 of the W3C Markup Validator, http://validator.w3.org/source/ will also point to my website concerning RPMs for SUSE Linux. Sierk Sierk Bornemann | Hannover | Germany e-mail: sierkb(a)gmx.de URL: http://sierkbornemann.de/

15 years

[Andreas Jaeger] [opensuse-factory] Package Manager major changes for Beta4 and FACTORY Tree

by Andreas Jaeger

FYI - I've set reply-to to the factory mailing list but it might be interesting for some of you, Andreas Andreas -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

15 years

Packaging for 10.1 Beta1

by Liviu Damian

Hi, I want to make some packages for SUSE Linux 10.1 Beta1. First thing I've done was to install y2pmsh, and create the additional profiles for 10.1. Unfortunately it seems some packages aren't available: package libselinux is not available. package c_compiler is not available. package mozilla-devel is not available. package avahi-compat-howl is not available. package avahi-compat-howl-devel is not available. package ilbc is not available. package ilbc-devel is not available. package silc-toolkit is not available. package silc-toolkit-devel is not available. Here are my installation sources: 0: [x] SUSE LINUX Version 10.0.42 (file:/srv/ftp/opensuse/distribution/SL-OSS-factory/inst-source/) 1: [x] SUSE LINUX Version 10.0.42 (ftp://ftp4.gwdg.de/pub/opensuse/distribution/SL-OSS-factory/inst-source) 2: [x] SUSE LINUX Version 10.0.42 (http://you.novell.hu/i386/10.1/SUSE-Linux10.1-Beta1-Extra/) I can't use build because it stops when searches for libselinux (..................can not find libselinux.rpm... exit.). Any advice or idea about how can I make RPMS for Beta1? Cheers, -- Liviu Damian Mobile phone: +40 741 226993 URL: http://liviudm.blogspot.com

15 years

Re: KDE 3.5.1?

by Hussam Al-Tayeb

Hi, I read the readme from ftp.kde.org Not to rush things, but how long is the delay estimated?

15 years

KDE 3.5.1?

by Joseph M. Gaffney

Some people on suseforums are curious about KDE 3.5.1 builds... is there any intention to package these, or is the plan to let it just go into 10.1? Thanks Joseph M. Gaffney aka CuCullin

15 years

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging February 2006