Mailinglist Archive: opensuse-buildservice (93 mails)

< Previous Next >
[opensuse-buildservice] Observations during update to 2.10
Hi all,

just some notes from the update of my test-OBS to 2.10:

https://github.com/openSUSE/open-build-service/blob/2.10/dist/README.UPDATERS#L17
Please run following command: '(cd /srv/www/obs/api/; rake
migrate_options_yml)'

This failed miserably before I had updated the RPMs, but is listed in the
README prior to the update.
After the update it still failed, until I did 'export RAILS_ENV="production"'

Lots of warnings, but they seem harmless:

test-obs:/srv/www/obs/api # RAILS_ENV="production" rake migrate_options_yml
/usr/lib64/obs-api/ruby/2.5.0/gems/rake-12.3.2/lib/rake/file_utils.rb:10:
warning: already initialized constant
FileUtils::RUBY
/usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.2/lib/rake/file_utils.rb:10: warning:
previous definition of RUBY was here
/usr/lib64/obs-api/ruby/2.5.0/gems/rake-12.3.2/lib/rake/file_utils.rb:109:
warning: already initialized constant
FileUtils::LN_SUPPORTED
/usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.2/lib/rake/file_utils.rb:109:
warning: previous definition of LN_SUPPORTED was
here
/usr/lib64/obs-api/ruby/2.5.0/gems/rake-12.3.2/lib/rake/file_utils_ext.rb:17:
warning: already initialized constant
Rake::FileUtilsExt::DEFAULT
/usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.2/lib/rake/file_utils_ext.rb:17:
warning: previous definition of DEFAULT was here
WARNING: Possible conflict with Rake extension: String#ext already exists
WARNING: Possible conflict with Rake extension: String#pathmap already exists
/usr/lib64/obs-api/ruby/2.5.0/gems/rake-12.3.2/lib/rake/file_list.rb:44:
warning: already initialized constant
Rake::FileList::ARRAY_METHODS
/usr/lib64/ruby/gems/2.5.0/gems/rake-12.3.2/lib/rake/file_list.rb:44: warning:
previous definition of ARRAY_METHODS was here
...


btw: why do we need both obs-bundled-gems and all the gems packaged on their
own again?

That's it for now.
I had to add a dependency for all obs services to srv-obs.mount, because they
were started before the NFS share was
mounted and then failed, but that's something that probably cannot be made to
work out of the box, because every setup
is different in that regard, and it can be done easily with systemd dropin
configs (I had to do the same with previous
obs versions).

Is the feature "configure to follow symlinks in /srv/obs/build" still on
anyone's watch list?
I adopted my old patch, now it looks like

--- a/src/backend/BSCpio.pm
+++ b/src/backend/BSCpio.pm
@@ -84,7 +84,7 @@ sub openentfile {
@$s = lstat($file);
return (undef, "$name: $file: $!\n") unless @$s;
if (-l _) {
- return (undef, "$name: $file: is a symlink\n") if !$ent->{'follow'} &&
!$follow;
+ # return (undef, "$name: $file: is a symlink\n") if !$ent->{'follow'} &&
!$follow;
} elsif (! -f _) {
return (undef, "$name: $file: not a plain file\n");
}

Best regards,

seife
--
Stefan Seyfried

"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
  • No further messages