July 2019 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Debian Testing builds all fail with awk / libreadline problem
by Harald Welte 23 Jul '19

23 Jul '19

Dear OBS team, Since July 22nd all Debian Testing builds on build.opensuse.org appear to fail due to awk no longer being able to find its matching libreadline. It would be great if somebody could investigate what's happening. This is not meant as pressure, I just simpyl don't know if this bug has already been reported and is known, or not. btw: Is there a [public] bug tracker regarding teh build.opensuse.org instance somewhere? Thanks in advance. Regards, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

3 3

[opensuse-buildservice] Where is the 'osc release' documentation?
by Brown, Nicholas 19 Jul '19

19 Jul '19

Hi, The manpage of 'osc' states: > release > Release sources and binaries > > This command is used to transfer sources and binaries > without rebuilding them. It requires defined re‐ > lease targets set to trigger="manual". Please refer the > release management chapter in the OBS book for > details. > > usage: > osc release [ SOURCEPROJECT [ SOURCEPACKAGE ] ] > > But I cannot find any chapter on release management or mention of osc release at https://openbuildservice.org/help/manuals/obs-reference-guide/ Is the documentation on using the release command and manual triggers? Thanks, Nick N��r��y隊Z)z{.��Wlz��qﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǜ�)]��Ǿ� ޮ�^�ˬz��

3 4

Re: [opensuse-buildservice] How to change a user's password in private OBS installation?
by Stefan Botter 19 Jul '19

19 Jul '19

Hi all, hi David On Thursday, July 18, 2019 5:06:51 PM CEST David Kang wrote: > On 7/17/19 11:47 AM, Stefan Botter wrote: : > > how do I - as admin - change a user's password in a private OBS > > installation, e.g. with the builtin user management? > > In previous versions something like > > ---- > > RAILS_ENV="production" /usr/bin/rails.ruby2.5-5.1.4 console > > user = User.where(:login => '<loginname>').first > > user.password = "<password>" > > user.password_confirmation = "<password>" > > user.save > > ---- > > worked. Now this still succeeds (no error messages), but the user > > cannot login with the new password. > > > > How can I change the password? > > You can do it with: > > user = User.where(:login => '<loginname>').first > user.password = "<password>" > > user.save! It did not work, but I found out, that the user still had the password in the deprecated_password* fields set. The above procedure sets the password in password_digest, but does not NULL the deprecated_password* fields, and the latter seem to have precedence. NULLing the old fields lets the user finally login. Issue #7948 created. Greetings, Stefan -- Stefan Botter zu Hause Bremen

1 0

[opensuse-buildservice] How to change a user's password in private OBS installation?
by Stefan Botter 17 Jul '19

17 Jul '19

Hi all, how do I - as admin - change a user's password in a private OBS installation, e.g. with the builtin user management? In previous versions something like ---- RAILS_ENV="production" /usr/bin/rails.ruby2.5-5.1.4 console user = User.where(:login => '<loginname>').first user.password = "<password>" user.password_confirmation = "<password>" user.save ---- worked. Now this still succeeds (no error messages), but the user cannot login with the new password. How can I change the password? Thank you very much, Stefan -- Stefan Botter zu Hause Bremen

1 0

[opensuse-buildservice] Disable an error that is not (I am fairly certain) an error
by Roger Oberholtzer 15 Jul '19

15 Jul '19

I am trying to build a package in OBS (https://build.opensuse.org/package/show/home:rogeroberholtzer/blt30) On a couple platforms, the build fails as shown here: [ 185s] ... running 50-check-gcc-output [ 185s] ... testing for serious compiler warnings [ 185s] (using /usr/lib/build/checks-data/check_gcc_output) [ 185s] (using //.build.log) [ 185s] [ 185s] I: Statement might potentially overflow a destination buffer, where a size larger [ 185s] than the actual buffer was specified [ 185s] E: blt3 destbufferoverflow bltPictCmd.c:2432:9 I have checked the code, and I do not think the error is correct. An array of structures is defined. This storage is passed to a function that copies that amount of the same structures into the memory. I think it is some new gcc test that is broken on the platforms that fail. Since I cannot patch something that is not actually broken, how can I disable this test from being fatal to the build. It is not fatal to the compile. It is some later test that obs does that fails. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] OBS Maintenance Process - How to release a maintenance update to different codestream?
by Srinidhi B 15 Jul '19

15 Jul '19

Hello Everyone, I've a question regarding OBS Maintenance Process: What is the best way to re-release a maintenance update into a different codestream? What I mean to ask is - a maintenance update released for codestream X needs to be released into codestream Y with following conditions: * Packages should not be rebuilt in codestream Y * Binaries should not be signed again I've written a script that does the following: 1. Run cmd=createmaintenanceincident on the Maintenance project to create a new incident 2. Create "patchinfo" package 3. Update patchinfo/_patchinfo - based on a very slightly modified version of code taken from obs_admin --create-patchinfo-from-updateinfo - enable build and publish manually (I'm yet to figure out how to create proper hash for enabling these at the package creation time) 4. Branch Channel package - osc branch -M <Channels-prj> <channel-pkg> <maintenance-incident> 5. Enable channel - osc enablechannel <maintenance-incident> <channel-pkg> 6. Upload / inject binaries and updateinfo.xml fetched from step 3 to "patchinfo" package What I found while talking to Adrian on IRC, I can't raise a release request for such a maintenance incident because the API can't find a package other than "patchinfo" in "succeeded" state. And even if I use _aggregates for these packages, then also, I can't raise a release request because "patchinfo" package is always "excluded" saying "no package enabled". How do I go about re-releasing a maintenance update? Regards, Srinidhi. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 7

[opensuse-buildservice] Raspian
by Martin Koegler 11 Jul '19

11 Jul '19

As Raspian 10 has been released (http://archive.raspbian.org/raspbian/dists/stable/ points to buster), would it be possible to add it to OBS too? mfg Martin -- 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] Observations during update to 2.10
by Stefan Seyfried 10 Jul '19

10 Jul '19

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.UPDATE… 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(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

Re: [opensuse-buildservice] Ubuntu Next and Fedora Rawhide builds failing: missing libpcre2
by Adrian Schröter 10 Jul '19

10 Jul '19

On Montag, 8. Juli 2019, 10:47:56 UTC Rosanne DiMesio wrote: > On Mon, 08 Jul 2019 09:30:33 +0000 > > Adrian Schröter <adrian(a)suse.de> wrote: > > as usual, some pointer where you reproduce the error would be welcome... > > https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel added in the config for ubuntu. > https://build.opensuse.org/package/show/Emulators:Wine:Fedora/wine-devel hm, that one is more questionable, it is provided by pcre2 and that one is also preinstalled in your build. Sorry, no time to debug it atm, but everyone can using "osc build" and tell me the solution :) -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany 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

3 4

[opensuse-buildservice] Missing Image Templates (and requested output types)
by Bryan Gartner 09 Jul '19

09 Jul '19

FYI, starting at https://studioexpress.opensuse.org/ and following the link to the image templates ( https://build.opensuse.org/image_templates ), I'm not seeing: - any SLE 12-SP4 options (was looking for JeOS in particular) - a delineation of SLE 15 vs 15-SP1 options And as a feature request, could an example type of - ISO (general purpose and/or Live) - OEM Expandable Disk - File system (for PXE) output format be also included in the respective Leap/Tumbleweed JeOS config.kiwi templates, please? 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

2 1