June 2006 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Mandriva / gcc-java
by Daniel Bornkessel 09 Jun '06

09 Jun '06

Hi. Mandriva has an expansion error on gcc-java ... I was told from a Mandriva developer that it has the same name and is on the normal distro (not jpackage tree). Could it be added? Thanks, -- Daniel Bornkessel Tel: +49 911 740 53 161 Novell :: SUSE R&D :: Internal Tools / Java Packaging ______________________________________________________________________ :wq

2 1

[opensuse-buildservice] SLES 9 target added
by Adrian Schröter 07 Jun '06

07 Jun '06

Hi, jfyi, a new project got added which can be used to create packages for SLES 9. The SUSE:SLES-9 repositories do contain all files from SLES9 with SP3 updates and also all packages from the official SDK. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian(a)suse.de --------------------------------------------------------------------- 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] Usability: list of failed packages
by Christian Boltz 07 Jun '06

07 Jun '06

Hello, possible usability improvement #2 for the web UI: Currently, it's hard to get a quick overview which of your packages failed building. You have to search the failures like easter eggs :-/ Real-world example: try to find out which of the KDE3 packages in [1] caused the expansion error... Current situation / problem: The project page [1] shows the number of suceeded and failed packages per build repository. If you want to know _which package_ failed building (which is the most important information here), you have to click each package separately [2] and check the status. This is really annoying when you have lots of packages in your project. Possible enhancement / solution: I can imagine several solutions: a) add a "[show build results]" link to the Action column of the Build Repositories table - the target page should show the results per package in the selected repository (OK / failed / expansion error) b) in the "packages" list, add some icon (like a red "X") on failed packages to indicate which package failed building on one or more repositories c) implement both a) and b) because both variants would be useful: a) displays the result _per repository_ ("what fails on SUSE 10.1?") b) displays the result _per package_ ("why does this package fail?") Opinions? Regards, Christian Boltz [1] like http://build.opensuse.org/project/show?project=KDE%3AKDE3 [2] like http://build.opensuse.org/package/show?package=kdebindings3-java&project=KD… (as always: the last one in the list failed. Murphy says it's the other way round if you start at the bottom ;-) -- Development is still fast. First I said it went from Ferrari to Lada, but that is not true. It went from Space Shuttle to Ferrari... slower...but still extremely fast. [Azerion in opensuse-factory] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org

3 2

[opensuse-buildservice] How to remove a target?
by Richard Bos 07 Jun '06

07 Jun '06

I have added a target to my project without name. It is now listed as 'standard', not so very descriptive. However, there seems to be no option to remove or rename a target. Question: is it possible to remove a target? If not could one of the buildservice administrators remove that target for me, please? See http://build.opensuse.org/project/show?project=home%3Arbos (to be removed target 'standard') -- TIA, Richard Bos Without a home the journey is endless --------------------------------------------------------------------- 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] Usability: renaming packages
by Christian Boltz 06 Jun '06

06 Jun '06

Hello, possible usability improvement #1 for the web UI: Currently, it's impossible to rename a package [1] in the build service. Current situation / problem: As already said, you can't rename a project. Instead, you have to delete the package, create a new one and upload all files again :-( Possible enhancement / solution: Add a "package name" field to the "edit package information" page. Opinions? Regards, Christian Boltz [1] "package" means the buildservice-internal package name [2]. It does _not_ mean the filename of the generated RPM which is a spec-file issue. [2] like "Fontlinge" in the headline of http://build.opensuse.org/package/show?package=Fontlinge&project=home%3Acbo… -- Im Handbuch? Auch wenn SuSE sie primär beilegt um mehr Versandkosten zu bezahlen und die Holzwirtschaft anzukurbeln sind sie doch manchmal ganz praktisch zum nachschlagen. [Manfred Tremmel in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org

1 0

Namespaces
by Marcus Rueckert 06 Jun '06

06 Jun '06

hi, on irc we had a discussion about adding some logical namespaces. It was started by looking for the right place for a php project. we now agreed on having a "server:" namespace. the first proposed projects in that namespace we see: server:apache (the former Apache project) server:mail (exim and home:choeger:postfix could be moved there) server:ftp server:php (php project, and php extensions, and my hardened php package) server:dns (i will move my pdns, mydns, nsd packages there. maybe the bind and dnsmasq package could move there aswell?:) ) It would be nice to have a server:voip aswell. peter nixon has some packages in that area iirc. :) The jpackage projects are moved into the Java: namespace. Some people might ask: why dont you just move php into the apache project. The answer is pretty short: Because it makes its impossible to build newer php against older apache versions. with the new layout we can add server:apache:<somedist> as build target to the php project aswell as the plain suse distros. :) So in long term i would suggest to join such logical project instead of having multiple "mixed purpose projects". if you want to add a package to such a project please contact the project owner on this list. keep up the good work everyone darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org

12 34

RE: [opensuse-buildservice] Re: Namespaces
by Bernard Li 06 Jun '06

06 Jun '06

Hi Jonh: The issue with "+" in the filename is already filed in bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=153725 Cheers, Bernard ________________________________ From: Jonh Arson [mailto:jonharson@gmail.com] Sent: Mon 05/06/2006 20:58 To: opensuse-buildservice(a)opensuse.org Subject: Re: [opensuse-buildservice] Re: Namespaces On Mon, 2006-06-05 at 21:10 +0200, Marcus Rueckert wrote: > On 2006-06-05 20:52:23 +0200, Cornelius Schumacher wrote: > > On Monday 05 June 2006 19:14, Richard Bos wrote: > > > > > > Including ":"? I think it is still possible to change the namespace > > > seperator to something else than ":". This to prevent problems with > > > programs like rsync.... > > > > I agree that we should try to avoid as many problems we can by choosing a > > neutral namespace separator for the project names. Alternatives to ":" could > > be the already mentioned "_" or "+" or possibly "." or "-". Looking at the > > current project names only "+" wouldn't need any changes to existing project > > names. > > > > So what do you like better (using four existing projects as examples and > > making character replacements where required): > > > > we should define some rules that ban the seperator from package names > aswell. and that will be hard. in that regard ":" was good. as projects > barely use it in their names, unlike "_", "-" or "+". (the plus sign is > forbidden by the buildserivce atm anyway.) Speaking about it, i tried uploading gtk+-2.8.18.tar.gz2 and the filename always get cropped to just gtk, those namespace thingy or whatever are really gonna be annoying if you use common char... what about ~ > i wonder if we just should force > > ns/project/package > > and stuff all projects without an explicit namespace into "unsorted" or > something like that. then we wouldnt need some special namespace marker > > anyway i think if rsync fells over the 2nd ":" in the url it is > definitely a sign for a broken url parser in rsync. > > darix > --------------------------------------------------------------------- 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] Project server:telephony Status Monitor
by Peter Nixon 06 Jun '06

06 Jun '06

http://build.opensuse.org/project/monitor?project=server%3Atelephony For some reason the Status Monitor on my new project is not working (It also appears to be not building any packages) -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

4 3

[opensuse-buildservice] Setting up a local instance of the build service
by Cory Aitchison 06 Jun '06

06 Jun '06

Are there any instructions on setting up and testing a local version of the build service? There is some functionality that I'd like to add but need a local instance first. Regards, Cory Aitchison --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org

3 2

[opensuse-buildservice] builderror in the buildserver for apt client
by Richard Bos 03 Jun '06

03 Jun '06

question about a builderror in buildserver for the apt client. The package builds fine on my home system, but the buildserver configure script fails with: checking for RPM libraries... -lrpm -lrpmdb -lrpmio -lz -lbz2 -lpopt ./configure: line 21210: syntax error near unexpected token `LIBXML2,libxml-2.0' ./configure: line 21210: `PKG_CHECK_MODULES(LIBXML2,libxml-2.0 >= 2.4)' error: Bad exit status from /var/tmp/rpm-tmp.60842 (%build) The pkgconfig libxml2 file is deliverd by: > rpm -qf /usr/lib/pkgconfig/libxml-2.0.pc libxml2-devel-2.6.23-14 Which is added as a buildrequired to the specfile. What am I missing that the buildserver fails to build this package? PS: is the suse specfile hint "# usedforbuild" still used during the build, or should it all be put in the Buildrequires specfile directive? Build log at: http://build.opensuse.org/package/live_build_log?package=apt&arch=i586&proj… Project page at: http://build.opensuse.org/package/show?package=apt&project=home%3Arbos -- TIA, Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice-help(a)opensuse.org

2 3