openSUSE Build Service July 2013

buildservice@lists.opensuse.org

53 participants
56 discussions

[opensuse-buildservice] Server Installation Help

by Jorge F. Hernandez

Hey guys, I'm trying to install OBS to a VM, everything installs without a problem, but when it gets to the login part, I'm stuck, I have no username/password for it and when I go to http://obsserver:5252 all I get is a message about XML, so I can't login that way either. Is there any documentation about how to install it? Thanks. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 5 months

[opensuse-buildservice] osc service log

by Michel Bourget

Hi all, ( plinnell on IRC suggested me to post my question here instead of the IRC forum. ) "service log" are not available, at least intuitively, using an "osc" interface. At SGI, we are in the process of moving to OBS. We exclusively use "_service" interface to pull source ( and metadata files ) from git repos. So, production-wise, troubleshooting "failed builds" requires capturing the "service" logs as well as the proper usual chroot "build" logs. This is crucial for us. I attempted to simply modify bs_service to essentially to: if (!open(SERVICE, '-|')) { + open(STDOUT, "| tee -a _service_log"); open(STDERR, ">&STDOUT"); The above works ( I can "osc cat ..." ) but only when all the _service steps exit 0 ! Useful but not quite :) So, the question: is there an osc method to unconditionally capture the already captured _service_error file and/or the _service_log ? Simply said, capture the latest _service log, regardless if it is a success or a failure; that's the point. The "osc api" method are not easy to "discover", to be honest. Any help, hints, guidance appreciated. Thanks in advance. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 5 months

[opensuse-buildservice] Test repo for runtime-requirement-completeness

by Joschi Brauchle

Hi everyone, currently, the OBS (website) has a method to show that there are BuildRequires missing for a specific package (i.e. the red "unresolvable" error). Is there a way to check if a repository (possible also incl. the repo it builds against) is also *publishing* all *runtime* dependencies of the published packages? I.e. if the repo plus its parent repos provides all packages that are required at runtime/installation? If not, I would add this as an OBS feature request. It would also be nice to have a dependency graph showing Build-/Requires relationsships between all packages in a repo (and possibly to the repos it builds against). Such a feature would ease the search for "zombie" packages in large repos, which once were needed as BuildRequires, but may be not needed anymore and thus could be deleted. Best regards, Joschi Brauchle

7 years, 5 months

[opensuse-buildservice] OBS support for Ubuntu/Debian on ARM

by Jan-Christoph Borchardt

Heya, Jan from ownCloud here. We had some requests for an ownCloud client for Ubuntu/Debian on ARM architecture. See for example here: https://github.com/owncloud/mirall/issues/338 Now that I have the ARM Chromebook myself and Ubuntu on it, I need it as well. Danimo (one of our client devs) said that I need to ask you folks if it’s possible to add that to OBS. OpenSUSE on ARM is already in for example. Hope this is the right channel to ask. Let me know if otherwise. Thanks! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 6 months

[opensuse-buildservice] build loop without result and error

by Petr Mladek

Hi, the "libreoffice" package in the "LibreOffice:Unstable" project and "openSUSE_12.3 x86_64" distro has been in some strange build loop for last few days. I am not sure what the problem is. I checked it several time. The status always was "building". The log was "only" few hours long => the build was automatically restarted several times. I wonder why. I do not see any build error and local build works. The i586 libreoffice package and x86_64 help packages have been built 7 days ago => it should not be caused by another commits in the openSUSE_12.3 or LibreOffice:Unstable repo. Do you have any idea, please? Do some errors trigger automatic rebuild? Is there any build time out? I think that it might help to force build on some more powerful hosts with more CPUs and more memory. Is it possible, please? Best Regards, Petr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 6 months

[opensuse-buildservice] /etc/init.d/obsworker does not start after reboot when running behind a proxy

by Martin Weber

It seems the curl command in obsworker ignores the no-proxy settings and tries to download the worker code from our proxy. OTOH, if I log in as root and issue a 'rcobsworker start', it does _not_ fail. Of course, when you log in, the proxy environment variables are set, but if obsworker is run as a child of the init process, none of theses env vars are set. In the obsworker code, I see that it sources /etc/sysconfig/proxy, but this sets shell variables, not env variables. Ciao, Martin -- Piepst der Rittal schon im Mai, ist den Juli Hitzefrei! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 6 months

[opensuse-buildservice] Private OBS instance - webui problems

by Guillaume Gardet

Hi, I am trying to get OBS on a private server but I face some issues. I followed this README: http://gitorious.org/opensuse/build-service/blobs/master/dist/README.SETUP When I want to login to the webinterface with default id/password (Admin / opensuse), I get this error: "Authentication failed" When I try to register a new user I get a 401 error: *********************************************************** <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> Authentication required! <![CDATA[/*> Authentication required! This server could not verify that you are authorized to access the URL "/person/register". You either supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required. In case you are allowed to request the document, please check your user-id and password and try again. If you think this is a server error, please contact the webmaster. Error 401 api.opensuse.org Tue Jun 4 22:33:56 2013 Apache/2.2.12 (Linux/SUSE) *********************************************************** Otherwise OBS server seems to be ok since osc commands works fine such as: osc -A https://192.168.0.21:444 ls Any idea what could be wrong in my setup ? If I use the OBS appliance (based on openSUSE 12.2), no problem, but I would like to get OBS working on openSUSE 12.3. Guillaume -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 6 months

[opensuse-buildservice] GSoC 2013 update for the week ending on 12/07/2013

by Shayon Mukherjee

Hello folks, So, here is my GSoC 2013 update for the week ending on 12/07/2013 1. What have I done last week? Fixed the minor bugs and styling mistakes. Made the code in [webui] more DRY. Also, previous test suites were failing which didnt allow me from making my first pull-request, so a lot of time was spent fixing the existing test suite and make sure all of them are passing now. Routing was also updated and lot of restructuring was done too. Users now have the ability to expand and collapse the comments. 2. What am I'm doing this week This week, I am out travelling for oSC (Yayy!), so I don't expect a lot of work to be done. But I still plan on writing some test suites and permission checks as much as possible. Plus, my mentor (henne) will be at oSC so we will be discussing the app in much more detail during the conference and work piece-by-piece on the feedback received for the existing pull-request. Important links Trello: https://trello.com/board/discussion-system/51a5ede2db062a7e6f001b7c Github: https://github.com/shayonj/open-build-service Cheers! Shayon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 6 months

[opensuse-buildservice] [PING] server:messaging SRs

by Marguerite Su

Hi, can some repo maintainers accept them? They're there for more than two weeks. I'm running a xmpp server using prosody...maybe I'm the only one using these packages for now? And I'm pretty sure the fixes are valid. Reasons: Most of the Lua dependencies there don't support Lua 5.2 at the upstream side. So it doesn't make sense to build them with lua 5.2. Greetings Marguerite -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 6 months

[opensuse-buildservice] package maintenance...am i doing this correctly?

by Darin Perusich

Hello All, I'm trying to update the sudo package in opensuse12.3 from the package in Base:System and I've been asked to create an mbranch, merge and commit the changes, then create a new maintenancerequest. I've been reviewing the package maintenance page, http://en.opensuse.org/openSUSE:Package_maintenance, and I just want to ensure i'm doing things properly before i commit things. I've created a branch of openSUSE:12.3:Update/sudo and checked out Base:System/sudo and "merged" them by manually coping the updated/new sources from Base:System/sudo into the branch, adding them, removing the old sources. I know I need to sync up the .changes but I don't want to simply overwrite the branches because there is 1 change added to the update that isn't in the Base:System package. I'm I going about this correctly or is there a better way to "merge" the changes? Should I be concerned about keeping the .changes entry or just clobber it, and include the bug number in the new .changes? Thanks! -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 years, 6 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service July 2013