October 2006 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Staled RPMs and Repositories
by Dominique Leuenberger 16 Oct '06

16 Oct '06

Hi, In my home directory, there are some Directories, that should be deleted (as well as outdated RPMs). - The directory for Debian_etch is empty and not used - The directory for SuSE Linux 10.0 is empty and not used - The directory for SuSE_Factory contains packages (same package, different versions?) Even though, the repository Factory is no longer activated in my home directory (I want to avoid the build of UFO:AI Data Package multiple times... so only one REPO active for the moment. Until I get fully known to OSC to enter the MetaData... btw: will this feature come also through the webinterface? That would be GREAT Thanks for 'cleaning up' and telling me how to avoid it in the future. Dominique

1 0

[opensuse-buildservice] Re: [RFC] Release numbers and the Kernel project
by Jan Blunck 16 Oct '06

16 Oct '06

On Sun, Oct 15, Andreas Gruenbacher wrote: > On Sunday 15 October 2006 13:53, Jan Blunck wrote: > > Therefore my proposal for fixing this issue: a buildservice package link > > should inherit the release number from its source package. All changes > > inside the linked package (additional patches, files, ...) should be added > > to this release number. > > I don't understand what you mean exactly: do you mean that when there are > changes other than plainly linking the package, then the release number > should be <linked-to-package-release-number> + 1, and if there are no > changes, the package should keep the original > <linked-to-package-release-number>? Correct. From talking to mls it seems that it is somehow a requirement that the linked packages have a higher release number if they have changes in. Therefore you can make sure that the package with the changes is installed if you have both available. > I'm not sure that we want to hardwire the way how release numbers are computed > for linked packages; I could imagine that we sometimes want to use the same > release numbers for the linked-from and linked-to packages, and in other > cases we want to keep the release numbers independent. Yes, but so far nobody came up with a usecase. > In the kernel case in particular, we need to associate each particular > check-in (i.e., each set of package sources) with a unique identifier; this > is sufficient so that all the packages will refer to the correct paths > in /usr/src/* and /lib/modules/*. Without it, building external kernel > modules would break. This is assured by increasing the release number of kernel-source package with every check-in. The internal pathnames of all packages refer to the release number of the kernel-dummy package. The problem I'm talking about are the external visible release numbers of the packages in the project. They differ although the packages are related to each other. --------------------------------------------------------------------- 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] iChain switch succeeded :)
by Adrian Schröter 13 Oct '06

13 Oct '06

Hi, the build service now runs via iChain. This means that you need to use your bugzilla/www.opensuse.org password from now on. The command line users need also to update the osc tool to version 0.9 to get access to it again. 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

5 11

[opensuse-buildservice] openSUSE build service goes iChain
by Adrian Schröter 12 Oct '06

12 Oct '06

Hi, we will switch tomorrow at 15:00 UTC the authentification system of the build service to iChain. This means that we will have some hickups around this time, esp until the DNS records have been updated. This does NOT mean that the build service will be open for everybody, but it does mean that you can use the same account/password as for the wiki also for the build service. We will also introduce https for the api, which means that you also need a new osc tool with the URL (or you can reconfigure it manually). 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 4

[opensuse-buildservice] Can't update x86_64 from KDE3 build service repos
by David Jopson 12 Oct '06

12 Oct '06

Hi all, I was directed here to try and get help with a problem I encountered today. If this is the wrong place to ask for help, please let me know where I mgiht be able to go for assistance. I am using SuSE 10.0 x86_64 with KDE 3.5 updated from 3.4 via the build service. In the past I have been able to get updates using YaST without issue, but today when I tried to update to KDE 3.5.5 it wouldn't work and YaST wants to downgrade me to KDE 3.4.2 because of failed dependencies. The problem is YaST is only seeing the i586 rpms from the repo. Clicking on the "Versions" tab within YaST's Software Update window confirmed this fact. I have refreshed, deleted, and re-entered the build service repos in YaST several times but it just doesn't want to find the x86_64 rpms. Someone at suseforums.net suggested it may have something to do with the fact that /opt/kde3/share/apps/krpmview/media.1/products contains: / SuSE-Linux-user-i386 0.0.0 as opposed to something x86_64 related. I don't know how valid that idea is since I have had no problems updating in the past, but I am not an expert by any means. Does anyone have any ideas on how I might fix this problem? Thanks in advance, Dave --------------------------------------------------------------------- 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] adding maintainer
by Pavel Nemec 12 Oct '06

12 Oct '06

Hi, could some add me as maintainer to KDE:Community games:strategy:realtime nick: pnemec Thank you -- Pavel Nemec package-maintainer http://en.opensuse.org/Czech_Packagers_Team --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: pnemec(a)suse.cz Lihovarska 1060/12 tel:+420 2 9654 2373 190 00 Praha 9 fax:+420 2 9654 2374 Ceska republika http://www.suse.cz

3 3

[opensuse-buildservice] Directory Delete please
by Peter Nixon 11 Oct '06

11 Oct '06

Can one of the admins please delete the following directories as I am no longer targeting them: http://software.opensuse.org/download/server:/telephony/Fedora_Extras_4/ http://software.opensuse.org/download/server:/telephony/SUSE_Linux_9.3/ Thanks -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc

1 0

Re: [opensuse-buildservice] Another Build possible error...
by Cameron Seader 10 Oct '06

10 Oct '06

How can i debug this? On Mon, 2006-10-02 at 12:07 -0600, Cameron Seader wrote: > How can i fix this in my Build? > > On Fri, 2006-09-29 at 18:10 +0200, Andreas Jaeger wrote: > > > "Cameron Seader" <cseader(a)novell.com> writes: > > > > > Greetings, > > > > > > What do you make of this? > > > > > > objdump: /var/tmp/monopod-0.6-build/usr/lib/monopod/Monopod.exe: File format > > > is ambiguous > > > > > > objdump: Matching formats: efi-app-ia32 pei-i386 > > > objdump: /var/tmp/monopod-0.6-build/usr/lib/monopod/entagged-sharp.dll: File format is ambiguous > > > objdump: Matching formats: efi-app-ia32 pei-i386 > > > > > > Is this something to be concerned about? I have uploaded two different sources and i get the same thing, it used to build without these messages. > > > What are these messages telling me? > > > > > > -Cameron > > > > This is factory? > > > > Could be new binutils that break our mono tests, we might need > > --target=pei-i386 to the script that calculates the mono > > dependencies (if that's the place where it fails)... > > > > Andreas > > > > > > Novell, Inc. Software for the Open Enterprise™ http://www.novell.com

3 3

[opensuse-buildservice] buildservice down
by Andreas Bauer 10 Oct '06

10 Oct '06

Hi, api.opensuse.org is currently not working for an unknown reason. We're investigating the problem. I'll post a mail if it is working again. Sorry for the problems. -- Andreas Bauer - Novell - SUSE Internal Tools --------------------------------------------------------------------- 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] Proposal for project in root namespace: GNOME:*
by Stanislav Brabec 10 Oct '06

10 Oct '06

Hallo Build Service maintainers. We are just discussing on creating of Build Service projects for GNOME. Possible structure is: GNOME:GNOME-UNSTABLE GNOME:GNOME216 GNOME:EXTRAS Maybe there will be more projects or the final structure will be different. Please comment suggested letter case and use "-" or "_" - whether to use GNOME:216, GNOME:GNOME216, GNOME:Gnome216, GNOME:GNOME-2.16 or GNOME:GNOME_2_16 to conform naming scheme of other projects in the Build Service. -- 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

7 18

[opensuse-buildservice] enable packages for a certain target
by Christoph Thiel 09 Oct '06

09 Oct '06

Hi there, wouldn't it make sense to add an <enable> tag along the lines of the <disable> tag that we already introduced some time ago? Being able to disable all targets with one line and then add just the targets that you want to build a package for, would be nice to have IMO. It's getting quite annoying to disable package that you just need on old dists, when you add new targets to your project. Comments, criticism, better ideas? ;) Regards, Christoph --------------------------------------------------------------------- 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] Proposal: move "cfengine" from home-project to "systemsmanagement:cfengine"
by Matthias G. Eckermann 09 Oct '06

09 Oct '06

Hi all, again me:-) any objections to move 'cfengine' to this more prominent place? so short MgE -- Voluminous documentation | Matthias G. Eckermann <mge(a)arcor.de> is part of the problem | Marienburger Str. 5A not part of the solution | 10405 Berlin (Tom DeMarco) | phone +49-30-44315730 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

Re: [opensuse-buildservice] [RFC] Blob & Conquer
by Dominique Leuenberger 06 Oct '06

06 Oct '06

>>> Reply on 06-10-2006 13:43:43 <<<> On Fri, Oct 06, 2006 at 11:56:14AM +0200, Dominique Leuenberger wrote: > > SuSE 10.1 and the binary of UFO:AI (not installable, as the question > for > > the data file, which is 160MB has not been answered on the > mailinglist > > yet. Most probably, I won't be able to provide UFO:AI as I initially > > wished, due to it's size. > > Maybe it can be packaged (built) in a way that it is at least not built > twentyfold, when only one rpm is suitable for more than one arch, or > even for different distribution version? (Sounds entirely possible for > a > noarch package.) > > Then it wouldn't seem so daunting, and with a few hundred Megabytes it > wouldn't actually use more space than (I guess) Apache which is built > on > 10 targets or so. > > The package meta understands 'disable' tags to disable build on certain > targets. Peter, thank you very much for these information, of course it is absolutely no problem to provide a single Data-RPM for ALL distributions. I have two questions on this topic now: - Can you point me out on how to 'disable' the build on different distributions (or even better: disable all except one?) And then more a endu-ser related question: Let's assume I build the Data-RPM for openSUSE 10.1 (as noarch of course), then if somebody subscribes the 10.2 repo, there is no problem, as the ufoai rpm has a 'requires ufai-data' statement, it will be found. But if somebody subscribes the 10.2 repository, the data-package would not be found. Any suggestions for a filesystem link in this case? The concern is especially important for people that are using rug / yast / 'whatever else than plain rpm' to be able to install the package as well. Regards, Dominique TMF is a global management and accounting outsourcing firm with 72 offices in 56 countries and over 1,800 professionals (September 2006). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses.

2 1

Re: [opensuse-buildservice] [RFC] Blob & Conquer
by Dominique Leuenberger 06 Oct '06

06 Oct '06

>>> Reply on 06-10-2006 11:50:39 <<<> Hi Dominique > On Friday 06 October 2006 10:34, Dominique Leuenberger wrote: > > Hi everybody, > > > > I'm getting more and more passionate player in the linux world and > > would like to share the games as RPMs with everybody. > Great > > > > So: if nowhere else at the moment 'Blob and Conquer' is being built, > I > > would start making packages for it. On the webpage, it's possible to > > download an RPM, but 'only' generic x86 of course. > > > > Comments are welcome! > > Dominique > I just want to ask if you are building those great games in right > project. I > think they should be located in games:*** name space, so everybody could > find > them. Pavel, Up to know I build everything in my Home-Project (as I started only a few weeks ago). under home:dimstar there is currently SuperTuxKart 0.2 available for SuSE 10.1 and the binary of UFO:AI (not installable, as the question for the data file, which is 160MB has not been answered on the mailinglist yet. Most probably, I won't be able to provide UFO:AI as I initially wished, due to it's size. For the last question about NoGravity, there were also no replies, thus I guess it's not built yet. For 'Blob & Conquer' I did not do anything yet (excpet playing it :-) ) as I did not want to do any double work. Dominique

4 3

[opensuse-buildservice] Fwd: building sometimes fails with 'su: incorrect password'
by Jiri Dluhos 06 Oct '06

06 Oct '06

Hello everyone, In last two or three days, I get random fails with building my packages (the LSB:Spec-3.1 project) with error message 'su: incorrect password'. This most often happens with the SL10.0 build. Please, could you (anyone ;-) ) check if some of the building hosts is not misconfigured? Thank you in advance, Best regards, Jiri Dluhos -- Jiri Dluhos, LSB development jdluhos(a)suse.cz SUSE LINUX, s.r.o. http://www.suse.cz Lihovarska 1060/12 +420 296 542 384 190 00 Praha 9 Czech Republic --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] [RFC] Blob & Conquer
by Dominique Leuenberger 06 Oct '06

06 Oct '06

Hi everybody, I'm getting more and more passionate player in the linux world and would like to share the games as RPMs with everybody. So: if nowhere else at the moment 'Blob and Conquer' is being built, I would start making packages for it. On the webpage, it's possible to download an RPM, but 'only' generic x86 of course. Comments are welcome! Dominique

2 1

[opensuse-buildservice] suggestion: limited trigger rebuild
by Andreas Jellinghaus 06 Oct '06

06 Oct '06

ok, I'm doing baby steps to get somewhere, and of course the first few versions of the spec file will be buggy. so I wonder: wouldn't it save resources on build.opensuse.org if I could first trigger a rebuild only on some plattform, wait if that succeeds, and only then trigger rebuild for other plattforms (e.g. the rest / all)? currently "trigger rebuild" will affect all build targets if I understand right and might be create a huge load on your system. Regards, Andreas --------------------------------------------------------------------- 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] starting to use the bulid-service
by Detlef Steuer 06 Oct '06

06 Oct '06

Hi, I´m building rpms for the statistics software R (www.r-project.org) for Suse-Linux since version 7.3 or so and would like to use the buildservice in the future. What I couldn´t find in an hour´s work on opensuse.org was some "getting started with the buildservice". Most probably I just missed a pointer and so would be grateful for a link. Since R is on the wishlist for integration with standard OpenSuse, I would also volunteer to work on this issue. (Such integration would be met by great interest in the R-community.) regards, Detlef Steuer --------------------------------------------------------------------- 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 noarch packages (systemmanagement:misc/puppet)
by Martin Vuk 05 Oct '06

05 Oct '06

hi, while buildnig noarch packages like systemmanagement:misc/puppet only the x86_64 variant is available in the repo after the build is finished. The build report says both are build, but I guess x86_64 packages just overrides the i586 in noarch dir. The problem is that x86_64 uses /usr/lib64/ruby which is not in ruby libpath on i586 system. So obviously i568 and x86_64 packages differ, althow they suppose to be arch independant. How schould I solve this? Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

Re: [opensuse-buildservice] begging for an account
by Dominique Leuenberger 04 Oct '06

04 Oct '06

>>> Reply on 04-10-2006 16:55:00 <<<> On 2006-10-04 13:57:46 +0200, Detlef Steuer wrote: > > According to the Build_Service_Tutorial (thx Dominique!) step 0 is to > ask for an account here. > > Please! > > this is not admin(a)opensuse.org > For protection of Detlef: on the Build_Service_Tutorial there is REALLY written you should address to this mailinglist for an account. [Quote] To make use of the Build Service you first need an account to login. ;-) As you can see on the Roadmap iChain authentification is currently not enabled (with that you can use your openSUSE account to log into the Build Service - cool). So currently you have to write an email to the buildservice-mailinglist and ask for an account. [/quote] Cheers, Dominique --------------------------------------------------------------------- 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] Announcement: New packages Beryl Project
by Jigish Gohil 04 Oct '06

04 Oct '06

I have been maintainging Compiz community packages on BS for a long time now. Recently the community has announced a fork of compiz - the Beryl Project, I would be maintaining those packages here at the build service. First packages should be released in couple of days. If anyone wants to test the 'preview' the packages are here: http://software.opensuse.org/download/home:/cyberorg/ Once released they would be available from here: http://software.opensuse.org/download/Compiz-Quinn/ You would require beryl-* and emerald packages to run beryl. Launch it with 'beryl-manager'. Cheers! Jigish -- CyberOrg Info Novell & IBM Partner 7 FF Unad Deep, Tower A Susen Tarsali Road Vadodara 390 009 T. +91 265 3042956 M +91 9898092956 Web. http://www.cyberorg.info --------------------------------------------------------------------- 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] Packages no longer existing / repositories not used
by Dominique Leuenberger 04 Oct '06

04 Oct '06

Hi, While testing some packages, I also added repositories for different other platforms. After deleting them, they seem to remain active for access via software.opensuse.org/download Is this normal behavious? Also the packages inside have not all been deleted, thus causing errors if I add for example the repository for SUSE-Factroy to my homedir (dimstar) again. Most packages don't get build now for factory. What did I do completely wrong and how to avoid it in the future? Also: can I exclude different thins from being built for a distribution like Fedora for example but still having the fedora repository for other packages? I'm sorry for the mess I might have created on the server. Dominique

1 0

Re: [opensuse-buildservice] starting to use the bulid-service
by Dominique Leuenberger 04 Oct '06

04 Oct '06

>>> Reply on 04-10-2006 14:50:03 <<<> Hi, > > I*m building rpms for the statistics software R (www.r-project.org) for > > Suse-Linux since version 7.3 or so and would like to use the > buildservice in the future. What I couldn*t find in an hour*s work on > opensuse.org was some "getting started with the buildservice". Most > probably I just missed a pointer and so would be grateful for a link. > Detlef, I used this site (http://en.opensuse.org/Build_Service_Tutorial) as a starter to get known to the system (not to long ago). And it seems to me the BS is really easy to handle. For account creatin, I think Adrian should be your man. Dominique

3 2

[opensuse-buildservice] Announcement: Beryl 0.1.0 release
by Jigish Gohil 04 Oct '06

04 Oct '06

Hello community, Yesterday we announced release of Beryl 0.1.0. Beryl is a fork of compiz maintained by the community at www.beryl-project.org. Beryl and Compiz gives the bling to your desktop making it fun to use. The packages are available for SUSE 10.1/SLE10 and openSUSE Factory/10.2. Here are the links to the packages. 10.1/SLE10: http://software.opensuse.org/download/X11:/XGL/SUSE_Linux_10.1/ 10.2/Factory: http://software.opensuse.org/download/X11:/XGL/SUSE_Factory/ 10.1/SLE10 running xorg7: http://software.opensuse.org/download/X11:/XGL:/10.1xorg7/10.1xorg7/ Apart from the Beryl packages the repository also contains upto date Compiz packages from Freedesktop git which can now use gnome themes and gnome-theme-manager. Compiz/Beryl can be run without XGL or AIGLX on xorg 7.1 and NVIDIA's new beta drivers. Install all the beryl packages including emerald and emerald-themes, launch by running beryl-manager. More information would be available here: http://forum.beryl-project.org/topic-4853-beryl-suse-packages File bugs/suggestions etc here: http://bugs.beryl-project.org/ Enjoy! -J ______________ CyberOrg --------------------------------------------------------------------- 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] Game from Wishlist / already done somewhere? !!NOSIGG!!
by Dominique Leuenberger 03 Oct '06

03 Oct '06

Hi, I'm just going a bit through the wishlists we have and, if nobody else already has packages for it, I would start building them first in my home, then if interest should be there, offering themalso for 'higher' repos. So: is already somebody packaging [nogravity description copied from Wishlist] NoGravity A 3D arcade space shooter. No Gravity is a fantastic and futuristic universe made of five intergalactic worlds. An arcade type game with great playability, where it is easy to plunge into space battles against spacefighters, space stations and more! [end description] Otherwise, if you agree, I'll try to package it for 10.1 (as I can test it with 10.1) and later versions. Dominique TMF is a global management and accounting outsourcing firm with 72 offices in 56 countries and over 1,800 professionals (September 2006). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses.

1 0