openSUSE Build Service October 2011

buildservice@lists.opensuse.org

58 participants
55 discussions

[opensuse-buildservice] Expired OBS Keys?

by King Thorin

It seems the OBS Security key (keyid 79EAFD54) on keys.gnupg.net has expired (2011-Apr-2). Would it be possible for someone to update it? I know an updated key has been generated (which expires 2013) as it can be found here: http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v4/xUb… Further details can be found via: http://lists.wald.intevation.org/pipermail/openvas-distro/2011-April/thread… Basically the issue came to light when following instructions: http://www.openvas.org/install-packages.html#openvas4_ubuntu_obs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

7 years, 5 months

[opensuse-buildservice] Use solid state disks [ssd] to improve obs build times.

by doiggl＠velocitynet.com.au

Hello With the opensuse build service [obs] getting more usage every day I wonder if this would make a diffence :- 1. Use solid state disks [ssd] to improve build times of package rpms on, perhaps point the BuildRoot or _tmppath to the ssd's Reason for asking. Improve the packaging times during busy times on obs. Cheers Glenn. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 years, 4 months

[opensuse-buildservice] OBS 2.3 corrections

by Joop Boonen

Hi all, I found some errors in de configurations of the OBS 2.3 server. I've attached the corrected files and the patches. It's related to: Documentation: /usr/share/doc/packages/obs-api/README.SETUP Apache vhosts configuration: /etc/apache2/vhosts.d/obs.conf I've added the api port 81 connection as a quick fix and as the internal doesn't really need to be encrypted. Should I create a bug report for this? Regards, Joop.

8 years, 7 months

[opensuse-buildservice] Add Mageia to OBS

by Stephan Kleine

Hi, could Mageia please get added to OBS? thanks a lot in advance, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] openSUSE 10.3 runs out of maintenance

by Adrian Schröter

Hello, is usual, openeSUSE 10.3 runs out of maintenance and I will remove all repos building against it in OBS. openSUSE:10.3 project has been moved to DISCONTINUED: namespace as announced a while ago. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH 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

8 years, 9 months

[opensuse-buildservice] distro independant rpms and debs for distro independant data?

by Paul Elliott

This question concerns both the OBS and packaging so I am sending to both lists. I am currently working on packaging the Swiss Ephemeris http://www.astro.com/swisseph/ I am currently at the planning scheming and experimentation stage. First I will do the library. But then there is the data. The data is about 60 files not all of which will be wanted by all people. There may be ways of grouping but I am not sure. Perhaps one rpm per file. The Web page says: > For this extended timespan the ephemeris requires 32 Mbytes of ephemeris > files. It would be a shame if this had to repeat for each distro. There may be other projects with even more data. This data is distro and architecture independent. I understand that there should be different rpm per distro because different distros link libraries differently and do other details differently. There could be rpm version dependencies. Perhaps one distro can not understand rpms from another distro as raw data. My question is this is there a lowest common denominator rpm format that can represent pure data (and a few text licensing files) and be understood by all distros? How would you get the build service to produce such rpms? After you produced them how would you get the build service to serve them for all rpm based distros? Same question for debs and the debian based distros? Unrelated question: a while back OBS debian binary repositories were debian compatible but the source repositories were not. Is this still true? -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

8 years, 10 months

[opensuse-buildservice] ANNOUNCE: OBS gitorious.org => github.com move .... DONE!

by Adrian Schröter

As announced earlier on this list, we have moved OBS and all offical related modules from gitorious.org to github.com. The new anonymous git url is git://github.com/openSUSE/$MODULE Some of the modules got renamed during this move: build-service => open-build-service sign => obs-sign build => obs-build shared-resources => obs-shared-resources (Not needed anymore since OBS 2.3) themes => opensuse-themes Not renamed, but moved modules are: * osc * osc2 * hermes * software-o-o Of course no commit, branch, tag or credential is lost. We did not moved older unmaintained or inofficial modules. In case you want to get your repo moved as well, please speak up. You can either do a new clone from github or change the origin URL in your local clone with the following commands: git rename origin gitorious.org git remote set-url origin git://github.com/openSUSE/open-build-service.git In general, a overview of the exiting official and unoffical modules and their source locations can be found here: http://en.opensuse.org/openSUSE:Build_Service_Tools All moved repositories have no commit permission on gitorious anymore. Users who (should) have push permissions: ========================================= First of all we want try to use kernel development workflow with github (since it has working email notifications and pull request mechanism). That means only the most frequent contributors have currently a push permission. All others should should do the fork & pull request step as described here: http://help.github.com/send-pull-requests/ If this model becomes a problem, we can switch back to peer review again. Please feel free to discuss about this on the obs mailing list. People with a github account and added into to the "OBS Core Developer" group can do the following to modify their local git clones: git rename origin gitorious.org git remote set-url origin git@github.com:openSUSE/open-build-service.git In case you think that you should have push permissions, but you don't have atm, please create a github account and drop us (either Sascha or me) a mail. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years

[opensuse-buildservice] osc checkout failures - Content-Length is not matching file size

by Malcolm Fernandes

We have encountered this error for a long time over different OBS/osc versions. An osc checkout fails with an error such as: A xorg-x11-drv-keyboard A xorg-x11-drv-keyboard/Makefile A xorg-x11-drv-keyboard/xf86-input-keyboard-1.6.0.tar.bz2 Content-Length is not matching file size for http://amigo:81/source/Trunk:MxC/xorg-x11-drv-keyboard/xorg-x11-drv-keyboar…: 735 vs 0 file size I had filed a bug a while ago, but have not seen any updates on that bug. https://bugzilla.novell.com/show_bug.cgi?id=660856 Has anyone else encountered this problem and is there a fix available? Thanks, Mal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 1 month

[opensuse-buildservice] Request help with Web OBS

by Nasa

Hi, I have been trying to compile some items against ubuntu 10.04 for some weeks now and had some initial help from Adrian (thanks!) who helped me get the other distros I was working on going. 10.04, however is causing me great pain. I looked at other projects that were/are compiling against 10.04 (and seemed to be working) and noted what I had identified as a potential problem existed amongst those projects as well, and they still completed. Thus I looked at the logs further and have identified other areas that maybe problematic... I am adding examples of both with hopes that someone would/could identify what I am messing up. preinstalling login... ar: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory tar: control.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors tar: data.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors preinstalling initramfs-tools... ar: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory tar: control.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors tar: data.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors preinstalling initscripts... ar: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory tar: control.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors tar: data.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Exiting with failure status due to previous errors installing autotools-dev dpkg-deb: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory dpkg: error processing .init_b_cache/autotools-dev.deb (--install): subprocess dpkg-deb --control returned error exit status 127 Errors were encountered while processing: .init_b_cache/autotools-dev.deb exit ... [ 19.242305] System halted. Thanks in advance, Nasa -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 1 month

[opensuse-buildservice] Looks like a large number of build servers are idle , something broke ?

by doiggl＠velocitynet.com.au

Hello Looks like a large number of build servers are idle , something broke ? Glenn example all of these show idle -(x86_64) build03 build09 build11 build12 https://build.opensuse.org/monitor -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

9 years, 1 month

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service October 2011