February 2016 - openSUSE Build Service

[opensuse-buildservice] openSUSE Leap 42.1: have choice for libwx_baseu
by Matwey V. Kornilov 17 Feb '16

17 Feb '16

Hello, At my test project [1] package 'erlang-wx-test' is unresolved for openSUSE Leap 42.1. Its requirement erlang-wx has choice for libwx_baseu. At the same time, erlang-wx can be installed without conflicts or choices on freshly installed openSUSE Leap system: # zypper in --no-recommends erlang-wx Загрузка данных о репозиториях... Чтение установленных пакетов... Разрешение зависимостей пакетов... The following 64 NEW packages are going to be installed: erlang-wx gdk-pixbuf-query-loaders gtk2-tools libatk-1_0-0 libcairo2 libdrm2 libdrm_amdgpu1 libdrm_intel1 libdrm_nouveau2 libdrm_radeon1 libgbm1 libgdk_pixbuf-2_0-0 libGLU1 libgtk-2_0-0 libjasper1 libjbig2 libmspack0 libpango-1_0-0 libpciaccess0 libpixman-1-0 libtiff5 libwayland-client0 libwayland-server0 libwx_baseu-2_8-0-compat-lib-stl libwx_baseu-2_8-0-stl libwx_baseu_xml-2_8-0-stl libwx_gtk2u_adv-2_8-0-compat-lib-stl libwx_gtk2u_adv-2_8-0-stl libwx_gtk2u_aui-2_8-0-compat-lib-stl libwx_gtk2u_aui-2_8-0-stl libwx_gtk2u_core-2_8-0-compat-lib-stl libwx_gtk2u_core-2_8-0-stl libwx_gtk2u_gl-2_8-0-compat-lib-stl libwx_gtk2u_gl-2_8-0-stl libwx_gtk2u_html-2_8-0-compat-lib-stl libwx_gtk2u_html-2_8-0-stl libwx_gtk2u_stc-2_8-0-compat-lib-stl libwx_gtk2u_stc-2_8-0-stl libwx_gtk2u_xrc-2_8-0-compat-lib-stl libwx_gtk2u_xrc-2_8-0-stl libX11-xcb1 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-render0 libxcb-shm0 libxcb-sync1 libxcb-xfixes0 libXcomposite1 libXcursor1 libXdamage1 libXfixes3 libXi6 libXinerama1 libXrandr2 libxshmfence1 libXxf86vm1 Mesa Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 pango-tools wxWidgets-compat-lib-config Here, I wonder whether it is a bug in erlang package or not, or something is missed in project config? [1] https://build.opensuse.org/project/monitor/home:matwey:erlang-wx-test -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] What am I doing wrong creating a new package?
by Dave Plater 14 Feb '16

14 Feb '16

Hi, I've never seemed to get this right, I either create a new package directory under my home:plater directory then download the packages src tarball or another distros src rpm and create or in the case of src rpm fix the spec file and then create a changes file with osc vc. I create the package in my home project in the build service using osc meta pkg -e and then use osc init, osc ar and osc ci to upload the files. This used to work once upon a time but lately I have to manually add the files to my build service package, delete the local package directory I've created and then check it out with osc co. Is there no easy way to create the package on my local machine and then upload to my home project? Thanks Dave P -- 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] Missing link display in webui
by Martin Koegler 13 Feb '16

13 Feb '16

I have linked two packages and added a patches via "<add name=..." nearly at the same time. https://build.opensuse.org/package/show/home:e9925248:branches:openSUSE:Lea… is correctly displayed. https://build.opensuse.org/package/show/home:e9925248:branches:openSUSE:Lea… does not list "links to .." and "has a link diff". A checkout of the package with -u just contains the _link file plus my patches. Simlar situation [although I converted from a branch to a link]: https://build.opensuse.org/package/show/home:e9925248:branches:openSUSE:Lea… is OK. https://build.opensuse.org/package/show/home:e9925248:branches:openSUSE:Lea… is missing the link display in the webui - -u checkout is OK. Regards, Martin -- 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] OBS:Server:2.6 for Leap 42.1
by Alex Naumov 11 Feb '16

11 Feb '16

Hello, it looks like OBS:Server:2.6 and OBS:Server:Unstable are still not there. When we plan to release some_of_OBS for Leap? :) Alex -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

Re: [opensuse-buildservice] v4 signs in obs-signd
by Michal Novotny 11 Feb '16

11 Feb '16

The main problem with the implementation of v4 rpm signatures is that the generated hash (sent to key server) now needs to "contain" the respective public key algorithm. According to RFC4880, these values are hashed (public key alg is between them): - One-octet version number (4). - One-octet signature type. - One-octet public-key algorithm. - One-octet hash algorithm. - Two-octet scalar octet count for following hashed subpacket data. Note that this is the length in octets of all of the hashed subpackets; a pointer incremented by this number will skip over the hashed subpackets. - Hashed subpacket data set (zero or more subpackets). - Two-octet scalar octet count for the following unhashed subpacket data. Note that this is the length in octets of all of the unhashed subpackets; a pointer incremented by this number will skip over the unhashed subpackets. However, the public key is not generally present on the client where the hash is generated, which is unfortunate. Because of that we cannot easily generate the final hash on the client. The preferred solution would be to send just the base hash state made just of rpm data (rpm's header-only SHA1/SHA256 hash and header+payload hash). It's the state before writing any additional values into the hash - that should be done on the remote (key-)server. The problem with this approach is that libgrypt library does not easily allow this as far as I have discovered. So far I haven't found a way to initialize gcry_md_context by the received data and then continue with hashing from there. At the moment, the hash is finalized prematurely for me, that is before writing the above mentioned additional data. The relevant piece of code is this: mdb = gcry_md_read(mfx.md, opt.def_digest_algo); // this itself finalizes the hash in gpg2: g10/sign.c. These are pretty much my findings so far. -- 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] v4 signs in obs-signd
by Miroslav Suchý 10 Feb '16

10 Feb '16

Hi, I just learn the hard way that gnupg2 had this change; --force-v3-sigs --no-force-v3-sigs --force-v4-certs --no-force-v4-certs These options are obsolete and have no effect since GnuPG 2.1. The problem is that these options are used by signd perl script from obs-signd. Those options are silently ignored now. However, when --files-are-digest is then used it errors with: "files-are-digests doesn't work with v4 sigs" Latest working gpg is 2.0.x. If you have your own instance of OBS be careful when upgrading to not upgrade gpg2. Does anybody started investigating or even writing support for files-are-digest for v4 sigs? -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 9

[opensuse-buildservice] force reevaluation of prjconf
by Olaf Hering 08 Feb '16

08 Feb '16

What command can be used, beside 'osc commit', to trigger a reevaluation of prjconf? If a pkg is in state "unresolvable" after commit, and the prjconf gets changed to solve the dependency no rebuild happens. A local 'osc build' works, but 'osc wipebinaries -r <repo>' or 'osc rebuild -f' will still use the previous state of prjconf. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 8

[opensuse-buildservice] why authentication required to retrieve build log from OBS
by Normand 03 Feb '16

03 Feb '16

Hi there, I noticed that I am not able to retrieve anymore from OBS a build log file, as reported by (1) it seems authentication is now required. Is it a planned change or is there an error somewhere ? (1) https://build.opensuse.org/build/openSUSE:Factory:PowerPC/standard/ppc64le/… === $wget https://build.opensuse.org/build/openSUSE:Factory:PowerPC/standard/ppc64le/… --2016-02-03 09:48:39-- https://build.opensuse.org/build/openSUSE:Factory:PowerPC/standard/ppc64le/… Resolving build.opensuse.org (build.opensuse.org)... 2001:67c:2178:8::12, 195.135.221.133 Connecting to build.opensuse.org (build.opensuse.org)|2001:67c:2178:8::12|:443... connected. HTTP request sent, awaiting response... 401 Unauthorized Username/Password Authentication Failed. === -- Michel Normand -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] osb appliance doesn't support http proxy ?
by Dieter Bloms 03 Feb '16

03 Feb '16

Hello, I try to setup the actual obs appliance 2.6.8-Build1.1 behind a http proxy without authentication. After a fresh install I configured the proxy in /etc/sysconfig/proxy and rebooted the appliance. A zypper refresh shows me, that it can accesss the internet (it ask me to accept a gpg key and list some packages to update). But it seems, that the obs stuff doesn't use the proxy settings. With netstat I see SYN_SENT from process "delayed_job.10" to the ip 130.57.66.6 Does obs support internet accesss trough a http proxy ? -- Regards Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the >From field. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] Open Build Service (OBS) 2.6.8 released
by Christian Bruckmayer 03 Feb '16

03 Feb '16

OBS 2.6.8 released ================== This release fixes several CVEs in OBS related dependencies (rails, sprockets, jquery, rack). The related CVEs are stated in the Release Notes. For more information, please see this blog article from the official rails website: http://weblog.rubyonrails.org/2016/1/25/Rails-5-0-0-beta1-1-4-2-5-1-4-1-14-… OBS 2.5 and 2.4 are also affected, but not yet fixed. Updaters from any OBS 2.6 release can just ugrade the packages and restart all services. Updaters from former releases should read the README.UPDATERS file. OBS update are available from the following projects: https://build.opensuse.org/project/show/OBS:Server:2.6 The appliance can be downloaded from http://openbuildservice.org/download Details from the Release Notes of 2.6.8: ======================================== Feature backports: ================== * none Changes: ======== * none Bugfixes: ========= * [webui] Update rails to version 4.1.14.1 to fix several security issues (CVE-2015-7576, CVE-2016-0751, CVE-2015-7577, CVE-2016-0752, CVE-2016-0753, CVE-2015-7581) * [webui] Update rack to version 1.5.5 to fix security issue (CVE-2015-3225) * [webui] Update jquery-rails to version 3.1.4 to fix security issue (CVE-2015-1840) * [webui] Update sprockets to version 2.11.3 (CVE-2014-7819) * [webui] Fix redirect after login for iChain and proxy mode * [backend] fix local building inside a project on a remote OBS instance * [backend] fix lost events on scheduler restart -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0