openSUSE Build Service January 2013

buildservice@lists.opensuse.org

78 participants
72 discussions

[opensuse-buildservice] Como Optimizar la Carga Fiscal y Laboral de las Escuelas

by Lic. Ana L. Montes

Usted podrá conocer qué dicen las últimas reformas fiscales y qué deben esperar las instituciones educativas en este 2013. - Últimas novedades fiscales para INSTITUCIONES EDUCATIVAS - Cómo optimizar la carga fiscal y laboral de las escuelas y universidades particulares Este evento le dará todos los conocimientos que necesita para dominar la normativa fiscal y de seguro social aplicable a su institución. Maximice los beneficios fiscales que su escuela o instituto obtiene, minimizando su carga hacendaria cumpliendo la ley al pie de la letra. Conozca a fondo sus obligaciones y responsabilidades, incluyendo ISR, IVA y todas las disposiciones del Código Fiscal, además de los ajustes a la legislación laboral que aplican específicamente al ámbito educativo, incluyendo la Ley Federal del Trabajo, del IMSS y de INFONAVIT. Tambien Conozca la respuesta a preguntas por ejemplo: cómo se tratarán ahora los salarios, qué estímulos fiscales existen para la educación privada, cuáles son las ventajas de percibir donativos deducibles y cuál es la normatividad del IMSS para afiliación de maestros. Incluye un analisis del posible impacto de la nueva reforma educativa. ¿Dónde se llevará a cabo? Lugar: Su computadora Fecha: 25 de Enero de 2013 Duración: 6 Horas Horario: De 10:00 a.m a 1:00 p.m y De 3:00 p.m. a 6:00 p.m. (Hora del Centro de México) 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@opensuse.org o Comuníquese a nuestro Centro Nacional de Atencion Telefonica: 01 - 800 - 212 - 9393 *Haga extensiva esta invitación a compañeros que les pueda ser de utilidad. *Para ver correctamente nuestros mensajes, páselos a la bandeja de entrada. Reciba un muy cordial saludo! Lic. Ana L. Montes Líder de Proyectos Desea ser removido y no recibir ningún tema de nuestra empresa, envíe un correo con asunto FinalizarMail -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] Linked projects and "Status" page in webui

by Srinidhi B

Hi, I just realized that the "Status" page in webui for a linked project doesn't list failing packages. I'm not sure if this is by design or a bug. OBS version: 2.3.7 Project setup: $ osc meta prj ProjectA <project name="ProjectA"> ... <repository name="standard"> <path project="openSUSE.org:openSUSE:12.2" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> $ osc meta prj ProjectB <project name="ProjectB"> ... <link project="OES:11:Update:Test"/> <repository name="standard" linkedbuild="all"> <path project="openSUSE.org:openSUSE:Factory" repository="standard"/> <path project="ProjectA" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> Note that linkedbuild="all" setting in ProjectB's "standard" repository will trigger rebuild of packages that do not have any real sources in ProjectB. Now, because of updated packages / dependencies coming from openSUSE:Factory, there could be some build failures in ProjectB. In the webui, the "Overview" page of "ProjectB" shows, let's say, "5 build errors", but if you go to the "Status" page of this project, there are no packages listed. After reading a lot of code around api, webui and backend, I found that status information of linked / aggregated packages are not listed in /status/project/<project> API call. Is this intentional? Is this information available from backend but not queried by the API? AFAIU, backend knows about these packages and their build status since scheduler understands "linkedbuild" property of a repository. Is my understanding incorrect? If I wanted these packages listed in the webui, where should I start looking / hacking? Regards, Srinidhi. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] Different rpmlint on local buid

by Alexandre D. Rogoski

Good day! I have very different rpmlints from OBS build and from my local build. OBS fails shamefully while my local build success. Please compare the openSUSE 12.2 build logs from home:aledr:branches/ntop and my local build. Local build log for openSUSE_12.2-x86_64: https://gist.github.com/4563928 Thanks. -- [ ]'s Aledr - Alexandre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

Re: [opensuse-buildservice] how to programmatically differentiate between linkpac and bco?

by Adam Spiers

Dirk Müller (dirk(a)dmllr.de) wrote: > Am 04.01.2013 00:06 schrieb "Adam Spiers" <aspiers(a)suse.com>: > > > If it's checked out unexpanded ("osc co -u") then it seems I can take > > a guess by looking for > > > > <patches> > > <branch/> > > </patches> > > > > in the _link file, but I'm not sure this is correct > > This is correct. > > > and it's not even > > possible when the sources are expanded, since then _link doesn't > > exist. Suggestions? > > I haven't tried it, but perhaps osc info does say it somewhere? Other than > that you could use osc cat to query the Server, but I'm not sure if your > goal was to avoid the roundtrip. Yes I was hoping to avoid that :-) > Maybe there is something hidden in the .osc dir :-) As you said in a separate mail, checking if the linkinfo in .osc/_meta has a baserev is a close-enough estimation, as usually links do not have baserevs. Thanks for the very helpful info! Here's the resulting script: https://github.com/aspiers/SUSE-dist/blob/master/bin/osc-classify-link -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] Grabbing build sources from github?

by Ben Martin

Hi, Does anyone know a simple method to grab the sources for an obs build from github? Also to trigger a rebuild when somebody does a git push to the github? Thanks in advance, and sorry for what seems a bit like an FAQ. Web searches don't seem to be popping up answers though :/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] b.o.o weather forecast?

by Will Stephenson

We're hosting a 12.3 bug squashing sprint late next week and next weekend. Is there any likelihood of planned downtime or slowness on build.opensuse.org in that period? Will -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] rake db:migrate failures

by Dominique Leuenberger a.k.a. Dimstar

Hi all, The OBS 2.3.9x unstable packages seem to come with some issues in the rake db:migration code. There is a collection of 6 files that I need to 'skip', as they fail with different errors. the files are (all rather old): 20111116100002_alter_issue_trackers.rb 20111206151500_kernel_issue_tracker_regexp.rb 20120120104301_disable_switch_per_issue_tracker.rb 20120120114301_fix_bnc_url.rb 20120216114303_rename_issue_table_columns.rb 20120319104301_disable_all_issue_trackers.rb And the respective errors are: 20111116100002_alter_issue_trackers.rb ###################################### -- change_table(:issue_trackers) rake aborted! An error has occurred, all later migrations canceled: Mysql2::Error: Duplicate column name 'kind': ALTER TABLE `issue_trackers` ADD `kind` ENUM('bugzilla', 'cve', 'fate', 'trac', 'launchpad', 'sourceforge') AFTER `name` Tasks: TOP => db:migrate (See full trace by running task with --trace) 20111206151500_kernel_issue_tracker_regexp.rb ############################################# == KernelIssueTrackerRegexp: migrating ======================================= rake aborted! An error has occurred, all later migrations canceled: undefined method `regex=' for nil:NilClass Tasks: TOP => db:migrate 20120120104301_disable_switch_per_issue_tracker.rb ################################################## rake aborted! An error has occurred, all later migrations canceled: Mysql2::Error: Duplicate column name 'enable_fetch': ALTER TABLE `issue_trackers` ADD `enable_fetch` bool DEFAULT 0 Tasks: TOP => db:migrate 20120120114301_fix_bnc_url.rb ############################# rake aborted! An error has occurred, all later migrations canceled: undefined method `url=' for nil:NilClass Tasks: TOP => db:migrate 20120216114303_rename_issue_table_columns.rb ############################################ rake aborted! An error has occurred, all later migrations canceled: No such column: issues.description Tasks: TOP => db:migrate 20120319104301_disable_all_issue_trackers.rb ############################################ rake aborted! An error has occurred, all later migrations canceled: undefined method `enable_fetch=' for nil:NilClass Tasks: TOP => db:migrate ====> Some of them are probably follow up errors, but none of them should happen.. Best regards, Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] Web interface: Avoiding editor

by Karl Eichwalder

>From time to time it is handy to edit files within the Web interface. Is there a simple way to avoid this "advanced" editor? I'd like to use the standard editor interface that comes with firefox; this "advanced" editor does not support keyboard navigation and has its own ideas about cut and paste... Sometimes less is more. -- Karl Eichwalder SUSE LINUX Products GmbH R&D / Documentation Maxfeldstraße 5 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] Built package doesn't appear in the download repository

by Nanuk Krinner

Hi, In systemsmanagement:chef:master[1] I build the package rpm.SLE_11[2]. The package never appears in the download repository[3] of the project. Why is this and how can I change this? The binary exists and can be downloaded manually[4]. Thanks, Nanuk [1]: https://build.opensuse.org/project/show?project=systemsmanagement%3Achef%3A… [2]: https://build.opensuse.org/package/binaries?package=rpm.SLE_11&project=syst… [3]: https://build.opensuse.org/project/repository_state?project=systemsmanageme… [4]: https://build.opensuse.org/package/binaries?package=rpm.SLE_11&project=syst… -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] OBS 101: How to threat packages with multiple spec files

by Sascha Peilicke

Hi guys, if you have an OBS package containing multiple spec files, you may have discovered that OBS only builds the spec file matching the OBS package name. If you want to have the other(s) spec file(s) built, you should use a link, don't use copypac! For example, devel:languages:python / python-nose is a OBS package containing four (!) spec files. In this case, documentation building is separate because doc building dependencies (python-Sphinx) would create a build cycle. A second set of packages are Python3-related, because d:l:p builds both Python and Python3 at the moment. So we end up with the following list of spec files [1]: python-nose/python-nose.spec python-nose/python-nose-doc.spec python-nose/python3-nose.spec python-nose/python3-nose-doc.spec As you can see here [2], only python-nose.spec is build, so we have to do the following (on a command line near you, given you have the rights to do it in the project): $ osc linkpac devel:languages:python python-nose \ devel:languages:python python-nose-doc $ osc linkpac devel:languages:python python-nose \ devel:languages:python python3-nose $ osc linkpac devel:languages:python python-nose \ devel:languages:python python3-nose-doc Even though you end up with four OBS packages, you only have to modify / fix "python-nose" due to the links. This is much better than using copypac (as I've seen recently). Of course you should only split up into several spec files if there's a very good reason for the extra work. Here are some: - To avoid build cycles - To off-load looong-running parts of a package build, like: + Running a testsuite ($PACKAGE-testsuite.spec) + Building documentation ($PACKAGE-doc.spec) - When building the same thing against a different set of (build) requirements, like: + Different $DYNAMIC_LANGUAGE interpreter versions (usually $INTERPRETER-$PACKAGE.spec) Footnotes: [1] https://build.opensuse.org/package/show?package=python-nose&project=devel%3… [2] https://build.opensuse.org/package/binaries?package=python-nose&project=dev… -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)

8 years, 8 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service January 2013