July 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] git submodules
by Mich; 27 Jul '11

27 Jul '11

Hi, I have a little problem with a package that I pull from git. The source tree has git submodules which are necessary for building. Running a shell script pulling in the submodules seems to be prohibited in an OBS instance. Handling the submodules just in another tar_scm service doesn't work either. So, which options do I have on the OBS? I mean, l could always run the whole thing on my local system and then repackage ... but I don't really fancy that solution. bye Michi -- 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] creating branch package with web interface.
by Paul Elliott 27 Jul '11

27 Jul '11

In http://en.opensuse.org/openSUSE:Build_Service_Collaboration we find: > Create Branch Project > > Firstly, we create a branch of the package (and its project) we want to > work on in our home project. Click on the "Actions" menu and afterwards on > "Branch package". > > This server creates a new project below home:$yourself:branches, the branch > project. This branch project has the same build setup as the original > source project. The command also creates the package inside of the branch > as a source link. I believe this is not up to date. I can not find an actions menu on my home project! But there is branch package from other project under "Packages". Could someone please tell me how things have been changed and then document the changes! -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

2 1

[opensuse-buildservice] [PATCH] cleanup stale loop devices left by kiwi
by Dinar Valeev 26 Jul '11

26 Jul '11

When worker or osc builds kiwi images in a chroot environment, for some reason there stale loop devices left. Which makes impossible later just delete buildroot. Architectures seems to be affected at least are x86_64,ppc. Maybe that patch is just workaround, but I cannot reproduce that issue with pure kiwi.

1 0

[opensuse-buildservice] Open Build Service 2.3 Beta 3 released
by Adrian Schröter 22 Jul '11

22 Jul '11

Open Build Service 2.3 Beta 3 ============================= Changes compared to Beta 2 are: * As ruby XML stack the nokogiri gem is used now. This required some larger changes, but it solves the ruby memory corruption errors. * obs-common package is obsolete. ActiveXML is part of obs-api now. * Larger number of bugfixes for the maintenance features. It includes also support for "osc mbranch" to handle packages with multiple build descriptsion (eg. kernel packages on SUSE). You can stop here when you read already Beta 1 announcement ,) OBS 2.3 main features ===================== The main features of this release are * Full distribution maintenance support. This includes support for the workflow in OBS and also the patch channel generation. This functionality can be used at full glance with coordination and review teams or just in parts. * Read access protection for projects (as planned for OBS 2.2) Apart from that we have many smaller improvements, esp. in the area of request handling and the webui integration. Download it =========== As usual, you find current packages or an appliance in openSUSE:Tools:Unstable project. OBS 2.3 Beta 3 is tagged as version 2.2.90. Please read here for usage details for the appliance: http://en.opensuse.org/openSUSE:Build_Service_Appliance Please find the full Release Notes below: ========================================= # # Open Build Service 2.3 # Please read the README.SETUP file for initial installation instructions or use the OBS Appliance from http://en.opensuse.org/Build_Service/OBS-Appliance There is also an install medium with installs OBS on hard disc now. README.UPDATERS file has informations for updaters. OBS Appliance users who have setup their LVM can just replace their appliance image without data loss. The migration will happen automatically. Main Features ============= The main topic of OBS 2.3 is to deliver a number of features to allow product maintenance handling with OBS. No external build or tracking tool is needed to do the typical maintenance workflow of a distribution team. The usage of these features are documented in the OBS book: http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/ OBS 2.3 comes also with a feature which was planned for the not released OBS 2.2 version. New created projects can set to hidden. That means no source or binary read access is possible. Please read the following for details: To be considered regarding read access checks ============================================= * "access" flag is hiding and protecting entire project. This includes binaries and sources. It can only be used at project creation time and can just be globally enabled (aka make it public again) afterwards. This flag can only be used on projects. * "sourceaccess" flag is hiding the sources to non maintainers, this includes also debug packages in case the distribution is supporting this correctly. This flag can also only be used at package creation time. There is no code yet which is checking for possible references to this package. This flag can be used on projects or packages. * "downloadbinary" permission still exists like before. However, unlike "access" and "sourceaccess" this is not a security feature. It is just a convinience feature, which makes it impossible to get the binaries via the API directly. But it still possible to get the binaries via build time in any case. Security aspects ================ Former OBS releases lack protection against XSS attacks. Esp. public instances should update to OBS 2.3, which is using rails plugins to protect against XSS attempts. This fixes (CVE-2011-0462). Building in "chroot" environments is known to be unsecure. XEN and KVM is considered to be a secure environment. However KVM is known to be unstable, it leads to build failures. Apache & mod_rails switch ========================= Former OBS versions used lighttpd as default web server. We have switched to apache with mod_rails (known as passenger) as default web server. We have also added an mod_xforward apache module to allow unloading the rails stack with long running requests to the backend. Please note that current apache2 versions have a known bug which cuts the http headers regardless to it's configuration. Please use apache2 from openSUSE:Tools project to get this fixed for now. Also the patched version of rubygem-passenger from openSUSE:Tools project is recommended. Known Regressions to 2.1: ========================= * none yet Features: ========= * web interface improvements: - package filtering - Generic authentification proxy support - delete request dialogs - request and review handling improvements - social features, i.e. show other user's projects and requests * api - review of requests by project or package maintainers is possible now (FATE #310806) - better Cross-Site Scripting (XSS) protection - larger number of request handling improvements * backend: Changes: ======== * web interface - bug reporting for projects/packages is only possible if a bugowner is set - XSS protection plugins are used now (CVE-2011-0462) * api - It was not possible so far to create submit requests from packages where no write access exists. This is possible now, but the source package maintainer will get asked for review the request. - the route /group/$GROUP is showing correct xml description and no directory anymore * new source service handling - Source services do not generate an extra commit for the result. Instead they work like source links, this means the generated files become visible with expand=1 parameter. - The state of the service is visible via serviceinfo element in package file list. * The backend is only accepting write access from the localhost by default. Build results can be still delivered from any host. This can be changed in BSConfig.pm Deprecated: =========== The following calls have been marked as deprecated, they will get removed in OBS 3.0 * api - /person/$LOGIN/group -> use /group?login=$LOGIN instead Requirements: ============= * The OBS server should not run on a system with less than 2GB memory. 4GB is recommended, esp. when the same system is also building packages. * Use osc 0.132 or later to get access to the new features. * Usage of Ruby on Rails version 2.3.11 is recommended. -- 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

1 1

[opensuse-buildservice] Weird listing of patterns using API
by Pavol Rusnak 22 Jul '11

22 Jul '11

Hi! When I do the following API request osc api "/search/published/pattern/id?match=project='GNOME:STABLE:3.0'" I get <collection matches="3"> <pattern name="GNOME 3" project="GNOME:STABLE:3.0" repository="openSUSE_11.4" filename="gnome3-32bit.ymp" filepath="GNOME:/STABLE:/3.0/openSUSE_11.4/gnome3-32bit.ymp" baseproject="openSUSE:11.4" type="ymp" /> <pattern name="GNOME 3" project="GNOME:STABLE:3.0" repository="openSUSE_11.4" filename="gnome3-64bit.ymp" filepath="GNOME:/STABLE:/3.0/openSUSE_11.4/gnome3-64bit.ymp" baseproject="openSUSE:11.4" type="ymp" /> <pattern name="GNOME 3" project="GNOME:STABLE:3.0" repository="openSUSE_11.4" filename="gnome3.ymp" filepath="GNOME:/STABLE:/3.0/openSUSE_11.4/gnome3.ymp" baseproject="openSUSE:11.4" type="ymp" /> </collection> But when I do osc meta pattern GNOME:STABLE:3.0 I see only two patterns: gnome3-32bit gnome3-64bit What is the third gnome3 pattern and how did it appear in the collection? (When I check the FTP tree, only the first two are present). -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] Re: [PATCH] [api] Select distinct isn't necessary anymore.
by Stephan Kulow 22 Jul '11

22 Jul '11

Freitag, 22. Juli 2011 sent OBS build: > From: Sascha Peilicke <saschpe(a)suse.de> > > Minor tweak, query time goes down from ~1.0ms to ~0.5ms. Before: 3.3s, after removal: time osc -A http://localhost:3001 my rq | wc WARNING: SSL certificate checks disabled. Connection is insecure! Failed to reach a server: timed out 0 0 0 real 1m40.383s So I would say the distinct _is_ necessary Greetings, Stephan -- 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] Mysterious behaviour for linked configuration
by JAFFREZIC Xavier 21 Jul '11

21 Jul '11

I am encountering a strange behavior on my local OBS (2.2.80 version) I have configured an "OBS setup" remote project which is pointing to : <remoteurl>https://api.meego.com/public</remoteurl> then I have configured a project with 2 local repository : - One repository is defined as : <path project="MeeGo:Meego:1.1:Core" repository="standard"/> - Second one is defines as : <path project="MeeGo:MeeGo:1.2:oss" repository="standard"/> The first one is not building and the second one is working well... Ok, I found the explanation : If I go on the MeeGo OBS, I can see that in the project name "MeeGo:1.1:Core", MeeGo is written with a big G ... In my "path project", it written with a small "g" ... Fine then problem comes here : Project name doesn't match ! Now let me explain what is strange : Whatever the way I will try to change the "g" case, It is not taken in account and it is replaced by a minus "g" I have tried to use the web UI, and edit the file but at save time my change are discarded I have tried "osc meta prj -e", but change is also discarded I also tried to create another project from scratch paying attention this to that but each time the "G" is replace by a "g"... - This doesn't occurs at all for MeeGo:1.2:oss - This also occurs for MeeGo:1.1:Core Any solution ? -- 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

2 1

Re: [opensuse-buildservice] source services and hg parameters
by Ramez Hanna 20 Jul '11

20 Jul '11

On Wed, Jul 20, 2011 at 12:21 PM, Ramez Hanna <rhanna(a)informatiq.org> wrote: > > i think for the tag you need to add "revision" parameter and set it to the tag name > the service would so > hg clone $url > and then > hg update $revision > and that is what gets tarred > > On Fri, Jul 15, 2011 at 1:15 PM, Togan Muftuoglu <toganm(a)opensuse.org> wrote: >> >> Hi >> >> I am trying to use the source services to pull the source of a project >> that is in a mercurial repo. >> >> What do I need to set in the _service file to make sure that only the >> default branch with a specific tag is pulled and compressed as a tar >> >> the branch is "default" and the tag I want to pull is Dev-3.1m6 >> >> Thanks >> -- >> To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org >> For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org >> > i think for the tag you need to add"revision" parameter and set it to the tag name the service would do hg clone $url and then hg update $revision and that is what gets tarred -- 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] [PATCH] Fix filelist check for new rpm
by Michal Marek 20 Jul '11

20 Jul '11

Directories in the rpm filelist have a trailing '/' now. Signed-off-by: Michal Marek <mmarek(a)suse.cz> --- checks-data/checkdirs | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/checks-data/checkdirs b/checks-data/checkdirs index e6fd431..7611a4f 100755 --- a/checks-data/checkdirs +++ b/checks-data/checkdirs @@ -18,6 +18,7 @@ my %myfiles; while (<STDIN>) { chomp; + s/\/$//; $myfiles{$_} = 1; while (1) { last unless s/\/[^\/]*$//; -- 1.7.6 -- 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] openSUSE:11.3:Update and openSUSE:11.4:Update re-setup
by Adrian Schröter 20 Jul '11

20 Jul '11

Hi, in preparation to switch to OBS 2.3 maintenance functionality, I will re-setup the projects for the released updates for 11.3 and 11.4 distribution now. This may affect you packagers today, because all the packages inside will be removed and reimported. So, people who build against :Update (which is not default), may see temporary problems or rebuild triggers. However, this will *NOT* affect any users just installing the updates to their system. We will generate the official Update stream afterwards out of these projects, but we will validate first that the result is correct before we redirect the users to the new repository (won't happen this week). In theory the projects should contain the same packages after the re-import, but I discovered already that our old in-house mechanism did it not always correctly. So there will be some minor changes. bye adrian PS: In case of any urgent trouble, there are the "openSUSE:11.3:Update:Old" & 11.4 projects, which contain the current content of :Update but some corrections. -- 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

1 0