openSUSE Build Service August 2012

buildservice@lists.opensuse.org

48 participants
53 discussions

[opensuse-buildservice] Re: unity for openSUSE

by Damian Ivanov

Oh. I forgot to reply to all and a few other things, 1) When adding Arch core etc repos I had manually to add the arch x86 and i386 it only showed arm. 2) unity already builds fine for Factory and 12.2, if you want to break your system you can install it ( even I didn't try it yet :D ) Regards, Damian 2012/8/24 Damian Ivanov <damianatorrpm(a)gmail.com>: > Hello Adrian, > > Thank you, YMMD (even it's still early though). > >> Since fedora updates are not static repos and our download on demand >> feature is not supporting non-static repositories atm, I do not want to >> add these repos, because I would need always manually to update it. > Thanks!! I was looking for an explanation but I could't find anywhere. > I would anyway like to come back to SuSE (user since 9.0), but am bound to > Fedora until openSUSE 12.3 (I guess 12.3, I need the automatic > multiseat support using loginctl/systemd) > which would be only possible with removing sysvinit, which I fully > understand you don't want for 12.2 > >> If it is just one or two packages you need, I can once import them manually >> though. > Yes. They are just one or two packages, I can remember just xulrunner > right now needed by > https://build.opensuse.org/package/files?package=globalmenu-extension&proje… > but we had also some other packages, we will have a look. > >> It should be active already on build.opensuse.org. It is complete, but >> officially still experimental and not yet released :) > Great. Did not know that and could not find out! > > Best regards, > Damian > > 2012/8/24 Adrian Schröter <adrian(a)suse.de>: >> Am Donnerstag, 23. August 2012, 13:24:15 schrieb Damian Ivanov: >> ... >>> Dear guys from OBS, dear Adrian: >>> I would ask you for a favor: >>> Could you please make it possible that we can add Fedora Updates and >>> Fedora Update-testing repo (if Fedora Rawhide would be supported too, >>> that would be brilliant) , we really need this (at the moment we use >>> some ugly hacks >>> having rpms from fedora updates in our source in OBS, which puts load >>> on your servers >>> and we can spend less time on the openSUSE port of unity) >> >> Since fedora updates are not static repos and our download on demand >> feature is not supporting non-static repositories atm, I do not want to >> add these repos, because I would need always manually to update it. >> >> If it is just one or two packages you need, I can once import them manually >> though. >> >>> Also please drop me a private message too (in case I am not on the >>> mailing list) when the OBS arch backend is arrived. >> >> It should be active already on build.opensuse.org. It is complete, but >> officially still experimental and not yet released :) >> >>> Xiao-Long Chen is also the maintainer of the successful port of unity >>> to arch (though he moved to Fedora as main distro) and we'd love to >>> just add the PKGBUILD >>> files to the packages in GNOME:Ayatana and these packages would >>> provide unity for SuSE, Fedora and Arch! >> >> Try it and tell ... >> >>> If someone wants to join us for a port of unity to other OBS supported >>> architectures feel free to contact us. >>> >>> Cheers, >>> Damian >>> >> -- >> 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

8 years, 4 months

[opensuse-buildservice] OBS + Summit + YOU

by Bryen M Yunashko

Often I've heard people in the North America region wish they could go to the annual openSUSE Conference in Europe. But for many reasons, can't afford to go or too far away. Now, we have the solution for you. We bring the conference to the United States. Next month, in Orlando, Florida, we will host the first ever North American openSUSE event -- openSUSE Summit [1]. This is your chance to meet fellow OBS users as well as the OBS team. Yes, Adrian Schroeter and his team will be there. Now you can meet in person and express your thoughts about OBS and hear what's new and exciting. In the evenings, sit back and pop a brewski with everyone. And if you're not an expert OBS user, no worries. The Summit offers a free workshops on RPM packaging and How to Work with OBS. Check out the full announcement of activities posted today at [2]. See you all in Florida! Bryen M Yunashko openSUSE Summit [1] http://summit.opensuse.org [2] http://news.opensuse.org/2012/08/23/reasons-to-attend-the-opensuse-summit/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 4 months

[opensuse-buildservice] Package Release 'lowered'

by Dimstar / Dominique Leuenberger

Hi, I was reported a weird behavior of packages in GNOME:Apps, specifically gnucash. osc buildhist GNOME:Apps gnucash openSUSE_12.1 x86_64 for example has this in the list 2012-08-03 08:24:11 28f8033d394dffaeae755db983f58b2f 35 2.4.10-38.3 2012-08-05 18:48:51 d2dd40f1c261c65516bdf1d04be6ca58 36 2.4.11-39.1 2012-08-07 04:30:46 d2dd40f1c261c65516bdf1d04be6ca58 36 2.4.11-39.2 2012-08-09 10:15:53 b66a20f770f53a7be1459c03824a0cab 37 2.4.11-37.1 2012-08-10 02:26:01 b66a20f770f53a7be1459c03824a0cab 37 2.4.11-37.2 => So around Aug 9, the release dropped down by 2.. Also interesting: Release 37 (which is normally between 36 and 38) was skipped: 2012-07-21 16:43:53 de907016bad800b089c3b8d8cde63047 34 2.4.10-36.1 2012-07-24 13:11:43 28f8033d394dffaeae755db983f58b2f 35 2.4.10-38.1 (ok, maybe there were two checkins shortly). osc log shows r37 as the current release (which explains why the current package is at 37). So, any explanation where r38 and r39 are coming from in the build hist and on users systems? This is not limited to gnucash, as can be seen here: osc buildhist GNOME:Apps transmission openSUSE_12.1 x86_64 2012-07-04 16:43:41 db55e49bd1d121526cda936d0c5706fa 71 2.52-73.2 2012-07-09 13:57:21 7921fb7db5cf542d4a2be57993b3953e 72 2.60-74.1 2012-07-24 12:28:00 d980394c3fce783f389274a38983dac8 73 2.60-73.1 Looking forward to hear from the masters on that one... would be great to find a way to avoid such cases, as it asks users to either downgrade (if they dup) or they might not get the next update (considering current being 37, the user having 39, he will likely not get '38'). (Actually, also something that disappeared somewhen: didn't we reset CI count when the version increased?) 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, 4 months

[opensuse-buildservice] unity on openSUSE, OBS question

by Damian Ivanov

Hi, As you may already know, on OBS the GNOME:Ayatana repo was taken over from Xiao-Long Chen and me some month ago, as we want to port unity to openSUSE and Fedora. May some of you have heard that unity is already working on Fedora from GNOME:Ayatana installable. I was on holiday this month and am back now on was excited that Xiao-Long already adjusted most spec files (we have separate spec files for SuSE and Fedora) to build/are OK with SuSE policies and I have now again some time for this project too. Now the real news for openSUSE: As we moved the BuildRequires and Requires and have seperate spec files for Fedora and openSUSE (where we adjusted the spec files), the indicators, the utouch framework, nux, other libs already build fine on openSUSE 12.2 and Factory. compiz (which is only one package since upstream version 0.9.8) and unity working on Fedora and should be building fine in few days for openSUSE too. So we are about at 90% that unity is working for SuSE too, the indicators are already usable for gnome3-fallback session. Dear guys from OBS, dear Adrian: I would ask you for a favor: Could you please make it possible that we can add Fedora Updates and Fedora Update-testing repo (if Fedora Rawhide would be supported too, that would be brilliant) , we really need this! Also please drop me a private message too (in case I am not on the mailing list) when the OBS arch backend is arrived. Xiao-Long Chen is also the maintainer of the successful port of unity to arch (though he moved to Fedora as main distro) and we'd love to just add the PKGBUILD files to the packages in GNOME:Ayatana and these packages would provide unity for SuSE, Fedora and Arch! If someone wants to join us for a port of unity to other OBS supported architectures feel free to contact us. Cheers, Damian -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 4 months

[opensuse-buildservice] Documents for Developers

by Aaron Yung

Hi, Anybody has the Documents about OBS for Developers? Thanks very much! ----- Go OBS -- View this message in context: http://opensuse.14.n6.nabble.com/Documents-for-Developers-tp4972357.html Sent from the opensuse-buildservice mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 4 months

[opensuse-buildservice] Network Timeout on attempting to contact static.opensuse.org

by doiggl＠velocitynet.com.au

Hello, When I try to access https://build.opensuse.org/ it connects to static.opensuse.org first and I get this error after waiting[1]. Whats broken ?, Does anyone else get this error ? Glenn [1] Network Timeout The operation timed out when attempting to contact static.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 5 months

[opensuse-buildservice] [ANNOUNCE] vc-osc.el - osc backend for emacs vc-mode

by Adam Spiers

Hi everybody, If you are an emacs user then this may be of interest to you. Last night I did a quick hack to produce vc-osc.el, so that most of the normal vc-mode keyboard shortcuts beginning with `C-x v' can now work in the normal manner. https://github.com/aspiers/vc-osc#readme Basic functionality works for me, but I have done very little testing so far. Please feel free to give it a try and submit issues / pull requests to github :-) Adam -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 5 months

[opensuse-buildservice] [gsoc] osc2 client - summary of week 12

by Marcus Hüwe

Hi, here’s a small summary of the 12th (coding) week. The last week I continued the work on the new user interface. As a result the "request" command is more or less implemented. Yesterday I pushed the current code and it's also possible to play around with it: - checkout the code [1] - cd osc2/osc/cli - export PYTHONPATH=/path/to/osc2 - python cli.py -h (for more information) Example: In order to list a request it is sufficient to run "python cli.py request api://your_project" (Note: all https requests are _insecure_ - so far the certificate etc. is not checked). Some implementation details: In my last mail/post I described how a new (sub)command can be specified so I'll leave out the details here. In the following I'll shortly explain how the arguments specified by the user at the commandline are passed to a function (which does the actual work - like listing the requests). class RequestList(CommandDescription, Request): """ ... """ cmd = 'list' args = 'api://project?/package?' opt_user = Option('U', 'user', 'list only requests for USER') func = call(request.list) As we can see the project and package parameters are optional. After the parsing process a so called "info" object is returned which encapsulates the specified arguments. Assume the user runs "request list api://test_prj" then the info object has the following attributes: info.apiurl = <the default apiurl> info.project = 'test_prj' info.package = None The question is how can we pass this data to the request.list function? A simple (and naive) approach would be to simply pass the "info" object to the request.list function that is "list" has the following signature "def list(info)". As a consequence inside the method we always have to use "info.project", "info.package" etc. which is a bit awkward - at least for parameters which are quite frequently used in the method definition. So it would be nice if there's a way to pass frequently used parameters directly to the method (that is they're declared as formal parameters in the method definition) and infrequently used parameters can still be accessed via the info object. Exactly like this it is currently implementend in osc2. So the following signatures would be correct for our example: def list(project, package, info) def list(project, package, user) def list(project, package, user, info) def list(project, info) def list(info, project) def list(project) # using the info object is not mandatory def list() # quite useless... ... Invalid signatures: def list(prj, pkg, info) def list(foo, info) ... So it is up to the developer how to define the signature of the request.list function - it is not completely dictated by osc:) Marcus [1] https://github.com/openSUSE/osc2 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 5 months

[opensuse-buildservice] Re: Debug versions of local libraries

by Lars Müller

On Tue, Aug 14, 2012 at 02:54:29PM +0200, Roger Oberholtzer wrote: > I would like to make debug information for libraries we make. Of course, > I can compile and link the libraries this way, and install them. But I > see that for openSUSE libraries, a better method is used: > > An RPM is made that contains the debug version of the library. This > version of the library is not used when the application is run normally. > This is used by gdb when running an application or examining a core > file. There seems to be some intelligence to this so that gdp knows > which version of the debug RPM is needed, and even suggests the command > to get that version installed. These debug version of the librarys are > perhaps installed in an alternate location from the regular use > versions. > > Is there a description for how this is accomplished on openSUSE? Of most > interest is how to set it up so that the debug version of the library is > available to gdb. I looked around on the openSUSE site, but could not > find anything. I guess I do not know where best to look... > > Yours sincerely, > > Roger Oberholtzer Thanks Roger for your feedback. I'm redirecting your question to the opensuse-buildservice(a)opensuse.org list. The initial posting was: http://lists.openSUSE.org/opensuse/2012-08/msg00328.html Instead to complain any of us is able to do the same by replying to the correct list, set Reply-To, and by this the discussion is moved forward to the correct list. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

8 years, 5 months

[opensuse-buildservice] C:\nppdf32Log\debuglog.txt pops up in working copy sometimes

by Thomas Renninger

Hi, I remember it's not the first time I delete this file. A quick find reveals that it shows up seldom, but sometimes: find .. |grep nppd ../mcelog/C:\nppdf32Log\debuglog.txt ../dracut/C:\nppdf32Log\debuglog.txt osc status ? C:\nppdf32Log\debuglog.txt From the modification date it looks like it has been added with my latest osc update call. In both above files I see exactly 18 lines of this: NPP_GetValue is called Nothing important/critical at all, just a cosmetic thing... Thomas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 5 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service August 2012