August 2007 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Release number overwritten by build server?
by Michel Salim 21 Aug '07

21 Aug '07

Hello, Is there a way to tell the buildserver to use the release number specified in the spec file? When building a package imported from another repository it automatically adds '.1' to the release number, which is fine, but if I override the .spec file with one of my own, shouldn't the revision number in the new spec be used? (e.g. home:msylvan/pidgin -- the last build I did, I overrode the revision number to 4.1 -- Factory's was 4 -- and ended up with RPMs revision 9.1. I think I might have built 8.1 and 7.1 before, when I was sourcing pidgin from home:sdrahn instead of Factory, and the build server might have remembered the old revision numbers) Thanks, -- Michel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] redundancy between pkg.dsc and debial.control?
by John Pye 21 Aug '07

21 Aug '07

Hi all Is there anything that can be done in Build Service to eliminate the redundancy of the package .dsc and debian.control files? Specifically, I have 'Build-Depends' fields in both of these and Build Service seems to be using the package .dsc file to perform the pre-build package installations, but then dpkg-buildpackage (or whatever is used internally) seems to be doing a check using the information in the debian.control file. My (fairly limited) experience of Debian packaging had led me to believe that the '.dsc' file is normally a resultant file, rather than an input that the user needs to generate. I wonder why Build Service has chosen to use the .dsc file in its implementation? What, if any, is the information present in the .dsc file that can not be obtaining from any of the other must-have debian/* files? Cheers JP --------------------------------------------------------------------- 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] package substitution for older products
by Cristian Rodriguez R. 20 Aug '07

20 Aug '07

Hi: Currenly, the following Substitutions needs to be applied to the OBS configs to avoid tons of %if 's %if 0%{?suse_version} < 1030 Substitute: libpcap-devel libpcap Substitute: libelf-devel libelf %endif Will be nice if someone can do this globally, Cheers. Cristian.

6 8

[opensuse-buildservice] osc release with new features
by Dr. Peter Poeml 20 Aug '07

20 Aug '07

Hi, Short changelog: - new "search" command - new "meta" command - initial support for commit messages - new "log" command (commit log) Full changelog: - added initial search support (some ideas are taken from the webclient): * when searching a package/project it is also possible to search for the search term in the <title /> and <description /> elements of a package/project. * show only exact matches - new meta command, replacing editmeta, editprj, createprj, editpac, createpac, edituser. Can either show existing meta, or edit it (--edit), or upload content (--file). Fix metadata change detection, which no longer relies on the timestamp of the temporary file. - log: - renamed previous "log" command to "buildlog" (short: bl) - implementing a log command to review the commit log - commit: - commit: implemented -m and -F option for the commit message. NOTE: if -m is used, osc uses a different mode of uploading files and commit them, namely the way which is currently documented in the api. So far, osc was uploading each file separately through the old backward compatible way. This way of committing can also be forced with do_commits = 1 in .oscrc. - other changes: - api now sends HTTP/1.1 400 Bad Request for invalid xml. Thus, show the reply body because it contains helpful info. - if PUT on metadata fails with a 500, and http_debug is True, print out the body of the server reply - improved exception handling in some places - updatepacmetafromspec: read spec files in utf-8, or whatever the preferred encoding is in the locale Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

8 28

[opensuse-buildservice] osc missing features
by Dirk Stoecker 20 Aug '07

20 Aug '07

Hello, during the usage of osc in last time I found 2 features missing: a) When I'm e.g. in my home project I can't use osc ci -"mxxx" to checkin all the changes in the subprojects. Why? b) osc build cannot be used to simulate BuildService builds: I would wish following option - When I'm in a package, the third argument with the specfile can be omitted and the build builds the package. Including following: 1) Getting all relevant files needed for this including the _link files 2) Applying patches like on buildservice 3) Build using the locally modified working copy c) Passing a package name as third argument should have same effect as b). Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 7

[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] important packages sources missing in openSUSE:Factory
by Stanislav Brabec 20 Aug '07

20 Aug '07

Hallo. I have just encountered many missing important packages in the openSUSE:Factory sources. For example: freetype2 libxml2 libxslt libgalago libgalago-gtk nvtv It seems, that all these packages are of type "one source repository, more spec files" in the Autobuild sources repository. I have a shell script, which could help with mirroring of such packages using osc link. I used it for mirroring of GNOME:UNSTABLE in past. Feel free to contact me if you are interested. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Mandriva 2007 byacc problem..
by Peter Nixon 20 Aug '07

20 Aug '07

installing byacc-1.9-18mdk /var/tmp/rpm-tmp.37816: line 1: /usr/sbin/update-alternatives: No such file or directory error: %post(byacc-1.9-18mdk.i586) scriptlet failed, exit status 127 mount: can't find / in /etc/fstab or /etc/mtab /bin/bash: halt: command not found Kernel panic - not syncing: Attempted to kill init! -- Peter Nixon http://peternixon.net/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Debian packaging convention on Build Service
by John Pye 20 Aug '07

20 Aug '07

Hi all I've previously asked a question about this but didn't get any bites. I would like to know what the reasoning is for the use of 'packagename.dsc' files on Build Service. As far as I can tell, the Debian equivalent of 'packagename.spec' is a set of several files, starting with these three: 1. debian.changes 2. debian.rules 3. debian.control These correspond, as I understand it, to (1) %changelog, (2) %build and %install sections, and (3) the package headers including 'Requires' and '%description' etc. As far as I can tell, the packagename.dsc file is produced by the build process in the same way that RPM produces a .src.rpm file. In other words, it is a by-product of the build, not one of the source files. You can generate the .dsc file from the above three files, but not the other way around. There are some more files required for debian packaging in some cases, for which purpose the 'debian.tar.gz' mechanism provided by Build Service seems to be quite satisfactory. I would propose that before the Build Service evolves too far, it might be worth considering revising the way that Debian packages are built here, for consistency in the approach across different distros. Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] expansion error: "nothing provides ${mypackage}"
by Ciro Iriarte 19 Aug '07

19 Aug '07

Hi, just added a new package that needs another package already present on my home project, but adding it to the BuildRequires of the new one gives me Expansion error, any thoughts? Regards, Ciro --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3