November 2006 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] A way to provide gpg key?
by Anders Norrbring 13 Nov '06

13 Nov '06

Is there a way to automatically provide the passkey to gpg and rpmbuild when using the 'build' scripts? Many times I build packages for both i586 and x86_64 and SUSE versions 9.3 -> 10.1 and SLES9 & 10. It would be really nice to automate all the passkey entries so I can run it all in one batch. -- Anders Norrbring Norrbring Consulting

4 10

[opensuse-packaging] Please update packages of libtidy an tidy!
by Sierk Bornemann 12 Nov '06

12 Nov '06

Hello, I am the package maintaner of the openSUSE packages tidy/libtidy, apache2-mod_tidy and w3c-markup-validator. Reading, that openSUSE 10.2 Beta 2 is announced, I want to stress, that until today the factory packages of tidy and its library, libtidy are not up-to-date (they are from 2005!). Since a very while (several month) most recent versions of Tidy and libtidy are available at openSUSE's software repository on http://repos.opensuse.org/Tidy/. Why didn't you take these? Please update your packages in openSUSE factory and use the newer versions out of the Software repository, so that these most recent versions will make it into final openSUSE 10.2. By the way: I want to have your ear, I want to propose, if it won't be attractive also to officially distribute the W3C Markup Validator (http://validator.w3.org/) with openSUSE on a regulary basis. Debian Etch and Fedora Core do this as well, these packages are part of the core distribution. It's in the W3 Consortium interest to spread the validator, having the benefit in mind, that local installed validators can keep the traffic to http://validator.w3.org/ in an affordable shape. The Validator packages are optimized for use on a local host/local net. Most recent W3C Validator packages for openSUSE are available at openSUSE's software repository on http://repos.opensuse.org/validators/ . Recent version is 0.7.3. There will be an official update to version 0.7.4 on Tuesday, november 14th. I have allready prepared packages of this new version, they are waiting to be shipped. I will feed the openSUSE Build System with 0.7.4 sources, as soon as the official W3C valiator website has been updated to this new release. Thanks in advance, Sierk Bornemann Sierk Bornemann | Germany e-mail: sierkb[at]gmx.de, bornemann[at]users.sourceforge.net URL: http://sierkbornemann.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 3

[opensuse-packaging] How to build for SLES9 SP3?
by Anders Norrbring 12 Nov '06

12 Nov '06

I use the latest build script as adviced by Ludwig last week, but I can't get SLES9 SP3 to build, don't know if it's my mistake, or a script problem. What I did; Copied all SLES9 GA CDs to a directory, added to script - build works. Copied the three SP3 CDs to the same location, overwriting the old versions - build doesn't work. The result for my first try is; "expansion error nothing provides sed needed by sendmail" Then I looked for sed; /iscsi/Archives/SuSE/sles9-i586/sles/suse/src/sed-4.0.9-31.1.src.rpm /iscsi/Archives/SuSE/sles9-i586/sles/suse/i586/sed-4.0.9-31.1.i586.rpm The files are there... -- Anders Norrbring Norrbring Consulting

1 0

[opensuse-packaging] Firestarter and suse 10.1 ATTN: David Bolt
by struth 07 Nov '06

07 Nov '06

I am trying to track down David Bolt through this list as I sa in the archives that he had got suse 10.1 and firestarter to work together. The below is a copy of my post to a forum:- I have been having problems getting Firestarter to work well with 10.1. I have tried the 9.? rpm and it seemed to act as a firewall ok but the events page never had anything in it. So I went to try and install it from source but the config kept telling me that I was missing old gnome files. Is there any advance on the firestarter and 10.1 front? Or can someone point to a better firewall that works fine with 10.1? The YAST one that is included, I can't get to allow specific addresses and I don't really want to learn all about iptables. Thanx for your time, spence

2 1

[opensuse-packaging] Update source breaks it all..
by Anders Norrbring 07 Nov '06

07 Nov '06

I just added a source for updates, mirrored locally and I've run createrepo on the dir. So, I added it in the config like this: url_suse="file:/iscsi/Archives/SuSE/inst_source/10.1" url_updates="file:/iscsi/Archives/SuSE/inst_source/10.1_up" add_sources="suse updates" So, then I tried to do a build, and this came out (hundreds of lines deleted).. root dir set to /store3/build.root.10.1-x86_64 running from system no ATTENTION: this is a one way ticket. Resetting this to true has not effect! initializing installation sources ... initializing target ... rebuilding RPM database ..................................................... ok reading RPM database ........................................................ ok Known sources: 0: [x] SUSE Linux 10.1 (file:/iscsi/Archives/SuSE/inst_source/10.1) 1: [x] file:/iscsi/Archives/SuSE/inst_source/10.1_up/ (file:/iscsi/Archives/SuSE/inst_source/10.1_up) [autorefresh] debug disabled 90 packages to install unresolvable dependencies: *** Conflicts *** Name: /bin/sh(*) Edition: EDITION-UNSPEC Referers: aaa_base-10.1-41 requires /bin/sh, Not-Available: any Name: /bin/bash(*) Edition: EDITION-UNSPEC Referers: aaa_base-10.1-41 requires /bin/bash, bind-utils-9.3.2-17 requires /bin/bash, groff-1.18.1.1-29 requires /bin/bash, less-394-12 requires /bin/bash, module-init-tools-3. 2.2-32.13 requires /bin/bash, perl-5.8.8-12 requires /bin/bash, pwdutils-3.0.7.1-17 requires /bin/bash, rpm-4.4.2-43.4 requires /bin/bash, util-linux-2.12r-35 requires /bin/bash Not-Available: any Ideas please.... -- Anders Norrbring Norrbring Consulting

4 16

[opensuse-packaging] Different Target-Distributions
by Dominique Leuenberger 07 Nov '06

07 Nov '06

hi, I'm packaging some of my RPMs in the buildService, others I can't put there for different reasons. For the latter, I'm using the build sh Script from openSUSE BS. Is there something like a DIST-TARGET to be defined or does this solely depend on the RPMs I offer it for the installation? ($BUILD_RPMS)? osc offers a feature like this, but I guess osc is not usable without putting the packages in the BS repositories, right? Thanks Dominique

1 0

[opensuse-packaging] Ubuntu Packages
by Dominique Leuenberger 01 Nov '06

01 Nov '06

Hi everybody, I know, I'm on the absolutely wrong mailinglist for the question, but OTOH, not that wrong: I am using a lot the build - script from openSUSE:Tools to create RPMs lately, mainly to distribute several softs not in the BS. Now, a friend asked me if I could also create a package for his Ubuntu Installation... Ubunut, being Debian based, uses .DEB - Packages. Is there an easy way for me to do this? Best would be by the possibility of continue to use the build script and the .spec files, as I'm quiet familiar with this by now. Or will I have to get some completely new environment to get this finally up and running for him? Regards, Dominique

1 0