Page 1 of 2

OpenSuse build service rpms

Posted: 24 Jul 2007, 22:16
by Agon
Currently available packages:
--> Spring 0.75b2
-> Binary, source, debug
Stable release.

--> Spring build 4165
-> Binary, source, debug
Warning unstable release.

--> SpringLobby 502
-> Binary, source, debug
Warning unstable release more informations at http://spring.clan-sy.com/phpbb/viewtopic.php?t=10371

Distribution / architecture support:
openSUSE_10.2
- i586
- x86_64
SUSE_Linux_10.1
- i586
- x86_64
SUSE_Linux_10.0
- i586
- x86_64
SLE 10
- i586
- x86_64

Only SpringLobby:
openSuse factory (Currently in developing distribution)
- i586
- x86_64
Fedora_7
- i586
- x86_64
Fedora_6
- i586
Fedora_5
- i586
Mandriva_2006
- i586

Link: http://download.opensuse.org/repositori ... :/accAgon/

Spring_unstable and SpringLobby packages will be updated each hour if I´m online.
*Edit* We are working on a better way to update the source. Currently auto updates disabled. *Edit*

Posted: 24 Jul 2007, 22:37
by Relative
I don't use Suse, but good job Agon.

Posted: 24 Jul 2007, 23:12
by Agon
Thanks. If some on uses one of this distribution: Ubuntu, SLE, Debian, Fedora or Mandriva and has some interest in making rpm packages he can contact me.

Edit: svn build 4089 released.

Posted: 25 Jul 2007, 10:42
by nicko117
Agon, what about the original repository made by cwh ?

http://software.opensuse.org/download/g ... :/realtime

It's not an "attack" i'ts just to understand why you had to make a new one ?

Another question, how does it works for version update ? Where does buildservice take the sources ? does it access to an external svn repo ?

(That's maybe the reason why you made a new repo, sources update must be done manually ? unless the internal svn from buildservice is used ...)

Posted: 25 Jul 2007, 16:26
by Tim Blokdijk
I had played around with RedHad before but Suse was my first "real" Linux OS, used it for quite a while but I moved to Debian and then to Ubuntu.. But great to see you hacking on it. :-)

Posted: 25 Jul 2007, 20:57
by Agon
Cwh does not update the Spring version, I don´t know why. Maybe he forget to look at the Spring webpage.
The opensuse build service is at an alpha state and they say before someone work outside his home folder he should try to make some packages and get some skill.
And I don´t want to damage the games:rts:spring repository.
Another reason why I use me home repository are the svn releases. And tryouts of new packages like splitting the AI/ Map/ Lobby Client and so on.

The source for stable releases is taken from the tarballs from the news page.
For the svn releases I check out the spring svn newest version and make my own tarball. Currently the buildbot does not make svn tarballs :cry: .
Currently I need to make the updates manually, opensuse build service will support this later.

The up-to-date stable version is 0.75b2 from my repo. games:rts:spring has 0.74b3.
You can easily update you spring version from 0.74b3 to 0.75b2.
Or if you think 0.75b2 does not work downgrade to 0.74b3.

It´s your choose.

Posted: 03 Aug 2007, 03:24
by Agon
Spring SVN updated to 4123.

Posted: 03 Aug 2007, 11:07
by BrainDamage
list of deps for mandriva 2007
Requires: libdevil1, libboost1, freetype, libSDL1.2 >= 1.2.0, python >= 2.4, libglew1.3, zlib1
BuildRequires: libdevil1-devel, libboost1-devel,freetype , libSDL1.2-devel >= 1.2.0, python >= 2.4, libglew1.3-devel, gcc-c++, scons, zip, zlib1-devel
i've intentionally left out the java packages as they aren't in the repositories for mandriva 2007, you'll have to get the official rpm from sun

if you want, i can correct myself your spec file and send you a patch

PS: AFAIK the builservice is capable of maintaining .deb builds too, how about you get togheter with yokoza1 and maintain a unique repository wich will contain builds for most of the distros?

Posted: 03 Aug 2007, 13:06
by Agon
You can write a patch. The problem is I don´t know much about .spec files or making rpm packages. The problem with Java is I´m using a rpm packages from openSuse build service that was build with the source from the sun packages.
I could make a workaround with uploading the sun java packages unpacking them and installing them. In the svn version spring rpm should not require Java, maybe I forgot to fix this in spring stable. I will look at it.
Support for more than openSuse distros would be very good. The openSuse build service is very good. But still not perfect and under develop, it´s a alpha.
Features of the service: Multiple distro support, rpm meta files or yum for getting informations about available packages for the package manager and automatic builds.
Automatic source updates will come but I don´t know when.

For the svn spring rpm packages I tried to checkout the svn source and to create a tarball on the openSuse build service and changing the version with "svn info http(s):**" but the problem is I don´t know how to make such a script in shell to split a string.

I don´t know how yokoza1 makes packages, but if he wants to join the one man team, no problems.
Help would be very helpfully.

Edit:
Spring-stable was correct, no dependence on java.
Spring-unstable was not correct, had dependence on java.
Now both packages will have no dependence on java. It will take some time to build the packages.

Edit02:
Builds done, now without java requires.
Checked it in smart.

Posted: 04 Aug 2007, 20:17
by Agon
Spring_unstable updated to revision 4136. <- Currently building, but should work.
Added SpringLobby revision 453.
Packages available for openSuse Factory / openSuse 10.2 / Suse Linux 10.1 / Suse Linux 10.0

For debian_etch / xUbuntu 7.04/6.04 / Mandriva_2006 / SLE 10 / SLES 10 I need support from someone who know how to make .spec files for this distributions.

Edit:
Building done.

Edit02:
SpringLobby updated to 472 and debug rpm is now available.

Edit03:
Spring_unstable updated to 4140, debug rpm now available for spring and spring_unstable.
Changed version/name check for spring_unstable, now only spring or spring_unstable can be installed. Unstable releases now look like this: 0.75b2.4140.7.1 (Spring public release).(spring svn revision).(buildnumber)

deb package

Posted: 05 Aug 2007, 19:25
by argt
I can try to make deb package if this helps. Is anyone working on .deb package already ? I don't mind doing the job alone, just want to know what has been done.
(and I'm not running ubuntu, so I might need some help from Ubuntu users to make proper deb for this distro).

Posted: 05 Aug 2007, 19:30
by imbaczek
yokozar AFAIK is making .debs.

Posted: 05 Aug 2007, 19:57
by Agon
Who wants to help me, he can help me.
Making .debs with openSuse build service is a bit tricky, but a documentation for that is available. The most problems are currently the dependency's. OpenSuse distributions have more installed packages than xUbuntu, Fedora, Debian and so on. I need to send a email with all this required packages that this packages should be included distribution based, means they would be installed as standard.

SpringLobby updated to 474.
Packages for Spring and Spring unstable now available for SLE 10.

Edit:
Now the spring_unstable and SpringLobby packages will be updated each hour if I´m online.

Posted: 13 Aug 2007, 17:00
by Agon
*Update*
Spring_unstabled updated.
SpringLobby updated.
SpringLobby has now Fedora 5/6/7 rpms.

*Update*
Spring_unstable updated.
Changed /bin/spring to /usr/games/spring in Spring_unstable.
Changed /bin/springlobby to /usr/bin in SpringLobby.
SpringLobby has now Mandriva_2006 packages.

Posted: 26 Aug 2007, 03:11
by Frans
hey, when I install your rpm, i notice there is no unitsync.so
now thats gonna be a problem for me... lol.

Posted: 26 Aug 2007, 03:12
by AF
It essentially rules out any use of AFLobby or SpringLobby with these rpms

Posted: 26 Aug 2007, 03:14
by Relative
You could compile the unitsync from svn for now.

Posted: 26 Aug 2007, 14:44
by Agon
There is a unitsync.so it is installed to /usr/$lib/unitsync.so .
You need to configure SpringLobby to this folder. Don´t forget to replace $lib with lib or lib64.

I know the rpm packages are not perfect but they work and I use them with out any problem.

Posted: 26 Aug 2007, 19:55
by AF
Why is unitsync.so placed there? Seems like a somewhat unnecessary deviation aswell as complicating the user install process and any documentation written for it.

I'd at least add in a wheres_unitsync.so.txt explaining this.

Posted: 26 Aug 2007, 20:53
by Agon
A normal Linux user should know this.
Every .so library is saved in /usr/$lib/ or in /$lib or in some other $lib path.