June 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Strategy voting reminder!
by Jos Poortvliet 28 Jun '11

28 Jun '11

Hi all! In 3 days, the voting for the openSUSE strategy has to be done. We've had only about 1/5th of our members vote and that's not a lot. Now I know we don't have any way to check if members are still very active so maybe most are not. But if you are, please, vote! Find the last article from news.o.o here: http://bit.ly/iB2Dzh And a direct link to voting: http://bit.ly/kZaAC2 You just have to log in with your connect account and VOTE! For 2 years people have been asking 'what does openSUSE want'. We tried to put that in the strategy. Ok, it is not perfect, but that is because we didn't appoint someone to tell us what we want but because we *asked*. And then, yes, you get compromise. Anything bad in there is there either because you didn't speak up (tssss bad bad) or the majority disagreed with you. And that is how it SHOULD work. It is what sets us apart from the other major distributions - we have no dictator or 'steering group'. But democracy also comes with responsibilities - voting! Now, enact your democratic duty, here: http://bit.ly/kZaAC2 Cheers, Jos

1 0

[opensuse-buildservice] Maintaining packages; trigger source download
by Johannes Weberhofer 28 Jun '11

28 Jun '11

I've submitted some packages to the obs. The packages have been accepted for inclusion into server:php:applications; now my status for the packages is: Package server:php:applications/mediawiki-texv, php5-pear-pel: - I've been added as user (without roles) - I can submit updates and accept requests to mediawiki-texvc - I can not trigger a source-download (that's why the package fails) Package server:php:applications/mediawiki, php5-pear-channel-pearhub : - I've not been added as user Q: Why is my user handled differently? Q: How can the source-download be triggered (why isn't it triggered automatically?) Q: Can I be added as maintainer/bugowner for the packages? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Discontinued F12 and F13
by Fritz Elfert 27 Jun '11

27 Jun '11

Hi, To whoever triggers the move of any repos into DISCONTINUED: Could you PLEASE be so kind and announce such an action on this list in *advance*? With a warning in advance (1-2 weeks), all those who want to keep their old stuff, would have a fair chance to archive it off-site. Now I'm wasting time (and valuable resources on OBS) by re-enabling them in my project, rebuilding them, archiving the resulting repos and *then* removing them again. Perhaps this could even be automated in the future? (Like some warning via mail to all those who have builds enabled against a soon-to-be-discontinued repo). Just an idea... -Fritz

2 1

[opensuse-buildservice] Strategy voting reminder!
by Jos Poortvliet 27 Jun '11

27 Jun '11

Hi all! In 3 days, the voting for the openSUSE strategy has to be done. We've had only about 1/5th of our members vote and that's not a lot. Now I know we don't have any way to check if members are still very active so maybe most are not. But if you are, please, vote! Find the last article from news.o.o here: http://bit.ly/iB2Dzh And a direct link to voting: http://bit.ly/kZaAC2 You just have to log in with your connect account and VOTE! For 2 years people have been asking 'what does openSUSE want'. We tried to put that in the strategy. Ok, it is not perfect, but that is because we didn't appoint someone to tell us what we want but because we *asked*. And then, yes, you get compromise. Anything bad in there is there either because you didn't speak up (tssss bad bad) or the majority disagreed with you. And that is how it SHOULD work. It is what sets us apart from the other major distributions - we have no dictator or 'steering group'. But democracy also comes with responsibilities - voting! Now, enact your democratic duty, here: http://bit.ly/kZaAC2 Cheers, Jos

1 0

[opensuse-buildservice] Dependency issues with the RPM removal check
by Olivier BONHOMME 27 Jun '11

27 Jun '11

Hello, I am trying to build some PHP applications packages. The applications is composed a main application and lots of plugins. Considering that, I created a specfile with generates several packages : One for the main app and others for plugins and the RPM plugins depends from the main app RPM. So in my specfile, I used the keywords Requires(post) and Requires(postun) for the plugins RPM to have dependencies on the main app. I use post and postun because the plugins needs to execute a script provided my the main app RPM. I imported the SPEC file in OBS and unfortunately there is an issue for the SLES 10 distribution : The remove task fails because a dependency issue. Indeed, it seems that even with the requires keyword, the remove script removes the main app RPM before plugin and it that case the execution script in %postun fails because the script is missing. The more strange thing is that this issue happens only for the SLES10 distribution. I talked about this issue on IRC and I heard that it could be a bug. So is it really a bug or am I doing something worng. If it is a bug, is there a workaround in order to build correctly the package ? Thanks for you answers Regards, Olivier BONHOMME -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] supporting different versions of a package in one project
by Wolfgang Rosenauer 27 Jun '11

27 Jun '11

Hi, I'm running into a nasty issue in one of my OBS projects. OBS supports to have the same package in different versions within one project basically. I'm using that since years but now I'm running into a special case which is not supported. So I would consider it a bug but wanted to bring it up here (maybe someone knows about a workaround). I have one package in two versions within one project but now I have two versions of another package where one requires the older version to build and the other requires the newer version to build. So I've specified versioned dependencies in BuildRequires but that is not sufficient. They are actually taken into account but now I get "unresolvable" for the older package as it doesn't find the previous version apparently. So could we support this case in future? And does anybody know a workaround to that? Otherwise I won't be able to release Firefox 5 in the mozilla repository w/o removing all older versions what I don't want to do. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] [gsoc] osc code cleanup - summary of week 5
by Marcus Hüwe 26 Jun '11

26 Jun '11

Hi, here's a small summary of the 5th (coding) week. I've spent most of the time with the url-like argument parser (more information can be found here [1] and here [2]). Additionally I cleaned up/reworked the remote file classes (now we have: RORemoteFile and RWRemoteFile). I also added an AbstractHTTPResponse and HTTPError class to the httprequest module (the main purpose of the AbstractHTTPResponse is to encapsulate a "concrete" http response (for instance it can be used as a wrapper around urllib(2)'s addinfourl class)). TODO for this week: * write a search module in order to find packages, projects, requests etc. * maybe we also need something like a source module (mainly to access the /source route) * think about working copy code cleanup/internal restructuring Marcus [1] oscargs module: http://gitorious.org/osc2/osc2/blobs/master/osc/oscargs.py [2] example usage/testcases: http://gitorious.org/osc2/osc2/blobs/master/test/test_oscargs.py -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Feedback on OBS Private instance installation at Renault Automotive
by JAFFREZIC Xavier 26 Jun '11

26 Jun '11

Hi everybody, I'm working at RENAULT Automotive and we are involved in the GenIVI alliance. For testing purpose, we need an OBS private instance for building our software stack and keep all of application graphics confidential. So I have started to install and configure a OBS instance using the opensuse wiki : http://en.opensuse.org/openSUSE:Build_Service_private_instance (written by Dominig Ar Foll as I understood) This was very useful for preparing the hardware, configuring the disk, downloading all the software images. With all these in formations, I was able to start quite quickly the OBS instance. I think, the wiki should contain a section concerning the quick test installation using only one hard drive (containing every things) . This solution wouldn't be safe at all for data's, but this would reduce the disk preparation to copying the appliance to it . But, the wiki is very complete to set an production OBS instance (with lots of optimizations) . But to set up this kind of Instance, you need an agreement from the management because you will need to buy a few equipment and the agreement could be easily obtained from a Demo based on an initial quick and dirty OBS installation. When the appliance started, it clearly does nothing and problems have started . (And there is no error message anywhere . That's driving crazy) First what was missing in the wiki was the proxy configuration (Dominig, with it great experience and with lot of patience, help me a lot to set up this proxy configuration). So, I have added a small section in the wiki corresponding to this. While the proxy is configured . the OBS still does nothing (Aaaargh !) Here is comes the tricky part . All tutorial on the net are based on copying the prj prjconf from another OBS instance, for which a login is required . I didn't understand anything to all of these . But it seems also that OBS has evolved a lot and all of these exotic manipulation aren't any more required for quickstarting a linked OBS . (but they maybe are for a standalone OBS instance) . Well, as a complementary information, I have used the 2.2.80 version on the OBS Appliance. Dominig show me the alternative way and almost everything can be done using only the WebUI .. Yes in that case, your OBS will be linked to an higher OBS instance, but this is sufficient for beginning .. So, the only thing that couldn't be done by the WebUI is to setup the OSC configuration file . (in fact, I don't now if it is mandatory regarding the OBS configuration but it's a very easy way to check that the OBS is properly configured). The tricks that Dominig has proposed is modify the .ossrc file to make the "apiurl" line pointing to the OBS that your are trying to configure. In that way, this insures that retrieval information mechanism will be done by the OBS itself. So it will also insure that the proxy settings are correct (remembering some headache!!!) . After that, thing becomes quite easy. I have used the OBS setup on the WebUI and select one of the 2 preconfigured choices. After switching back to the osc command line on the OBS itself, I have issued some osc ls MeeGo.com (as MeeGo.com is predefined settings) command which returns nothing . But osc ls MeeGo. Com: x (where x is not a project name) and I get the complete list of all available project on the linked instance : That means, my obs is now alive and working !!! The final point was to define a build target . It take some times to understand that would be done by configuring properly the home projet of the Admin . (Now, I know that could be done on any project .) Dominig explain me what I need to add with raw config editor in the home:Admin project. He says, put the following line inside the Admin:project <repository name="MeeGo.com"> <path repository="standard" project=" MeeGo.com:MeeGo:1.2.0:oss"/> <arch>i586</arch> </repository> I understand a bit later the exact meaning of each line . Finally I upload a source package (from meego source) and it build ... bingo ! So as a conclusion, setting up a linked Private instance of an OBS is not complicated . But, I didn't find this on the net . And clearly the name OBS didn't help for this. Working in automotive world, we are sometimes searching for information about the CAN (Controler Area Network) technology which is the embedded automotive network . You can easily imagine that CAN isn't a relevant keyword with Google. OBS seems to have nearly at the same efficiency!!! So I think, I will add this configuration method on the opensuse wiki . My chance was, that Dominig is a very nice guy and I met him at a previous GenIVI workshop . Without his help, I would be still searching on the web !!! (and surely becoming crazy..) Xavier JAFFREZIC RENAULT Automotive Research Depatrment Software Specialist -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] Re: Introducing 0install developers
by Adrian Schröter 26 Jun '11

26 Jun '11

Am Wednesday, 15. June 2011, 12:36:00 schrieb Jos Poortvliet: ... > > There is no fundamental difference in making an RPM package from > > a specfile, compared with making a XML+TBZ package with 0compile. > > > > In the .rpm, you have the metadata, signature and archive combined > > into one file while in ZI you have them separated into two files. So, you prefer to compile and to build from scratch instead of building an rpm and converting it ? No problem in general, but how would the base system be installed. I think there is not anything like a complete linux just build via 0install packages, right ? So we would need to support some rpm/deb base system, adding more packages as build dependencies (rpm or 0 ?) and build the 0install package on top. Sounds a bit of a mixture like an rpm build and a kiwi build to me. > Anders, Thomas, here is the documentation on adding a build target: > http://en.opensuse.org/openSUSE:Build_Service_adding_build_targets this is end-user information, not really OBS developer informations. If you want to support the 0install xml files, you need to add support to the build script and it's parsing modules first. When this is done, one should be done to 90% https://www.gitorious.org/opensuse/build/ The build script can work complete standalone, no need to setup an OBS to work on it. > > However I'm not sure this'll work for 0install. > > So, people on the OBS ML, could you tell the gents if you're interested in > working with them on this and where they should start with getting a 0install > build target? > > Cheers, > > Jos > > [1] http://0install.net/ > [2] https://build.opensuse.org/project/show?project=home%3Atalex5 -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Potential bug?
by Nelson Marques 26 Jun '11

26 Jun '11

Hi I'm having a few issues while trying to build a Banshee package for the Banshee Repository. The build process fails because it fails to find a file which should be installed by this package: dbus-sharp-glib. Now the issue is: * The build log claims either dbus-sharp-glib and dbus-sharp-glib-devel are installed; * The /installed-pkg on the build chroot cage suggests both are installed; * Both packages are actually in the buildcache, so they are actually being pulled; * The devel package (which installs ok) does require the normal package (dbus-sharp-glib, which is found not to be installed). The build fails because dbus-sharp-glib isn't installed... a simple "rpm -qa | grep dbus-sharp-glib" or "rpm -qa --last" shows it isn't installed. Some time ago I've actually successfully build this package (with another spec), it's on the Banshee:Unstable repositories (the binaries and .src.rpm). I've also tested with the spec from that src.rpm, but it turns out with exactly the same error, which suggests there is most likely a bug introduced in a recent update on OBS. Guys any help on how to debug this further would be most welcomed as this bug (or whatever that is) is preventing an update on Banshee in Factory and on the Banshee:Unstable repo. Thanks in advance, Nelson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1