January 2016 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Mismatch between Debian repository metadata and binaries
by David Adam 02 Feb '16

02 Feb '16

Hi all, Somehow we have a mismatch between the metdata in the repository for our package and the actual downloadable binaries. We have this repository: http://download.opensuse.org/repositories/shells:/fish:/release:/2/ The Debian 7 packages file is http://download.opensuse.org/repositories/shells:/fish:/release:/2/Debian_7… and contains: Filename: ./amd64/fish_2.2.0-1_amd64.deb Size: 1722112 MD5sum: 140e31df39226c87543102df8092c967 but: $ wget http://download.opensuse.org/repositories/shells:/fish:/release:/2/Debian_7… ... Length: 1717944 (1.6M) [application/x-deb] Saving to: ‘fish_2.2.0-1_amd64.deb’ $ md5sum fish_2.2.0-1_amd64.deb b7a86950372a9d3bb81894fc258cae5f fish_2.2.0-1_amd64.deb Is there something I've done wrong? The only thing I've changed recently was to update the expiry on the repository signing key, after which I rebuilt the packages. Is there a way to rebuild the repository metadata, or should I just rebuild all the packages again? Thanks, David Adam shells:fish maintainer zanchey(a)ucc.gu.uwa.edu.au

1 1

[opensuse-buildservice] post-build-checks
by Martin Koegler 27 Jan '16

27 Jan '16

https://github.com/openSUSE/post-build-checks/blob/master/checks/06-check-i… It calls the RPM install scripts with 2, the uninstall scripts with 1. This means upgrade [https://meinit.nl/rpm-spec-prepostpreunpostun-argument-values]. While upgrading, a package should keep its modifications. So shouldn't the parameters be 1 for install and 0 for uninstall. 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] Can't access OBS (HTTP Error 401: basic auth failed)
by Till Dörges 26 Jan '16

26 Jan '16

Hello all, since a few days I can't access build.opensuse.org anymore: user@box:> osc -A https://build.opensuse.org ls Server returned an error: HTTP Error 401: basic auth failed The problem persists, even if I start from scratch mv ~/.oscrc ~/.oscrc.old rm ~/.osc_cookiejar The credentials are correct. Login via browser works, too. Using the debug switch doesn't give me anything obvious osc --http-full-debug -A https://build.opensuse.org ls What the client sends, looks OK (I replaced the base64 encoded string, but it definitely does contain the correct credentials): send: 'GET /source HTTP/1.1\r\nAccept-Encoding: identity\r\nHost: build.opensuse.org\r\nConnection: close\r\nAuthorization: Basic <REPLACED>=\r\nUser-agent: osc/0.145\r\n\r\n' The reply then reads reply: 'HTTP/1.1 401 Unauthorized\r\n' header: Date: Mon, 25 Jan 2016 18:58:53 GMT header: Server: Apache/2.2.12 (Linux/SUSE) header: Strict-Transport-Security: max-age=31536000 header: Cache-Control: no-cache header: Vary: Accept-Encoding header: X-XSS-Protection: 1; mode=block header: WWW-Authenticate: basic realm="API login" header: X-Opensuse-Runtimes: {"view":0.0,"db":1.019252,"backend":0,"xml":0} header: X-Request-Id: d3115a6c-b7b6-45eb-bfac-d3dfc6ae55ee header: X-Opensuse-APIVersion: %version header: X-Runtime: 0.010875 header: X-Frame-Options: SAMEORIGIN header: X-Content-Type-Options: nosniff header: X-Opensuse-Errorcode: anonymous_user header: X-Powered-By: Phusion Passenger 5.0.22 header: Status: 401 Unauthorized header: Content-Type: application/xml; charset=utf-8 header: Connection: close header: Transfer-Encoding: chunked I tested with OSC versions 0.145 and 0.152. Why does it not work anymore? Any help is appreciated as usual! Thanks and regards, 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 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] All project targets report "repository setup is broken, build not possible" and api.opensuse.org/public is down
by Neal Gompa 25 Jan '16

25 Jan '16

Hello, On Thursday, I set up a new instance of OBS, expecting for it to be as functional as all the previous ones I had before. However, I wound up being unable to build anything with it, because all the build targets don't work. The error it reports is "The repository setup is broken, build not possible". After quite a bit of digging, I found out that api.opensuse.org/public is returning HTTP 404 errors, which I believe is preventing my OBS instances from configuring and building packages. I'm running OBS Unstable, but I've also verified the problem with OBS 2.6.7 as well. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 14

[opensuse-buildservice] Is OBS down? Or did I break my system?
by Greg Freemyer 23 Jan '16

23 Jan '16

> osc build Server returned an error: HTTP Error 401: Authorization Required I've tried from a couple different packages I've built locally before. I may have corrupted .oscrc yesterday (I used vi to make a change, but I did a "osc build" since then.) Thanks Greg -- Greg Freemyer www.IntelligentAvatar.net -- 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] Problems with devel:languages:python
by Johannes Weberhofer 22 Jan '16

22 Jan '16

Dear all! Since a week or soit's nearly impossible to build packages for devel:languages:python. I'm working on https://build.opensuse.org/package/show/devel:languages:python/python-acme which I need to build a new version of https://build.opensuse.org/package/show/home:weberho:branches:devel:languag… ; the pyton-acme project has been built successfully several times, but building the letsencrypt package which requires python-acme always shows "nothing provides python-acme = 0.2.0". Any idea what can be done? Is there a problem with the OBS? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- 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] Problem with testing (ThinkingSphinx)
by Frank Schreiner 19 Jan '16

19 Jan '16

Hi, since a few days I get some error messages while doing testing Steps to reproduce * Clone git * bring up a Vagrant machine ("vagrant up") * ssh to vagrant machine "vagrant ssh" * start tests "make -C /vagrant/src/api test" ** this simply executes script/api_test_in_spec.sh This leads to an error with ThinkingSphinx (tries to connect to 127.0.0.1) (for detailed errors see the following link) http://pastebin.com/yjzcfYmd Could somebody shade some light on me ? What I'am doing wrong, or give me some feedback (whether it works or not on your side ?) THX M0ses -- 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] Re: [opensuse] Re: openSUSE-SU-2016:0144-1: critical: Security update for openssh
by Wolfgang Rosenauer 18 Jan '16

18 Jan '16

Hi, something in the OBS project is broken. It looks like an internal issue to me. At least I have no idea how this could have happened. https://build.opensuse.org/package/show/openSUSE:Evergreen:11.4/openssh.363 Note the "the repository setup is broken". I think someone on OBS side is hopefully looking into it already. Wolfgang Am 18.01.2016 um 10:04 schrieb Ti Kan: > Dear openSUSE admin, > > What happened to this patch? I tried to update my Evergreen 11.4 > system but this patch did not show up. My repositories are > configured correctly and I used to update the system just fine. > > Thanks, > > -Ti > > On Sat, Jan 16, 2016 at 03:11:02AM +0100, opensuse-security(a)opensuse.org wrote: >> openSUSE Security Update: Security update for openssh >> ______________________________________________________________________________ >> >> Announcement ID: openSUSE-SU-2016:0144-1 >> Rating: critical >> References: #961642 #961645 >> Cross-References: CVE-2016-077 CVE-2016-0777 CVE-2016-0778 >> Affected Products: >> openSUSE Evergreen 11.4 >> ______________________________________________________________________________ >> >> An update that fixes three vulnerabilities is now available. >> >> Description: >> >> - CVE-2016-0777: A malicious or compromised server could cause the >> OpenSSH client to expose part or all of the client's private key >> through the roaming feature (bsc#961642) >> - CVE-2016-0778: A malicious or compromised server could could trigger >> a buffer overflow in the OpenSSH client through the roaming feature >> (bsc#961645) >> >> This update disables the undocumented feature supported by the OpenSSH >> client and a commercial SSH server. >> >> >> Patch Instructions: >> >> To install this openSUSE Security Update use YaST online_update. >> Alternatively you can run the command listed for your product: >> >> - openSUSE Evergreen 11.4: >> >> zypper in -t patch 2016-48=1 >> >> To bring your system up-to-date, use "zypper patch". >> >> >> Package List: >> >> - openSUSE Evergreen 11.4 (i586 x86_64): >> >> openssh-5.8p1-11.1 >> openssh-askpass-5.8p1-11.1 >> openssh-askpass-debuginfo-5.8p1-11.1 >> openssh-askpass-gnome-5.8p1-11.1 >> openssh-askpass-gnome-debuginfo-5.8p1-11.1 >> openssh-debuginfo-5.8p1-11.1 >> openssh-debugsource-5.8p1-11.1 >> >> >> References: >> >> https://www.suse.com/security/cve/CVE-2016-077.html >> https://www.suse.com/security/cve/CVE-2016-0777.html >> https://www.suse.com/security/cve/CVE-2016-0778.html >> https://bugzilla.suse.com/961642 >> https://bugzilla.suse.com/961645 >> > -- 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] Syncing Tumbleweed with SUSE Manager
by Malcolm 16 Jan '16

16 Jan '16

Hi Is it possible for a repodata directory structure and files to be created at; http://download.opensuse.org/tumbleweed/repo/oss/suse/ http://download.opensuse.org/tumbleweed/repo/non-oss/suse/ I have no issues with Leap from; http://download.opensuse.org/distribution/leap/42.1/repo/oss/suse/ http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/suse/ http://download.opensuse.org/update/leap/42.1/oss/ http://download.opensuse.org/update/leap/42.1/non-oss/ But on SuMa 2.1 I get the following for example on non-oss when trying a manual sync; /usr/bin/spacewalk-repo-sync --channel opensuse-tumbleweed-non-oss RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: opensuse-tumbleweed-non-oss. (failure: repodata/repomd.xml from opensuse-tumbleweed-non-oss: [Errno 256] No more mirrors to try.) Please verify its path and try again -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.51-60.20-default up 15:56, 4 users, load average: 0.14, 0.24, 0.29 CPU AMD A4-5150M @ 2.70GHz | GPU Radeon HD 8350G -- 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] recommended workflow for updating a service
by Hans-Peter Jansen 13 Jan '16

13 Jan '16

Hi, given one has created a download service with osc add URL, and adjusted that to mode="disabled" and added a recomression, what is the recommended workflow to update this to a new upstream release, apart from vi _service, adjust, versions, run disabled service, sha256sum the new file, update _service, and run is again.. Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0