- openSUSE Packaging

Updated package aqbanking
by Rauch Christian 14 Nov '05

14 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Updated package 'aqbanking' (http://www.aquamaniac.de/aqbanking/) to 1.6.1 Should be available by now on [1]. [1] ftp://ftp.gwdg.de/pub/linux/misc/suser-crauch/ Christian Rauch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDeEnxayhvFxrDZlkRAlIWAJ4kH09wMH+x3MKoM4v2wqeAwM6IngCfUKG+ hnzPx2gEPLJ6u1aP24hHUTk= =Cgnx -----END PGP SIGNATURE-----

2 1

gcc-3.4.4 + ssp spec
by Damian Mihai Liviu 14 Nov '05

14 Nov '05

Hello, If there is someone here with enough time to help me create a spec for gcc-3.4.4 with ssp please contact me via e-mail or IM: e-mail: this e-mail ;-) Yahoo: liviudm_cisco ICQ: 311535578 Jabber: liviudm(a)jabber.org Cheers, -- Damian Mihai Liviu Mobile: +40 741 226993; Fax: +1 347-632-4117 Phone : +1 360-526-6441; +1 347-632-4117; +44 0870-3403339 URL: http://liviudm.blogspot.com

2 2

Darwin Information Typing Architecture (DITA XML)
by Karl Eichwalder 13 Nov '05

13 Nov '05

Do you think it is worth adding the Darwin Information Typing Architecture (DITA XML) to SUSE Linux? DITA XML is a topic oriented way of managing documentation. It is a standard driven by IBM and accepted by OASIS. For more info, see http://xml.coverpages.org/dita.html

2 2

Looking for a way to select a certain to get a certain package selection
by Rainer Krienke 10 Nov '05

10 Nov '05

Heloo I am not quite sure if this is the right place to ask but perhaps someone has an idea. What I am looking for is a way in a standard SuSE installation (via NFS) to initially get a certain package selection that I created on my own. I want to install every host with the same selection of packages and want to have as little setupwork for this. auto_yast turned out not to be useful here. Up to suse9.3 this was quite simple. Basically I simply created a new .sel file in <base>/suse/setup/descr/ and put the name of this selection at the end of the file selection in the same directory. Later when the installation started the installer would automatically select the last entry from "selections" as the base software selection. This worked fine up to suse9.3. In 10.0 I only have a choice in between "KDE", "Gnome" and "Minimal" as base selections. I can manually add a addon selection but ideally this is exactly what I would like to avoid. I could also overwrite the default selections for KDE, Gnome and Minimal with my own one, but this is not the ideal solution if I ever want to have a default installation. So my question is, if one can configure somewhere somehow what base package selections yast2 offers when starting the installation or if this is hard coded into the installer Can anyone give me a hint? -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke(a)uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------

2 1

rpm filesystem fails to install due to nfs
by Richard Bos 10 Nov '05

10 Nov '05

I get the following error msg: linux:/var/cache/apt/archives # rpm -Uvh filesystem_10.0-4.2_i586.rpm Preparing... ########################################### [100%] 1:filesystem warning: can't chown /home (Operation not permitted) ########################################### [100%] error: unpacking of archive failed on file /home: cpio: chmod failed - Operation not permitted This is because my /home filesystem is nfs mounted. It seems that the file system rpm, has problems with it. Is this a bug in the filesystem rpm? -- Richard Bos Without a home the journey is endless

2 2

Scribus 1.3.1
by Marcel Hilzinger 10 Nov '05

10 Nov '05

I made an RPM yesterday on SL 9.3. works on 10.0, too. Anybody interested? -- Mit freundlichen Grüßen, Marcel Hilzinger Linux New Media AG Süskindstr. 4 D-81929 München Tel: +49 (89) 99 34 11 0 Fax: +49 (89) 99 34 11 99

3 7

Updated package taxbird
by Rauch Christian 10 Nov '05

10 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Updated package 'taxbird' (http://www.taxbird.de) to 0.4. Should be available within 24 hours on [1]. Dependency libgeier available in version 0.3 on my repo. [1] ftp://ftp.gwdg.de/pub/linux/misc/suser-crauch/ Christian Rauch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDcv/0ayhvFxrDZlkRAn94AJ0dsI5Daq0diiUgOFT+mld8AF1Z3QCfaDqV J5Y9gPRnFowBmIf13L/UqNs= =fU38 -----END PGP SIGNATURE-----

1 0

new packages in suser-liviudm
by Damian Mihai Liviu 09 Nov '05

09 Nov '05

Hi, I would like to announce 3 new packages in suser-liviudm: chmlib-0.37.4-1.i686.rpm chmlib-devel-0.37.4-1.i686.rpm xchm-1.2-1.i686.rpm The packages will be available tomorrow at 9:10AM GMT time because gwdg.de is syncing my repository only once a day (that was my choice). Cheers, -- Damian Mihai Liviu Mobile: +40 741 226993; Fax: +1 347-632-4117 Phone : +1 360-526-6441; +1 347-632-4117; +44 0870-3403339 URL: http://liviudm.blogspot.com

1 0

kdepim errors
by Damian Mihai Liviu 08 Nov '05

08 Nov '05

Hi, I'm trying to compile kdepim and I get the following error: ../../kode/kxml_compiler/kxml_compiler --custom-parser /usr/src/packages/BUILD/kdepim-3.4.2/kresources/featureplan/kde-features.rng echo > dummy.cpp makeobj[0]: Leaving directory `/usr/src/packages/BUILD/kdepim-3.4.2' error: Bad exit status from /var/tmp/rpm-tmp.22779 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.22779 (%build) The spec file is almost untouched (added BuildArch: i686, Packager: me and changed the Release from 18 to 18.SUPER.1). CFLAGS, CXXFLAGS and LDFLAGS are used (check my blog). Any idea? Cheers, -- Damian Mihai Liviu Mobile: +40 741 226993; Fax: +1 347-632-4117 Phone : +1 360-526-6441; +1 347-632-4117; +44 0870-3403339 URL: http://liviudm.blogspot.com

4 6

Packager communication + teamwork (was: mplayerplug-in)
by Pascal Bleser 07 Nov '05

07 Nov '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James Ogley wrote: >> in the moment, Rainer Lay hasn't much time, so i'll try to "fix" missing rpms >> for 10.0. mplayerplug-in is now online on packman. ;) > > Cool, I've removed my packages now. > Teamwork - it's a beautiful thing :) Well, as I said/wrote again and again, it definately shows that we've been lacking a common communication media. Duplicate packages, recurring issues, maybe discussing over common style/guidelines for spec files, etc... At least that's the kind of things I hope we'll be able to talk about in some time (or maybe right now). We definately need to work much closer together. Most specifically, having duplicate packages is a big issue: 1) often they're not compatible and/or conflict: different package name, different subpackaging, ... 2) issues for end-user who have several repositories in their inst sources That's certainly the worst issue of them all, as we all want to give end-users a good experience and easy of use, without what we wouldn't do all this packaging stuff ;) 3) duplicated work Partly wasted time and effort for us packagers - and time sure is a valuable resource for all of us. This also means that we should keep this list clear from any support question ("yast gives me an error when I try to do a netinstall"-alikes). Package-related bug reports.. hmm... why not. Someone from SUSE mentioned that we could also use the openSUSE bugzilla to report issues about our "community-made" packages. I don't remember who it was... Adrian, AJ, Christoph... ? I would have a proposal: every time one of us makes a new package (not a new release, but start packaging a project you didn't do before), send a mail on this list. Like that, if someone else already packages/maintains it, we/they can discuss who maintains it, in order to avoid duplication. What do you guys think ? Feasible ? Too much overhead ? Also, when we find out about cool RPM/spec tricks, gotchas, bugs, tools, scripts, whatever, publicize it here. This list can also be used to extend our know-how. If some information is considered interesting or important enough to be "sticky", we can write it on the opensuse wiki. If noone is against it, I'll start doing so right now. What about everyone maintaining a public repository introducing himself here ? - - shortly - - what repository do you maintain (suser-guru, usr-local-bin, packman, suser-gbv, ...) - - what kind of software in your repo (anything, multimedia, server stuff, ...) - - what SUSE versions do you build for - - repo URLs/formats - - email address, jabber ID, ... Or maybe a page on the opensuse wiki ? 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) iD8DBQFDX05Sr3NMWliFcXcRAo0VAJ42bRQvrIjNfl+gxh3UEDBBouuJ0ACfZCr6 SUDyfdtnlZwyXvHPUBcUHxM= =YAFG -----END PGP SIGNATURE-----

13 15