August 2015 - openSUSE Build Service - openSUSE Mailing Lists

Re: [opensuse-buildservice] Support for RHEL 7.1 ppc64LE platform
by Dinar Valeev 01 Sep '15

01 Sep '15

On Thu, Aug 20, 2015 at 12:55 PM, Priya Seth <seth.osc(a)gmail.com> wrote: > Thanks for your response Dinar. > Let me try to summarize, what I understand here, if I am pulling the > sources from a repository somewhere on OBS project and the source does > not have a .dsc file, I will have to provide it. I would have to do > the same for all dependencies-sub-dependencies recursively if they are > not available there, as well? i.e. if I fail to find additional > project paths where this binary / dependency has already been built. > If a package is already part of distro, then its binary would already > be available on OBS. Hi, It is simply like this: If distro is imported: then you have binaries to build against. if you build a new package with a dependency which is not part of a distro, then you have to provide dependent binary first. > > On Wed, Aug 19, 2015 at 7:05 PM, Dinar Valeev <dinarv(a)gmail.com> wrote: >> On Wed, Aug 19, 2015 at 2:55 PM, Priya Seth <seth.osc(a)gmail.com> wrote: >>> Thanks, Dinar for your response and apologies for the late reply. >>> >>> I am looking at the wordpress project as an example: >>> https://build.opensuse.org/project/show/home:priya_seth:wordpress >>> I have added the dsc file for wordpress to my project space, but looks >>> like I have to do the same recursively for all its dependencies and >>> sub-dependencies. Is that understanding correct? >> If imported distro have binaries, then you don't need to rebuild them. >> If you have dependency which is not part of a distro, >> you should rebuild or provide additional project path where binaries >> could be found. >>> I noticed that most of the packages / repositories have the rpm spec >>> files, but not the .dsc files for debian distributions. So, every time >>> I have to build an Ubuntu package, I would need to add the .dsc file, >>> even if it is the base version of the package which is already in the >>> distro (with no additional porting changes). Is that correct? >> So you're pulling sources somewhere from OBS project? Well, it is up >> to project maintainer for what distro he wants to >> provide binaries. >> >> If imported distro have binary, it is used a build dependency. >> >> I don't understand you here. You want a build dependency which is part >> of a distro,but it doesn't have dsc file? >> >> Dinar, >>> >>> Thanks for your help with this. >>> Regards, >>> Priya >>> >>> >>> >>> >>> On Fri, Aug 14, 2015 at 7:56 PM, Dinar Valeev <dinarv(a)gmail.com> wrote: >>>> On Thu, Aug 13, 2015 at 9:06 AM, Priya Seth <seth.osc(a)gmail.com> wrote: >>>>> Hi All, >>>>> >>>> Hi, >>>>> I am new to the openSUSE:BuildService at , so please excuse me if my >>>>> questions are too basic. >>>>> >>>>> I was referring to the information at: >>>>> https://en.opensuse.org/openSUSE:Build_Service_supported_build_targets >>>>> >>>>> and it seems that RHEL 7.1 on ppc64le is currently not a supported by >>>>> this service. Do we have any plans of supporting this in the near >>>>> future? >>>> Binaries are not imported as far I can see. Neither 7.1. >>>> >>>> Adrian, are there any plans to import 7.1? >>>>> >>>>> I was also trying to build a package (nginx) on Ubuntu 14.04 ppc64le >>>>> but the status is shown as "Excluded". Looks like there are no rules >>>>> to build a debian package. I tried uploading a source package for >>>>> nginx along with it .deb file in my project area and could build that >>>>> successfully, but had to build the upload and build the missing >>>>> dependencies recursively as well. >>>>> >>>>> Is there any specific repository of packages that have been >>>>> tried/built on ppc64LE Ubuntu 14.04? Or would a package need to be >>>>> built from scratch along with all its dependencies (recursively?)? Is >>>>> there any document that can help understanding this? >>>> Could you please provide project/package so I can see your >>>> package/repository setup. >>>> So far that works for me: >>>> <repository name="u"> >>>> <path project="Ubuntu:14.04" repository="standard"/> >>>> <arch>ppc64le</arch> >>>> </repository> >>>> >>>> Along with rpm spec file you need to have foo.dsc describing how to >>>> build deb packages >>>>> >>>>> Any help/pointers on this would be of great help. >>>>> >>>>> Thanks! >>>>> -- >>>>> To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org >>>>> To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org >>>>> >>>> -- >>>> To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org >>>> To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org >>>> -- 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] repoid 'Debian Jessie' is illegal on 2.6
by Carsten Höger 31 Aug '15

31 Aug '15

Hi, after I manually built the dpkg package required for debian repo creation (why doesn’t that exist for SLE12?), I see this error in the publisher log: Mon Aug 31 15:51:23 2015 publishing backend-develop/Debian:Jessie publish failed for backend-develop, Debian:Jessie : 400 remote error: repoid 'Debian Jessie' is illegal sleeping 10 seconds... sleeping 10 seconds... sleeping 10 seconds... sleeping 10 seconds... sleeping 10 seconds... sleeping 10 seconds... sleeping 10 seconds... sleeping 10 seconds... [...] repeating infinitely who is that remote? and what repoid it is referring to? buildservice:~ # osc meta prj backend-develop <project name="backend-develop"> <title>backend-develop</title> <description/> <person userid="Admin" role="maintainer"/> <person userid="carsten.hoeger" role="maintainer"/> <repository name="RHEL-7"> <path project="RedHat:RHEL-7" repository="standard"/> <arch>x86_64</arch> </repository> <repository name="DebianJessie"> <path project="Debian:Jessie" repository="standard"/> <arch>x86_64</arch> </repository> </project> buildservice:~ # osc meta prj Debian:Jessie <project name="Debian:Jessie"> <title>Debian Jessie (8.0r1)</title> <description>Debian Jessie (8.0r1).</description> <person userid="Admin" role="maintainer"/> <repository name="standard"> <arch>x86_64</arch> </repository> </project> that is not very different to buildservice:~ # osc -A https://build.opensuse.org meta prj Debian:8.0 <project name="Debian:8.0"> <title>Debian Jessie (8.0r1)</title> <description>Debian Jessie (8.0r1).</description> <person userid="adrianSuSE" role="maintainer"/> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> -- mit freundlichen Gruessen/with best regards, Carsten Hoeger Open-Xchange GmbH -------------------------------------------------------------------------------- Open-Xchange AG, Rollnerstr. 14, 90408 Nürnberg, Amtsgericht Nürnberg HRB 24738 Vorstand: Rafael Laguna de la Vera, Carsten Dirks Aufsichtsratsvorsitzender: Richard Seibt European Office: Open-Xchange GmbH, Martinstr. 41, D-57462 Olpe, Germany Amtsgericht Siegen, HRB 8718, Geschäftsführer: Frank Hoberg, Martin Kauss US Office: Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA --------------------------------------------------------------------------------

2 3

[opensuse-buildservice] Donate CPU cycles to the OBS.
by jcsl 31 Aug '15

31 Aug '15

Hi. Just as is done in scientific and other kind of projects, is it possible to install a client that allows CPU cycles to be donated to the OBS? For example, my desktop is relatively powerful (Phenom 2 X6, 16 GB of RAM), and I currently don't perform intensive tasks on it. So I could donate those unused CPU cycles while you the computer is on. Many users complain of not being able to contribute to the project for various reasons. I think this would be a way to contribute and help improve the project because it would increase the processing power available for the various tasks that the project encompasses. Greetings. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

Re: [opensuse-buildservice] Re: Category definition
by Dmitriy Perlow 30 Aug '15

30 Aug '15

Michael Behrisch <behrisch(a)users.sourceforge.net> Sun, 30 Aug 2015 22:16:45 +0300: > Am 30.08.2015 um 15:52 schrieb Dmitriy Perlow: >> For some reason 'Science' is bad for oS > 13.2: > > Thank you, that did the trick. > > Should I file a bugreport for that or is there already one? > > Best regards, > Michael You could of course. I haven't searched for relevant tickets. If so please post link here to vote for it. Somebody has to update wiki in order to correspond modern Factory rules. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

Re: [opensuse-buildservice] Re: Category definition
by Dmitriy Perlow 30 Aug '15

30 Aug '15

Michael Behrisch <behrisch(a)users.sourceforge.net> Sun, 30 Aug 2015 00:42:42 +0300: > Hi Malcolm, > thanks for your help. > > Am 29.08.2015 um 03:57 schrieb Malcolm: >> On Sat 29 Aug 2015 01:25:24 AM CDT, Michael Behrisch wrote: >> >>> Hi, >>> can anyone help me with the error in this build: >>> https://build.opensuse.org/package/live_build_log/home:behrisch/sumo/openSU… > >> Use the -r option to replace with those two.... >> https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#.25suse_u… >> > > > I tried and failed, still the same error. > > Any other ideas? Hello. For some reason 'Science' is bad for oS > 13.2: https://build.opensuse.org/request/show/327916 -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- 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] Donate CPU cycles to the OBS.
by jcsl 30 Aug '15

30 Aug '15

Hi. Just as is done in scientific and other kind of projects, is it possible to install a client that allows CPU cycles to be donated to the OBS? For example, my desktop is relatively powerful (Phenom 2 X6, 16 GB of RAM), and I currently don't perform intensive tasks on it. So I could donate those unused CPU cycles while you the computer is on. Many users complain of not being able to contribute to the project for various reasons. I think this would be a way to contribute and help improve the project because it would increase the processing power available for the various tasks that the project encompasses. Greetings. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Category definition
by Michael Behrisch 29 Aug '15

29 Aug '15

Hi, can anyone help me with the error in this build: https://build.opensuse.org/package/live_build_log/home:behrisch/sumo/openSU… ? There seems to be a problematic category definition, the desktop file says: Categories=Education;Engineering;Science; and the spec %suse_update_desktop_file %{name} Education Science The openSuse 13.x builds do not complain, only Tumbleweed. I already tried removing the line from the desktop file but it did not help. I am grateful for any hints. 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

2 2

[opensuse-buildservice] Temporary hold on accepting devel:language:python requests
by Todd Rme 27 Aug '15

27 Aug '15

Short version: please do not accept any submit requests or make any other changes to devel:languages:python until the following package has built at least once: python-jupyter_ipywidgets Long version: For the last 16 days I have been trying to get all of the core Jupyter packages in devel:languages:python and devel:languages:python3. Jupyter is a renaming and modularization of the enormously popular IPython project. This has been very slow going, because they split the packages into many parts, and these parts have a lot of dependencies (including quite a few new ones). These dependencies include many common python packages. That means that, in OBS, if any of these dependencies is changed in any way (or any of its dependencies are changeda, and so on), then everything is rebuilt from scratch. And unfortunately these new packages seem to be given a very low priority for building, which means it takes a long time before OBS actually gets around to building them. This means it is a process of: get a package in, wait 2 days for it to build, get another package in, wait 2 days for it to build, and so on for weeks. I have one more package to go: python-jupyter. Once it is in, the process is complete. For the last 4 days I have been waiting for the python-jupyter_notebook package to build. It had one dependency left before it was going to build, and then an submit request python-Cython was accepted. Since this is a dependency of all of the jupyter-related packages, everything will need to rebuild now. That may very well mean another 2 days wait for me. Until all of its dependencies have built at least once, I can't properly package python-jupyter. It will outright refuse to build. Of the two dependencies that have not built yet, python-jupyter_ipywidgets package is the most "leaf" one. That means that once it has built once, all of the other dependencies have as well. So if everyone could refrain from making any changes of any kind to devel:languages:python until that package has been built at least once, I would greatly appreciate it. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 5

[opensuse-buildservice] Re: [opensuse-packaging] Temporary hold on accepting devel:language:python requests
by Todd Rme 27 Aug '15

27 Aug '15

On Thu, Aug 27, 2015 at 4:24 PM, Axel Braun <Axel.Braun(a)gmx.de> wrote: >> Gesendet: Donnerstag, 27. August 2015 um 15:50 Uhr >> Von: "Todd Rme" <toddrme2178(a)gmail.com> >> An: "openSUSE Packaging Mailingliste" <opensuse-packaging(a)opensuse.org>, "openSUSE buildservice" <opensuse-buildservice(a)opensuse.org> >> Betreff: [opensuse-packaging] Temporary hold on accepting devel:language:python requests > >> These dependencies include many common python packages. That means >> that, in OBS, if any of these dependencies is changed in any way (or >> any of its dependencies are changeda, and so on), then everything is >> rebuilt from scratch. And unfortunately these new packages seem to be >> given a very low priority for building, which means it takes a long >> time before OBS actually gets around to building them. This means it >> is a process of: get a package in, wait 2 days for it to build, get >> another package in, wait 2 days for it to build, and so on for weeks. > > Does it help if you build locally for the moment? > (no, I wont submit anything...) No, because local builds can't be used as dependencies for building other local packages, AFAIK. I plan to build python-jupyter locally and then submit it, the problem is its dependencies are not built yet remotely, and building those locally doesn't help. -- 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] Build failure due to a missing RSA key ?
by Olav Reinert 27 Aug '15

27 Aug '15

Hi, On OBS I have branched a package in order to submit a change request. However, the build of the package fails very quickly, making it impossible for me to test my change. The build log only contains a single line: could not retrieve ssl certificate: 400 remote error: Need an RSA key for openssl signing, please create a new key for home oreinert This seems like an issue with OBS? The build log can be found here: <https://build.opensuse.org/package/live_build_log/home:oreinert:branches:de…> Regards, Olav -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 6