openSUSE Build Service November 2006

buildservice@lists.opensuse.org

47 participants
76 discussions

Re: [opensuse-buildservice] RFC: games:data

by Dominique Leuenberger

>>> Reply on 15-11-2006 13:07:19 <<<> On Wed, Nov 15, 2006 at 11:05:21AM +0100, Dominique Leuenberger wrote: > > Hello, > > > > are there any objections of creating the project games:data? > > > > The sole purpose would be to store DATA Blobs of Games (I'd start > > filling it with DATA of UFO:AI, RC6 to be released soon). > > The idea is to have inside only a SINGLE repository, with a name like > > 'GENERIC' > > > > This would allow to have the data file only built a single time. The > > disadvantage for the user (at the moment) is the need to subscribe to > > two repos for the game to come in. (also look at other posts from me > and > > Adrian on this topic). > > > > But I think that's still the better deal than having the Data blob (~ > > 160MB for UFO) built several times. > > > > Post your comments please. > > Looks ok to me. Against which repo/arch do you plan the packages in > games:data? How do you plan to name this %repo-%arch? I suggest to > link the packages in games:data in the project, where the non-data > package resides, and disable the build of them in this project to have > it somewhat self-documented, what we're doing here. > Stefan, The idea was to make a repository 'Generic' (name subject of discussion) (in the Webinterface, add repo, advances, name Generic and base it on SUSE 10.1/Standard) I'd only activate i586, but that's just to have it compile anything. The package anyhow is set as noarch. The link from the games:strategy:turn-based to the other is basically a good idea. Maybe I'll come back to you for some help with this (as I'm only able to access the webinterface at the moment, the possibilities are somewhat limited) Dominique

15 years, 7 months

[opensuse-buildservice] Need a BuildService account

by raghu gs

Hello Everybody I have a Novell keychain account, And i want to package some nifty gnome applications using opensuse buildservice, I didn't even ask or would create a separate folder, I just want put my packages created using buildservice in GNOME:/Community/, Expecting your reply Raddy

15 years, 7 months

[opensuse-buildservice] Re: Repositories below http://software.opensuse.org/download/games:/

by Dominique Leuenberger

>>> Reply on 14-11-2006 9:02:43 <<<> Am Wednesday 08 November 2006 16:03 schrieb Dominique Leuenberger: > > >>> Reply on 08-11-2006 17:02:11 <<<> Am Thursday 19 October 2006 > 13:06 > > > > schrieb Dominique Leuenberger: > > > We discussed to extend yum repos to support links to other repos as > > > well. > > > This means you add the amarok4 repo for example and this implicit > > > > adds > > > > > also > > > the KDE4 repo. When you remove amarok4 repo, the KDE4 repo > disappears > > > > as > > > > > well. > > > But this would be an extension to the current yum/rpm-md format > > > > which > > > > > needs > > > to be discussed (and proposed in a valid way) on the yum ml. > > > > > > I would be happy if someone could spend some time on this issue :) > > > > > > > don't misunderstand me: I like the split in this cattegory, and I > > > > > > think > > > > > > > it's important, but it would also be very interesting to have the > > > > possibility to subscribe only to one Repository (technically, it > > > > IS > > > > > > possible... remains just the question, if it can be implemented > on > > > > > > the > > > > > > > Build Service). > > > > Adrian, do you know if there is already something going on in this > > direction? > > I do not think so. > > > If not, I could try to work out something on the yum ml, trying to > feel > > if such a thing would be completely new idea or how far something > alike > > is already developed there. > > That would be great :) > > bye > adrian > Adrian, The people from YUM ML are more than unwilling to implement any new things inside YUM, they already claim it to be much to complicated :-) BUT: a solution came up, which is already implemented and based on the .repo files: Such a file CAN contain more than one Repository including all infos, like: [channelName] name=A sample repository baseurl=http://..../BinaryRepo/OS/Version gpgcheck=1 gpgkey=..... enabled=1 [channelName-data] name=A sample data repository baseurl=http://..../DataRepo/ gpgcheck=1 gpgkey=..... enabled=1 By adding the .repo file, both Repos would be added. This means, that we should try more to push the usage of these .repo files than subscribing directly to a channel. Do you know: can these repo files already be understood by rug/zmd/libzypp/yast ? Maybe a small enhancement on them, that when adding a repository they look for *.repo and interpred them (in case only a URL, without a .repo is given) And then one question for UFO:AI: I would like to move that one to Games:Strategy:turn-based (which has not been done due to this data-sharing problem). Can the Build-Server be configured to have a games:data repository and add that one as a 2nd repository in the .repo file of at least games:strategy:turn-based? Probably it could suite other games as well: I think Wesnoth, Torcs and so on also have unified DATA Files all over the repositories. So this one could be added to all games:* repos. Looing forward for a reply / comments Dominique

15 years, 7 months

Re: [opensuse-buildservice] release number for moved packages

by Dominique Leuenberger

>>> Reply on 10-11-2006 12:32:07 <<<> On Thu, Nov 09, 2006 at 11:25:29AM +0100, Dr. Peter Poeml wrote: > > If we move or copy a package from one project to another, what > happens > > to the release number? > > > > I suppose, it starts to count from the beginning. Is that correct? > > It starts with the release number contained in the specfile. > Hi, I guess that is a not-yet-implemented theorie. Up to now, I've never seen BS using my Release-Number inside a spec file, but always replacing it with n.1 / n+m.1 (or by retriggering n.o / n.o+1) But it would be nice if at least the spec file would be respected (as on a local build, the spec file is fully respected for this) Dominique

15 years, 7 months

[opensuse-buildservice] Rebuilding everything?

by Mauricio Teixeira (netmask)

Strange things happened overnight. When I woke up this morning and went checking my home project on the BS, I found out that every single package is being rebuilt. Even though some already finished, I still have 57 packages on 'scheduled' status, and 3 on 'blocked' (which I've never seen before on BS). Anyone knows what's happening? -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 7 months

[opensuse-buildservice] Add ipw2200 to drivers:wlan

by Mauricio Teixeira (netmask)

Hi! I've just build the most recent ipw2200 driver for 10.1, and I whish to know if there is any interest on having it on drives:wlan project. Thanks. -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 7 months

[opensuse-buildservice] New project: usr-local-bin

by James Ogley

Would there be any objections to me creating a new project 'usr-local-bin' for the packages that have historically formed the usr-local-bin project? -- James Ogley james(a)usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 7 months

Re: [opensuse-buildservice] release number for moved packages

by Dominique Leuenberger

>>> Reply on 10-11-2006 13:59:54 <<<> On 2006-11-10 11:34:02 +0100, Dominique Leuenberger wrote: > > >>> Reply on 10-11-2006 12:32:07 <<<> On Thu, Nov 09, 2006 at > > 11:25:29AM +0100, Dr. Peter Poeml wrote: > > > > If we move or copy a package from one project to another, what > > > happens > > > > to the release number? > > > > > > > > I suppose, it starts to count from the beginning. Is that > correct? > > > > > > It starts with the release number contained in the specfile. > > > > > > > Hi, > > > > I guess that is a not-yet-implemented theorie. Up to now, I've never > > seen BS using my Release-Number inside a spec file, but always > replacing > > it with n.1 / n+m.1 (or by retriggering n.o / n.o+1) > > > > But it would be nice if at least the spec file would be respected (as > > on a local build, the spec file is fully respected for this) > > i am getting tired to explain this. the buildservice _has_ to keep its > release number. if it would always honor the release number you could > get into the situation where you cant update your package as you have a > smaller release number. with the current way we guarantee your newly > build packages are always installable. Darix, In normal case, this is probably true, but in a case I just had, it was BAD: - I have a package in my home-repo, linked to an outside, public repo. - I modify a pkg in my home repo - as linking is not working in the BS, I have to delete the link in games:... - I recreate the link in games:... BS builds the package, starting with %{version}-1.1, even though the old package was 'already' at 1.2. So the only solution I had in this case was retriggering the build process twice to fix this. In my SPEC-File was written Release 2.1. You see, it might be a good choice to interpret the release in case it's a higher number compared to what BS is offering/suggesting. There ARE some pacckagers, that seem to think from time to time when they do something. Regards, Dominique

15 years, 7 months

[opensuse-buildservice] GNOME:* projects in Build Service: current status

by Stanislav Brabec

Hallo. GNOME projects have been finally created. Simple description follows. GNOME:STABLE: This project contains packages from the stable branch of GNOME. Current status: Initial sync was done. Will be synced with SuSE Linux FACTORY. No development here. Please send any changes to GNOME maintainers (sbrabec(a)suse.cz, rodrigo(a)novell.com, gekker(a)novell.com) and ask them to include them to factory. Each backport specific change must use %if %suse_version. GNOME:UNSTABLE: Testing of forthcoming GNOME version. Once it will be considered as stable, packages will be copied to GNOME:STABLE and further development will continue in GNOME:UNSTABLE. Current status: Independent development can be done here. No usable packages are here. If no packages will appear here soon, it is possible, that we will use this repository after 10.2 release for testing of move of whole (STABLE) GNOME to /usr. GNOME:Community: Repository for any related GNOME packages, opened for anybody, who wants to participate, with no connection to SuSE Linux releases. If anybody else is interested to become a maintainer, I can add him/her to all of these projects. Feel free to submit to any projects, but remember the sync policy. If you will do any successful change in the synced project, please don't forget to send the change to SuSE Linux GNOME maintainers. You will get confirmation about accepting it to FACTORY. There is not yet any policy about sync dates and times. I plan to do it manually at least for next few weeks. Please suggest any future policy (weekly, 2-3 times a week, daily, if package foo is building correctly in factory, anything else). Note: Maybe it is technically possible to check for changes from the last sync, but I am not sure, whether it is / it is not an effective way. -- 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

15 years, 7 months

[opensuse-buildservice] BS kernel for 10.1 needs upgrade

by Mauricio Teixeira (netmask)

The current kernel for SUSE 10.1 on BS is 2.6.16.13-4, while the most recent kernel it is 2.6.16.21-0.25. Is it possible to upgrade? -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

15 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service November 2006