November 2006 - openSUSE Build Service

[opensuse-buildservice] Factory java-devel expansion error
by Peter Nixon 20 Aug '07

20 Aug '07

SUSE_Factory expansion error have choice for java-devel: java-1_4_2-cacao-devel java-1_4_2-gcj-compat-devel -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc --------------------------------------------------------------------- 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] build03 broken?
by Thomas Anders 08 Dec '06

08 Dec '06

Last night's builds for the net-snmp project show a number of build failures for the various repos, all of them happening on build03 and all of them ending in md: stopping all md devices. System halted. Is build03 broken? +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 6

[opensuse-buildservice] Problem with BLAS / LAPACK libraries
by David Strozzi 05 Dec '06

05 Dec '06

Hi, There's a small problem with the linear algebra library BLAS and LAPACK in opensuse. These are Fortran libraries. I (and others) have trouble using the libraries with SciPy (python scientific computing package). The problem seems to be that different Fortran compilers use different symbol names for some output routines. When one compiles scipy, there are some Fortran routines that get compiled, I think with g77 by default (maybe not). You can compile and install scipy, but when you try importing it in python you get an error of undefined symbol _gfortran_st_write in the LAPACK library. I have the most recent blas and lapack opensuse builds (940). The official suse-type webpage I got these from say they were compiled with egcs, which is a. wrong (egcs merged back into gcc a long time ago) and b. ill-defined (since g77 and gfortran are both part of gcc). As you search the web, you see that it's part of the lore that "Suse's BLAS is buggy, you have to compile yourself." Not good for Suse! While I'm on it, it's not clear what implementation of BLAS opensuse uses. My guess is it's the reference implementation from lapack's page on netlib, which is not optimized. Better ones exist, like gotoBLAS. Maybe that can be made a suse package? At the least it would help if it were spelled out exactly which Fortran compiler was used to make opensuse's blas. If they can be compiled to allow multiple Fortran compilers to play nicely with them, even better. Cheers, David

2 4

[opensuse-buildservice] Is there a server problem (Error: can't get ............)
by Richard Bos 04 Dec '06

04 Dec '06

I get this output, after starting the build for wireshark: Putting files in AC_CONFIG_AUX_DIR, `..'. Error: can't get 'https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log?n…' HTTP Error 500: Internal Server Error Debugging output follows. url: https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log?n… response: [left out the debug output] And this for 10.1 Requires: wireshark = 0.99.4 Obsoletes: ethereal-devel Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/wireshark-0.99.4-build warning: Could not canonicalize hostname: build08 Wrote: /usr/src/packages/SRPMS/wireshark-0.99.4-7.1.src.rpm Wrote: /usr/src/packages/RPMS/x86_64/wireshark-0.99.4-7.1.x86_64.rpm Error: can't get 'https://api.opensuse.org/result/home:rbos/SL-10.1_x86_64/wireshark/x86_64/l…' HTTP Error 500: Internal Server Error [left out the debug output] # osc results wireshark> osc results SL-10.0_i586 i586 failed: https://api.opensuse.org/result/home:rbos/SL-10.0_i586/wireshark/i586/log SL-10.0_x86_64 x86_64 failed: https://api.opensuse.org/result/home:rbos/SL-10.0_x86_64/wireshark/x86_64/l… SL-10.1_i586 i586 succeeded SL-10.1_x86_64 x86_64 building SL-9.3_i586 i586 disabled SL-9.3_x86_64 x86_64 disabled SLES_9 x86_64 disabled SLES_9 i586 disabled SLE_10 x86_64 expansion error: nothing provides libadns-devel SLE_10 i586 expansion error: nothing provides libadns-devel Server problem? -- 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

3 4

[opensuse-buildservice] non-SuSE repos for x86_64?
by Thomas Anders 04 Dec '06

04 Dec '06

Am I correct to assume that the BS currently doesn't have any fedora/debian/ubuntu/mandriva repos for x86_64? Releasing spec files that haven't been tested on x86_64 is hardly acceptable these days. Can fedora/debian/ubuntu/mandriva repos (ordered according to my priorities) for x86_64 be added soon, please? +Thomas -- Thomas Anders (thomas.anders at blue-cable.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] local Fedora_Extras_5 build?
by Thomas Anders 04 Dec '06

04 Dec '06

Doing a local "osc build Fedora_Extras_5 i586 my.spec" currently fails with: - --- snip --- The following package could not be verified: /var/tmp/osbuild-packagecache/Fedora:Core5/standard/i386/SysVinit-2.86-2.2.2.i386.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#4f2a6fd2) - If the key is missing, install it first. For example, do the following as root: gpg --keyserver pgp.mit.edu --recv-keys 4f2a6fd2 gpg --armor --export 4f2a6fd2 > /root/keyfile-4f2a6fd2 rpm --import /root/keyfile-4f2a6fd2 Then, just start the build again. - --- snap --- Isn't this something that "osc build" should take care of for me? Otherwise, am I expected to run the mentioned commands manually in the chroot? Or am I missing something else? +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] Removing packages
by Jigish Gohil 30 Nov '06

30 Nov '06

Hi all Could there be some sort of system in place which informs if the package being deleted is linked by someone else? This way we can move the package from one project to another if the original packager does not want to maintain it. With many more packages and project cross linking might get quite complex, so if the package is linked by say 5 projects those links should also be preserved if the package is moved. I had linked intltool 0.35 from project jarpack, which is now deleted, that is why this suggestion. Cheers -J -- 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

1 0

[opensuse-buildservice] a
by Frederic 29 Nov '06

29 Nov '06

--------------------------------------------------------------------- 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] SLES9 ghostscript-library expansion error
by Peter Nixon 27 Nov '06

27 Nov '06

expansion error have choice for ghostscript_any needed by ghostscript-library: ghostscript-serv ghostscript-x11 Can this be solved on the BS or should I just add another "if" to my spec file? Regards -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Re: lapack
by Richard Guenther 27 Nov '06

27 Nov '06

(sorry for the lame reply, I'm not on os-bs and replying to a forward with attached body does not work for me - so, top-posting) First, for problems please file bugreports. Now, packages are always compiled with the system (fortran) compiler, which is gfortran since 10.0 (where do you get the impression from that it is built with g77? what is 'The official suse-type webpage' here?). The undefined symbol is because you need to link against libgfortran, so this looks like a scipy bug. "Suse's BLAS is buggy, you have to compile yourself." This is a very unspecific statement, I cannot help here. Yes, the lapack/blas is from netlib, not some optimized version. Hope this helps, Richard. ---- Hi, There's a small problem with the linear algebra library BLAS and LAPACK in opensuse.| These are Fortran libraries.| I (and others) have trouble using the libraries with SciPy (python scientific computing package).| The problem seems to be that different Fortran compilers use different symbol names for some output routines.| When one compiles scipy, there are some Fortran routines that get compiled, I think with g77 by default (maybe not).| You can compile and install scipy, but when you try importing it in python you get an error of undefined symbol _gfortran_st_write in the LAPACK library. I have the most recent blas and lapack opensuse builds (940).| The official suse-type webpage I got these from say they were compiled with egcs, which is a. wrong (egcs merged back into gcc a long time ago) and b. ill-defined (since g77 and gfortran are both part of gcc). As you search the web, you see that it's part of the lore that "Suse's BLAS is buggy, you have to compile yourself."| Not good for Suse! While I'm on it, it's not clear what implementation of BLAS opensuse uses.| My guess is it's the reference implementation from lapack's page on netlib, which is not optimized.| Better ones exist, like gotoBLAS.| Maybe that can be made a suse package? At the least it would help if it were spelled out exactly which Fortran compiler was used to make opensuse's blas.| If they can be compiled to allow multiple Fortran compilers to play nicely with them, even better. Cheers, David -- Richard Guenther <rguenther(a)suse.de> Novell / SUSE Labs --------------------------------------------------------------------- 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] Debian_Etch setup problem?
by Thomas Anders 25 Nov '06

25 Nov '06

Building on Debian_Etch in the BS currently fails for me with: -su: line 0: cd: /usr/src/packages/BUILD: No such file or directory (see https://api.opensuse.org/result/net-snmp/Debian_Etch/net-snmp-main-snapshot…) while a local build works perfectly fine. What's wrong? +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) --------------------------------------------------------------------- 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] how to carefully push a package
by Detlef Steuer 24 Nov '06

24 Nov '06

into inclusion in the main distribution? Are there defined milestones a packages must pass? (Besides a clean build, of course.) What are showstoppers? Is there a predefined way to work a package`s way up into OpenSuse? Or does the intention to include packages from BS into OpenSuse even exist? Is there some document that defines what should happen with BuildService´s packages in the long term? I´m asking because I get regular requests from the R community if it would be possible to include R on the Suse-CDs. Can anyone with more knowledge say anything about it? I´d be very happy to receive any hints. Regards, Detlef --------------------------------------------------------------------- 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] apologies
by James Tremblay 24 Nov '06

24 Nov '06

Gentlemen, I would like to apologize for my misstep in protocol. I have started a new project called "Education" http://en.opensuse.org/Education and I did not ask here first. Please accept my apologies for this and take a moment to look at the project. I am very new to all this and I need\would like your help. I need guidance, ideas, contributions and experienced maintainers. Thanks for all your patience James --------------------------------------------------------------------- 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] Expansion issues
by Andrew Wafaa 23 Nov '06

23 Nov '06

In trying to build on SLE10/SLES9/SUSE9.3 I'm getting to expansion errors for a couple of missing packages. These are check and doxygen for SLE10, check for SLES9/SUSE9.3. I also need to specify a different version of autoconf for Factory (require 2.59). Could someone recommend the best way to overcome these issues please? Many thanks, Andy -- Andrew Wafaa Tel: +44 (0)7974 074546 e-Mail: andrew(a)forcev.net http://www.forcev.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] xUbuntu_6.06: expansion error: have choice for awk needed by base-files: mawk gawk
by Thomas Anders 23 Nov '06

23 Nov '06

Building on xUbuntu_6.06 fails for me with: expansion error: have choice for awk needed by base-files: mawk gawk Is this a problem with my .dsc (Project net-snmp, package net-snmp-main-snapshot) or a BS bug? +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 6

[opensuse-buildservice] Other Platforms than (open)SUSE in BS
by Dominique Leuenberger 22 Nov '06

22 Nov '06

hi, In home: repos and on some other spaces, it's common to also find Mandriva and Fedora Repositories (badly not for the latest releases, so onlt FC5 and Mandriva 2006). Who is deciding if they also get added to games:*, server:* and so on? Is it just, when I want it, I add it? And I fix whatever spec file of whatever package I would like to build? Then one more question: What construction can I use to work around the different naming conventions for the distros? something like %if %suse BuildRequires: alsa-devel %else if %mandriva buildRequires: libalsa-devel %endif Are there some specific implementations for this? Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

Re: [opensuse-buildservice] How to "stack" projects?
by Detlef Steuer 22 Nov '06

22 Nov '06

thx to all for the quick answers. I tried to build in home:dsteuer first where building failed because of "R not in path". Probably I did not look hard enough to identify the real problem and concluded that R-base was missing. Anyway: some spec-file modifications later it just works. Thx again, Detlef On Wed, 22 Nov 2006 11:09:42 +0100 "Dominique Leuenberger" <Dominique.Leuenberger(a)TMF-Group.com> wrote: > > > >>> Reply on 22-11-2006 12:08:02 <<< > > > Hi, > > > > I*ve the package R-base successfully built in home:dsteuer. > > Now I want to add a project named "littler", which has > BuildRequires: > > R-base. > > R-base naturally is not in any of the repositories I want to build > > littler for. > > > > How can I do that? Is it possible? I guess yes, but I can*t figure > it > > out. > > > > The two pakcages have to be in the same project, and then you can > easily give BuildRequires: r-base to the 2nd package. > While r-type is not ready, you should see status 'blocked' on the other > package. > > I have the same with some games, depending on SDL_net, that needed a > fix and another depended on cmake in a newer version (that is now > luckily gone). > > 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] How to "stack" projects?
by Detlef Steuer 22 Nov '06

22 Nov '06

Hi, I´ve the package R-base successfully built in home:dsteuer. Now I want to add a project named "littler", which has BuildRequires: R-base. R-base naturally is not in any of the repositories I want to build littler for. How can I do that? Is it possible? I guess yes, but I can´t figure it out. Detlef --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 9

[opensuse-buildservice] webclient error
by Nashif, Anas 22 Nov '06

22 Nov '06

Hi, I am trying to access a package in my home project without success, I get the following error: OpenSUSE Webclient Error: Error Details: Errorcode: Message: Backend Error: 404 Details: excess hash entries: workerid The package I am trying to access is wsmancli. Any idea what is going wrong here? Anas

3 2

Re: [opensuse-buildservice] x86_64 %files
by Detlef Reichelt 22 Nov '06

22 Nov '06

Hi Andrew, Andrew Wafaa <andrew(a)forcev.net> schrieb: >I am trying to build Hula, and so far I am only able to build for SUSE 10.1 >i586. x86_64 is failing due to a missing entry in %files, which I am aware >of. hm, don't see a missing file for x86_64, have a look on my hula.rpm in my bs-home: http://software.opensuse.org/download/home:/drcux/SUSE_Linux_10.1/ Detlef --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

Re: [opensuse-buildservice] How to "stack" projects?
by Dominique Leuenberger 22 Nov '06

22 Nov '06

>>> Reply on 22-11-2006 12:08:02 <<< > Hi, > > I*ve the package R-base successfully built in home:dsteuer. > Now I want to add a project named "littler", which has BuildRequires: > R-base. > R-base naturally is not in any of the repositories I want to build > littler for. > > How can I do that? Is it possible? I guess yes, but I can*t figure it > out. > The two pakcages have to be in the same project, and then you can easily give BuildRequires: r-base to the 2nd package. While r-type is not ready, you should see status 'blocked' on the other package. I have the same with some games, depending on SDL_net, that needed a fix and another depended on cmake in a newer version (that is now luckily gone). 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] zhu3d
by Pavel Nemec 22 Nov '06

22 Nov '06

Hi, i packed zhu3d - which is viewer of mathematical functions. See: http://kde-apps.org/content/show.php?content=43071 I have package in my home directory home:pnemec for SL10.0 10.1 and factory I`d like to move it to science zhu3d need qt4 (libqt4 - KDE:Qt) I am not sure how to add resources only for one package if this is possible? Please add me as maintainer to science project if you want me add zhu3d to it. Thanks Pavel -- Pavel Nemec Software Engineer https://wiki.innerweb.novell.com/index.php/SLEPOS --------------------------------------------------------------------- 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 5

[opensuse-buildservice] x86_64 %files
by Andrew Wafaa 21 Nov '06

21 Nov '06

Hi and hopefully I want anger too many people with my question. I am trying to build Hula, and so far I am only able to build for SUSE 10.1 i586. x86_64 is failing due to a missing entry in %files, which I am aware of. My question is this: How do I specify the requirement in %files for x86_64 so that I can build both i586 and x86_64 architectures from the same spec file. Many thanks, Andy -- Andrew Wafaa, RHCT Tel: +44 (0)7974 074546 e-Mail: andrew(a)forcev.net http://www.forcev.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 5

[opensuse-buildservice] python-devel issues
by Andrew Wafaa 21 Nov '06

21 Nov '06

Thanks to Michael and Daniel, I am now able to build on x86_64 but this has now thrown up an issue. I am now getting the following error from the build service which is what I get on my own box: configure: error: Dragonfly requires python-devel, or python built with shared library support (--enable-shared) I have specified python-devel already, so what else do I need to do? Prior to changing my spec to show the different architecture %files I didn't get this error. Regards, Andy -- Andrew Wafaa Tel: +44 (0)7974 074546 e-Mail: andrew(a)forcev.net http://www.forcev.net --------------------------------------------------------------------- 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] problem with build in BS
by Pavel Nemec 21 Nov '06

21 Nov '06

I have strange problem with my package Reveal (home:pnemec Reveal) package use qmake to build himself and it compile libraries together in install phase !!! In local build (osc build) everything is ok. But in build service it faild with this message: + make install g++ -o /var/tmp/reveal-1.2.-build/usr/bin/Reveal tmp/config.o tmp/reveal.o ... [snip] .... -lpthread mkdir: cannot create directory `/usr/share/Reveal/': Permission denied make: *** [install_credits] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.25280 (%install) As i stated in local build everything is writed and installed into right directory under /var/tmp/reveal-1.2.-build/ why not in build in BS ??? Pavel -- Pavel Nemec Software Engineer https://wiki.innerweb.novell.com/index.php/SLEPOS --------------------------------------------------------------------- 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

2 2

[opensuse-buildservice] more newby questions: project / package structure?
by Andreas Jellinghaus 20 Nov '06

20 Nov '06

Hi, how are projects and packages structured? is it a fixed "one name for the project and then one for the package" system, or are further subdirs possible? I wonder about this: recent discussions with rpm experts have shown me that merging several spec files into one only creates a horrible maintainence hell. also they have compelling arguments, that one rpm for all distributions was something they tried for years with lots of work, and it never worked well. so I see as best solution to have codenames (e.g. fc3,fc4,fc5, sles9, sles10, oss10.0, dapper, edgy, etch, sarge, ...) and for each distribution *.spec.$codename or *.diff.gz.$codename. but this would require work on the build system side, and I get the impression noone wants that. the alternative from my side would be per distro packages. e.g. instead of "openct" I could have packages "openct.fc" and "openct.os" and "openct.sles" and "openct.sarge" and so on, upload spec files for each. this wouldn't require changes in the code base, and give me the flexibility I need, so I can simply build new packages for my open source projects, with minimal changes to the last spec file the distribution provides. but that way the list of packages might grow very long. is it possible to structure projects/packages a different way (i.e. path mechanism, no flat one project, one package subdir structure)? Regards, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 13

[opensuse-buildservice] Translation table SUSE / Mandriva - Repos
by Dominique Leuenberger 20 Nov '06

20 Nov '06

Hi, It seems there is sort of a translation table to replace the BuildRequires from openSUSE to Mandriva. At least, when entering BuildRequires, many -mdk.rpms get installed with similiar names, but not exactly what I typed (or the get stripped off) An example for the latter case: I have a .spec file with BuildRequires: libvorbis-devel This one does not get a failure in Mandriva_2006 build (so probably got stripped out). Unfortunately, it did not get replaced with libvorbis0-devel (the Mandriva name of the lib) Is this translation table visible? Can there work be done on it? And another thing: How could I get support for Mandriva 2007 inside the BS? Is this somehow possible? Planned for the future? Regards, 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] Re: [opensuse] Favorite E-mail Clients
by Pavel Nemec 20 Nov '06

20 Nov '06

Dne Monday 20 November 2006 08:57 jste napsal(a): > Dne Monday 20 November 2006 04:09 John Meyer napsal(a): > > I'd like to know what you guys favorite e-mail client is. I've tried I think this is very interesting topic. I create wiki page, feel free to add your remakrs. http://en.opensuse.org/Mail Pavel -- Pavel Nemec Software Engineer https://wiki.innerweb.novell.com/index.php/SLEPOS --------------------------------------------------------------------- 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

1 1

[opensuse-buildservice] i586 buildhosts need some asprin
by Peter Nixon 20 Nov '06

20 Nov '06

Hi Guys The i586 buildhosts still appear to be passed out from a weekend of partying.. (The passed out sometime Saturday evening as far as I can tell) Any chance of kicking them awake and giving them an asprin? Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

Re: [opensuse-buildservice] Other Platforms than (open)SUSE in BS
by Dominique Leuenberger 17 Nov '06

17 Nov '06

>>> Reply on 17-11-2006 17:13:04 <<< > On 11/17/06, Dominique Leuenberger <Dominique.Leuenberger(a)tmf-group.com> > wrote: > > > something like > > > > %if %suse > > BuildRequires: alsa-devel > > %else if %mandriva > > buildRequires: libalsa-devel > > %endif > > > > We are using the following in our repository, you can check those specs > out. > > %if "%_repository" == "SUSE_Linux_10.1" || "%_repository" == "SLE_10" > BuildRequires: xorg-x11-compat70-devel > %endif > %if "%_repository" != "SUSE_Linux_10.0" > BuildRequires: libdrm-devel > %endif > > http://build.opensuse.org/project/show?project=X11%3AXGL > > Cheers > Thank you very much... I'll have a look into this. Are the set variables somewhere documented or are they just a good guess? (ok: _repository IS guessable) Dominiue --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Re: [opensuse-buildservice] RFC: Game blobAndConquer
by Dominique Leuenberger 17 Nov '06

17 Nov '06

>>> Reply on 17-11-2006 10:45:40 <<<> Hi Everybody, > > For some time I'm maintaining the game blobAndConquer in my home-Repo > (home:dimstar). > On most machines this game seems to work and I'm wondering if you'd > have some objections if I move it to games:action. > > Don't just hurry in and say: of course, go for it! > > First have a look at it. It is a 3rd person shooter (unlike doom, which > is 1st person!) but it has quiet a level of violence. > Release 0.6 got ublished these days and starts to support localisation. > So if somebody has some spare time and some language knowledge, we're > also happy for language contributions, besides of testings of course. > > What do you all think about it? > What does a 'no reaction' on this mailinglist mean? - No, we don't want it - yes sure, there are no objections - Why the hell should we care... do whatever you want Just curious... Or everybody is just to busy with the Factroy build of 10.2, which looks quiet good already :-) Dominique

3 2

[opensuse-buildservice] RFC SuperTuxKart 0.2.0 in games:action
by Dominique Leuenberger 17 Nov '06

17 Nov '06

Hi everybody. Would it be ok for everybody, if I move the game SuperTuxKart to games:action? Or you have a better suggestion on where to put it? Dominique (Stefan: in case this should be agreed, can you give me accs to games:action?) - dimstar

2 1

[opensuse-buildservice] linking libqt4 and dbus
by Pavel Nemec 16 Nov '06

16 Nov '06

Hi, i need build some packages (zhu3d and Reveal) which need libqt4. Darix advice me not to link package directly, because they will be builded again in my project. And use osc editmeta to add sources. This is osc editmeta home:pnemec <project name="home:pnemec"> <title>pnemec's Home Project</title> <description>packages for my personal use</description> <person userid="pnemec" role="maintainer"/> <repository name="SUSE_Factory"> <path repository="standard" project="SUSE:Factory"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="SUSE_Linux_10.0"> <path repository="standard" project="SUSE:SL-10.0"/> <path repository="SUSE_Linux_10.0" project="KDE:KDE4"/> <path repository="SUSE_Linux_10.0" project="DBUS"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="SUSE_Linux_10.1"> <path repository="standard" project="SUSE:SL-10.1"/> <path repository="SUSE_Linux_10.0" project="KDE:KDE4"/> <path repository="SUSE_Linux_10.1" project="DBUS"/> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> But building still faild with complain about SUSE_Linux_10.0 x86_64 expansion error nothing provides libdbus-1.so.3()(64bit) needed by i586 expansion error nothing provides libdbus-1.so.3 needed by libqt4-devel SUSE_Linux_10.1 x86_64 expansion error nothing provides libqt4-devel,nothing provides libqt4-x11,nothing provides libqt4-sql,nothing provides libqt4-qt3support i586 expansion error nothing provides libqt4-devel,nothing provides libqt4-x11,nothing provides libqt4-sql,nothing provides libqt4-qt3support Where i am doing mystake? -- Pavel Nemec Software Engineer https://wiki.innerweb.novell.com/index.php/SLEPOS --------------------------------------------------------------------- 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

4 5

Re: [opensuse-buildservice] linking libqt4 and dbus
by Adrian Schröter 16 Nov '06

16 Nov '06

Am Thursday 16 November 2006 15:46 schrieb Pavel Nemec: > Dne Thursday 16 November 2006 15:31 jste napsal(a): > > Am Thursday 16 November 2006 15:28 schrieb Pavel Nemec: > > > Dne Thursday 16 November 2006 14:37 jste napsal(a): > > > > In this way the dbus-1 package from 10.0 gets selected, but this one > > > > does not provide .so.3. It should work with that: > > > > > > > > <repository name="SUSE_Linux_10.0"> > > > > <path repository="SUSE_Linux_10.0" project="KDE:KDE4"/> > > > > <path repository="standard" project="SUSE:SL-10.0"/> > > > > <arch>i586</arch> > > > > <arch>x86_64</arch> > > > > </repository> > > > > > > No it do not work :( > > > > please note that the order is important. KDE:KDE4 needs to be the first > > one, which it isn't atm. > > I note it and change order, it also did not help > > > In fact it is also enough to keep only the KDE:KDE4 repository, > > SUSE:SL-10.0 is anyway taken when a package does not exist in KDE:KDE4, > > because that one does build against SUSE:SL-10.0 as well. > > darix pointed this out also (irc) but even removing this line did not help. > > but now : > expansion error: nothing provides libdbus-1.so.2 needed by kdebase3 hm, this is caused, because KDE:KDE4 brings a new dbus-1 package which is actually incompatible with the one on 10.1 :/. So, the SUSE Linux 10.1 repo for KDE:KDE4 seems not to be usable for me at all, because it will most likely not be installable. Stephan Binner updated it lately, we need to ask him, if this makes sense. But you seem to have a similar problem, you need a newer dbus-1 than on SL-10.1, right ? And we do not have newer dbus-1 packages atm, which can be installed beside. 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 2

[opensuse-buildservice] baselibs
by Wolfgang Rosenauer 16 Nov '06

16 Nov '06

Hi, since baselibs support is still not there in the buildservice and the mozilla repository is therefore pretty useless for people on x86-64 I wonder if it's possible to get it working locally at least with (osc) build. The build package has some files and configs so that it looks like some support of it: /usr/lib/build/baselibs.conf /usr/lib/build/baselibs_global.conf /usr/lib/build/mkbaselibs So what's the status of it? Wolfgang --------------------------------------------------------------------- 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] waiting for approval
by Jordi Massaguer i Pla 16 Nov '06

16 Nov '06

Hi all, I am sending this email here because I do not know where should I send it. Sorry if it is the wrong place. I have asked, more than one month ago, for an account into the build-service, so I can evaluate the platform and see if it is useful in our implementations: packages building and customized distribution building. I do not mean to be rude, but I would like to hear from you. I am really excited for looking closer to the build-service, as I think it can make opensuse a greater distribution, and make the difference to other distros. Greetings, jordi ----------------------------------------------- Jordi Massaguer Pla openTrends Solucions i Sistemes phone: +34 93 320 84 14 fax: +34 93 300 35 27 jordi.massaguer(a)opentrends.net --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

Re: [opensuse-buildservice] RFC: games:data
by Dominique Leuenberger 16 Nov '06

16 Nov '06

>>> Reply on 16-11-2006 9:25:44 <<<> 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. > Just as a follow up and as publicity :-) UFOAI RC6 got released yesterday evening. The packages are prepared and are waiting for some free time on the BS to be built. As agreed, the data files are now in games:data -> repository Generic and the binaries (i586 and x86-64) are in games:strategy:turn-based Regards and thanks for all your valuable help and support! Dominique

1 0

[opensuse-buildservice] Build service noob unable to get package going
by Joe Shaw 15 Nov '06

15 Nov '06

Hi, I just started using the build service to try to build a package and I am growing increasingly frustrated as to why it won't build. The web client feels very much like a black box to me, and so I don't understand why my builds aren't working. >From the build log: ----- building beagle.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- error: File /usr/src/packages/SOURCES/beagle-firefox-makefile.patch: No such file or directory The patch is listed in the spec file: Patch1: %{name}-firefox-makefile.patch and applied: %prep %setup -q %patch1 And included in the file list: Files beagle-0.2.12.tar.gz [Download] [Remove] beagle-firefox-makefile.patch [Download] [Remove] beagle-terminal-lockdown.patch [Download] [Remove] beagle.spec [Edit] [Download] [Remove] build_libbeagle_only.diff [Download] [Remove] libbeagle.spec [Edit] [Download] [Remove] Anyone have any idea what's going on, or (perhaps more importantly) how I can get more information on the build environment? The package is contained in my home project (home:joeshaw). Thanks, Joe --------------------------------------------------------------------- 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: games:data
by Dominique Leuenberger 15 Nov '06

15 Nov '06

>>> Reply on 15-11-2006 13:34:58 <<<> hi, > > i would be in favor of fixing the thebuildservice so noarch is only > build once. than you can just create a new package inside the normal > game project and have the package build only once. > > another way to ensure your package is build only once: > disable the package for the x86_64 architecture. > > then it will be build on i586 only aswell. > > i dont think we need 2 projects here. > Darix, It's not only to build it 'once' per Repository (anyhow the file will be overwritten as it's noarch, it's just a waste of CPU power) but also the files stored on the disc only once, even while offering the game on severeal repos (10.0, 10.1, Factory, SLED). Otherwise I have the need to put the Data RPM (which is 160MB) in ALL the repos... and I'm just filling the server with almost 1GB like this. I don't thik THAT would be much appreciated. Dominique

2 1

[opensuse-buildservice] RFC: games:data
by Dominique Leuenberger 15 Nov '06

15 Nov '06

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. Dominique

4 3

Re: [opensuse-buildservice] RFC: games:data
by Dominique Leuenberger 15 Nov '06

15 Nov '06

>>> 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

1 0

[opensuse-buildservice] Need a BuildService account
by raghu gs 14 Nov '06

14 Nov '06

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

2 1

[opensuse-buildservice] Re: Repositories below http://software.opensuse.org/download/games:/
by Dominique Leuenberger 14 Nov '06

14 Nov '06

>>> 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

1 0

Re: [opensuse-buildservice] release number for moved packages
by Dominique Leuenberger 13 Nov '06

13 Nov '06

>>> 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

4 4

[opensuse-buildservice] Rebuilding everything?
by Mauricio Teixeira (netmask) 13 Nov '06

13 Nov '06

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

5 6

[opensuse-buildservice] Add ipw2200 to drivers:wlan
by Mauricio Teixeira (netmask) 11 Nov '06

11 Nov '06

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

3 5

[opensuse-buildservice] New project: usr-local-bin
by James Ogley 10 Nov '06

10 Nov '06

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

7 27

Re: [opensuse-buildservice] release number for moved packages
by Dominique Leuenberger 10 Nov '06

10 Nov '06

>>> 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

1 0

[opensuse-buildservice] GNOME:* projects in Build Service: current status
by Stanislav Brabec 10 Nov '06

10 Nov '06

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

1 0

[opensuse-buildservice] BS kernel for 10.1 needs upgrade
by Mauricio Teixeira (netmask) 10 Nov '06

10 Nov '06

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

5 7