Yet another OBS 2.1 release is out there. It brings the final compatibility
with OBS 2.3 instances and has an extra protection layer against programming
errors on the rails level.
You find it as usual in the openSUSE:Tools:2.1 project. This the last chance
to switch there, if you do not want to get the OBS 2.3 RC candidate from openSUSE:Tools
project.
Repositories are available here:
http://download.opensuse.org/repositories/openSUSE:/Tools:/2.1/
The Changelog:
==============
- enforce rubygems < 1.6.0 to avoid runtime errors
- update to version 2.1.17
Feature backports:
==================
* Support linking to remote OBS 2.3 package which contains links with vrev attribute
Changes:
========
* Added new default targets for SUSE Linux Enterprise SP1 and SP2 builds
* Removed RHEL-4 default target (EOL)
* Additional protection layer against a possible undetect security leak due to mass-assignment handling
Bugfixes:
=========
* reopen not accepted reviews when re-opening a request
* fixed icon links in distribution list
* fixed execution with rails 2.3.8 on SLE 11 SP 1
--
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
Hi list,
(Apparently) there are problems with the official kernel for 12.1
(3.1.9-1.4-desktop) and openafs :
When compiling the linux kernel in AFS with "make -j 10"
the (multicore) machine just freezes, slighter
symptoms are a bug message in the log-message like :
Mar 9 11:08:50 mflin03 kernel: [ 355.532788] BUG: scheduling while
atomic: ls/2242/0x00000002
I talked to the openafs-developers and they said, they're doing the
right thing.
And indeed the kernel from Tumbleweed (3.2.9-13-desktop) works fine.
So, I'd like to conflict the kernel 3.1.9-1.4-* with
openafs-kmp-* or better require kernel >= 3.2.9-13-*.
Is something like that possible ?
Or do I have to put the conflict in some base-package ?
Beside that, I could just wipe the 12.1 binaries until there is a new
kernel that works with openafs.
Any hints ?
Many thanks,
Christof
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi:
I am trying to build for PPC in my local workstation (x86_64) but I
cannot go futher than downloading packages...
build aborts with an unfriendly :
WARNING: It is guessed to build on hostarch 'x86_64' for 'ppc' via QEMU.
Verifying integrity of cached packages
using keys from openSUSE:Factory
Writing build configuration
Running build
[Errno 2] No such file or directory ( broken error handling here)
It happends to want to execve() /sbin/powerpc32 in the host which of
course fails..
Any pointers how to make qemu actually work ?
Cheers !
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
since yesterday ppc glibc, gcc, etc. are rebuilding again and again. So
my packages are blocked.
First I thought that's just some kind of bootstrapping but now I think
it will never finish.
Anybody knows whether everything is ok or not?
cu,
Rudi
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello.
I tried my own instances based on current branch 2.3 and instances from openSUSE:Tools:unstable -- the behavior is the same:
- have no problems with connection to openSUSE.org instance
- in case if I connect instances to each other, I see endlessly repeated loop in slave OBS instance scheduler log:
lost sync with server, was at N
next: N
There 'N' is some number from lastevent.
Did somebody faced to this problem?
--
Best Regards,
Denis Pynkin
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I added 2 new worker hosts and stopped obs-worker service on old host
several days ago. However, OBS web UI /monitor page still shows my old host
and does not show two new ones. Builds are running just fine, which means
that obs server knows about new workers and uses them.
Any idea how to fix this? At least where to look in the code?
I am using obs 2.1.16 on OpenSUSE 11.4
Regards,
Ed
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
in the server:mail/exim repository we see some very old build results
lurking.
Exim is at version 4.77 while we see several build results of 4.69 and
4.71 as soon as you search starting at
http://software.openSUSE.org/121/en for example.
I guess this is the result of others linking to the server:mail/exim
project.
Is it possible to purge these 4.69 and 4.71 builds?
Or is it required to remove all builds including the current exim 4.77
and then 4.77 gets build again?
Cheers,
Lars
--
Lars Müller [ˈlaː(r)z ˈmʏlɐ]
Samba Team
SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Hi,
I run a private OBS on 12.1 from Tools:unstable.
Since I updated (run zypper up) on last Monday (12.03) I get every hour a
cron mail with:
'''''''''''''''''''''''''
From: Cron Daemon <wwwrun(a)pingi8.linux-pingi.de>
To: wwwrun(a)pingi8.linux-pingi.de
Subject: Cron <wwwrun@pingi8> cd /srv/www/obs/api/ && RAILS_ENV=production rake -s jobs:updateissues
rake aborted!
Wrong type NilClass. Not allowed!
Tasks: TOP => jobs:updateissues
(See full trace by running task with --trace)
..............................
I did run RAILS_ENV=production rake db:migrate
If I run it with trace I get:
###############################################################
pingi8:~ # cd /srv/www/obs/api/ && RAILS_ENV=production rake --trace -s jobs:updateissues
** Invoke jobs:updateissues (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute jobs:updateissues
rake aborted!
Wrong type NilClass. Not allowed!
/usr/lib64/ruby/1.8/xmlrpc/create.rb:207:in `conv2value'
/usr/lib64/ruby/1.8/xmlrpc/create.rb:230:in `conv2value'
/usr/lib64/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `collect'
/usr/lib64/ruby/1.8/xmlrpc/create.rb:227:in `each'
/usr/lib64/ruby/1.8/xmlrpc/create.rb:227:in `collect'
/usr/lib64/ruby/1.8/xmlrpc/create.rb:227:in `conv2value'
/usr/lib64/ruby/1.8/xmlrpc/create.rb:118:in `methodCall'
/usr/lib64/ruby/1.8/xmlrpc/create.rb:117:in `collect'
/usr/lib64/ruby/1.8/xmlrpc/create.rb:117:in `methodCall'
/usr/lib64/ruby/1.8/xmlrpc/client.rb:419:in `call2'
/usr/lib64/ruby/1.8/xmlrpc/client.rb:410:in `call'
/usr/lib64/ruby/1.8/xmlrpc/client.rb:617:in `send'
/usr/lib64/ruby/1.8/xmlrpc/client.rb:617:in `method_missing'
/srv/www/obs/api/app/models/issue_tracker.rb:54:in `update_issues'
/srv/www/obs/api/lib/tasks/delayed_job.rake:17
/srv/www/obs/api/lib/tasks/delayed_job.rake:15:in `each'
/srv/www/obs/api/lib/tasks/delayed_job.rake:15
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `call'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `execute'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `each'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `execute'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:158:in
/`invoke_with_call_chain'
/usr/lib64/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:151:in
/`invoke_with_call_chain'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:144:in `invoke'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:112:in
/`invoke_task'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in
/`top_level'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in
/`each'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in
/`top_level'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in
/`standard_exception_handling'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:84:in
/`top_level'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:62:in `run'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in
/`standard_exception_handling'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:59:in `run'
/usr/lib64/ruby/gems/1.8/gems/rake-0.9.2/bin/rake:32
/usr/bin/rake:19:in `load'
/usr/bin/rake:19
Tasks: TOP => jobs:updateissues
#############################################################
I did another update yesterday, no change.
Karsten
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
