April 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Where is my home project?
by Matwey V. Kornilov 11 Apr '12

11 Apr '12

Hi, I am logged in and got "Your home project doesn't exist yet. You can create it now by entering some descriptive data and press the 'Create Project' button.", but several hours ago my home:matwey project has been existed. I can found my subprojects via search and all packages seem to be there. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] subscribe
by Jeremiah Foster 10 Apr '12

10 Apr '12

-- ============================================= Jeremiah C. Foster エレミアフォスター Open Source Technologist Pelagicore AB Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden Mobile: +46 (0)730 93 0506 E-Mail: jeremiah.foster(a)pelagicore.com ============================================= === NOTE === The information contained in this E-mail message is intended only for use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. ============= -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Cannot make changes to "configuration" of a OBS 2.3 instance
by Srinidhi B 08 Apr '12

08 Apr '12

Hi, I was hoping to debug this problem in detail and probably, provide a patch to fix the problem. Unfortunately, I haven't managed to do either and I just wanted to make sure that this problem was known before the final release of OBS 2.3. If you login to a OBS 2.3 instance as "Admin" or a different user that has "admin" privileges, you'll see a "Configuration" page in webui's home page. In this form, if you make a change to "description" or "title" fields and submit the form, you'll receive "Failed to save configuration" error message. In the api log, you'll see something like this: [INFO |#26067] Processing ConfigurationsController#update (for ::1 at 2012-04-03 03:08:40) [PUT] [INFO |#26067] Parameters: {"title"=>"My Open Build Service", "description"=>" \r\n The <a href=\"http://openbuildservice.org\">Open Build Service (OBS)</a>\r\n is an open and complete distribution development platform that provides a transparent infrastructure for development of Linux distributions, used by openSUSE, MeeGo and other distributions.\r\n Supporting also Fedora, Debian, Ubuntu, RedHat and other Linux distributions.\r\n \r\n \r\n The OBS is developed under the umbrella of the <a href=\"http://www.opensuse.org\">openSUSE project</a>. Please find further informations on the <a href=\"http://wiki.opensuse.org/openSUSE:Build_Service\">openSUSE Project wiki pages</a>.\r\n \r\n\r\n \r\n The Open Build Service developer team is greeting you. In case you use your OBS productive in your facility, please do us a favor and add yourself at <a href=\"http://wiki.opensuse.org/openSUSE:Build_Service_installations\">this wiki page</a>. Have fun and fast build times!\r\n \r\n"} [FATAL|#26067] Suse::ValidationError (request validation error: Start tag expected, '<' not found): lib/opensuse/validator.rb:166:in `validate' lib/opensuse/validator.rb:47:in `validate_xml_request' If I understand the code correctly, then the webui isn't sending a well formed XML request to api and Nokogiri doesn't like it - I know that's obvious :) But I couldn't figure out how to solve this problem and thus I shall let the experts handle this. The above log was taken from one of the latest OBS appliances downloaded from openSUSE:Tools:Unstable running 2.2.992 versions of obs-api and obs-server packages. Srinidhi. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Fork and build?
by Roger Luedecke 08 Apr '12

08 Apr '12

I wanted to fork a couple projects so I could have them build for my system... there seems to be no way to add a build-target. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] "(E) Attention, copyright is not mentioned in spec files as source or patch."
by Florian Höch 06 Apr '12

06 Apr '12

Hi, I'm trying to submit a package to openSUSE factory, but get the error seen in the subject of this message (from factory-auto). Honestly, I don't even know what the error is supposed to mean. Running osc service localrun source_validator as mentioned in the details of the error gives me "too few arguments". Adding the specfile as last argument gives me "too many arguments". The manpage doesn't contain usage information for that particular operation either. I tried looking at the build service specfile guidelines, but couldn't discern any info that seemed related. The specfile in question already contains a copyright comment. Pointers welcome. -- Florian Höch -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] weird bug with disabled builds
by Jon Nelson 05 Apr '12

05 Apr '12

I recently ran into an issue (or perhaps multiple issues) which took me a while to resolve, and I think there is at least one bug here. I'm using obs 2.1.17.2. I was asked to determine why a package (foo) was building using another package (bar) from the same project, despite bar being disabled for build, publish, and with 'use for build' also disabled. I tried many incantations of 'wipebinaries' and yet I could still clearly see the rpms in /srv/obs/build/<project>/. The first issue is that (a), an upstream project was providing a newer version of "bar" but it wasn't being used. That seemed weird, but maybe explainable. The much more worrisome issue is that I had to re-enable building, let it build, disable building (again), and use wipebinaries to finally get "bar" to *actually* get removed. -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Getting old _service:*.spec file in a _link
by Cristian Morales Vega 05 Apr '12

05 Apr '12

See https://build.opensuse.org/package/files?package=lightspark&project=home%3A… The _service:format_spec_file:lightspark.spec file uses CMAKE_SKIP_RPATH instead of the CMAKE_BUILD_WITH_INSTALL_RPATH from the original .spec file. It's from an old revision and I have no idea why it appeared there when I added the "<topadd>%define _with_ffmpeg 1</topadd>" line to the _link file. If you check the date you can see the _service file is older than the original .spec file!! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 8

[opensuse-buildservice] Strange behaviour on Kernel:stable i586
by Paolo Pantò 05 Apr '12

05 Apr '12

Hi, lately it seems that something in the Kernel:stable project is not resolved correctly, especially in the i586 arch. Package "preload" shows "unresolvable" in https://build.opensuse.org/project/monitor?project=Kernel%3Astable although the associated kernel packages are built fine. Other projects that refer to this one, are showing also this "unresolvable" message in the i586 arch. Kernel modules for Tumbleweed seems to be also affected. Tumbleweed uses the same kernel packages, eg: https://build.opensuse.org/project/monitor?project=Virtualization%3AVirtual… https://build.opensuse.org/project/monitor?project=multimedia%3Aaudio%3AKMP Currently "i586 unresolvable" reports: nothing provides kernel-desktop-devel = 3.3.1-18 needed by kernel-syms, nothing provides kernel-pae-devel = 3.3.1-18 needed by kernel-syms, nothing provides kernel-xen-devel = 3.3.1-18 needed by kernel-syms Any clues? Thanks, Paolo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] server:mail python-policyd-spf SLE 11 problems.
by Boyd Lynn Gerber 04 Apr '12

04 Apr '12

Hi, I have been unable to get the SLES 11 targets to build. When I first started I have all SLES and non SUSE targets building with python-policyd-spf.spec.begin. I know I had the syntax wrong with >=> but it worked. I now have the python-policyd-spf.spec file working for all but the SLES 11 targets. I did not have to try and add the line to chmod to add +x but I thought adding it where I did would allow the build it does not. I have lost most of my knowledge when I had my stroke like illness back in Aug/Sep 2009. So, I am really at a loss. I have fought with this now for a week. Any ideas will be greatly apprecated. Thanks, -- Boyd Gerber <gerberb(a)zenez.com> 801 849-0213 ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] 12.1 and obs-server install
by Jussi Hakala 04 Apr '12

04 Apr '12

Using packages from the 12.1 tools repo, installed obs-server and proceeded with the instructions given in [1]. Everything went relatively well, until importing base distribution [2] to backend, namely after using obs_mirror_project, the import did not go so well: $ obs_mirror_project openSUSE:12.1 standard i586 $ rcobsscheduler restart $ cd /srv/www/obs/api/script $ RAILS_ENV="production" ruby import The last command gave me an exception stack, with key issue being: uninitialized constant Suse::Validator::SCHEMA_LOCATION (NameError) Tried adding require File.dirname(__FILE__) + '/../config/environment.rb in the import script, which gave me some warnings about things already defined, but included the file defining SCHEMA_LOCATION and I got forward. I had to edit /srv/obs/projects/openSUSE:12.1.xml as well, mostly to remove some group privileges as the groups were not present my local db. After that, I got --> storing projects openSUSE:12.1 => success --> storing packages for project 'openSUSE:12.1' <-- fin and everything seemed to be okay. However, when I log in to my local obs, it asks me to connect a remote open build service instance for default base distribution. I'm pretty sure that was what I just did manually? Or is it something I need to do even if I use curl to upload openSUSE.org.xml to my local server from the package and import the base distribution from command line? Using osc, I get $ osc -A https://myhost.mydomain.com:444 ls deleted openSUSE.org openSUSE:12.1 which suggests that the project I imported is there. The documentation doesn't mention anything about this after the importing part. Is there a more complete documentation somewhere? Everything I googled seemed to be out of date. Regards, Jussi [1] /usr/share/doc/packages/obs-server/README.SETUP [2] Sections 4.1-4.2 in the documentation -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0