openSUSE Build Service June 2008

buildservice@lists.opensuse.org

61 participants
68 discussions

[opensuse-buildservice] openSUSE Build Service Status Report.
by Adrian Schröter 03 Jun '08

03 Jun '08

present: rlihm, jcborn, tpatzig, froh, adrian, mjung, mls Topics ====== Status reports 1.0 release package wizard General Status reports: ======================= rlihm: * Created LinuxTag flyer promoting Build Service * Discussed with Zonker about OBS promotion, created OBS logo suggestion. jcborn: * Fighting against YaST dependencies to get a image to install from. * Working in home project tpatzig: * Starship is in usable state now. mls: * worked on debian transform app. froh: * working on new server package sets, focusing on openSUSE and SLE 10 packages * thinking about test case to run and test obs server package during build adrian: * doing LinuxTag presentation, good visited and filled with interested people * Hunting a bug in api.o.o to be able to add missing devel projects in openSUSE:Factory poeml: * testing branch requests and submit request handling * preparing server for 11.0 release. 1.0 release: ============ Planned release date is next monday/tuesday. * devel projects need to be added for all Factory packages (AI: adrian) * osc branch request should offer ignore devel (AI: poeml) * osc should report created branch project (AI: poeml) * Factory ftp generation. (AI: adrian) * Add config option to copy master-boot-record package into 64bit arch (AI: mls) Package Wizard ============== Michal Marek submitted a first and experimental version of his package creation wizard. It is part of the general web interface. Michal thinks about further steps to make packaging easier via some kind of auto detection. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) 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] Backports
by Leonardo Chiquitto 03 Jun '08

03 Jun '08

Hello, Is there a way to build packages from Factory on - lets suppose - SLE10 without creating a new package (and thus duplicating the original one) in my home project? Eventually, I need to do this kind of backporting and I couldn't find a way to ask something like this to the Build Service: "build package Factory/foo on SLE10 and put the resulting binaries in my home project". Thanks, Leonardo --------------------------------------------------------------------- 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] New Project Outside of Home
by Jason Record 03 Jun '08

03 Jun '08

I would like request two projects be added to the build service that are outside my home:<login> namespace. They are: Package Name: ntsutils Title: NTS Troubleshooting Utilities Description: A noarch package that contains supportconfig and chkbin. These tools are used heavily is troubleshooting system and application issues. Supportconfig gathers system information and organizes it to assist in resolving problems quickly. Chkbin checks and confirms a binary and it's shared library dependencies. Internal SVN Repo: https://wssarch.lab.novell.com/svn/ntsutils Package Name: sc-plugins Title: Supportconfig Plugins Description: A set of plugin scripts to be included with a supportconfig tar ball. Plugins are scripts that extend supportconfig functionality. Internal SVN Repo: https://wssarch.lab.novell.com/svn/sc-plugins It appears the best place for these packages is openSUSE:Tools. However, I'm open to wherever it fits best. Jason Record Novell Technical Services World Wide Support Linux OS Novell, the leading provider of Information Solutions jrecord(a)novell.com 801-861-5955

2 1

[opensuse-buildservice] Upgrading CentOS_5 to CentOS_5.1 or adding 5.1
by Mike Veltman 03 Jun '08

03 Jun '08

We actually need 5.1 for our packages, would it be possible to get a 5.1 CentOS repo, or can we help with that ? With regards, Mike (Gwayne) --------------------------------------------------------------------- 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] eeePC repository
by Andrew Wafaa 02 Jun '08

02 Jun '08

Aloha all, If at all possible would it be possible to combine all the efforts to get openSUSE/SLE to run on the elfin eeePC? I was thinking of trying to get a drivers:eeePC namespace and have all of the current packages in there. I have copied the packagers in on this just in-case they're not subscribed to the ML. This would make things from a user's perspective so much easier and also enable better knowledge sharing as people are duplicating efforts. Also some are packaging items that other packagers could benefit from. Also would it be possible to look at getting all the drivers working on 11.0, please? The speed benefit of the next release will be oh so more appreciated in the little device. Many thanks for your work in packaging the drivers so far and hopefully it can be that little bit better :) FunkyPenguin -- Andrew Wafaa, openSUSE Member: GNOME Team. awafaa(a)opensuse.org | http://opensuse.org/GNOME openSUSE: Get It, Discover It, Create It at http://www.opensuse.org http://www.wafaa.eu --------------------------------------------------------------------- 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] eclipse-bs status report, week 22
by Michal Marek 02 Jun '08

02 Jun '08

[GREEN] - no update due to Long writing his undergraduate thesis, should be finished next week or on 2008-06-17 at the latest --------------------------------------------------------------------- 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] proposal or repository for branding, wallpapers, artwork, themes etc.
by Stanislav Brabec 02 Jun '08

02 Jun '08

Hallo. I would like to propose a new repository (repositories) for several types of artwork: Branding I am thinking about subprojects with particular brandings. First planned item is the "Example" branding template. Proposing: Branding:Example or Artwork:Branding:Example Wallpapers and backgrounds It would be nice to package popular Propaganda abstract wallpapers set altogether with desktop integration stuff (KDE+GNOME wallpapers, nautilus background patterns,...). Proposing: Artwork or Artwork:Wallpapers Themes and metathemes Maybe bad idea. Could be GNOME:Themes, KDE:Themes or Artwork:GNOME, Artwork:KDE. Technical topic: Some of these project would be completely distro independent. Is it possible to create such build to prevent duplicated packaging of identical files? -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- 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] spec file wizard
by Michal Marek 02 Jun '08

02 Jun '08

Hi, I'm working on a new feature of the buildservice, a wizard that helps with creating spec files (and in the future maybe with other tasks). See http://lizards.opensuse.org/2008/05/26/learning-ruby/ . I now have a working prototype, including a webclient interface. It consists of - A controller on the api (frontend), that sends a set of xml-encoded questions to the client, receives answers from the client and either asks more questions (suggesting defaults where possible) or generates a spec file - A webclient part that converts the xml questions into a HTML form, let's the user fill in the form and sends the responses to the api. It should be possible to also write an osc command that asks the questions on terminal instead. Here are some screenshots of the webclient: http://michal.markovi.net/images/bs-wizard-2008-05-30-1.png http://michal.markovi.net/images/bs-wizard-2008-05-30-2.png http://michal.markovi.net/images/bs-wizard-2008-05-30-3.png http://michal.markovi.net/images/bs-wizard-2008-05-30-4.png http://michal.markovi.net/images/bs-wizard-2008-05-30-5.png http://michal.markovi.net/images/bs-wizard-2008-05-30-6.png http://michal.markovi.net/images/bs-wizard-2008-05-30-7.png http://michal.markovi.net/images/bs-wizard-2008-05-30-8.png http://michal.markovi.net/images/bs-wizard-2008-05-30-9.png An example of the an xml document describing the questions: $ curl -n 'http://localhost:3001/source/home:mmarek/hello/_wizard' <?xml version="1.0" encoding="UTF-8"?> <wizard last="false"> <label>Step 1/2</label> <legend>What do you want to package?</legend> <entry name="tarball" type="file"> <label>Source tarball to upload</label> <legend></legend> <value></value> </entry> </wizard> - label and legend are self-explanatory. - value is the default value to present to the user. - If the last attribute of the root element is true, it means that the client shouldn't send any further replies. - There can be an arbitrary number of <entry> elements, each representing a question to ask - The name attribute of an entry has the same meaning as in HTML forms - type can currently be one of - file: the client should PUT a file to the package directory in a *separate* request and send the filename as response (e.g. tarball=foo.tar.gz) - text or longtext: text data, longtext expects a multiline text (e.g. the package description) Client sends back either a GET request with the data in the query string or a POST request encoding the data either as application/x-www-form-urlencoded or multipart/form-data (i.e. anything rails handles). All communication with the API happens via the /source/<project>/<package>/_wizard url, which means that the client must first create the package by uploading a dummy _meta (see the wizard_new action in the webclient). To maintain it's state, the frontend stores a wizard.xml file in the package directory. I know it's a hack, but it seemed as the easies way for the time being :). $ curl -sn 'http://localhost:3001/source/home:mmarek/hello/wizard.xml' | xmllint -format - <?xml version="1.0"?> <wizard> <data name="name">hello</data> <data name="tarball">hello-2.3.tar.bz2</data> <guess name="license">GPL v2 or later</guess> <guess name="version">2.3</guess> </wizard> The patch is attached. Note that this my first ruby code ever (I started reading some tutorials this week), so please bear with me. If some of the ruby & rails experts have some time to review the patch for security, bugs, style, etc, that would be great. Michal

3 3

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service June 2008