January 2008 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Re: Novell ID's for OSC Plugins
by Rodrigo Moya 14 Jan '08

14 Jan '08

Hi (sorry for the late answer) On Wed, 2007-11-28 at 18:09 +0100, Dr. Peter Poeml wrote: > Hi, > > thank you for your contributions! > > On Wed, Nov 28, 2007 at 04:01:25PM +0100, Adrian Schröter wrote: > > On Wednesday 28 November 2007 00:57:23 wrote JP Rosevear: > > > Hi Adrian, the two novell id's are "rodrigomoya" and "maw" for the osc > > > plugin developers. > > > > both have been added to the openSUSE svn. Please tell, if you want to get also > > commit mails for the svn. > > > > Checkout with > > > > svn co https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice > > > > Peter, can you define a directory where osc plugins should get submitted ? > > I'd suggest either a new directory > trunk/buildservice/src/clientlib/python/osc-plugins > or a subdirectory > trunk/buildservice/src/clientlib/python/osc/osc/plugins or > trunk/buildservice/src/clientlib/python/osc/osc-plugins > > IMO, one of the latter makes sense if the plugins should be > installed/packaged by default, together with osc. But then they could > just as well be implemented directly in osc, I guess. > > But if the plugins are something which is not generally useful, or > should not be enabled by default, they should probably go into a > separate directory (the former directory I suggested). > ok, so here's the list of the plugins we already have, for discussion of what should be included now and what should wait: * osc-createspec: creates a .spec file from a set of templates. Right now, we only have 'base', which creates a very basic .spec file, and 'gnome'. We should have similar templates for KDE/java/python/whatever-based apps, etc * osc-linkdereference: dereferences a linked package. I think this mostly works ok, so should be mostly ready to add to the buildservice SVN. Michael? * osc-listpatches: lists patches for a set of packages. It displays summaries of all packages and their patches. This is mostly ready for inclusion. * osc-patchlint: lint for patches, following the guidelines at: http://en.opensuse.org/GNOME/Patches . These have been reviewed within the opensuse-gnome team. Is this useful outside of GNOME? Could we have these (or something similar) guidelines for the whole distro? * osc-rewritespec: organize and rewrite parts of .spec files, like ordering the Patch* lines. This is still incomplete. * osc-deps: showd dependencies of a package. Incomplete * osc-editchanges: like autobuild's 'vc'. Incomplete * osc-mergefrom: merge 2 packages, not ready yet, although it might almost be. Michael? * osc-speclint: lint for .spec files. It's mostly working, so should be mostly ready for inclusion. what do you think? -- Rodrigo Moya <rodrigo(a)novell.com> --------------------------------------------------------------------- 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] Local BS after build is succeeded, it is scheduled again.
by Oliver Bengs 12 Jan '08

12 Jan '08

Hello all, Yesterday, I updated my local installation from 0.1.1 to 0.5. I am building the packages in a chroot envroiment. The packages succeeded, but the scheduler wouldn't get it. I got the following error after the build: rpc failed: socket write: Connection reset by peer I saw this message in the screen session from the worker. If I interpreted it correct, then the worker cannot send the package to the server, because there is no rpc socket. kind regards -- Oliver Bengs Key fingerprint = 8F45 91CA 4038 41D3 2FF7 8A65 D3A3 3358 A16E A024 http://jacklab.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] Problems with publishing and _aggregate in the science and home:werner2101 repo
by Werner Hoch 12 Jan '08

12 Jan '08

Hi all, I've some problems with the repos I'm working in: https://build.opensuse.org/project/monitor?project=home%3Awerner2101 https://build.opensuse.org/project/monitor?project=science Problem 1: publishing of build packages I've updated a few packages (geda-*, ...) but they don't appear in the download area. For example: all geda-* packages should have version 1.2.1: http://download.opensuse.org/repositories/home:/werner2101/openSUSE_10.3/x8… The latest published packages have the date 20071226 and older. Problem 2: _aggregate --> blocked I've aggregated some packages from science in home:werner2101 and vice versa. All aggregated packages are marked as blocked. Problem 3: no source uploaded In the science repo, the package kicad does not build. It tells that there's no source, but the source packages are there. Any clue, what's wrong in the repos? Regards and happy new year. Werner --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] Fedora8: have choice for text-www-browser needed by docbook-utils: lynx elinks w3m
by Ben Martin 11 Jan '08

11 Jan '08

As per http://en.opensuse.org/Build_Service/Tips_and_Tricks#Expansion_errors Perhaps using the default of lynx?

3 2

[opensuse-buildservice] different buildinfo for factory
by Marcus Hüwe 11 Jan '08

11 Jan '08

Hi, is it intended that factory's buildinfo xml file differs from other suse versions? In contrast to e.g. openSUSE:10.2 or openSUSE:10.3 the "bdep"-nodes in the factory buildinfo xml miss some attributes like "version", "release" and "arch". Example: - factory: <bdep name="aaa_base" preinstall="1" runscripts="1" notmeta="1" project="openSUSE:Factory" repository="standard" /> - opensuse 10.2: <bdep name="aaa_base" preinstall="1" runscripts="1" notmeta="1" version="10.2" release="38" arch="i586" project="openSUSE:10.2" repository="standard" /> Marcus --------------------------------------------------------------------- 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] osc RPM package
by Dirk Stoecker 11 Jan '08

11 Jan '08

Hello, the osc tool has following requirement: Error: you need build.rpm with version 2007.3.12 or newer. See http://download.opensuse.org/repositories/openSUSE:/Tools/ Please add this as Requires: to the osc RPM. 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

4 4

[opensuse-buildservice] webclient patch
by Dirk Stoecker 11 Jan '08

11 Jan '08

Hello, attached is a little patch to the webpage for status monitor: a) adding sorting b) removed redundant stuff due to new design Ciao -- http://www.dstoecker.eu/ (PGP key available)

2 1

[opensuse-buildservice] reporting bugs against buildservice projects/packages now possible
by Andreas Bauer 11 Jan '08

11 Jan '08

Hi all, I just enabled the link to bugzilla in the OBS webclient. It uses a new role called 'bugowner' to determine the assignee of a reported bug. Bugowner roles can be given by using the [Add User] link in the webclient, or adding another <person/> element using osc. As soon as a bugowner is set, a link called [Report Bug] appears below the description on the project/package pages. Clicking this link will open the bugzilla new bug form with product, category and assignee preset to the (hopefully) correct values. Packages inherit the bugowner role from their project like the maintainer role. The role is not propagated through namespaces though. It is possible to set more than one bugowners, although currently it doesn't make much sense. A single assignee is picked more or less randomly from the available ones. Comments welcome, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 14

[opensuse-buildservice] byacc-1.9-20mdk problem with update-alternatives
by Peter Nixon 11 Jan '08

11 Jan '08

byacc-1.9-20mdk seems to have a problem: installing byacc-1.9-20mdk /var/tmp/rpm-tmp.2603: line 1: /usr/sbin/update-alternatives: No such file or directory error: %post(byacc-1.9-20mdk.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! This causes any packages that require byacc to not build in Mandriva_2007 Cheers -- 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

2 1

[opensuse-buildservice] Publishing to non-oss repository?
by Jasem Mutlaq 11 Jan '08

11 Jan '08

Hello, After the build service, what's the procedure to submit and publish the packages on openSUSE official non-oss repository? Anyone specific to contact? Regards, Jasem --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1