December 2005 - openSUSE Packaging - openSUSE Mailing Lists

Where to place template files
by Richard Bos 12 Jan '06

12 Jan '06

I have a whole bunch of template files, where to place/locate template files? Is this /etc/<package>/... or would it be better to put those in /usr/share/<package>/...? Below a list with files, perhaps it helps tp detemine the location? ./etc/kolab/amavisd/templates/en_US/charset ./etc/kolab/amavisd/templates/en_US/template-dsn.txt ./etc/kolab/amavisd/templates/en_US/template-spam-admin.txt ./etc/kolab/amavisd/templates/en_US/template-spam-sender.txt ./etc/kolab/amavisd/templates/en_US/template-virus-admin.txt ./etc/kolab/amavisd/templates/en_US/template-virus-recipient.txt ./etc/kolab/amavisd/templates/en_US/template-virus-sender.txt /etc/kolab/templates/amavisd.conf.template ./etc/kolab/templates/clamd.conf.template ./etc/kolab/templates/cyrus.conf.template ./etc/kolab/templates/DB_CONFIG.slapd.template ./etc/kolab/templates/fbview.conf.template ./etc/kolab/templates/freebusy.conf.template ./etc/kolab/templates/freshclam.conf.template ./etc/kolab/templates/httpd.conf.template ./etc/kolab/templates/httpd.local.template ./etc/kolab/templates/imapd.conf.template ./etc/kolab/templates/imapd.group.template ./etc/kolab/templates/kolab.conf.template ./etc/kolab/templates/kolab_smtpdpolicy.conf.template ./etc/kolab/templates/ldap.conf.template ./etc/kolab/templates/ldapdistlist.cf.template ./etc/kolab/templates/ldaptransport.cf.template -- Richard Bos Without a home the journey is endless

2 1

gimp-beta
by James Ogley 30 Dec '05

30 Dec '05

Just uploading new gimp-beta[-devel] packages to the usr-local-bin repo/component/channel. 10.0-i[56]86 + src -- James Ogley james(a)usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org

1 0

kdebindings3-python and kdegraphics3-pdf dependency problem
by Richard Bos 24 Dec '05

24 Dec '05

I get the following problem when updating kdebindings3-python and kdegraphics3-pdf: The following packages have unmet dependencies: kdebindings3-python: Depends: python-qt (= 3.5.0-9) but 3.5.0-8 is to be installed kdegraphics3-pdf: Depends: xpdf-tools but it is not installable Seems a bug in the packages to me, can I report that here or should I go somewhere else? -- Richard Bos Without a home the journey is endless

1 0

"Virtual"/"meta" packages
by Pascal Bleser 23 Dec '05

23 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Another idea... let's call it "meta" or "virtual" packages... Make empty packages that pull several dependencies using their Requires tags to make packagers' life easier. e.g. Name: meta-c++-devel Version: 1.0.0 Release: 1 Requires: make libtool autoconf automake gcc-c++ Requires: libstdc++ libstdc++-devel libgcc glibc-devel (empty files, empty %setup, empty %build, empty %install) Note that such a "meta" package should be arch-specific (not "noarch") because it could be that on some architecture you need different packages than on others (e.g. an x86-optimized assembler would be included in the "meta-c++-devel" package on x86 and x86_64, but not on ppc or s390). That way, when packagers need to "BuildRequires" the C++ development environment for another package, it's just a matter of: Name: libfoo++ Version: 3.4.5 Release: 39 ... BuildRequires: meta-c++-devel ... SUSE's y2pmbuild already partly offers that functionality by expanding "virtual" names in "neededforbuild" to a set of real dependencies, but the issue with that approach is that it works only when using y2pmbuild. The solution above would work with any package manager (yast2, smart, yum, apt, ...) and with any RPM building frontend (rpmbuild, y2pmbuild, abuild, ...), and could even easily "hide" the gory details of what packages are required on 10.1, 10.0, on 9.3, ... to have a specific environment (e.g. on SUSE < 9.2, it's "libjpeg" whereas on SUSE >= 9.2 it's "libjpeg libjpeg-devel"). Mauricio "netmask" Teixeira and I talked about that idea, as Mauricio told me that Connectiva has that approach with so-called "task" packages (task-c++-devel, etc...). They also use it to do the same as SUSE Linux' "selections" (*.sel files in yast2 repositories), e.g. "task-mail-server", but that's a different story ;) I could really use such a "meta-gnome-devel" package ;))) 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) iD8DBQFDpnsEr3NMWliFcXcRAq2rAKCV2t6NNCaNW4R7LBr0tZS98ONIWwCgptY0 CGMefs6HAWaP0Djcd6v1cCc= =ptnB -----END PGP SIGNATURE-----

3 3

[Proposal] Suggests/Enhances Support in RPM/YaST
by Marcus Rueckert 21 Dec '05

21 Dec '05

hi, beside the minor problems we had with th rpm 4.4.2 update, we got a new cool feature: Enhances/Support Flags for a rpm. Some people might know them from Debian. Sadly RPM doesnt honor those flags yet. But SmartPM and the new YaST Package manager will support them. Semantics behind the 2 rpm tags --------------------------------- Basically both work similar to Provides/Requires. Atm the information will be just passed into the base package. RPM wont tell you about the relation ship. That work has to be done by high level tools. 1. Suggests ============= "Suggests" is a weak "Requires". You can suggest big packages, you dont want to enforce. A prominent example might be the hard requirement in taskjuggler to kdepim. Especially Gnome users dont like that much. 2. Enhances ============= "Enhances" can be used to promote addon packages. An amarok addon could declare itself as an enhancement of the amarok base package. That way we dont have to know all possible addon packages in the base package, but still be able to present the information to the user. Klaus Kaempf mentioned as another possible use case enhances on hardware detected in the box. Atm we install the synaptic driver in the default selection without checking if the box has a synaptics touch pad. xorg-xinput-synaptics could specify "Enhances: hwinfo(x11:synaptic-touchpad)" and SaX2 will only ask to install this rpm if the hardware is really found. Possible Solution inside YaST ------------------------------- Below the package listing you have this small info box where you can read the package description/technical informations/Requires|Provides list. An additional tab could be added to this area and the list of additional packages could be shown there. Or the usual dependency solving dialog could be presented. comments/critics welcome. Marcus p.s.: the original bug for this proposal https://bugzilla.novell.com/show_bug.cgi?id=136757

10 14

Gaim 2.0 beta
by James Ogley 21 Dec '05

21 Dec '05

Before I do the honours for 10.0, was anyone else planning to package up the new beta of gaim? James -- James Ogley james(a)usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Make Poverty History: http://makepovertyhistory.org

4 9

Re: [opensuse-packaging] kdenetwork3-InstantMessaging vs kopete (fwd)
by Will Stephenson 19 Dec '05

19 Dec '05

> From: Pascal Bleser <pascal.bleser(a)skynet.be> > > I'd like to discuss the fact that the kopete package is called > "kdenetwork3-InstantMessaging". After doing some research (and with some > help), I know that the decision to name that package this way comes from > SUSE (and not from the KDE team). That's partly right - kde svn modules are all packaged as kmodulename3, then any subpackage splits are at the discretion of the SUSE KDE maintainers. > I think it's not a good idea to name kopete that way, although the name > isn't the issue, but the version number. In fact, it's e.g. > kdenetwork3-InstantMessaging-3.5.0, but in reality it's some kopete version > (e.g. 0.11.x) This is an issue for every KDE application - kdepim3 contains kmail 1.9. It's only a problem in cases like this where the app team decides to do an out-of-kde-module release. > This raises a number of issues, where the most important is: now there's > going to be a kopete 0.12.0 very soon... how are we supposed to name/number > the package ? > > - we can't name it kdenetwork3-InstantMessaging-3.5.1, because when KDE > 3.5.1 will be released (possibly with a different kopete version but, most > importantly, built against another version of kdelibs3) it will collide > - we can't name it kopete either (with a > Conflicts:kdenetwork3-InstantMessaging) because end users won't see that as > an upgrade of kdenetwork3-InstantMessaging > - we /could/ use the release to provide an upgrade, but that's > a) misusing the release tag for what is actually a different version > number b) a pain to maintain, because maybe SUSE releases an update > kdenetwork3-InstantMessaging (with kopete 0.11.x) and then we'd have to > re-package it with a higher release number than SUSE > c) just an evil > workaround and trickery whereas the issue should be solved by giving the > package its correct name in the first place > > Could someone from SUSE please provide some feedback on this ? Stephan ? AJ > ? Would it be possible to rename kdenetwork3-InstantMessaging-3.5.0 to > kopete-0.11.x ? To me, it really doesn't make any sense to call it > "kdenetwork3-InstantMessaging", kopete is not even tightly bound to a > specific KDE release, it just creates issues for community packagers who > want to provide packages of the latest kopete version. I'd disagree about the trickery and incorrect package name charges. Its correct name according to convention is kdenetwork3-XXX. The problem here is of the Kopete dev team's making (which I belong to). Kopete has been tied to the KDE release cycle since KDE 3.2, it's only for this 0.12 release that we have broken this link. I'm looking for a solution that will allow us to upgrade from 3.5.x to kopete-0.12 to <future location of kopete> 4.0, 3.6, etc. I'll get back to you when I find it. Will Stephenson

2 1

kdenetwork3-InstantMessaging vs kopete
by Pascal Bleser 19 Dec '05

19 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi yall I'd like to discuss the fact that the kopete package is called "kdenetwork3-InstantMessaging". After doing some research (and with some help), I know that the decision to name that package this way comes from SUSE (and not from the KDE team). I think it's not a good idea to name kopete that way, although the name isn't the issue, but the version number. In fact, it's e.g. kdenetwork3-InstantMessaging-3.5.0, but in reality it's some kopete version (e.g. 0.11.x) This raises a number of issues, where the most important is: now there's going to be a kopete 0.12.0 very soon... how are we supposed to name/number the package ? - - we can't name it kdenetwork3-InstantMessaging-3.5.1, because when KDE 3.5.1 will be released (possibly with a different kopete version but, most importantly, built against another version of kdelibs3) it will collide - - we can't name it kopete either (with a Conflicts:kdenetwork3-InstantMessaging) because end users won't see that as an upgrade of kdenetwork3-InstantMessaging - - we /could/ use the release to provide an upgrade, but that's a) misusing the release tag for what is actually a different version number b) a pain to maintain, because maybe SUSE releases an update kdenetwork3-InstantMessaging (with kopete 0.11.x) and then we'd have to re-package it with a higher release number than SUSE c) just an evil workaround and trickery whereas the issue should be solved by giving the package its correct name in the first place Could someone from SUSE please provide some feedback on this ? Stephan ? AJ ? Would it be possible to rename kdenetwork3-InstantMessaging-3.5.0 to kopete-0.11.x ? To me, it really doesn't make any sense to call it "kdenetwork3-InstantMessaging", kopete is not even tightly bound to a specific KDE release, it just creates issues for community packagers who want to provide packages of the latest kopete version. thanks 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) iD8DBQFDpdLer3NMWliFcXcRAnAFAJ4g4vsjTgMerV1Uf4gglUPpxuSZ+gCfQJ/4 IYoI5gmgEpeR07QQY5W6m+8= =FOsv -----END PGP SIGNATURE-----

3 6

ghostscript packages
by Volker Kuhlmann 18 Dec '05

18 Dec '05

The x11/x11alpha device in ghostscript 8.15 (SUSE 10.0), and used by e.g. gv and kghostview, only produces utter rubbish as output and is therefore useless. ghostscript 8.53 is noticably better, but still not as good as 7.07.1. Question: has anyone tried to make packages for gs 8.53 and/or 7.07 which install in an alternative location, so they can be installed in addition to the system packages? I have tried with 7.07 as from Suse 9.2 (removing omni, hpijs, cdj880 as that stuff simply doesn't compile), but the packaging needs more work (interaction with cups - should prob disable that, fonts - can be shared with 8.15). Thanks, Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.

2 2

Python packages and noarch
by Pascal Bleser 18 Dec '05

18 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I'm getting productive with my new x86_64 box and noticed something... let's say "annoying" :) I have quite some python module packages around and when they only include ".py" files (and not ".so" files), I mark them as BuildArch:noarch Now I noticed while installing a python package (noarch) that it isn't found by python. The reason: as it's noarch, it's being installed in /usr/lib/python2.4 (having built it on an x86 box, and not an x86_64). But python only looks up its modules in /usr/lib64/python2.4 Does this mean that *all* python packages must be arch-specific, even when they're not (because they only include Python code and not native shared libs), just to have that path set correctly ? (that's a least what it looks like) 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) iD8DBQFDpUyXr3NMWliFcXcRAp1BAJ9DtArUzz7Gf6k0Esr0DZrTzOhFwACfVAew 8ScMB+ffubF7IVVfwfyCQCQ= =RKkv -----END PGP SIGNATURE-----

2 1

Building 32bit libs
by Brandon Barker 14 Dec '05

14 Dec '05

Hello, I would like to rebuild SDL as a 32 bit library for use in SuSE 10 x86_64 (there is a patch that I need to apply to the sources, which is why I need to rebuild). I've tried the following, but the libraries will not be loaded by my desired application (after I've patched it): export CC="gcc -m32" export LD="ld -m elf64_i386" export AS="gcc -c -m32" export LDFLAGS="-L/usr/lib" linux32 ./autogen.sh linux32 ./configure --libdir=/usr/lib --x-libraries=/usr/X11R6/lib && linux32 make The installed libraries will not load with my application, though the ones that shipped with SuSE linux work fine. Any insights into the build process here would be much appreciated. Thanks, -- Brandon Barker Phone: (859) 749-4634 Email: brandonbarker(a)ieee.org

3 3

Re: [opensuse] Build Service team minutes (initial offsite meeting)
by Henne Vogelsang 12 Dec '05

12 Dec '05

Hi, On Friday, December 09, 2005 at 19:48:02, Henne Vogelsang wrote: > On Friday, December 09, 2005 at 18:22:42, Juergen Weigert wrote: > > > - an impressive plan how the openSUSE engine might actually work, > > - and a solid TODO-list for getting a prototype up and running ... > > - to be shown at FOSDEM in February. > > We will make a Q&A session in our official IRC channel #opensuse on > freenode.net. All members of the Build Server Team will be there on > Monday the 12th of December at 17:00 CET and you can bug us for details > and ask all your questions. So be there or be square! :) I forgot. openSUSErs from other timezones or with a personal schedule clash can submit questions to the Q&A session page[1]. We will try to answer them in the session. You will also find a transcript of the session there. Henne [1] http://www.opensuse.org/BST_IRC_SESSIONS -- Henne Vogelsang, http://hennevogel.de "To die. In the rain. Alone." Ernest Hemingway

2 1

Build Service team minutes (initial offsite meeting)
by Juergen Weigert 12 Dec '05

12 Dec '05

Hello SUSE-openers and friends of openSUSE! openSUSE now has formed a Build Service Team. Well, not really 'now' -- two weeks ago. Our web page is at http://www.opensuse.org/Build_Service_Team We started with a 2-day meeting at a remote hotel in Bärnfels, a small town in the beautiful franconian countryside. During the meeting, it started to snow and we had to dig out our cars afterwards. Anyway, we came home with - an impressive plan how the openSUSE engine might actually work, - and a solid TODO-list for getting a prototype up and running ... - to be shown at FOSDEM in February. Now read yourself: http://www.opensuse.org/BST_3linden_Minutes_en There is also a PDF version (16 Pages, 800k) version for offline reading, linked also at the bottom of http://www.opensuse.org/Build_Service_Team Happy hacking! cheers, Jw. -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw(a)suse.de wide open suse_/ _---|____________\/ \ | 0911 74053-508 (tm)__/ (____/ /\ (/) | __________________________/ _/ \_ vim:set sw=2 wm=8

4 4

YaST2 repository for projects/mozilla
by Pascal Bleser 06 Dec '05

06 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think someone already asked for this but it seems nothing has happened... so here we go again ;) Would it be possible to add a YaST2 repository for the projects/mozilla stuff ? A lot of people are upgrading their firefox to 1.5 at the moment but for beginners who don't necessarily know how to use smart or apt-rpm, it's a bit painful to use bare-bones rpm. 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) iD8DBQFDlN96r3NMWliFcXcRAtVDAKCRoK6CC5wh9TQhF+RtnVUF1zLCvgCgk06/ /ddblDayDvrrl7deA1ZK3zQ= =3S9M -----END PGP SIGNATURE-----

3 2

Proposing community repositories in YaST2
by Pascal Bleser 05 Dec '05

05 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Some (many) weeks ago, I started a discussion with a few SUSE folks about adding a feature in YaST2 that would download a list of community repositories from a central location (opensuse.org) - in a similar fashion as YOU does - and propose it as a checklist (including a description, etc...) to the end-user. She'd just need to click the community repository and it would be included in the list of installation sources for YaST2. The main issue (besides YaST2 developers most certainly not being happy about adding a feature ;)) is legal: some repositories (such as packman and mine) provide packages that are not unencumbered for distribution in some countries, most notably the US (e.g. lame, mad, MPlayer). SUSE Linux would still not _include_ such repositories but would _link_ to them, indirectly. Although this seems unproblematic, it is not, see the Heise case (lost in german court because they published an article that links to a piece of software with which one can read encrypted DVDs). Adrian and/or AJ wanted to ask Novell's legal dept about it, but there has not been any feedback up to now. As I can imagine both of you guys have shitloads of work to do all the time, I post this mail as a reminder. And if you have some more information about it, it would be nice to let us know :) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v FOSDEM 2006 -- 25+26 February 2006 in Brussels -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDlDwFr3NMWliFcXcRAl4wAJ9AO8FYVDlK76Iu15sEoYT1rQW0ZgCfdElW dh6sxsrSHk57PxXg8nIzKUw= =EAHJ -----END PGP SIGNATURE-----

3 3

"error: gpg-error.h:" running make
by James PEARSON 03 Dec '05

03 Dec '05

Hello all, Excuse me if this is not the correct place for this question. I am (was?) trying to build the new version of "sylpheed-claws-2.0.0-rc1" under opensuse 10.0 (linux 2.6.13-15) just for fun. I used the same "configure" options that are used in "sylpheed-claws-1.9.100-0.pm.1.src.rpm" - the current version. ./configure --host=i686-suse-linux --build=i686-suse-linux --target=i686-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 --enable-crash-dialog --enable-openssl --enable-spamassassin-plugin --enable-pgpcore-plugin --enable-pgpmime-plugin --enable-pgpinline-plugin --enable-aspell --enable-ldap --enable-jpilot --enable-gnomeprint --enable-clamav-plugin --disable-mathml-viewer-plugin --enable-dillo-viewer-plugin --enable-compface The ".configure" runs fine. If, however, I try to do a "make|gmake" or "rpmbuild --rebuild --target=i686 sylpheed-claws-1.9.100-0.pm.1.src.rpm", I get a pile of errors related to "gpgme.h" file I was hoping that someone could give a few ideas on what I could try next. The first sign of the error is "/usr/include/gpgme.h:53:23: error: gpg-error.h: No such file or directory..." ##################################################### ERROR during build (SHORT) ##################################################### -DPIC -o .libs/passphrase.o In file included from passphrase.h:23, from passphrase.c:48: /usr/include/gpgme.h:53:23: error: gpg-error.h: No such file or directory In file included from passphrase.h:23, from passphrase.c:48: /usr/include/gpgme.h:95: error: syntax error before ‘gpgme_error_t’ /usr/include/gpgme.h:96: error: syntax error before ‘gpgme_err_code_t’ /usr/include/gpgme.h:97: error: syntax error before ‘gpgme_err_source_t’ /usr/include/gpgme.h:101: error: syntax error before ‘gpgme_err_make’ /usr/include/gpgme.h:101: error: syntax error before ‘source’ ##################################################### ERROR during build (LONG) ##################################################### ... mkdir .libs gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../ -I../../common -I../../gtk -pthread -I/opt/gnome/include/glib-2.0 -I/opt/gnome/lib/glib-2.0/include -I/opt/gnome/include/gtk-2.0 -I/opt/gnome/lib/gtk-2.0/include -I/opt/gnome/include/atk-1.0 -I/opt/gnome/include/pango-1.0 -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/X11R6/include -I/usr/include/libpng12 -I/opt/gnome/include/glib-2.0 -I/opt/gnome/lib/glib-2.0/include -Wno-deprecated-declarations -I/usr/local/include -g -O2 -Wall -MT passphrase.lo -MD -MP -MF .deps/passphrase.Tpo -c passphrase.c -fPIC -DPIC -o .libs/passphrase.o In file included from passphrase.h:23, from passphrase.c:48: /usr/include/gpgme.h:53:23: error: gpg-error.h: No such file or directory In file included from passphrase.h:23, from passphrase.c:48: /usr/include/gpgme.h:95: error: syntax error before ‘gpgme_error_t’ /usr/include/gpgme.h:96: error: syntax error before ‘gpgme_err_code_t’ /usr/include/gpgme.h:97: error: syntax error before ‘gpgme_err_source_t’ /usr/include/gpgme.h:101: error: syntax error before ‘gpgme_err_make’ /usr/include/gpgme.h:101: error: syntax error before ‘source’ /usr/include/gpgme.h: In function ‘gpgme_err_make’: /usr/include/gpgme.h:103: error: ‘source’ undeclared (first use in this function) /usr/include/gpgme.h:103: error: (Each undeclared identifier is reported only once /usr/include/gpgme.h:103: error: for each function it appears in.) /usr/include/gpgme.h:103: error: ‘code’ undeclared (first use in this function) /usr/include/gpgme.h: At top level: /usr/include/gpgme.h:114: error: syntax error before ‘gpgme_error’ /usr/include/gpgme.h:114: error: syntax error before ‘code’ /usr/include/gpgme.h: In function ‘gpgme_error’: /usr/include/gpgme.h:116: error: ‘GPG_ERR_SOURCE_USER_1’ undeclared (first use in this function) /usr/include/gpgme.h:116: error: ‘code’ undeclared (first use in this function) /usr/include/gpgme.h: At top level: /usr/include/gpgme.h:121: error: syntax error before ‘gpgme_err_code’ /usr/include/gpgme.h:121: error: syntax error before ‘err’ /usr/include/gpgme.h: In function ‘gpgme_err_code’: /usr/include/gpgme.h:123: error: ‘err’ undeclared (first use in this function) /usr/include/gpgme.h: At top level: /usr/include/gpgme.h:128: error: syntax error before ‘gpgme_err_source’ /usr/include/gpgme.h:128: error: syntax error before ‘err’ /usr/include/gpgme.h: In function ‘gpgme_err_source’: /usr/include/gpgme.h:130: error: ‘err’ undeclared (first use in this function) /usr/include/gpgme.h: At top level: /usr/include/gpgme.h:136: error: syntax error before ‘err’ /usr/include/gpgme.h:145: error: syntax error before ‘err’ /usr/include/gpgme.h:150: error: syntax error before ‘err’ /usr/include/gpgme.h:156: error: syntax error before ‘gpgme_err_code_from_errno’ /usr/include/gpgme.h:161: error: syntax error before ‘code’ /usr/include/gpgme.h:166: error: syntax error before ‘gpgme_err_make_from_errno’ /usr/include/gpgme.h:166: error: syntax error before ‘source’ /usr/include/gpgme.h:170: error: syntax error before ‘gpgme_error_from_errno’ /usr/include/gpgme.h:522: error: syntax error before ‘gpgme_error_t’ /usr/include/gpgme.h:545: error: syntax error before ‘}’ token /usr/include/gpgme.h:664: error: syntax error before ‘*’ token /usr/include/gpgme.h:667: error: ‘gpgme_error_t’ declared as function returning a function /usr/include/gpgme.h:667: error: ‘gpgme_error_t’ redeclared as different kind of symbol /usr/include/gpgme.h:95: error: previous declaration of ‘gpgme_error_t’ was here /usr/include/gpgme.h:676: error: ‘gpgme_edit_cb_t’ declared as function returning a function /usr/include/gpgme.h:682: error: ‘gpgme_new’ declared as function returning a function /usr/include/gpgme.h:688: error: ‘gpgme_set_protocol’ declared as function returning a function /usr/include/gpgme.h:716: error: ‘gpgme_set_keylist_mode’ declared as function returning a function /usr/include/gpgme.h:724: error: syntax error before ‘gpgme_passphrase_cb_t’ /usr/include/gpgme.h:728: error: syntax error before ‘gpgme_passphrase_cb_t’ /usr/include/gpgme.h:744: error: ‘gpgme_set_locale’ declared as function returning a function /usr/include/gpgme.h:759: error: ‘gpgme_signers_add’ declared as function returning a function /usr/include/gpgme.h:788: error: ‘gpgme_get_sig_key’ declared as function returning a function /usr/include/gpgme.h:794: error: ‘gpgme_io_cb_t’ declared as function returning a function /usr/include/gpgme.h:803: error: ‘gpgme_register_io_cb_t’ declared as function returning a function /usr/include/gpgme.h:892: error: ‘gpgme_data_new’ declared as function returning a function /usr/include/gpgme.h:902: error: ‘gpgme_data_new_from_mem’ declared as function returning a function /usr/include/gpgme.h:911: error: ‘gpgme_data_new_from_cbs’ declared as function returning a function /usr/include/gpgme.h:913: error: ‘gpgme_data_new_from_fd’ declared as function returning a function /usr/include/gpgme.h:915: error: ‘gpgme_data_new_from_stream’ declared as function returning a function /usr/include/gpgme.h:922: error: ‘gpgme_data_set_encoding’ declared as function returning a function /usr/include/gpgme.h:933: error: ‘gpgme_data_new_with_read_cb’ declared as function returning a function /usr/include/gpgme.h:940: error: ‘gpgme_data_new_from_file’ declared as function returning a function /usr/include/gpgme.h:947: error: ‘gpgme_data_new_from_filepart’ declared as function returning a function /usr/include/gpgme.h:951: error: ‘gpgme_data_rewind’ declared as function returning a function /usr/include/gpgme.h:959: error: ‘gpgme_get_key’ declared as function returning a function /usr/include/gpgme.h:1007: error: ‘gpgme_cancel’ declared as function returning a function /usr/include/gpgme.h:1014: error: field ‘reason’ declared as a function /usr/include/gpgme.h:1041: error: ‘gpgme_op_encrypt_start’ declared as function returning a function /usr/include/gpgme.h:1044: error: ‘gpgme_op_encrypt’ declared as function returning a function /usr/include/gpgme.h:1053: error: ‘gpgme_op_encrypt_sign_start’ declared as function returning a function /usr/include/gpgme.h:1056: error: ‘gpgme_op_encrypt_sign’ declared as function returning a function /usr/include/gpgme.h:1078: error: ‘gpgme_op_decrypt_start’ declared as function returning a function /usr/include/gpgme.h:1080: error: ‘gpgme_op_decrypt’ declared as function returning a function /usr/include/gpgme.h:1086: error: ‘gpgme_op_decrypt_verify_start’ declared as function returning a function /usr/include/gpgme.h:1088: error: ‘gpgme_op_decrypt_verify’ declared as function returning a function /usr/include/gpgme.h:1141: error: ‘gpgme_op_sign_start’ declared as function returning a function /usr/include/gpgme.h:1144: error: ‘gpgme_op_sign’ declared as function returning a function /usr/include/gpgme.h:1187: error: field ‘status’ declared as a function /usr/include/gpgme.h:1205: error: field ‘validity_reason’ declared as a function /usr/include/gpgme.h:1221: error: ‘gpgme_op_verify_start’ declared as function returning a function /usr/include/gpgme.h:1224: error: ‘gpgme_op_verify’ declared as function returning a function /usr/include/gpgme.h:1254: error: field ‘result’ declared as a function /usr/include/gpgme.h:1317: error: ‘gpgme_op_import_start’ declared as function returning a function /usr/include/gpgme.h:1318: error: ‘gpgme_op_import’ declared as function returning a function /usr/include/gpgme.h:1320: error: ‘gpgme_op_import_ext’ declared as function returning a function /usr/include/gpgme.h:1326: error: ‘gpgme_op_export_start’ declared as function returning a function /usr/include/gpgme.h:1328: error: ‘gpgme_op_export’ declared as function returning a function /usr/include/gpgme.h:1333: error: ‘gpgme_op_export_ext_start’ declared as function returning a function /usr/include/gpgme.h:1336: error: ‘gpgme_op_export_ext’ declared as function returning a function /usr/include/gpgme.h:1360: error: ‘gpgme_op_genkey_start’ declared as function returning a function /usr/include/gpgme.h:1362: error: ‘gpgme_op_genkey’ declared as function returning a function /usr/include/gpgme.h:1371: error: ‘gpgme_op_delete_start’ declared as function returning a function /usr/include/gpgme.h:1373: error: ‘gpgme_op_delete’ declared as function returning a function /usr/include/gpgme.h:1380: error: ‘gpgme_op_edit_start’ declared as function returning a function /usr/include/gpgme.h:1383: error: ‘gpgme_op_edit’ declared as function returning a function /usr/include/gpgme.h:1389: error: ‘gpgme_op_card_edit_start’ declared as function returning a function /usr/include/gpgme.h:1392: error: ‘gpgme_op_card_edit’ declared as function returning a function /usr/include/gpgme.h:1412: error: ‘gpgme_op_keylist_start’ declared as function returning a function /usr/include/gpgme.h:1415: error: ‘gpgme_op_keylist_ext_start’ declared as function returning a function /usr/include/gpgme.h:1418: error: ‘gpgme_op_keylist_next’ declared as function returning a function /usr/include/gpgme.h:1421: error: ‘gpgme_op_keylist_end’ declared as function returning a function /usr/include/gpgme.h:1463: error: ‘gpgme_op_trustlist_start’ declared as function returning a function /usr/include/gpgme.h:1467: error: ‘gpgme_op_trustlist_next’ declared as function returning a function /usr/include/gpgme.h:1470: error: ‘gpgme_op_trustlist_end’ declared as function returning a function /usr/include/gpgme.h:1506: error: ‘gpgme_get_engine_info’ declared as function returning a function /usr/include/gpgme.h:1513: error: ‘gpgme_engine_check_version’ declared as function returning a function /usr/include/gpgme.h:1533: error: syntax error before ‘GpgmePassphraseCb’ In file included from passphrase.c:48: passphrase.h:32: error: ‘gpgmegtk_passphrase_cb’ declared as function returning a function passphrase.c:297: error: ‘gpgmegtk_passphrase_cb’ declared as function returning a function passphrase.c: In function ‘gpgmegtk_passphrase_cb’: passphrase.c:303: error: ‘GPG_ERR_NO_ERROR’ undeclared (first use in this function) passphrase.c:312: error: ‘GPG_ERR_CANCELED’ undeclared (first use in this function) gmake[5]: *** [passphrase.lo] Error 1 gmake[5]: Leaving directory `/space1/sylpheed-claws-2.0.0-rc1/src/plugins/pgpcore' gmake[4]: *** [all-recursive] Error 1 gmake[4]: Leaving directory `/space1/sylpheed-claws-2.0.0-rc1/src/plugins' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/space1/sylpheed-claws-2.0.0-rc1/src' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/space1/sylpheed-claws-2.0.0-rc1/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/space1/sylpheed-claws-2.0.0-rc1' gmake: *** [all] Error 2 ##################################################### Has anyone else had the above error(s). The first one is "/usr/include/gpgme.h:53:23: error: gpg-error.h: No such file or directory" Any help would be greatly appreciated. TIA James

4 4

Fedora Directory server
by etherboot＠gmail.com 03 Dec '05

03 Dec '05

Is anybody working on packaging the just released Fedora Directory (LDAP) Server 1.0? http://directory.fedora.redhat.com/ I hope this is the right place to ask this question.

2 1

openSUSE @ FOSDEM 2006
by Pascal Bleser 03 Dec '05

03 Dec '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Being part of the core FOSDEM organization staff, I'd like to trigger this again, giving a few more details. Christoph Thiel wrote: > Hi everyone, > the sixth Free and Open source Software Developers' European Meeting > (commonly known as FOSDEM, [http://www.fosdem.org/] will take place > during the last week-end (25&26) of February 2006 in the city of Brussels, > Belgium. It's an annual 2-day event hosting talks, tutorials, and stalls > for the free software/open source community. It is organized by volunteers > at the Université Libre de Bruxelles in Belgium. Access to all parts of > FOSDEM is free, but donations and sponsors are welcome to help fund the > event. As a side note for those who don't know the event... FOSDEM is one of the top FOSS events in Europe (for many projects it's even the major event of the year). Last time (2005) we had an estimated 2500-4000 visitors over the week-end (it's a gross estimation, as the entrance is free we don't have any exact numbers ;)), with even more visitors to expect this year (number of visitors has been growing constantly every year). Yes, you read that right: entrance is free for everyone (although donations are welcome, and you get T-shirts, O'Reilly books, ... ;)). While other events in Europe are larger in terms or raw size (e.g. LinuxTag), we believe to have the edge in terms of quality and "being a _real_ community event". FOSDEM is particularely appreciated for not being spoiled by sponsor/big vendor talks/show-offs as well as being highly technical, packed with talks by key developers and project leaders of the Free and Opensource community. As an example, here's last edition's (2005) lineup in the main tracks: Ethan Galstad (Nagios), Marty Roesch (Snort), Gerald Combs (Ethereal), Alexander Dymo (KDevelop), Andreas Zeller (DDD), Benoit Minisini (Gambas), Mathias Ettrich (KDE), Olivier Fourdan (XFCE), Alex Larsson (Nautilus), Marius Mauch (Gentoo), Jeff Johnson (RPM), Stuart Winter (Slackware), Alax Cox (Kernel), Alasdair Kergon (Kernel), Pat Mochel (Kernel), Olle Mulmo (Globus), Alan Robertson (Linux HA), Ken Preslan (OpenGFS) => http://fosdem.org/2005/index/schedule.html We also provide FOSS projects with so-called "DevRooms" (Developer Rooms) where we basically assign conference rooms to various projects (upon request), where they can schedule their activities as they wish (talks, hacking, sessions with other projects, ...). Here's the list of devrooms/projects we have this year: openSUSE, KDE, Gentoo, GNOME, Debian, Embedded Linux, Mozilla Europe, openGroupware, GNUstep, Tcl/Tk, Jabber, GNU Classpath (GCJ+Kaffee+Harmony+GNU Classpath+SableVM+...), Calibre, Ada, Debian (and one I may not disclose as of now ;)). Last year, the talks in the devrooms alone summed up to 140 over the week-end (not counting the 24 talks in the main tracks + 2 introductory + 1). Just to make clear this is a major event and a place to make a lot of contacts as well as to attend great talks ;) > As you may have already noticed (because Pascal blogged about it), we will > have an openSUSE 'DevRoom' (Developer Room) @ FOSDEM and most likely a > booth as well. Therefore, we are in the very early stages of preparation > and would like to team up with you to organize the openSUSE @ FOSDEM > event. Precisely, I think that would be the most interesting option. - - getting information about the progress and future plans of openSUSE/SUSE Linux from Novell/SUSE staff members - - people from the openSUSE community make presentations about e.g. SUPER, SLICK, community repositories, documentation, ... - - serve as a showcase to other FOSS projects and visitors But, and that's probably the most interesting part, we can also make use of that event to make very interactive sessions, where we (Novell/SUSE staff + community members) meet up to discuss future directions, possible improvements, initiatives, etc... We'll have a large room with 150 or 200 seats for the whole week-end (= 1.5 days). The event kicks off at 10:30 with the 2 introductory talks, and from 13:00 on the devrooms and main tracks have their go. This means for devrooms: - - Saturday 25th Feb: 13:00 - 17:00 - - Sunday 26th Feb..: 10:00 - 17:00 We also organize a few side activities: - - key and CAcert signing - - Tutorial sessions (6 x 1h) - - hacker rooms, open for anyone - - a buffet at a hotel in Brussels (good occasion to meet a lot of interesting people ;)) Wireless internet connectivity is provided almost everywhere, with cabled access available in the "hacker rooms" (and in most DevRooms). Also, LPI will organize 4 Linux certification exam sessions over the week-end, at a (*very*) reduced rate (exact price to be announced in the next few days). > To start off, we would like to get your opinion on what topics, > presentation, talks, tutorials, etc. you would expect from openSUSE @ > FOSDEM? And if you would like to deliver a presentation, talk, tutorial? > The ultimate goal would be to have presentations distributed equally > amongst community members and SUSE / Novell employees. > > Here are some possible topics, that are basis for discussion far: > - presentations > + openSUSE in general (what happend so far, what's up next) Yes, also to give a chance to visitors and people from other projects to have a look at what openSUSE really is and what (y)our plans are. > + openSUSE build infrastructure That's a must. Adrian, you won't escape from doing this talk ;))) And for end of February, maybe we could even see a demo... ? ;) > + SUSE Linux 10.1 - highlights and features > - dicussion > + SUSE Linux 10.2 - dicussion / plans for the future That pretty much hits what I mentioned above, an open discussion about openSUSE's future. > + Usability and Documentation > - tutorials > + packaging the SUSE-way This could be held by someone from Packman (or me) ;) > + using the build infrastructure > + LIVE CD construction Or rather a presentation of SUPER or SLICK. > + Customizing SUSE Linux > > That's it for the moment, we are all looking forward to a lively discussion > and a great collaboration. ... which didn't really happen up to now. Cmon folks, there have been a lot of people criticizing openSUSE for "not being open enough", now that's a great occasion to show off and move forward as a community ;) As a side note, every project that has a devroom _must_ send in a schedule of the planned activities. The deadline hasn't been set yet, but expect it to be something like mid January. That means we have to start discussing it right now. Who would be interested a) to come to the event, and attend the openSUSE devroom b) participate and make a presentation or demo (30-45) on something about openSUSE/SUSE Linux c) propose a topic to be presented by Novell/SUSE staff members Send in some feedback. 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.0 (GNU/Linux) iD8DBQFDj4Xqr3NMWliFcXcRAhTwAJ9qa+jsytj3YLkmBCvxH4nz2P4OnwCfa+bE 9/5Jc+EXekQDV7Ozd21yx4E= =XCrg -----END PGP SIGNATURE-----

3 2

fpc
by Peter Czanik 02 Dec '05

02 Dec '05

Hello, Anyone tried to compile Free Pascal Compiler on openSUSE? It's on the whishlist ( http://www.opensuse.org/Wishlist_Productivity#F ), added by somebody else, but I need it as well. I wanted to compile it. They have source rpm as well ( http://www.freepascal.org/download.html ). Just one little problem: fpc is required to compile itself ;-) Would be nice, if somebody solved this 'catch 22' for 10.1! Bye, Peter

2 3

Announcement: tools for web developers (tidy, mod_tidy, w3c markup validator)
by Sierk Bornemann 02 Dec '05

02 Dec '05

Hi! I am primary a web developer, and my interest is very high, that the popular SUSE Linux offers tools to make a (web-)developer's life easier. Fedora has an eye on developers, also Debian. Why not also SUSE? Making the openSUSE platform interesting for developers more than ever before? Since month, I build my own RPMs of tidy (http://tidy.sourceforge.net) and mod_tidy (http://mod-tidy.sourceforge.net/) which both have been also taken as a basis for SuSEs current tidy packages on ftp://ftp.suse.com/pub/projects/apache/tidy/ and mod_tidy packages on ftp://ftp.suse.com/pub/projects/apache/apache-mod_tidy/. Unfortunately, SUSEs official packages are not updated so regulary, as I wish they could be, so I want to point to my resources on http://sierkbornemann.de/pub/tools/tidy/ and http://sierkbornemann.de/pub/tools/mod_tidy/, where I store much more up-to-date RPMs for SUSE Linux. The mod_tidy packages, recently shipped with SUSE Linux 10 are outdated. Since I have overtaken the project, some important things have been changed (updated License, updated code, etc.). These URLs on my personal site are still inofficial (for developers only). I hope, that in long time view the official SuSE resources get in sync with wether my packages, which try to be as close and up-to-date as possible to the original, or with the official resources. Since several weeks, I also offer the official W3C Markup Validator of http://validator.w3.org/ as a RPM for SUSE Linux. These packages are still located on http://sierkbornemann.de/pub/tools/w3c-markup-validator/. As it happened with my tidy and mod_tidy packages, I hope, my w3c validator packages will be copyied to one of SUSEs FTP-Servers and offered from there to the public (here again, I want to keep the traffic to my server in a reasonable limit, that's because I hope, that somebody of Novell/SuSE gives them a place on a public SuSE FTP server). Concerning the W3C Markup Validator, I went on optimizing it for local use (the W3C developers themselves have an eye on it and made a lot of adjustments). It's easy to install and configurate. Hints for improvements are welcome (this belongs to the validator as to tidy and to mod_tidy). For the near future, I aim SUSE Linux packages of the W3C Validator to be also mentioned on http://validator.w3.org/source/ (besides Fedora and Debian packages). I have strong encouragement from the Validator Dev team in continuing so. and I still hope, Novell/SUSE is able to give me more official assistance (minimum: updating more frequently the packages taken from me). So, have a look into my packages, try them out. Any help for improvements and advocacy is welcome. Sierk Bornemann Sierk Bornemann | Hannover | Germany e-mail: sierkb(a)gmx.de URL: http://sierkbornemann.de/

2 2

Patch RPM's and the -P option
by Scott Lowrey 02 Dec '05

02 Dec '05

The rpm command on SuSE 9.1 and 9.3 provides a patch select option (-P, --patches). I have not had a chance to review rpm on OpenSUSE, yet but will be doing that soon, so apologies if this message appears to be a bit misdirected - it's not. :-) Anyway, I'm guessing that a patch RPM is a "partial package" that does not contain all files, instead providing only the files that have been updated? If I issue the "rpm -qPa" command, I see a small subset of RPMs - notably, those that appear to have been applied as part of an online update. The Red Hat/Fedora/rpm.org guides and the master RPM change list do not document a -P option. Can someone give me some background? Is this a SuSE creation? What distinguishes a patch RPM from a regular RPM? I do know that any RPM can be considered a "patch" or "update", but I have a need to track RPMs that have been specifically applied in response to customer problem reports - this feature seems to meet that need. Thanks for your help. -Scott Lowrey

6 7

SynCE 0.9.1 out there since 2005-07-08
by Joern Ende 01 Dec '05

01 Dec '05

Hi Folks, a new version of SynCE (software to sync a windows CE based PDA to linux) has been released. http://sourceforge.net/projects/synce/ There are new releases of orange and unshield to. On the SuSE 10.0 DVD and in the repos there is only the version 0.9.0 from 2004-09-12. The new release has a lot of bugfixes and new features. Perhaps any of the packagers out there could build rpms for SuSE 10.0. Regards JOern

2 5