September 2010 - openSUSE Build Service

[opensuse-buildservice] Fwd: Re: [yast-devel] Displaying Package Descriptions
by Karl Eichwalder 10 Sep '10

10 Sep '10

The Web interface does not honor the "traditional" markup-less formatting of the package descriptions. Simply replacing every \n with <br /> leads to strange results. Instead, please replace \n\n with </p><p> (paragraph end and start, iff a paragraph follows). Another rule is, lines starting with * are unordered list items. Maybe, there are more rules. Please, coordinate with the yast developers. I'm sorry about these ambiguities, but it is often hard to convince developers to use a proper markup language... ----- Forwarded message from ke(a)suse.de ----- Date: Thu, 09 Sep 2010 13:43:33 +0200 From: Karl Eichwalder <ke(a)suse.de> Reply-To: Karl Eichwalder <ke(a)suse.de> Subject: Re: [yast-devel] Displaying Package Descriptions To: Johannes Meixner <jsmeix(a)suse.de> Cc: Tim Serong <tserong(a)novell.com>, yast-devel(a)opensuse.org Karl Eichwalder <ke(a)suse.de> writes: > Johannes Meixner <jsmeix(a)suse.de> writes: > >> On Sep 8 04:42 Tim Serong wrote (shortened): >>> # rpm -q --qf '%{DESCRIPTION}' $PACKAGE | sed \ >>> -e 's/\&/\&/g' \ >>> -e 's/</\</g' \ >>> -e 's/>/\>/g' | awk \ >>> 'BEGIN { print "<pre>" } { print } END { print "</pre>" }' > > Thanks, but <pre> is a no-op. These days, various PDAs with small > displays are in use, and then, there is this ncurses yast interface... BTW, the BS is also one of these "players" and it keeps line-breaks, but uses a proportional font... For example, see https://build.opensuse.org/package/binary?arch=i586&filename=opensuse-manua… This is why formatted text without self-explaining markup sucks. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org ----- End forwarded message ----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Can't find valid boot/<arch>/ layout failed
by Matthias Praunegger 09 Sep '10

09 Sep '10

Hello list! I'm working on my project (desktop4education, http://d4e.at) and I want to build it with the openSUSE Build Service. My first try: osc co openSUSE:11.3 _product:openSUSE-dvd5-dvd-i586 ... osc build -> Then I got the following error message: [I] ProductData:getVar(REPO_ONLY) is not set Sep-08 08:25:28 <3> : Can't find valid boot/<arch>/ layout failed [W] Creating boot methods failed, medium maybe not be bootable -- Matthias desktop4education http://d4e.at/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 9

[opensuse-buildservice] Grouping OBS repos into services
by J. Daniel Schmidt 08 Sep '10

08 Sep '10

What do you think about the following idea? The openSUSE software management zypp knows about a service type called RIS [1] (sometimes referred to as NU type [2]). It allows to group repos together to a service that can then easily be added to the system. This would ease administration of many openSUSE installations. A user would just need to add his own or preferred service to his systems to get all needed repos assigned. It is even possible to later change the service as the software management will update the repo settings on a service refresh. The openSUSE project could offer a new webservice that allows any registered user to create such a service. Users could group any OBS project repos into a service, give it a name and a description. The webservice could look like this (see "services" as a placeholder): services.opensuse.org -> HTML: login and manage your services (group any OBS repos into services) services.opensuse.org/<user_name> -> HTML: list all repos of a user services.opensuse.org/<user_name>/<service_name> -> HTML: show the service with a short description and all containing repos services.opensuse.org/<user_name>/<service_name>/repo/repoindex.xml -> XML: deliver a service this is the place where the software managemanet looks for the service By default all home-projects of a user that are in the same hierarchy level could be available grouped as a service as well: services.opensuse.org/<user_name>/home:abc:KDE-5.5 or services.opensuse.org/<user_name>/home:abc:server:mailserver ... such services dynamically change when a new project is created. The openSUSE project could also offer some generic services like services.opensuse.org/opensuse/KDE-latest services.opensuse.org/opensuse/Gnome-latest services.opensuse.org/opensuse/Ruby-on-rails ... a.s.o. Easily possible as well: services.opensuse.org/pacman/Mediaplayer [1] http://old-en.opensuse.org/Standards/Repository_Index_Service [2] http://old-en.opensuse.org/Standards/NU_Service Ciao, Daniel -- J. Daniel Schmidt <jdsn(a)suse.de> SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] Download Statistics
by Srivats P 08 Sep '10

08 Sep '10

Hi, Are per project/package download statistics planned in the near/distant future? I remember seeing somewhere that it is "already implemented but needs to be optimized" - but I can't find that page now. A 2009 post (http://lists.opensuse.org/opensuse-buildservice/2009-03/msg00071.html) seem to indicate that it was added and removed? Regards, Srivats -- 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] loop module in qemu-kvm of build service
by Praveen_Paladugu＠Dell.com 07 Sep '10

07 Sep '10

Kiwi image builds require loop devices in the qemu virtual Machine used by OBS server. But the kernel that qemu boots into doesn't seem to have "loop" built in. It is compiled as a module.=20 I tried to load the loop module in init_buildsystem (with modprobe loop) script which is run by the kernel during boot. =20 Since the modules.dep file is not available, this will not work. How else can I load "loop" module into the kernel in the VM for the kiwi builds to work? Following are the versions of packages I am using: build-2010.06.29-68.1.noarch obs-common-2.0.1-1.1.x86_64 obs-signd-2.0.81-1.1.x86_64 obs-api-2.0.82-4.1.x86_64 obs-worker-2.0.82-4.1.noarch obs-utils-2.0.82-4.1.x86_64 obs-service-verify_file-0.1-2.1.noarch obs-service-download_url-0.1-7.1.noarch obs-source_service-2.0.82-4.1.x86_64 obs-server-2.0.82-4.1.x86_64 obs-productconverter-2.0.82-4.1.x86_64 Thank you Praveen-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

Re: [opensuse-buildservice] notify-osd and notifyconf
by Dominique Leuenberger 07 Sep '10

07 Sep '10

Hi Nelson, >>> Nelson Marques <nmo.marques(a)gmail.com> 09/06/10 9:35 PM >>> >Hi all, > > My name is Nelson and I'm toying around with osc and build service for >some time. Though I'm far for being proficient with openSUSE tools or >openSUSE packaging, I'm trying to get hang of this. > > I've taken notify-osd[1] and notifyconf[2] which are based on launchpad >and tried to build them (with some questionable success), and not >exactly following the standard rules. > > I would love to make this packages available as an option for GNOME >users on openSUSE. I have much too learn and and I do have some spare >time to work them out. > > Any feedback on faulty stuff on the specs and some help with links to >documents where I can get information to work around some flaws detected >will be most welcomed, so that they can comply with openSUSE standards. > > My build service user name is 'ketheriel' and I have my home here[3]. First, let me welcome here! It's great to see some new names popping by. As for your spec file, I did have a look at it and there is actually not many things that would need to be changed at all. I'd say you got a very good start on this one. Most of the things I probably won't find links though to point out where it's documented... somewhere in the wiki; starting point would be [0]. Small things like the Group selected for the package: System/Libraries is really meant for libraries. Stuff, that should only ever be pulled in as a dependency. [1] Shows a list of valid groups, together with explanation which one could be used in what case. Then, the build log can give you valuable information about common errors at the end. In your case, it spit's out that you use a macro, %doc, in the changelog. Can be possibly dangerous, as macros are also expanded there. Rewriting this as %%doc would solve this warning. Your %prep section could probably just be changed to %prep %setup -q %patch0 -p0 Setup will create the subfolder named %{name}-%{verision} and this will be set as the new base folder. As such, you also do not have to change inside this folder. Less to type, less places, an error can slip in. %build section: %configure already contains a --prefix parameter, which is set to %{_prefix}. In case of openSUSE this actually is evaluated to /usr, as such your parameter is just redundant. Does this app work with parallel building? You can try to use %__make %{?_smp_mflags} (this will expand to something like "make -j 4", depending on the host it runs on) %install section: Do not rm the %buildroot. This is done in %clean For make install DESTDIR=$RPM_BUILD_ROOT, you can use the macro %make_install %files section: That's all fine. Only if you would change the %prep to just be %setup, you would have to remove the various %name-%version references... but other than that, this is all fine. As for %changelog, at openSUSE we split this out in an external file, the .changes file. Using "osc vc" you can create a new entry at the top of the file with the correct timestamp and formatting. The general rule there is to not exceed the 67 characters (same as the dashed line). I think that's all I see for now. Should you have any questions left, feel free to ask. Best regards, Dominique [0] http://en.opensuse.org/openSUSE:Packaging_guidelines [1] http://old-en.opensuse.org/SUSE_Package_Conventions/RPM_Groups -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 07 Sep '10

07 Sep '10

present: mls, coolo, tom, mhuewe, adrian Topics: * Status round * Request diff * Source page * 2.1 release Status round: ============= mls: * source changes which came indirect via source link are not high prio build jobs anymore * working on support for path overwrite for kiwi image builds * added acceptinfo to accepted requests adrian: * added request diff api call which makes use of acceptinfo * working on webui source page * added source services which alles to git/svn clone/update repositories, tar, compress and update spec file according to new version. Allows snapshots via one api command or via "osc service remoterun" * Working on OBS installable appliance. Currently broken build due to problem with loopback device. mhuewe: * rewrote osc commit handling * fixed kiwi build for products, it downloads the binaries with the binaries with cpio per package container. Request diff ============ Discussing the new api request diff call: * to be done: add "unified" diff and limiter options for the call. * Add fate entry for improving diff webui interface OBS 2.1 release =============== * Beta release is planned this week, but current master is not ready. Source webui page ================= Discussing the webui showing the package sources. Conclusions: * add baserev support for link view * move commit history to own page and offer to show the diff there (with optional linkrev=base option) * unify rev and src md5 field * show just the last commit * change float button boxes to a combo box like approach, do the same with the small icons on the project and package overview page. -- 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

[opensuse-buildservice] Switching to 2.x
by Johannes Lahti 07 Sep '10

07 Sep '10

Hello everyone! I'm currently maintaining OBS 1.7. in a development project for my company and we decided to try switching to OBS 2. I did a clean installation on a new server with the latest version (2.0.6). Now I'm facing a couple of problems: 1) In the OBS 1.7 we have a local distro installed by copying the binaries to /srv/obs/build/<prj>/<arch>/:full -folder. However in the 2.0.6 there's no /srv/obs/build -folder at all. I searched the mailing list archives and I spotted one message where the advice was to setup "OBS interconnect" using "Setup OBS" in the webui. Is this correct? 2) If I click "Setup OBS" on the front page, I get this error: "undefined method `const_defined' for Object:Class". Thanks for any advice! -Johannes -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Re: [PATCH] [api] Don't fail on diffing request which submit new packages
by Marcus Hüwe 07 Sep '10

07 Sep '10

On 2010-09-06 20:24:01 +0200, OBS build-service wrote: > From: Adrian Schröter <adrian(a)suse.de> > > --- > src/api/app/controllers/request_controller.rb | 17 +++++++++++------ > 1 files changed, 11 insertions(+), 6 deletions(-) > > diff --git a/src/api/app/controllers/request_controller.rb b/src/api/app/controllers/request_controller.rb > index 64f1e7a..49d9f07 100644 > --- a/src/api/app/controllers/request_controller.rb > +++ b/src/api/app/controllers/request_controller.rb > @@ -390,16 +391,20 @@ class RequestController < ApplicationController <SNIP> > - # for requests accepted with OBS 2.0 and before, this can not work in all cases > - path = "/source/%s/%s?oproject=%s&opackage=%s&cmd=diff&expand=1" % > - [CGI.escape(action.source.project), CGI.escape(action.source.package), CGI.escape(action.target.project), CGI.escape(action.target.package)] > - if action.source.data['rev'] > - path += "&rev=#{action.source.rev}" > + # for requests not yet accepted or accepted with OBS 2.0 and before > + if DbPackage.find_by_project_and_name( action.target.project, action.target.package ) > + path = "/source/%s/%s?oproject=%s&opackage=%s&cmd=diff&expand=1" % > + [CGI.escape(action.source.project), CGI.escape(action.source.package), CGI.escape(action.target.project), CGI.escape(action.target.package)] > + if action.source.data['rev'] > + path += "&rev=#{action.source.rev}" > + end > + else > + diff_text = "New package: " + action.target.project + "/" + action.target.package + "\n" + diff_text Hmm there's no need for this check. If we pass the "missingok=1" query parameter to the backend we should be able to diff against a "missing"/non-existent package. Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Mandriva 2010 i586 build failure
by Kyrill Detinov 07 Sep '10

07 Sep '10

Friday 03 September 2010 Failed build with log: ... installing libwxgtku2.8-devel-2.8.10-3mdv2010.0 error: unpacking of archive failed on file /usr/share/doc/libwxgtku2.8-devel/docs/html/logo.gif;4c800288: cpio: read failed - Bad file descriptor exit ... x86_64 is OK. Package: https://build.opensuse.org/package/show?package=myrulib-git&project=home%3A… -- WBR Kyrill -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3