openSUSE Build Service January 2013

buildservice@lists.opensuse.org

78 participants
72 discussions

Re: [opensuse-buildservice] Stalled submit requests
by Matwey V. Kornilov 18 Feb '15

18 Feb '15

Hm... You have inspired me to try this on the coming weekend. :) With obs rest/xml api, I need a tiny python script to manage all the things out. It is easy, you're right. 2012/10/18 Jos Poortvliet <jos(a)opensuse.org>: > On Sunday, October 07, 2012 12:09:43 Matwey V. Kornilov wrote: > >> Hi, > >> > >> Is there a page to see full list of submit requests, ordered by date? This > >> statistics is of quite interest. > >> > >> For instance, there is no reaction for two month: (It is not ok for devel: > >> project, I think) > >> > >> >> https://build.opensuse.org/project/requests?project=network%3Amessaging%3Aam > >> qp > >> > >> I think, having such a page, such statistics, one would be able to > >> redistribute his power. > > > > Not a bad idea at all - it'd nice to show which projects need some help, > which are doing very well etcetera. Maybe a top-ten of fastest SR/MR > solvers, too ;-) > > > > Crazy idea: Adrian responded to you that it is possible to request this info > from the API. If you got the skillzz to do that, it'd be nice to publish > those statistics somewhere - and that part I could help with. Something like > a weekly overview of the health of the OBS projects and stuff like that. > > > > Up for it? > > > > /Jos -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 9

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released
by Adrian Schröter 17 Feb '15

17 Feb '15

Open Build Service(OBS) 2.3.4 just got released =============================================== This is a bugfix release in first place. But also the distribuition default target list has been updated. This release is most important for cross build support. Building against openSUSE 12.2 and Factory for ARM architecture works now out-of-the-box. OBS 2.3.4 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Feature backports: ================== * Added "Hostarch" in _buildinfo for osc local builds of cross builds Changes: ======== * package meta creation of package copy command is not copying relationships and devel definitions anymore. * Added openSUSE 12.2 to default target list * Removed openSUSE 11.4 from default target list (EOL soon) * Fedora 15 is EOL, removed from default list Bugfixes: ========= * backend: allow access to access protected project repositories when users are in both projects. * backend: increase vrev on package source copy * webui: fixed underscores in code listings * webui: Do not expose user email address in anonymous mode * obsworker: do not fail when no /etc/sysconfig/proxy exists * build: fixed cross architecture initilisation for chroot builds -- Adrian Schroeter SUSE Linux Products GmbH 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

4 4

[opensuse-buildservice] Expired OBS Keys?
by King Thorin 02 Jul '13

02 Jul '13

It seems the OBS Security key (keyid 79EAFD54) on keys.gnupg.net has expired (2011-Apr-2). Would it be possible for someone to update it? I know an updated key has been generated (which expires 2013) as it can be found here: http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v4/xUb… Further details can be found via: http://lists.wald.intevation.org/pipermail/openvas-distro/2011-April/thread… Basically the issue came to light when following instructions: http://www.openvas.org/install-packages.html#openvas4_ubuntu_obs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

[opensuse-buildservice] New project openSUSE:Current?
by Cristian Morales Vega 18 Mar '13

18 Mar '13

Sometimes you have appA in your repo building for both old and new openSUSE versions. appA depends on libA > X, but only the latest openSUSE version provides it. openSUSE <latest-1> came with libA <X-1>. The solution is to package libA > X for the old distributions and usually you do that linking to the devel project. I would like an openSUSE:Current project that would always contains the latest supported version of the packages. Right now the packages from openSUSE:12.1:Update, but once 12.2 is released it should be changed to openSUSE:12.2:Update. This way I could link to those packages instead of linking to the devel project. It would let me compile appA in old distros while giving to the users a libA package that is not soooooo unsupported (this would be officially unsupported anyway, but...). I would like this since it's a single place to change when a new openSUSE version is released (If needed I can do it). Looking at the openSUSE:12.1:Update project metadata I guess it would just need be something like <project name="openSUSE:Current"> <title>Current version of openSUSE</title> <description></description> <link project="openSUSE:12.1:Update"/> <debuginfo> <enable/> </debuginfo> </project> But I'm not sure since I never really saw a doc explaining the meaning of <link> in the *project metadata*, only in _link files. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 8

[opensuse-buildservice] [ANNOUNCE] new osc plugin: prdiff for comparing projects
by Adam Spiers 13 Mar '13

13 Mar '13

Hi all, I wanted a way to quickly compare a project with its "upstream" project, and a quick hack ended up as a new osc plugin: https://gist.github.com/616b476a9c592a0a2a89 (Copy to your ~/.osc-plugins or /var/lib/osc-plugins to try it.) Example usages: $ osc prdiff --include=client openSUSE:Factory Cloud:OpenStack:Factory differs: python-glanceclient identical: python-keystoneclient differs: python-novaclient differs: python-quantumclient identical: python-swiftclient $ osc prdiff --new-only --exclude='crowbar|rubygem' \ systemsmanagement:chef:10:staging \ systemsmanagement:crowbar:2.0 identical: couchdb identical: erlang identical: gecode identical: js differs: rabbitmq-server new only: all-barclamps-good new only: fakechroot new only: libyaml new only: ruby new only: ruby-common new only: ruby19 new only: sleshammer $ cd ~/OBS/home/aspiers/branches/devel/languages/ruby/ $ osc prdiff --diffstat --requests differs: ruby-common generate_buildrequires.sh | 31 ++++++++++++++++++++++++++----- ruby-common.changes | 8 ++++++++ 2 files changed, 34 insertions(+), 5 deletions(-) 148023 State:new By:aspiers When:2013-01-11T11:04:14 submit: home:aspiers:branches:devel:languages:ruby/ruby-common -> devel:languages:ruby Descr: - Fix it to work even if all-good has just been created locally via mkpac and doesn't exist server-side yet. - Improve support for running within a branch of the original project. This allows submitreqs which change all-good.spec. Feedback welcome. I'd also like to know if it makes sense to include this in osc core (my vote is yes, but I'm biased ;-) Cheers, Adam -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 10

[opensuse-buildservice] devel:languages:smalltalk dead?
by Michael Behrisch 13 Mar '13

13 Mar '13

Hi, while looking for a recent scratch http://scratch.mit.edu/ in opensuse I found that there are different versions of squeak running around in X11:Sugar and devel:languages:smalltalk. The latter project seems not to have seen any updates for almost three years, so I decided to submit all of my changes to Education (where scratch lives). Is there any smalltalker who wants to revive it or is it better to have it all in Education? Best regards, Michael -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] local packages do not override global packages
by Olaf Hering 07 Feb '13

07 Feb '13

The package ocaml-findlib in devel:languages:ocaml has a BuildRequires: "camlp4". In the same project ocaml-camlp4-devel (from package ocaml) provides "campl4". But this provides is not used, instead the package 'camlp4' from the main openSUSE_12.1 project is used: devel:languages:ocaml/ocaml-findlib $ obs r -v openSUSE_12.1 i586 unresolvable: nothing provides ocaml = 3.12.0-11.1.2 needed by camlp4 nothing provides ocaml(Arg) = 877340141c0babb58b3aaef2f5b70fc9 needed by camlp4 openSUSE_12.1 x86_64 unresolvable: nothing provides ocaml = 3.12.0-11.1.2 needed by camlp4 nothing provides ocaml(Arg) = 877340141c0babb58b3aaef2f5b70fc9 needed by camlp4 Is this a bug in the dependency solver? I reported it via bugzilla, but got no reply up to now: https://bugzilla.novell.com/show_bug.cgi?id=781120 Olaf -- 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] prjconf Prefer: with distribution version check?
by Hans-Peter Jansen 06 Feb '13

06 Feb '13

Hi, I would like to use a prjconf clause like this: # aaa_base-malloccheck doesn't exist before %if 0%{?suse_version} < 1220 Prefer: -post-build-checks %endif in order to build packages for older systems, that do not have that malloccheck, without messing with each and every failing .spec.. Unfortunately, that doesn't work. Any idea on how to archive that? Thanks, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 19

Re: [opensuse-buildservice] new steam license
by Andrew Wafaa 01 Feb '13

01 Feb '13

On 31 January 2013 14:25, Guus <guus.poort(a)upcmail.nl> wrote: > Do my opensuse friends realise steam is still in beta. > Me and others are testing it. But allot cant because there is no official > package. > > Is this gonna drag on, untill me and many other have switched to a different > distro ? > (a few already have) > This is not a threat, I am seriously concerned. > > Valve is beta testing, we need opensuse users, to test too. > So they can give feedback to Valve. > How are they gonna do this, if they cant install it ? > > For years the graphic drivers, are a weak spot on Linux. > Thanks to Valve, Amd and nvidia are releasing better drivers. > > A few of us, posted on the steam forum, that we wanted opensuse to be > supported. > Valve listened to us, so they put a link to a repo on their official steam > for Linux page. > A repo which is not working. > > I am not just ranting, I also emailed Valve about this. > Valve made a new license, so we are allowed to make a rpm. > > It would be shame if opensuse misses out because of this. > > Valve is trying hard, and we should help them. > I agree with everything you're saying, but there is a process to go through - ESPECIALLY when legal is concerned. The fact that they have modified their license to allow for redistribution is great, but as it is not open source and the OBS is hosted by SUSE we need to comply with their legal obligations. Yes, it may suck but that's how things are. > > Op 31-1-2013 6:55, Andrew Wafaa schreef: > >> On 30 January 2013 21:51, Guus <guus.poort(a)upcmail.nl> wrote: >>> >>> Hi all >>> >>> THe steam package can return ! >>> >>> Guus >>> >>> http://login.kristshell.net/~olorin/Steam/License%20Agreement.html >>> >>> YOU SHOULD CAREFULLY READ THE ENTIRE FOLLOWING LICENSE AGREEMENT >>> BEFORE INSTALLING THIS SOFTWARE PROGRAM. THIS AGREEMENT CONTAINS >>> IMPORTANT >>> TERMS THAT AFFECT YOUR LEGAL RIGHTS. BY INSTALLING THE SOFTWARE PROGRAM, >>> YOU >>> AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO >>> THE >>> TERMS OF THIS AGREEMENT, PLEASE DO NOT INSTALL THIS SOFTWARE PROGRAM. >>> >>> The software application(s) (the “Program”) is the copyrighted work of >>> Valve >>> Corporation (“Valve”) or its suppliers. >>> All rights reserved, except as expressly stated herein. The Program is >>> provided solely for installation by end users >>> according to the terms of this License Agreement, except as provided >>> below >>> regarding permitted redistributions. All >>> use of the Program is governed by the terms of the Steam subscriber >>> agreement located at www.steampowered.com/agreement >>> (the “Steam Agreement”), as such terms may be updated from time to time, >>> which terms are incorporated into this License >>> Agreement by this reference. Any use, reproduction or redistribution of >>> the >>> Program not in accordance with the terms of >>> the License Agreement and the Steam Agreement is expressly prohibited. >>> >>> LICENSE AGREEMENT >>> >>> 1. Grant of Licenses. >>> >>> A. Personal Use Limited Installation License. Valve hereby grants, and by >>> installing the Program you thereby accept, a >>> limited, non-exclusive license and right to install one (1) copy of the >>> Program on each of your computers solely for >>> your personal use. >>> >>> B. Limited Redistribution License. Valve hereby grants, and you accept, a >>> limited, terminable, non-exclusive license to >>> reproduce and distribute an unlimited number of copies of the Program; >>> provided that the following conditions are >>> met: >>> >>> (i) you must distribute the Program in its entirety; >>> >>> (ii) you may not modify the Program, except that, in the case of the >>> Linux >>> version of the Program, you may modify >>> scripts and other documentary and graphical files, but not any files >>> containing the term “bootstrap” in the file >>> name, provided that you do not modify any icons, change any copyright or >>> other notices, or alter this or any >>> other license agreement that is included with the Program, and provided >>> further that any modifications you >>> make are identified by you as modifications from the original Program >>> provided by Valve; >>> >>> (iii) you may repackage the Program and distribute it with another >>> software >>> program, provided that you do not >>> integrate the Program in any way with that other software program, or >>> combine the Program with that other >>> software program in a manner that would require you to distribute the >>> Program under any open source or other >>> license terms different from these terms. >>> >>> (iv) you may not charge any separate fee or receive any compensation >>> attributable to the Program; >>> >>> (v) you must include this License Agreement provided with the Program and >>> ensure that it will display and be >>> required to be accepted by the end user in the same manner as is required >>> by >>> the Program in the form received >>> by you; and >>> >>> (vi) you must preserve in all copies of the Program all copyright and >>> legal >>> notices that are attached to the copy >>> of the Program received by you. >>> >>> C. Restrictions/Reservation of Rights. Except as expressly set forth >>> elsewhere in this License Agreement, >>> you may not, in whole or in part: copy, photocopy, reproduce, translate, >>> reverse engineer (with the exception of >>> specific circumstances where such act is permitted by law), derive source >>> code from, modify, disassemble, >>> decompile, or create derivative works based on the Program; remove any >>> proprietary notices or labels on the >>> Program; or attempt in any manner to circumvent any security measures >>> designed to control access to the Program. >>> You may not package the Program with, or pre-install the Program on, any >>> hardware, without obtaining a separate >>> license from us. The Program is licensed to you as a single product. Its >>> component parts may not be separated for >>> use on more than one computer. You may not sell, grant a security >>> interest >>> in, rent, lease or license the Program to >>> others without the prior written consent of Valve. The Program is >>> licensed, >>> not sold. Your license confers no title or >>> ownership in the Program or copies thereof. >>> >>> 2. Ownership. All title, ownership rights and intellectual property >>> rights >>> in and to the Program and any and all >>> copies thereof (including but not limited to any titles, computer code, >>> themes, objects, characters, character names, >>> stories, dialog, catch phrases, locations, concepts, artwork, animations, >>> sounds, musical compositions, audio-visual >>> effects, methods of operation, moral rights, any related documentation, >>> and >>> “applets” incorporated into the Program) >>> are owned by Valve or its licensors. The Program is protected by the >>> copyright laws of the United States, >>> international copyright treaties and conventions and other laws. All >>> rights >>> are reserved. The Program contains certain >>> licensed materials and Valve’s licensors may protect their rights in the >>> event of any violation of this Agreement. >>> >>> 3. Termination. This License Agreement is effective until terminated. You >>> may terminate the License >>> Agreement at any time by destroying the Program. We may terminate your >>> rights set forth in Section 1.B. of this >>> License Agreement at any time upon notice to you. This License Agreement >>> shall automatically terminate in the >>> event that you fail to comply with the terms and conditions contained >>> herein. In such event, you must immediately >>> destroy the Program. The provisions of Sections 2, 3, and 5-7 will >>> survive >>> any termination of the Agreement. >>> >>> 4. Export Controls. The Program may not be re-exported, downloaded or >>> otherwise exported into (or to a >>> national or resident of) any country to which the U.S. has embargoed >>> goods, >>> or to anyone on the U.S. Treasury >>> Department’s list of Specially Designated Nationals or the U.S. Commerce >>> Department’s Table of Denial Orders. By >>> installing the Program, you are agreeing to the foregoing and you are >>> representing and warranting that you are not >>> located in, under the control of, or a national or resident of any such >>> country or on any such list. >>> >>> 5. WARRANTY DISCLAIMERS; LIMITATION OF LIABILITY; NO GUARANTEES. >>> DISCLAIMERS >>> OF WARRANTY AND LIMITATIONS ON LIABILITY SET FORTH IN THE STEAM >>> AGREEMENT, >>> AND/OR >>> ELSEWHERE IN THE STEAM AGREEMENT, APPLY TO YOUR USE OF THE PROGRAM. AS >>> NOTED >>> IN >>> THE STEAM AGREEMENT, FOR EU CUSTOMERS, SUCH PROVISIONS DO NOT REDUCE YOUR >>> MANDATORY CONSUMERS’ RIGHTS UNDER THE LAWS OF YOUR LOCAL JURISDICTION. >>> >>> 6. Warranties/Indemnities Relating to Redistribution. If you choose to >>> redistribute the Program, you represent >>> and warrant that any modifications you make to the Program, if any, and >>> your >>> particular combination of the Program >>> with any other software or hardware, do not infringe on any third-party >>> intellectual property rights. You agree to >>> defend, indemnify and hold harmless Valve, its licensors, and its and >>> their >>> affiliates from all liabilities, claims and >>> expenses, including attorneys’ fees, that arise from or in connection >>> with >>> your redistribution of the Program or your >>> breach of this License Agreement. Valve reserves the right, at its own >>> expense, to assume the exclusive defense and >>> control of any matter otherwise subject to indemnification by you. In >>> that >>> event, you shall have no further obligation >>> to provide indemnification to Valve in that matter. >>> >>> 7. Miscellaneous. Provisions relating to applicable law and jurisdiction, >>> and dispute resolution, set forth in the >>> Steam Agreement shall apply to any disputes arising under this Agreement. >>> This License Agreement and the Steam >>> Agreement terms incorporated herein may be amended, altered or modified >>> at >>> any time by Valve in Valve’s sole >>> discretion. In the event that any provision of this License Agreement >>> shall >>> be held by a court or other tribunal of >>> competent jurisdiction to be unenforceable, such provision will be >>> enforced >>> to the maximum extent permissible and >>> the remaining portions of this License Agreement shall remain in full >>> force >>> and effect. This License Agreement and >>> the Steam Agreement constitute and contain the entire agreement between >>> the >>> parties with respect to the subject >>> matter hereof and supersede any prior oral or written agreements. >>> >>> You hereby acknowledge that you have read and understand the foregoing >>> License Agreement and agree that the >>> action of installing the Program is an acknowledgment of your agreement >>> to >>> be bound by the terms and conditions of >>> the License Agreement contained herein, including the Steam Agreement. >>> >>> >>> ----- >>> Geen virus gevonden in dit bericht. >>> Gecontroleerd door AVG - www.avg.com >>> Versie: 2013.0.2890 / Virusdatabase: 2639/6068 - datum van uitgifte: >>> 01/30/13 >>> >>> -- >>> To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org >>> To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org >>> >> It can only return after having the license reviewed by SUSE Legal and >> the package would need to be hosted in the Non-OSS repo and have the >> EULA appear prior to install much in the same way that Flash or >> Acrobat do. >> >> -- >> Andrew Wafaa >> IRC: FunkyPenguin >> GPG: 0x3A36312F >> >> >> ----- >> Geen virus gevonden in dit bericht. >> Gecontroleerd door AVG - www.avg.com >> Versie: 2013.0.2890 / Virusdatabase: 2639/6068 - datum van uitgifte: >> 01/30/13 >> >> >> > > > > ----- > Geen virus gevonden in dit bericht. > Gecontroleerd door AVG - www.avg.com > Versie: 2013.0.2890 / Virusdatabase: 2639/6068 - datum van uitgifte: > 01/30/13 > -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 14

[opensuse-buildservice] Guia de Estados Financieros para Directores No Financieros
by Lic. Carolina Moo Aldana. 31 Jan '13

31 Jan '13

Guía de Comprensión de Estados Financieros para Directores No Financieros ¿Dónde se llevará a cabo? Lugar: Su computadora. Fecha: 25 de Febrero de 2013. Duración: 3 Horas. Horario: De 10:00 a.m a 1:00 p.m. (Hora del Centro de México). La habilidad de revisar estados financieros y tomar decisiones inteligentes es esencial para los Directores y Gerentes que dirigen el rumbo de sus compañías, sin embargo, para muchos de ellos el mundo de las finanzas y sus términos son a menudo ¡confusos, poco claros y frustrantes!, desaprovechando el potencial de esta información, cuando en realidad… dentro de esos números se encuentran las respuestas necesarias para tomar las decisiones claves del negocio. Descubra en este evento cómo comprender desde un punto de vista ESTRATÉGICO, AMENO Y PRÁCTICO, los diferentes reportes financieros que usted necesita para dirigir con éxito su organización. Adquiera el folleto completo y sin compromiso, sólo responda este correo con los siguientes datos: Nombre(imprescindible) : Empresa : Teléfonos (imprescindible): E-mail: opensuse-buildservice(a)opensuse.org o Comuníquese a nuestro Centro Nacional de Atencion Telefonica: 01 - 800 - 212 - 9393 Reciba un muy cordial saludo! Lic. Carolina Moo Aldana. Líder de Proyectos Para darte de baja y no recibir ningún tema de nuestra empresa, envíe un correo con asunto Nomasinfo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service January 2013