August 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] obs Application error when accessing https://build.opensuse.org/
by doiggl＠velocitynet.com.au 18 Aug '10

18 Aug '10

Hello, I get this error [1]when accessing this page [2] [1] Application error Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html [2] Glenn -- 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] OBS: set release number of package?
by Jon Nelson 18 Aug '10

18 Aug '10

Is there a way to tell the OBS to set the release number of a package to some arbitrary number (or to increase it by some number)? For example, let's say foo version 1.0 and has been checked in 3 times and rebuilt twice. I think the package would then be foo-1.0-3.2.$arch.rpm. Let's say I'd like to set the check in count to 5 (and reset the build count). Is there an easy way to do this without /actually/ checking in a number of dummy commits? -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 8

[opensuse-buildservice] GIT OBS release tags
by Maultuz 18 Aug '10

18 Aug '10

The next time a release, could it be made an annotated object(git tag -a 2.0.6) I'm asking because it would me much easier to understand what changes a snapshot archive is made from. When I look in openSUSE:Tools:Unstable => obs- server I'll find obs-server-2.0.89.tar.bz2 and that tells me nothing. If the tags where an annotated object `git describe` could be used for the version tag i.e. “2.0.5-143-gb9f73fc” then I could use `git log/diff 2.0.5..b9f73fc` or `git log/diff b9f73fc..HEAD` etc. -- 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] Safe way to remove /srv/obs/source folders
by Davis_Phillips＠Dell.com 18 Aug '10

18 Aug '10

Greetings, I posed this questions a week back or so and I wanted to check again. Concerning OBS 1.6: Is considered a best practice for deleting the folders under /src/obs/source? The uploaded tarballs & spec files are being to consume a large amount of space on our front end servers. We would like to archive what we can in an effort to clean up the environment. Thanks in advance! Thanks! Davis Phillips Release Engineer Dell | PG Release Engineering office + 1 512 723 5910 -- 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] Linking two (private) OBS servers at different sites.
by Troy Telford 16 Aug '10

16 Aug '10

Is there a guide anywhere that talks about how to link two different OBS servers, so that when a project/package that is on one server can be linked to on another server (separated by distance and low-bandwidth; so it makes sense to send source code instead of keeping the package mirror constantly updating). I've seen the example where (openSUSE 11.3's obs packages) have /srv/obs/packages has openSUSE.org.xml. I've tried modifying that example, and set it to point between the two servers, and had some success; I've linked some packages and when the package on one system is updated, the changes transfer to the other. I can copypac, linkpac, aggregate pac, for the most part. However, if I look in /srv/obs/log/scheduler_arch.log, I see the following repeated endlessly: 2010-08-09 19:02:13: waiting for an event... retrying watcher for http://obsapi.foo.bar.com/public setting up watcher for http://obsapi.foo.bar.com/public 2010-08-09 19:03:16: waiting for an event... response from watcher for http://obsapi.foo.bar.com/public 400 remote error: Bad Request retrying in 60 seconds Any ideas on what I might be missing? Thanks. Thanks. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 6

[opensuse-buildservice] unresolvable status preventing package build, when same provide is available from two packages
by Frederic Crozat 16 Aug '10

16 Aug '10

Hi, I'm having an issue when trying to build jpilot for SLE10, which can be seen on https://build.opensuse.org/package/show?package=jpilot&project=mobile% 3Asynchronization%3ASTABLE jpilot is trying to use pilot-link / pilot-link-devel (which is now provides by libpisock-devel, which obsoletes/provides pilot-link-devel) as a build requirement but it looks like OBS is trying to use pilot-link-devel / pilot-link packages from SLE10 (which is older) rather than the one from the project. Is it a bug ? For now, I'm changing buildrequirement to libpisock-devel as a workaround. -- Frederic Crozat <fcrozat(a)novell.com> Novell -- 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] Running OBS Rails app in sub directories.
by Leaf John 16 Aug '10

16 Aug '10

My situation is, I could export obs service through only one port( 80 ), I have only one server, and the server has only one domainname.so I've to run different rails app by different sub dirs. I tried the strip uri feature of lighttpd, and I added this line to rails.inc: "max-procs" => rails_procs, "idle-timeout" => 3600, + "strip-request-uri" => strip_uri, ) ) ) Than I add another obs-80.conf to vhosts.d, add this content: HTTP["url"] =~ "^/webui/" { ...... strip_uri="/webui" include "vhosts.d/rails.inc" } Than I visit my server like, http://myip/webui, and I got the front page all right, but no link works, no style sheet, even no images in the web page. >From the html source I see that all links point to some absolute address like /stylesheet/xxx.css, /images/opensuse.png.. So, My question is, is there any solutions for this case? If not where can I do the modifications to solve the link address issue? Modifications won't be an easy task, cause the absolute path will save some energy in web page generation, but it won't be a task not possible. -- Best Reagres, Leaf Johnson<leafjohn(a)gmail.com> -- 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] osc collab hardcoded to build.o.o?
by Robert Xu 15 Aug '10

15 Aug '10

Hi all, I decided to play around with osc collab on my home project on build.o.o, then on my local bs, but I noticed that it defaults to build.o.o even if .oscrc says to use my local bs as the apisrv. Is this supposed to happen? -- later, Robert Xu -- 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] Integrating SCM with OBS
by brook.hong＠nokia.com 13 Aug '10

13 Aug '10

Hi ALL, I had started a discussion about integrating SCM with OBS in our company. And now when I checked back http://en.opensuse.org/Category:Build_Service, I found there was an interesting wiki page(http://en.opensuse.org/openSUSE:Build_Service_Concept_GitUpstreamSuppo… talking about the similar task, also noticed that some of you have started relevant work. Here I would like share my thoughts. Follows my writing in my earlier emails. ====================================== For example, we would like to have Meego OBS to build a package -- gstreamer, which is located at http://git.gitorious.org/maemo-multimedia/gstreamer.git. With current OBS, we need fetch all the code from gitorious, create a compressed tar file, then upload the tar file, spec/dsc file to OBS source server, these files will go into /srv/obs/sources/gstreamer/. OBS scheduler(bs_sched) will detect the file change, and trigger a rebuild. If source repository URL is included in the meta file of this package as below <package project="devel" name="gstreamer"> <title>gstreamer</title> <description>gstreamer</description> <sources>http://git.gitorious.org/maemo-multimedia/gstreamer.git</sources> </package> Then create a new server in OBS, may be named as bs_scmagent, which focuses on the following tasks -- * maintain a package list for all the packages whose meta data file includes a source repository URL, * connect to SCM server to detect code change, * if changed, fetch code from SCM, tar them, put the new file into /srv/obs/sources/gstreamer/, let bs_sched to trigger a rebuild. bs_scmagent needs to support plugin, which is to give support for different kinds of SCM. For compatibility, a special value is needed to indicate that the files were uploaded manually. <package project="devel" name="gstreamer"> <title>gstreamer</title> <description>gstreamer</description> <sources>native</sources> </package> How to detect code change? For git, Polling seems to be the only solution since it is distributed version control system. Thus, we need tune up the polling way for performance consideration. * polling not that frequently, for example, once n hours(n can be configured from webui or osc, and is limited between a range) * if developer wants his code change being built immediately, an osc action will be involved, he can run "osc remoteupdatesource gstreamer" to tell bs_scmagent to get latest code. ====================================== "osc git refresh" mentioned in http://en.opensuse.org/openSUSE:Build_Service_Concept_GitUpstreamSupport seems much like "osc remoteupdatesource" I proposed. I like the idea of generating a diff from SCM as a patch for spec file, but I don't like "git" as an action of "osc". I prefer the interfaces to be clear, osc is osc, git is git, don't mess them up. Also how about other SCMs except git? What's your progress now? ---------------- Best Regards, Brook Hong -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 6

[opensuse-buildservice] Packages appear excluded, although they shouldn't
by Hans-Peter Jansen 13 Aug '10

13 Aug '10

Hi, Repo: https://build.opensuse.org/project/repositories?project=home%3Afrispete%3AK… Build explicitely disabled for CentOS_CentOS-5 and Fedora_13 Now I wanted to split the python-kde package, depending on the build target in python-kde4-44 and python-kde4-45. osc meta pkg home:frispete:KDE python-kde4-44: <build> <disable repository="KDE_Distro_Factory_openSUSE_11.1"/> <disable repository="KDE_Distro_Factory_openSUSE_11.2"/> <disable repository="KDE_Distro_Factory_openSUSE_11.3"/> <enable repository="KDE_Distro_Stable_openSUSE_11.1"/> <enable repository="KDE_Distro_Stable_openSUSE_11.2"/> <enable repository="KDE_Distro_Stable_openSUSE_11.3"/> <disable repository="openSUSE_11.1"/> <disable repository="openSUSE_11.2"/> <enable repository="openSUSE_11.3"/> </build> osc meta pkg home:frispete:KDE python-kde4-45: <build> <disable repository="KDE_Distro_Stable_openSUSE_11.1"/> <disable repository="KDE_Distro_Stable_openSUSE_11.2"/> <disable repository="KDE_Distro_Stable_openSUSE_11.3"/> <disable repository="openSUSE_11.1"/> <disable repository="openSUSE_11.2"/> <disable repository="openSUSE_11.3"/> <enable repository="KDE_Distro_Factory_openSUSE_11.1"/> <enable repository="KDE_Distro_Factory_openSUSE_11.2"/> <enable repository="KDE_Distro_Factory_openSUSE_11.3"/> </build> If I understand this correctly, BS should build python-kde4-44 for KDE_Distro_Stable* and openSUSE_11.3, while python-kde4-45 should build for KDE_Distro_Factory*. But: eric | python-enchant | | python-kde3 | | | python-kde4 | | | | python-kde4-44 | | | | | python-kde4-45 | | | | | | python-logilab-astng | | | | | | | python-logilab-common | | | | | | | | python-pylint | | | | | | | | | python-pysvn | | | | | | | | | | python-qscintilla | | | | | | | | | | | python-qt | | | | | | | | | | | | python-qt4 | | | | | | | | | | | | | python-rope | | | | | | | | | | | | | | python-sip | | | | | | | | | | | | | | | qgit | | | | | | | | | | | | | | | | qscintilla CentOS_CentOS-5 i586 (published) CentOS_CentOS-5 x86_64 (published) Fedora_13 i586 (published) Fedora_13 x86_64 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.1 i586 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.1 x86_64 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.2 i586 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.2 x86_64 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.3 i586 (published) . . . x . . . . . . . . . . . KDE_Distro_Factory_openSUSE_11.3 x86_64 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.1 i586 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.1 x86_64 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.2 i586 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.2 x86_64 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.3 i586 (published) . . . . x . . . . . . . . . . . KDE_Distro_Stable_openSUSE_11.3 x86_64 (published) . . . . . . . . . . . . . openSUSE_11.1 i586 (published) . . . . . . . . . . . . . openSUSE_11.1 x86_64 (published) . . . . . . . . . . . . . openSUSE_11.2 i586 (published) . . . . . . . . . . . . . openSUSE_11.2 x86_64 (published) . . . . x . . . . . . . . . . . openSUSE_11.3 i586 (published) . . . . x . . . . . . . . . . . openSUSE_11.3 x86_64 (published) something excludes them which I don't understand. <OT> BTW, it would be cool to have a python-kde4 package (e.g package with a single name), that builds either from KDE 4.4.4, or KDE 4.5.0, without the need to obfuscate the spec with %if..%endif. Is that possible? </OT> Thanks, Pete -- 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] Status of ARM in OBS?
by Greg Freemyer 13 Aug '10

13 Aug '10

All, I see discussion in OpenFate about ARM support in factory, but no status as to what if anything has been done at this point. My understanding a month or two ago is that the Arm crosscompile environment was going to be re-enabled to see what the status was. Can anyone provide an update? Thanks Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] Re: [PATCH] [api] correct default permissions for roles maintainer, reader, downloader to be in line with ACL
by Adrian Schröter 12 Aug '10

12 Aug '10

That breaks my permanent running test suite runner here: # RAILS_ENV=test rake db:migrate --trace (in /abuild/obs-git/build-service/src/api) DEPRECATION WARNING: Rake tasks in vendor/plugins/mdd/tasks are deprecated. Use lib/tasks instead. (called from /usr/lib64/ruby/gems/1.8/gems/rails-2.3.8/lib/tasks/rails.rb:10) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate == FixAclPermissions: migrating ============================================== rake aborted! An error has occurred, all later migrations canceled: Mysql::Error: Duplicate entry '12-3' for key 'roles_static_permissions_all_index': INSERT INTO `roles_static_permissions` (`created_at`, `static_permission_id`, `role_id`) VALUES ('2010-08-12 16:49:15', 12, 3) /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connection_adapters/abstract_adapter.rb:221:in `log' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connection_adapters/mysql_adapter.rb:323:in `execute' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connection_adapters/abstract/database_statements.rb:259:in `insert_sql' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connection_adapters/mysql_adapter.rb:333:in `insert_sql' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connection_adapters/abstract/database_statements.rb:44:in `insert_without_query_dirty' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connection_adapters/abstract/query_cache.rb:19:in `insert' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/has_and_belongs_to_many_association.rb:78:in `insert_record' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/association_collection.rb:119:in `<<' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/association_collection.rb:412:in `add_record_to_target_with_callbacks' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/association_collection.rb:118:in `<<' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/association_collection.rb:116:in `each' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/association_collection.rb:116:in `<<' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/association_collection.rb:141:in `transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/transactions.rb:182:in `transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/association_collection.rb:140:in `transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/associations/association_collection.rb:115:in `<<' ./db/migrate//20100812100000_fix_acl_permissions.rb:9:in `up_without_benchmarks' ./db/migrate//20100812100000_fix_acl_permissions.rb:8:in `each' ./db/migrate//20100812100000_fix_acl_permissions.rb:8:in `up_without_benchmarks' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:365:in `__send__' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:365:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:491 /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:567:in `call' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:567:in `ddl_transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:490:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:477:in `each' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:477:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:401:in `up' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:383:in `migrate' /usr/lib64/ruby/gems/1.8/gems/rails-2.3.8/lib/tasks/databases.rake:112 /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib64/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 On Thursday 12 August 2010 16:47:53 OBS build-service wrote: > From: Martin Mohring <martinmohring(a)linuxfoundation.org> > > --- > .../migrate/20100812100000_fix_acl_permissions.rb | 25 ++++++++++++++++++++ > 1 files changed, 25 insertions(+), 0 deletions(-) > create mode 100644 src/api/db/migrate/20100812100000_fix_acl_permissions.rb > > diff --git a/src/api/db/migrate/20100812100000_fix_acl_permissions.rb b/src/api/db/migrate/20100812100000_fix_acl_permissions.rb > new file mode 100644 > index 0000000..b5b9dbe > --- /dev/null > +++ b/src/api/db/migrate/20100812100000_fix_acl_permissions.rb > @@ -0,0 +1,25 @@ > +class FixAclPermissions < ActiveRecord::Migration > + def self.up > + reader = Role.find_by_title 'reader' > + maintainer = Role.find_by_title 'maintainer' > + downloader = Role.find_by_title 'downloader' > + > + sourceperm = StaticPermission.find_by_title('source_access') > + [maintainer,reader].each do |role| > + role.static_permissions << sourceperm > + end > + > + privperm = StaticPermission.find_by_title('private_view') > + [maintainer,reader,downloader].each do |role| > + role.static_permissions << privperm > + end > + > + downloadperm = StaticPermission.find_by_title('download_binaries') > + [maintainer,downloader].each do |role| > + role.static_permissions << downloadperm > + end > + end > + > + def self.down > + end > +end > -- 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

1 0

[opensuse-buildservice] Finding packages built for openSUSE and Ubuntu
by R. Tyler Ballance 12 Aug '10

12 Aug '10

Howdy folks, I am working on a post about OBS and I can't for the life of me find any examples of applications that are being built with OBS for multiple platforms (like openSUSE and Ubuntu). Either I'm not guessing the right packages, or the web search on software.opensuse.org isn't properly finding them :) What are some good "highlights" packages that are built for multiple platforms with OBS I can shine the spotlight on? It seems even our beloved Banshee and F-Spot aren't built for Ubuntu with it :-/ Cheers, -R. Tyler Ballance -------------------------------------- GitHub: http://github.com/rtyler Twitter: http://twitter.com/agentdero

4 3

[opensuse-buildservice] cpio fatal error?
by Robert Xu 12 Aug '10

12 Aug '10

Hi all, I'm running into a serious error that's failing all my builds with the openSUSE.org:Fedora:13 repository When build tries to unpack the first package after preinstall, it gives me "cpio: Bad magic". Did anything happen? -- later, Robert Xu -- 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] [PATCH] [api]Add the support for updating user info to LDAP server(optional)
by Zhang, Vivian 11 Aug '10

11 Aug '10

Hi, Here is a patch to provide the support for Admin updating the user info to LDAP server (when LDAP_MODE is set) with API user management UI. Please help to review it. The user can use other LDAP client tool for the data updates, while it is good to provide the option of using the API user management UI for the updating, which is more user friendly. vivian. >From 29c1c937f7ae220239520fc469870545597bbf84 Mon Sep 17 00:00:00 2001 From: Vivian Zhang <vivian.zhang(a)intel.com> Date: Tue, 10 Aug 2010 23:56:43 -0400 Subject: [PATCH] [api]Add the support for updating user info to LDAP server(optional) --- .../app/controllers/active_rbac/user_controller.rb | 39 ++++++ src/api/config/environments/production.rb | 13 ++ src/api/lib/active_rbac_mixins/user_mixins.rb | 122 ++++++++++++++++++++ 3 files changed, 174 insertions(+), 0 deletions(-) diff --git a/src/api/app/controllers/active_rbac/user_controller.rb b/src/api/app/controllers/active_rbac/user_controller.rb index 49f84c5..be1683b 100644 --- a/src/api/app/controllers/active_rbac/user_controller.rb +++ b/src/api/app/controllers/active_rbac/user_controller.rb @@ -75,6 +75,17 @@ class ActiveRbac::UserController < ActiveRbac::ComponentController params[:user][:groups] = [] if params[:user][:groups].nil? @user.groups = params[:user][:groups].collect { |i| Group.find(i) } + # Create the new user to LDAP server if LDAP_UPDATE_SUPPORT is enabled + if defined?( LDAP_MODE ) && LDAP_MODE == :on + if defined?( LDAP_UPDATE_SUPPORT ) && LDAP_UPDATE_SUPPORT == :on + result = User.new_entry_ldap(params[:user][:login], params[:user][:password],params[:user][:email]) + if result + flash[:error] = result + return + end + end + end + # the above should be successful if we reach here; otherwise we # have an exception and reach the rescue block below flash[:notice] = 'User was created successfully.' @@ -144,8 +155,23 @@ class ActiveRbac::UserController < ActiveRbac::ComponentController redir_to_opts[:onlyunconfirmed] = 1 end + # Record the old login name, which might be changed by the user + login = @user.login + # Bulk-Assign the other attributes from the form. if @user.update_attributes(params[:user]) + # Sync the new user data to LDAP server, if LDAP_UPDATE_SUPPORT is enabled + if defined?( LDAP_MODE ) && LDAP_MODE == :on + if defined?( LDAP_UPDATE_SUPPORT ) && LDAP_UPDATE_SUPPORT == :on + result = User.update_entry_ldap(login, params[:user][:login], params[:user][:email], params[:user][:password]) + if result + flash[:error] = result + redirect_to :action => 'edit' + return + end + end + end + flash[:notice] = 'User was successfully updated.' redirect_to redir_to_opts else @@ -172,7 +198,20 @@ class ActiveRbac::UserController < ActiveRbac::ComponentController # redirects to the #show action with the selected's user's ID. def destroy if not params[:yes].nil? + login = User.find(params[:id]).login User.find(params[:id]).destroy + #Delete the user in LDAP server, if LDAP_UPDATE_SUPPORT is enabled + if defined?( LDAP_MODE ) && LDAP_MODE == :on + if defined?( LDAP_UPDATE_SUPPORT ) && LDAP_UPDATE_SUPPORT == :on + result = User.delete_entry_ldap(login) + if result + flash[:error] = result + redirect_to :action => 'list' + return + end + end + end + flash[:notice] = 'The user has been deleted successfully' redirect_to :action => 'list' else diff --git a/src/api/config/environments/production.rb b/src/api/config/environments/production.rb index 7d72469..27f9ce8 100644 --- a/src/api/config/environments/production.rb +++ b/src/api/config/environments/production.rb @@ -58,6 +58,19 @@ LDAP_AUTHENTICATE=:ldap LDAP_AUTH_ATTR="userPassword" LDAP_AUTH_MECH=:md5 +# Whether to update the user info to LDAP server, it does not take effect +# when LDAP_MODE is not set. +# Since adding new entry operation are more depend on your slapd db define, it might not +# compatiable with all LDAP server settings, you can use other LDAP client tools for your specific usage +LDAP_UPDATE_SUPPORT = :off +# ObjectClass, used for adding new entry +LDAP_OBJECT_CLASS = ['inetOrgPerson'] +# Base dn for the new added entry +LDAP_ENTRY_BASE = "ou=OBSUSERS,dc=EXAMPLE,dc=COM" +# Does sn attribute required, it is a necessary attribute for most of people objectclass, +# used for adding new entry +LDAP_SN_ATTR_REQUIRED = :on + SOURCE_HOST = "localhost" SOURCE_PORT = 5352 diff --git a/src/api/lib/active_rbac_mixins/user_mixins.rb b/src/api/lib/active_rbac_mixins/user_mixins.rb index 6f5462a..ce72871 100644 --- a/src/api/lib/active_rbac_mixins/user_mixins.rb +++ b/src/api/lib/active_rbac_mixins/user_mixins.rb @@ -317,6 +317,128 @@ module UserMixins return nil end + # This static method tries to update the entry with the given info in the + # active directory server. Return the error msg if any error occured + def self.update_entry_ldap(login, newlogin, newemail, newpassword) + logger.debug( " Modifying #{login} to #{newlogin} #{newemail} using ldap" ) + + ldap_con = initialize_ldap_con(LDAP_SEARCH_USER, LDAP_SEARCH_AUTH) + if ldap_con.nil? + logger.debug( "Unable to connect to LDAP server" ) + return "Unable to connect to LDAP server" + end + user_filter = "(#{LDAP_SEARCH_ATTR}=#{login})" + dn = String.new + ldap_con.search( LDAP_SEARCH_BASE, LDAP::LDAP_SCOPE_SUBTREE, user_filter ) do |entry| + dn = entry.dn + end + if dn.empty? + logger.debug( "User not found in ldap" ) + return "User not found in ldap" + end + + # Update mail/password info + entry = [ + LDAP.mod(LDAP::LDAP_MOD_REPLACE,LDAP_MAIL_ATTR,[newemail]), + ] + if newpassword + case LDAP_AUTH_MECH + when :cleartext then + entry << LDAP.mod(LDAP::LDAP_MOD_REPLACE,LDAP_AUTH_ATTR,[newpassword]) + when :md5 then + require 'digest/md5' + require 'base64' + entry << LDAP.mod(LDAP::LDAP_MOD_REPLACE,LDAP_AUTH_ATTR,["{MD5}"+Base64.b64encode(Digest::MD5.digest(newpassword)).chomp]) + end + end + begin + ldap_con.modify(dn, entry) + rescue LDAP::ResultError + logger.debug("Error #{ldap_con.err} for #{login} mail/password changing") + return "Failed to update entry for #{login}: error #{ldap_con.err}" + end + + # Update the dn name if it is changed + if not login == newlogin + begin + ldap_con.modrdn(dn,"#{LDAP_NAME_ATTR}=#{newlogin}", true) + rescue LDAP::ResultError + logger.debug("Error #{ldap_con.err} for #{login} dn name changing") + return "Failed to update dn name for #{login}: error #{ldap_con.err}" + end + end + + ldap_con.unbind() + return + end + + # This static method tries to add the new entry with the given name/password/mail info in the + # active directory server. Return the error msg if any error occured + def self.new_entry_ldap(login, password, mail) + require 'ldap' + logger.debug( "Add new entry for #{login} using ldap" ) + ldap_con = initialize_ldap_con(LDAP_SEARCH_USER, LDAP_SEARCH_AUTH) + if ldap_con.nil? + logger.debug( "Unable to connect to LDAP server" ) + return "Unable to connect to LDAP server" + end + case LDAP_AUTH_MECH + when :cleartext then + ldap_password = password + when :md5 then + require 'digest/md5' + require 'base64' + ldap_password = "{MD5}"+Base64.b64encode(Digest::MD5.digest(password)).chomp + end + entry = [ + LDAP.mod(LDAP::LDAP_MOD_ADD,'objectclass',LDAP_OBJECT_CLASS), + LDAP.mod(LDAP::LDAP_MOD_ADD,LDAP_NAME_ATTR,[login]), + LDAP.mod(LDAP::LDAP_MOD_ADD,LDAP_AUTH_ATTR,[ldap_password]), + LDAP.mod(LDAP::LDAP_MOD_ADD,LDAP_MAIL_ATTR,[mail]), + ] + # Added required sn attr + if defined?( LDAP_SN_ATTR_REQUIRED ) && LDAP_SN_ATTR_REQUIRED == :on + entry << LDAP.mod(LDAP::LDAP_MOD_ADD,'sn',[login]) + end + + begin + ldap_con.add("#{LDAP_NAME_ATTR}=#{login},#{LDAP_ENTRY_BASE}", entry) + rescue LDAP::ResultError + logger.debug("Error #{ldap_con.err} for #{login}") + return "Failed to add a new entry for #{login}: error #{ldap_con.err}" + end + ldap_con.unbind() + return + end + + # This static method tries to delete the entry with the given login in the + # active directory server. Return the error msg if any error occured + def self.delete_entry_ldap(login) + logger.debug( "Deleting #{login} using ldap" ) + ldap_con = initialize_ldap_con(LDAP_SEARCH_USER, LDAP_SEARCH_AUTH) + if ldap_con.nil? + logger.debug( "Unable to connect to LDAP server" ) + return "Unable to connect to LDAP server" + end + user_filter = "(#{LDAP_SEARCH_ATTR}=#{login})" + dn = String.new + ldap_con.search( LDAP_SEARCH_BASE, LDAP::LDAP_SCOPE_SUBTREE, user_filter ) do |entry| + dn = entry.dn + end + if dn.empty? + logger.debug( "User not found in ldap" ) + return "User not found in ldap" + end + begin + ldap_con.delete(dn) + rescue LDAP::ResultError + logger.debug( "Failed to delete: error #{ldap_con.err} for #{login}" ) + return "Failed to delete the entry #{login}: error #{ldap_con.err}" + end + ldap_con.unbind() + return + end + # This static method tries to update the password with the given login in the # active directory server. Return the error msg if any error occured def self.change_password_ldap(login, password) -- 1.6.1 -- 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] Linked projects and submitting requests
by Anas Nashif 11 Aug '10

11 Aug '10

Hi, I am running the latest unstable packages targeting 2.1 and have found the following scenario not working. - Project A has all packages - Project A:Staging is a linked project using <link project="A" /> - Package X is in project A I do: osc branch A:Staging X (branching package X from project A:Staging) I checkout the branch and do a change and submit a request, it goes to A:Staging Now, when I try to accept the change, I get: Errorcode: 400 Message: broken link: linked package 'X' is empty Isnt that supposed to work? Anas-- 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] [PATCH] Unable to delete user via API
by Srinidhi B 11 Aug '10

11 Aug '10

Hi, If you try to delete a user from the api (Rails app), you will get a message saying: "You sent an invalid request!" After looking at api/app/controllers/active_rbac/user_controller.rb, I found that you can only POST to destroy and can only GET on delete. So here's another trivial patch that allows deletion of users from the Rails app. Srinidhi. diff --git a/src/api/app/views/active_rbac/user/delete.rhtml b/src/api/app/views/active_rbac/user/delete.rhtml index 90025b2..cf6b983 100644 --- a/src/api/app/views/active_rbac/user/delete.rhtml +++ b/src/api/app/views/active_rbac/user/delete.rhtml @@ -7,7 +7,7 @@ depending on this user (articles, for example). <strong>This action cannot be reverted!</strong> </p> -<% form_for :group, :url => { :action => :delete, :id => @user } do |form| %> +<% form_for :group, :url => { :action => :destroy, :id => @user } do |form| %> <%= submit_tag 'Yes', :name => 'yes' %> <%= submit_tag 'No', :name => 'no' %> -<% end %> \ No newline at end of file +<% end %> -- 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] [PATCH] Add changing password feature in the UI
by Zhang, Vivian 10 Aug '10

10 Aug '10

Hi, Please help to review these 2 patches. They're adding the feature of changing passwords in the UI(attached the screenshot) and works properly with common authentication mode and LDAP mode. This new feature is configurable and can be easily disabled by the user who does not want it. Thanks vivian

4 4

[opensuse-buildservice] mandriva-10.0 misses lib64lcms-devel on x86_64
by Kai-Uwe Behrmann 09 Aug '10

09 Aug '10

Hello, In one build I struggle with the lcms and gutenprint dependencies. They are not resolvable with lcms-devel eigther. Here an example log file: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=cinep… According to zarb.org it should be in the distro. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org -- 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] problem with .deb builds
by Nicholas Tung 09 Aug '10

09 Aug '10

Hi all, I'm running into a cryptic error with a .deb build for Ubuntu on OBS (below). Any help would be much appreciated, thanks! Thanks in advance, Nicholas — ntung at ntung — https://ntung.com — CS major @ UC Berkeley dpkg-source: warning: extracting unsigned source package (/usr/src/packages/SOURCES/sketch-cegis-1.4.0.dsc) dpkg-source: info: extracting sketch-cegis in /usr/src/packages/BUILD dpkg-source: error: missing orig.tar or debian.tar file in v2.0 source package ----------------------------------------------------------------- ----- building sketch-cegis-1.4.0.dsc (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- -su: line 0: cd: /usr/src/packages/BUILD: No such file or directory System halted. -- 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] [PATCH] osc-1.2.8 doesn't know about "signing" state
by Srinidhi B 08 Aug '10

08 Aug '10

Hi, When using osc-1.2.8 against 2.0.5 server, I got this: $ osc prjresults home:srinidhi osc: warn: unknown status 'signing'... please edit osc/core.py, and extend the buildstatus_symbols dictionary. So here is a small patch that adds "signing" state. I chose "S" just like that. Srinidhi. diff --git a/osc/core.py b/osc/core.py index df16258..ce5387e 100644 --- a/osc/core.py +++ b/osc/core.py @@ -185,6 +185,7 @@ buildstatus_symbols = {'succeeded': '.', 'scheduled': 's', 'excluded': 'x', 'dispatching': 'd', + 'signing': 'S', } -- 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] Error in osc; checkin doesn't run
by Sascha 'saigkill' Manns 06 Aug '10

06 Aug '10

Hello Mates, i've just updated my Spec from Skrooge [1]. But if i'm typing 'osc ci' i've got this message: error: Summary field must be present in package: (main package) ERROR: source_validator failed Has anyone seen this before? [1] http://susepaste.org/3530166 -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English)

2 4

[opensuse-buildservice] 'clicfs' not found / kiwi
by Javier Llorente 06 Aug '10

06 Aug '10

Hello listmates, I am trying to build a 11.2-based OEM image on the Build Service and I am getting the following error: 'clicfs' not found. https://build.opensuse.org/package/live_build_log?arch=x86_64&package=open- pc-image&project=spins%3Aopen-pc%3Aimages&repository=images How can I add it to my kiwi build environment? Another question: how can I build the OEM image against whatever version of kiwi is on Virtualization:Appliances? Thanks, -- Javier Llorente

2 6

[opensuse-buildservice] Safe way to remove /srv/obs/source folders
by Davis_Phillips＠Dell.com 05 Aug '10

05 Aug '10

Hello, I was wondering if there is considered a best practice for deleting the folders under /src/obs/source? The uploaded tarballs & spec files are being to consume a large amount of space on our front end servers. We would like to archive what we can in an effort to clean up the environment. Thanks in advance! Thanks! Davis Phillips Release Engineer Dell | PG Release Engineering office + 1 512 723 5910 -- 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] Question about Package Deletion
by Davis_Phillips＠Dell.com 05 Aug '10

05 Aug '10

Greetings everyone, I was hoping that someone would have a quick fix for an issue we are experiencing: There is a bad package in one of our projects: %{name} I can't delete the project or the package using osc or the front end. I temporarily removed the home page directories as a dependencies - this isn't preventing the project deletion. But: oscbdc rdelete --force OpenManage:640:HudsonBuilder_2 Server returned an error: HTTP Error 404: Not Found package '%{name}' does not exist in project 'OpenManage:640:HudsonBuilder_2' How do we get rid of this? I've already removed the %{name} files & folders in that repository on the frontend server: find /srv/obs/build/OpenManage:640:HudsonBuilder_2/ -name \*name\* | xargs sudo -u obsrun rm -rf And the :depends binary in the /srv/obs/builds repository holds this value. Is there a database table or something else we should look at first? Thanks! Davis Phillips Release Engineer Dell | PG Release Engineering office + 1 512 723 5910 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2