October 2016 - openSUSE Build Service - openSUSE Mailing Lists

Re: [opensuse-buildservice] Denying source access?
by Adrian Schröter 14 Oct '16

14 Oct '16

On Dienstag, 4. Oktober 2016, 18:48:12 CEST wrote Erico Mendonca: > Yes, same error. > Looking at the source, I found /srv/www/obs/api/app/helpers/flag_helper.rb. The check is actually in app/controllers/source_controller.rb def update_package_meta at least when you see the change_package_protection_level error. So, better double-check that your used user has really the Admin role: osc api /person/$used_user > The default flags are declared here, but I found nowhere in the DB where these flags associated with the projects/packages. > If I change the default here to “disable”, the source disappers from all projects (obviously), so this is the flag I need to set (and I can’t). > > > -- > — Erico Mendonça > Dedicated Support Engineer > SUSE > > Em 04/10/16 10:52, "Adrian Schröter" <adrian(a)suse.de<mailto:adrian@suse.de>> escreveu: > > On Dienstag, 27. September 2016, 17:02:05 CEST wrote Erico Mendonca: > Hello all, > I need to restrict source access in a few packages. I found out about the “<sourceaccess><disable/></sourceaccess>” tags, but whenever I try to edit a package, either via the WebUI or via “osc meta pkg -e”, I get a permission error: > BuildService API error: change_package_protection_level (403) > admin rights are required to raise the protection level of a package. > However, I do have all permissions for the package. I even tried as Admin with the same results. Any ideas? > This is a private OBS instance running OBS 2.7.2. > > Can you try with > > osc meta prj -e ... > > ? Does it show the same error? > > -- > > Adrian Schroeter > email: adrian(a)suse.de<mailto:adrian@suse.de> > > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) > Maxfeldstraße 5 > 90409 Nürnberg > Germany > > > > -- Adrian Schroeter email: adrian(a)suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- 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] the impact of 'Prefer' during dependency solving
by Olaf Hering 14 Oct '16

14 Oct '16

How does a 'Prefer: x' in prjconf influence the solver which calculates the required packages for build? Does it only affect failures like 'have choice for x < N: A B'? Or would it also affect the selected version of 'x' if two pkgs provide 'x' in different versions? The prjconf in Factory and 42.2 have "Prefer: -ffmpeg2-devel". This pkg provides 'pkgconfig(x) = 1'. Another pkg "x2" in the projects above provides 'pkgconfig(x) = 2'. There are pkgs which have "BuildRequires: pkgconfig(x)" and I think the solver just picks the one with the higher version number, so the "Prefer:" is likely unneeded. Within Factory and 42.2 the "Prefer:" does not cause trouble. In a private prj with Factory or 42.2 as base project the "Prefer:" does cause trouble, because there is likely no "UnPrefer:". In that private prj there is a pkg "x0" which provides "pkgconfig(x) = 0". The private repo has "Prefer: -x0" in prjconf. In addition there are pkgs which have one of "BuildRequires: pkgconfig(x)", "BuildRequires: pkgconfig(x) = 0", "BuildRequires: pkgconfig(x) = 1" and "BuildRequires: pkgconfig(x) < 2". Since "Prefer: -ffmpeg2-devel" was added to Factory/42.2 all pkgs with "BuildRequires: pkgconfig(x) < 2" are now in state unresolvable: have choice for pkgconfig(x) < 2: x0 ffmpeg2-devel This could be solved by adding 'Prefer: ffmpeg2-devel' to prjconf. How would such change affect pkgs with "BuildRequires: pkgconfig(x)"? Will the solver pick "ffmpeg2-devel" or "x2" for unversioned BuildRequires? Olaf

1 0

Disregard vs decline (was: [opensuse-buildservice] Mass-rejecting SRs)
by Robert Munteanu 10 Oct '16

10 Oct '16

> $ for sr in $(grep -Po '^\d+' < leap_srs); do echo "osc rq decline > -m 'Mass decline for pear submissions Leap 42.2, as no maintainer has > stepped up'" $sr; done Seems I spoke to soon, as apparently I can't decline requests for Leap 42.2 as a devel project maintainer: HTTP Error 403: Forbidden post_request_no_permission No permission to decline request 430219 Also, in the UI the action is labeled as 'Disregard', not 'Decline'. There is no osc rq decline support, so how do I perform this action using osc? Using `osc api` would work, but I'm not sure of the exact arguments to pass. I looked at what the OBS web UI does when 'disregarding' a SR, but it does not seem to be talking to the backend. Thanks, Robert -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] Mass-rejecting SRs
by Robert Munteanu 09 Oct '16

09 Oct '16

Hi, I'd like to do a mass rejection of some SRs submitted against a given project. However, I'm not sure how to isolate the SRs using osc. The output of osc my is not very friendly for scripting as the id and the name of the project + package are on different lines. Any suggestions of how to extract the SR ids based on project name + package name ( regexp ) would be very welcome. Thanks, Robert -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] OBS getbinaries failed
by Martin Koegler 06 Oct '16

06 Oct '16

https://build.opensuse.org/package/live_build_log/home:e9925248:grandorgue/… failed with: getbinaries: missing packages: libffi4 If a package is missing, I would expect, that the build stays in unresolvable state. Regards, Martin -- 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] Leap in OBS
by Stanislav Baiduzhyi 06 Oct '16

06 Oct '16

I can see that some projects are already building for Leap_42.1, but it is not in the checkboxes on Repositories tab on OBS project page, and in advanced repo UI there are so many of them that it is quite confusing. Will it be added to the checkboxes eventually, to make some packages "Leap ready"? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 7

[opensuse-buildservice] Direct update 13.1/2.6 -> 42.1/2.7?
by Till Dörges 06 Oct '16

06 Oct '16

Hi all, currently I've OBS 2.6 running under openSUSE 13.1. I'd like to update both OBS (to 2.7) and OS (to Leap 42.1). I guess the conservative approach would be: 13.1/2.6 -> 13.2/2.6 -> 13.2/2.7 -> 42.1/2.7 Is there any known reason why a direct update to Leap 42.1 and OBS 2.7 should not work? I'm asking because OBS 2.6 has not been released for 42.1 and OBS 2.7 has not been released for 13.1 under http://download.opensuse.org/repositories/OBS:/Server:/. TIA -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de Tel. +49 - 40 - 244 2407 - 14 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 Wir sind auf der it-sa: 18.-20.10.2016 http://www.it-sa.de -- 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] Source RPMs in OBS
by Roger Oberholtzer 05 Oct '16

05 Oct '16

When I build packages in OBS, I get a source RPM for each architecture (e.g., i586, x86_64). I am curious what the differences might be in these source RPMs. I would guess there are two possible sources of differences: the package's .spec file and the OBS macros used when making the source RPMs. Are there directives in either of these that are resolved when the source RPM is built, resulting in a different source RPMs on a specific platform? I ask because I am considering making a local copy of the source RPMs I have in OBS so that, in an emergency, they can be used to rpmbuild --rebuild the package locally. This is working fantastic for me. But I have been using the source rpm for each platform. Do I really need to do this? The built binary RPMs I build locally are, of course, for the platform on which I run rpmbuild. Does this question make sense? -- 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 4

[opensuse-buildservice] Denying source access?
by Erico Mendonca 04 Oct '16

04 Oct '16

Hello all, I need to restrict source access in a few packages. I found out about the “<sourceaccess><disable/></sourceaccess>” tags, but whenever I try to edit a package, either via the WebUI or via “osc meta pkg -e”, I get a permission error: BuildService API error: change_package_protection_level (403) admin rights are required to raise the protection level of a package. However, I do have all permissions for the package. I even tried as Admin with the same results. Any ideas? This is a private OBS instance running OBS 2.7.2. -- Erico Mendonça Dedicated Support Engineer SUSE N��r��y隊Z)z{.��Wlz��qﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǜ�)]��Ǿ� ޮ�^�ˬz��

2 1

[opensuse-buildservice] Upgrading to OBS 2.7, database migrate fails
by Troels Hansen 04 Oct '16

04 Oct '16

Hi there, I'm trying to upgrade to OBS 2.7, and I need to migrate the DB. The instructions (from https://github.com/openSUSE/open-build-service/blob/master/dist/README.UPDA…) tell my to run "RAILS_ENV="production" rails.ruby2.3 db:migrate" However, I get an 'Error: Command 'db:migrate' not recognized' Am I doing something wrong? (obviousle I am).... -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3