April 2007 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] linking to packages built with the build service
by Robert Schiele 06 Sep '07

06 Sep '07

Hello! Currently there is no way to link to a package built on the build service because if we do so this link will break on every rebuild since the release number will change. Because of that I recommmend to automatically create symbolic links without the version number as we have in the update directories on ftp.suse.com. For example: zypper.rpm -> zypper-0.6.15-0.1.i586.rpm If we do so we can just link to http://software.opensuse.com/download/.../packagename.rpm. This link will never break due to an automatic rebuild. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."

6 13

[opensuse-buildservice] Factory java-devel expansion error
by Peter Nixon 20 Aug '07

20 Aug '07

SUSE_Factory expansion error have choice for java-devel: java-1_4_2-cacao-devel java-1_4_2-gcj-compat-devel -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 7

[opensuse-buildservice] RFC: osc support for SLES9 / Python 2.3
by Dr. Peter Poeml 13 Aug '07

13 Aug '07

SLES9 ships with Python 2.3. With my latest code changes, I noticed that I changed things in a way incompatible to Python 2.3 (using decorators). (I basically noticed this because byte-compiling failed according to the build log, although the build didn't actually fail due to that. I saw it by pure luck.) This can easily be fixed, so I removed the decorators and started to test osc on SLES9, and found more problems on the way. Python 2.3 didn't have a cookielib module, and it is not easy to add it because parts of it live integrated in the urllib2 module. Still, it is straightforward to just skip cookie support if not available. But there were further problems, which prevent the current codebase from working with Python 2.3. I fixed some further issues, and got as far as to a working 'osc build'. However, the next problem I'm facing is that I can't commit files (gets an internal server error back), and since urllib2 is not as easy to debug as newer versions, I stopped there for now. Overall, the situation gives me the impression that osc hasn't been working on SLES9 lately, or maybe since a long time, and nobody did ever complain about it. The download statistics show 6 or 7 osc package downloads in the last 50 days for SLES9. What do you think. Is it worth pursuing this further? Or should we maybe simply no longer build osc for SLES9? All other platforms in the buildservice seem to have Python 2.4 or newer. Peter -- Allen Gewalten zum Trutz sich erhalten. SUSE LINUX Products GmbH Research & Development

1 1

[opensuse-buildservice] openSuse 10.2 and Truecrypt: Old version and wrong "summary"
by Johannes Kastl 13 May '07

13 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, I found out there is a repository containing truecrypt on the opensuse buildservice. So I installed it, and tried to mount my containers: Incorrect version of kernel module loaded - version 4.3 required So I visited truecrypt.org, and found a rpm package for version 4.3. Installed it, works. BUT: Why is this version not on the buildservice? And why do I get the following output when searching for truecrypt using apt: > SUSE 10.2 #apt search truecrypt > truecrypt-kmp-xen - Library for simple parsing and seeking of files and streams based on the Ogg file format > truecrypt-kmp-bigsmp - Library for simple parsing and seeking of files and streams based on the Ogg file format > truecrypt-kmp-default - Library for simple parsing and seeking of files and streams based on the Ogg file format > truecrypt-kmp-debug - Library for simple parsing and seeking of files and streams based on the Ogg file format > truecrypt-kmp-xenpae - Library for simple parsing and seeking of files and streams based on the Ogg file format Huh, Ogg files? What is wrong there? Im not sure where to complain about / tell people about this issue, so I thought buildservice might be right. CC the packager as well. > Name : truecrypt-kmp-default Relocations: (not relocatable) > Version : 4.2a_2.6.18.2_34 Vendor: openSUSE Build Service > Release : 7.1 Build Date: Di 23 Jan 2007 11:31:03 CET > Install Date: (not installed) Build Host: build02 > Group : System/Libraries Source RPM: truecrypt-4.2a-7.1.src.rpm > Size : 176682 License: TrueCrypt License Version 2.0 > Signature : DSA/SHA1, Di 23 Jan 2007 11:31:04 CET, Key ID 3b3011b76b9d6523 > URL : http://www.truecrypt.org > Summary : Library for simple parsing and seeking of files and streams based on the Ogg file format > Description : > TrueCrypt is a software system for establishing and maintaining an on-the-fly-encrypted volume (data storage device). > > On-the-fly encryption means that data are automatically encrypted or decrypted right before they are loaded or saved, without any user intervention. > No data stored on an encrypted volume can be read (decrypted) without using the correct password/keyfile(s) or correct encryption keys. > > Entire file system is encrypted (i.e., file names, folder names, contents of every file, and free space). > > Authors: > -------- > - TrueCrypt Foundation <ennead(a)truecrypt.org> > - Paul Le Roux > Distribution: security:privacy / openSUSE_10.2 Regards, OJ - -- Men of quality are not afraid of women for equality. (unknown) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFGNeLPMAex/QZx/TMRAgt4AJ9FCDcCKeeE+4Gij8XwCzClZcFh9gCfcBnx 0lzK6fsgNZtj3i2CdicYE+8= =Sag1 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 7

[opensuse-buildservice] preferred rpms and ccache
by Michael Wolf 09 May '07

09 May '07

Yo In home:maw, I have two packages which may be of interest to other people using the build service. First is a patched version of osc. It has two patches. One patch, pubkey-instructions.patch, is pretty straightforward, and I think it should be committed to svn. Another patch, preferred-rpms.patch, lets you run osc with the environment variable OSC_PREFERRED_RPMS set. This allows you to run builds with your own packages - it's useful when you update foo, and then get to work on bar, upon which foo depends. Sure, foo will be rebuilt automatically by the build service, but sometimes it takes a while; this way you can keep on working. As is, it's pretty hacky and kind of dumb (osc will download the packages needed to build your package even if that package already exists in your preferred rpms directory), but it might be useful to other people anyway. It's been very useful for me, at any rate. (Is there already a better way to do this? I couldn't find it...) Second is a patched version of ccache. This links /usr/local/bin/{gcc,cc,g++,c++} to /usr/bin/ccache. The result is that ccache is transparently invoked when building, no need modify your .spec or anything like that. Also, the default cache size is raised to 3G and ccache's directory goes into /.ccache. To use, you currently need my patched osc; put the ccache package into your preferred rpms directory and build away. At the risk of stating the obvious, I don't advise installing this package outside of osc build roots. Together, these make building large packages (such as firefox) and groups of many packages with lots of interdependencies (such as gnome) much faster. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 6

[opensuse-buildservice] Parser chokes on %if 0%{?suse_update_desktop_files:1}
by Pascal Bleser 02 May '07

02 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The parser doesn't seem to be able to catch %if 0%{?suse_update_desktop_files:1} Not that it's necessarily needed to be able to handle all the possible spec file notations with stuff like that but... is the limitation wrt knowing whether that macro is defined in /usr/lib/rpm/*, or with the notation 0%{xxx:1} ? 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.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGM9irr3NMWliFcXcRAvW3AJ9k7BKMq3HEQWp0r4cYLStc26jcnwCfVe1s i/fFIBcVeH42aTjK1+UgdiI= =3AJx -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Why are configure arguments of Fedora .spec files ignored ?
by Amilcar do Carmo Lucas 02 May '07

02 May '07

Hi all, I have a .spec file that works fine for all SuSE and Mandriva distros. http://build.opensuse.org/package/edit_file?file=KDevelop3.spec&package=KDe… But for fedora it always executes: + ./configure --host=x86_64-redhat-linux-gnu --build=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info Instead of doing what I typed in the .spec file: ./configure --disable-subversion \ --enable-new-ldflags \ --disable-dependency-tracking \ %if %{disable_gcc_check_and_hidden_visibility} --disable-gcc-hidden-visibility \ %endif --disable-rpath \ %if %{debug} == 0 --disable-debug \ --disable-warnings \ %endif %if %{final} --enable-final \ %endif --with-qtdoc-dir=%{_docdir}/qt-devel-%{qt_version}/html/ \ --with-kdelibsdoc-dir=%{_docdir}/HTML/en/kdelibs-apidocs/ \ --with-qt-libraries=$QTDIR/lib \ --with-extra-libs=%{_libdir} Why are Fedora's configure arguments hardcoded ? Why is it a fedora bug only ? Why to SuSE and Mandriva work fine ? Thanks, -- Amilcar Lucas KDevelop.org webmaster --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] expansion error: have choice for smtp_daemon needed by php5: exim sendmail postfix
by Cristian Rodriguez R. 01 May '07

01 May '07

Hi Folks: As current Factory "minimal installation" does not contain an MTA, I have added Requires: smtp_daemon as a dependency in the php5 package ( php mail() function requires sendmail binary to work) however, now everytime I build PHP extensions in the server:php_extension project.. I get. "expansion error have choice for smtp_daemon needed by php5: exim sendmail postfix" PHP extensions requires php5-devel (which Requires: php5) to build correclty outside the php tree, and this prompt is actually expected to show when the user is installing the package with a package manager (as I dont want to force people to choose a particular MTA, I just want a sendmail comaptible binary) however, in the buildservice I have no way to choose what mta to install and build fails.. will be nice if smtp_daemon is just mapped to postfix in the build hosts. Cya. Cristian.

1 1

[opensuse-buildservice] Buildservice stopped building for i586?
by Truth 30 Apr '07

30 Apr '07

Hi all, I started building my home:/Thruth/celestia this morning(UTC+8), and found that it didn't build i586 packages although x86_64 packages were seccessfully built. I modified and saved the spec and x86_64 building process started automatically as usually. But i586 packages, be it 10.2 10.1 or SLE 10, didn't start to build. They just kept still, labelled succedded, not even scheduled. At that time, there were only my x86_64 celestia packages and package M17N:handedict-SUSE_Factory - i586 building according to Build Service Status. So I retriggered all builds. x86_64 built again. But i586 still showed no change, satisfied to be succedded with the old version. I disabled all archs then enabled them all to retrigger. Once again, x86_64 were built nice but i586 did not change. Someone have a look at the bug please. Regards, Thruth --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] How to organize your obs?
by Leo Eraly 30 Apr '07

30 Apr '07

Hi, We now have our OBS running but we would like to have different repositories for testing and for production. How do you guys arrange this on your installations? e.g: I upload packageX with version 1.0 to my testing project, after some testing I want to make it available in the production project. After a while I upload a new version of packageX to my testing project but the version in the production repository should remain on version 1.0 untill I decide it can be replaced by the newer version. My idea was to link the packages from testing to production but I'm afraid this causes problems when uploading a new package to the testing project... Thanks in advance Leo -- Leo Eraly <leo at unstable dot be> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0