August 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Another cleanup round on build.opensuse.org
by Adrian Schröter 28 Aug '11

28 Aug '11

Hi, Please excuse the cross post. I want to do another clean up round in OBS as done end of last year: http://lists.opensuse.org/opensuse-buildservice/2010-11/msg00218.html Again repositories of projects which did not saw a change since quite some time will get removed. Unlike last year, only source changes are taken into account. This will affect 2.329 home projects and 74 other projects out of 20.846 projects. Please review the following list of projects and speak up when you don't want to get the repositories removed: non-home projects: http://www.suse.de/~adrian/OBS-remove-list-candidates home projects: http://www.suse.de/~adrian/OBS-remove-list-candidates-home The FAQ from last time: Why remove repos and not just disable the build ? This will free disk space on our servers and also on all mirrors. As result we can be mirrored more easily. Will any source get lost ? No. How to enable it again ? Just add the wanted repos again. There is a project which has not been touched, but the repos are still anyway important ! Just drop me a mail .... Why not drop the entire project now that we have an undelete function ? I thought about that, but currently the webui just says that the project does not exist. It is not able to show the former content and does not offer to undelete it, so that might be too agressive for now. Why not drop people a mail and ask them to remove it ? Way too many accounts have no valid email adress and past experience showed that people do often not react when they lost interesst in their project. My plan is to do the removal next week, except more discussion about this is needed. Just tell me your opinion, also when you support this ;) thanks adrian -- 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

6 6

[opensuse-buildservice] Nonfree packages on OBS
by Tejas Guruswamy 26 Aug '11

26 Aug '11

I've noticed some non-free packages being built on the OBS - for example flash-player, wireless drivers e.g. broadcom-wl, dubious media packages e.g. ffmpeg, and many more mentioned as forbidden on the wiki http://en.opensuse.org/openSUSE:Build_Service_application_blacklist In addition to being questionable legally, it's not really in the spirit of the OBS to upload binary blobs anyway. While I don't want to spoil anyone's fun, it would suck if anyone got into trouble for this, especially SUSE. So what is the best way to deal with this? Do we email the users? If they don't respond, should admins delete packages? Maybe an automatic blacklist could be implemented when creating a package, to prevent the most common forbidden packages being uploaded? Also, I think part of the problem is that there is no workflow for people who want to help update packages in openSUSE:*:NonFree. How can, if at all, a user contribute to those packages without breaking the rules? Is, for example, creating a branch allowed? Regards, Tejas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 14

[opensuse-buildservice] scons vs. autotools
by Roger Oberholtzer 26 Aug '11

26 Aug '11

Is it possible to build a package using scons rather than autotools? For example, the gpsd project has changed to only supporting scons. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- 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] lyx in Publishing fails for SLE_11 i586
by Cor Blom 26 Aug '11

26 Aug '11

Hi, LyX fails to build for SLE_11/i586. The reason is that two versions of texlive are mixed and thus there is a conflict. Texlive-bin-devel is from the project Publishing itself, but texlive-devel is taken from SLE_11 (although it is available in Publising). Result: file X from install of texlive-devel-2007-219.34.6.noarch conflicts with file from package texlive-bin-devel-2010-74.1.i586 Can someone look into this please? Or is there something I can do about it? I would be nice to have everything green. As far as I can see "gle-graphics" is the only other package in Publishing that is having this problem. Regards, Cor Blom -- 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] [PATCH] [obs-service-tar_scm] add new parameter 'gitdepth'
by Markus Lehtonen 25 Aug '11

25 Aug '11

Add's a new parameter, 'gitdepth' that can be used to define the "history depth" of the git clone/pull. Default behavior stays the same, i.e., tar_scm creates a shallow clone with depth=1. Special value "full" can be used to create full-depth clones/pulls that fetches the complete history. --- tar_scm | 13 +++++++++++-- tar_scm.service | 3 +++ 2 files changed, 14 insertions(+), 2 deletions(-) diff --git a/tar_scm b/tar_scm index 5ca91ff..da7a9fe 100644 --- a/tar_scm +++ b/tar_scm @@ -18,6 +18,7 @@ MYPREFIX="" MYFILENAME="" MYREVISION="" MYPACKAGEMETA="" +MYGITDEPTH="1" while test $# -gt 0; do case $1 in @@ -61,6 +62,10 @@ while test $# -gt 0; do MYOUTDIR="$2" shift ;; + *-gitdepth) + MYGITDEPTH="$2" + shift + ;; *) echo Unknown parameter $1. echo 'Usage: tar_scm --scm $SCM --url $URL --outdir $OUT' @@ -88,6 +93,10 @@ if [ -z "$MYOUTDIR" ]; then echo "ERROR: no output directory is given via --outdir parameter!" exit 1 fi +if [ "$MYGITDEPTH" == "full" ]; then + # A bit hackish way of fully deepening a clone / getting a non-shallow clone + MYGITDEPTH=999999999 +fi SRCDIR=$(pwd) cd "$MYOUTDIR" @@ -166,7 +175,7 @@ elif [ "$MYSCM" == "git" ]; then # update existing content for speed/bandwidth reasons cd "$TAR_DIRECTORY" OLDVERSION=`git show --pretty=%at | head -n 1` - git pull || exit 1 + git pull --depth="$MYGITDEPTH" || exit 1 if [ -n "$MYREVISION" ]; then git checkout "$MYREVISION" || exit 1 fi @@ -180,7 +189,7 @@ elif [ "$MYSCM" == "git" ]; then mv "$TAR_DIRECTORY" "${FILE}" || exit 1 else # new checkout - git clone --depth 1 "$MYURL" "${FILE}" || exit 1 + git clone --depth "$MYGITDEPTH" "$MYURL" "${FILE}" || exit 1 if [ -n "$MYREVISION" ]; then cd "$FILE" git checkout "$MYREVISION" || exit 1 diff --git a/tar_scm.service b/tar_scm.service index 844f629..d1064a3 100644 --- a/tar_scm.service +++ b/tar_scm.service @@ -35,5 +35,8 @@ <description>Package the meta data of SCM to allow the user or OBS to update after un-tar</description> <allowedvalue>yes</allowedvalue> </parameter> + <parameter name="gitdepth"> + <description>Git history depth. Special value "full" clones/pulls full history. Only valid if SCM git is used.</description> + </parameter> </service> -- 1.7.3.4 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4

[opensuse-buildservice] [gsoc] Archlinux backend for OBS final evaluations report
by Nikolay Rysev 25 Aug '11

25 Aug '11

Hello, all! This mail is final evaluations report for my project. Unfortunately not all initial goals [from my proposal] were done due to my illness, but I have some results which I want to present. Overall "what is done": - Arch module for "build" which can: * parse PKGBUILDs and extract dependencies * parse .PKGINFO files from .pkg.tar.?z pakages and get info about it - Helper script, which gets repository metadata and prints information about packages in build corresponding format (package metadata parsing functions are also in arch module, so anyone can use them if needed) - Setup of Archlinux-specific build environment in init_buildsystem - Actual build in "build" script Now Archlinux backend is able to do _standalone_ builds. It's interesting, but it's not what we want. Of course I'll continue my work to fully integrate Archlinux support to OBS (independently of final evaluations results and after end of this GSoC). Now I plan to add support to libsatsolver [1] and integrate into OBS [2] (after polishing of the backend, see below). Some notes about current implementation: it's not ideal. I see some bugs with dependency tracking (maybe we need to improve common code used for all distros, don't sure). Also it lacks support of multi-package PKGBUILD's and repos with not official-like structure. See TODO for more information [3]. Code is still located in my personal repo on gitorious (I think it's not ready yet to be merged with opensuse offcial repo) [4]. If you have any questions, suggestions or anything else — feel free to contact me. [1] https://gitorious.org/opensuse/sat-solver [2] https://gitorious.org/opensuse/build-service [3] https://gitorious.org/~madgnu/opensuse/madgnu-archlinux-build/blobs/master/… [4] https://gitorious.org/~madgnu/opensuse/madgnu-archlinux-build PS: I want to say *big thanks* to my mentor, Michael Schröder, and also to Sascha Peilicke and Adrian Schröter. -- wbr, Nikolay -- 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] prjconf data available to source services
by Troy Telford 24 Aug '11

24 Aug '11

I'm trying to write a set of source services that are similar to what already exist, but with one change: I want to be able to pull data from an obs project conf. (that way I can use essentially the same package/_service for multiple versions of the same program). Use case: I have a project "foo", for which all of the packages in it use source services to download their source from git. I want to be able to have a subproject "foo:version". I'd like to be able to define the source service such that I can define the revision (an/or versions) in the project config file. (ie. osc meta prjconf --edit foo). I can easily achieve this if I can use the data in the prjconf: $osc meta prjconf foo Macros: %scm_branch master %scm_version dev $osc meta prjconf foo:version Macros: %scm_branch 3.4 %scm_version 3.4 And it can be queried using: $(osc meta prjconf <active project> | grep '%scm_branch' | awk '{print $2}') But, here, I have a few questions: - Can 'osc' be executed from a source service? - If it can, what user does it run as? - How is it authenticated to OBS? - Is it possible to query the data without authenticating? (ie. a curl/wget command to the api, for example). Finally: Is this even necessary? Is there a way I can just access the prjconf from a source service? Thanks -- Troy Telford -- 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] webui: repository switch flag for build, publish ... problem
by Christian 24 Aug '11

24 Aug '11

Hi, you can only switch flag "ONE" time. then there is no "on mouse over event" anymore and you can't switch another. You need to reload complete page (Ctrl+F5). This is anoying :( Could this please be fixed ? Cheer -- Christian --------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de --------------------------------------------------- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

Re: [opensuse-buildservice] prjconf not working as expected
by Ann Davis 24 Aug '11

24 Aug '11

Hi, >>> On 8/24/2011 at 03:40 AM, in message <20110824094044.GA7770(a)suse.de>, Michael Schroeder <mls(a)suse.de> wrote: > On Tue, Aug 23, 2011 at 06:12:11PM -0600, Troy Telford wrote: >> I've been trying to figure this one out: I have my own instance of OBS, >> and have the following line in my prjconf (for CentOS 6) >> >> Required: redhat-rpm-config > > That should work. > >> I realize the official ones on build.opensuse.org use: >> Substitute: python python redhat-rpm-config > > Which means that it only gets added if "python" is BuildRequired. > >> My question is why "Required: redhat-rpm-config" doesn't work - when >> the buildroot is finished, and the RPM is about to start, I get the >> following error: > > Maybe some other package obsoletes it, when you look at the build log, > does it get installed? I also have my own instance w/ a CentOS 6 repo. I modifed the prjconf to add "Required: redhat-rpm-config" and comment out "Substitute: python python redhat-rpm-config". My package still builds fine. Regards, Ann > > Cheers, > Michael. -- 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] prjconf not working as expected
by Troy Telford 24 Aug '11

24 Aug '11

I've been trying to figure this one out: I have my own instance of OBS, and have the following line in my prjconf (for CentOS 6) Required: redhat-rpm-config I realize the official ones on build.opensuse.org use: Substitute: python python redhat-rpm-config My question is why "Required: redhat-rpm-config" doesn't work - when the buildroot is finished, and the RPM is about to start, I get the following error: ----------------------------------------------------------------- ----- building cpower.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://n009.americas.sgi.com/home:bhaxo/CentOS_6.0/562eecc211d1eabc044dca86e…' /home/abuild/rpmbuild/SOURCES/cpower.spec error: Failed build dependencies: redhat-rpm-config is needed by cpower-2.5-sgi.cl6.1.1.noarch Thanks. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1