October 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] openSUSE 10.3 runs out of maintenance
by Adrian Schröter 21 Feb '12

21 Feb '12

Hello, is usual, openeSUSE 10.3 runs out of maintenance and I will remove all repos building against it in OBS. openSUSE:10.3 project has been moved to DISCONTINUED: namespace as announced a while ago. bye 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

2 2

[opensuse-buildservice] Installing on Mandriva via OBS repo
by Nicholas Peterson 20 Oct '11

20 Oct '11

Hi All, I am trying to install my program on Mandriva but can't seem to add the OBS repository. It seems that the command urpmi.addmedia doesn't work with the normal RPM PM. Someone on IRC mentioned that I could specify a different type for the repository in my OBS raw config to automatically generate a urpmi compatible repo. What do I put as the type for my Mandriva repo to make it urpmi compatible? Thanks, Nick -- Nick Peterson Programmer @ Siepel Lab Cell: (480) 600-2544 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

7 31

Re: [opensuse-buildservice] compiler flags issue on openSUSE 11.2 (gcc4.4.1) and factory
by Di Pe 18 Oct '11

18 Oct '11

OK, did that but halts before it can finish the configure. Is there another way to access the logs? an alternative solution would be: ln -s /usr/include/et/com_err.h /usr/include/com_err.h that's how I got it to work on my own box. But I could not do that in the build service because I was getting permission denied errors. Thanks # # %configure # cat config.log # %{__make} %{?_smp_mflags} # # %install # #%{__rm} -rf %{buildroot} #not needed # %{__make} DESTDIR=%{buildroot} install # Using BUILD_ROOT=/abuild/root_8/.mount Using BUILD_ARCH=x86_64:i686:i586:i486:i386 Doing xen build in /dev/abuild/8_root build22 started "build msktutil.spec" at Fri Apr 16 22:36:06 UTC 2010. Building msktutil for project 'home:dipe' repository 'openSUSE_11.2' arch 'x86_64' srcmd5 'b92ec11f13803a767e9d68f94555f1b4' processing specfile /abuild/root_8/.build-srcdir/msktutil.spec ... running changelog2spec --target rpm --file /abuild/root_8/.build-srcdir/msktutil.spec init_buildsystem --cachedir /var/cache/build --prepare --clean --rpmlist /abuild/root_8/.build.rpmlist /abuild/root_8/.build-srcdir/msktutil.spec build rpmlint-Factory ... preinstalling aaa_base... preinstalling acl... preinstalling attr... preinstalling bash... preinstalling coreutils... preinstalling diffutils... preinstalling filesystem... preinstalling fillup... preinstalling glibc... preinstalling grep... preinstalling insserv... preinstalling libacl... preinstalling libattr... preinstalling libbz2-1... preinstalling libgcc44... preinstalling libxcrypt... preinstalling m4... preinstalling libncurses5... preinstalling pam... preinstalling permissions... preinstalling libreadline6... preinstalling rpm... preinstalling sed... preinstalling tar... preinstalling zlib... preinstalling libselinux1... preinstalling liblzma0... preinstalling libcap2... preinstalling libpcre0... preinstalling libpopt0... preinstalling libelf1... preinstalling liblua5_1... preinstalling util-linux... preinstalling perl-base... preinstalling libdb-4_5... preinstalling libsepol1... preinstalling libblkid1... preinstalling libuuid1... copying packages... reordering...done booting XEN kernel ... xm create -c /var/run/bsworker_8/build/xen.conf name=build:8_root memory=750 disk=phy:/dev/abuild/8_root,hda1,w disk=phy:/dev/abuild/8_swap,hda2,w extra=quiet init=/.build/build panic=1 console=ttyS0 Using config file "/var/run/bsworker_8/build/xen.conf". Started domain build:8_root PCI: Fatal: No config space access function found i8042.c: No controller found. doing fast boot FATAL: Module ext4 not found. Creating device nodes with udev Boot logging started on /dev/xvc0(/dev/console) at Fri Apr 16 22:36:29 2010 Waiting for device /dev/hda1 to appear: ok fsck 1.41.1 (01-Sep-2008) [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda1 /dev/hda1: clean, 2561/1826816 files, 185686/7296000 blocks fsck succeeded. Mounting root device read-only. Mounting root /dev/hda1 mount -o ro,defaults -t ext3 /dev/hda1 /root mount: can't find /root/proc in /etc/fstab or /etc/mtab 2nd stage started in virtual machine machine type: x86_64 swapon on /dev/hda2 swapon: /dev/hda2: found swap v1 signature string for 4 KiB PAGE_SIZE swapon: /dev/hda2: pagesize=4096, swapsize=2097152000, devsize=2097152000 mount: none already mounted or //proc busy mount: according to mtab, none is already mounted on /proc logging output to //.build.log... processing specfile /.build-srcdir/msktutil.spec ... init_buildsystem --cachedir /var/cache/build --repository zypp:// /.build-srcdir/msktutil.spec build rpmlint-Factory ... running aaa_base preinstall script running aaa_base postinstall script Updating etc/sysconfig/language... Updating etc/sysconfig/backup... Updating etc/sysconfig/boot... Updating etc/sysconfig/kernel... Updating etc/sysconfig/suseconfig... Updating etc/sysconfig/clock... Updating etc/sysconfig/proxy... Updating etc/sysconfig/windowmanager... Updating etc/sysconfig/sysctl... Updating etc/sysconfig/cron... Updating etc/sysconfig/news... Updating etc/sysconfig/shutdown... Updating etc/passwd...unchanged Updating etc/group...unchanged Updating etc/shadow...new initializing rpm db... installing filesystem-11.2-12.2 installing pcre-7.9.0-2.3.1 installing terminfo-base-5.6-91.2 installing glibc-2.10.1-10.4 installing audit-libs-1.7.13-4.2 installing fillup-1.42-245.3 installing gdbm-1.8.3-373.7 installing glibc-locale-2.10.1-10.4 installing keyutils-libs-1.2-109.2 installing libattr-2.4.44-2.2 installing libbz2-1-1.0.5-36.6 installing libcap2-2.16-4.2 installing libdb-4_5-4.5.20-98.4 installing libelf1-0.142-3.7 installing libgmp3-4.3.1-2.2 installing libltdl7-2.2.6-47.7 installing liblua5_1-5.1.4-6.2 installing liblzma0-4.999.9beta-2.2 installing libpopt0-1.13-4.2 installing libselinux1-2.0.80-5.2 installing libsepol1-2.0.36-2.2 installing libxcrypt-3.0.2-3.2 installing net-tools-1.60-734.1 installing patch-2.5.9.122-2.1 installing perl-base-5.10.0-72.5 installing zlib-1.2.3-140.2 installing libncurses5-5.6-91.2 installing libpcre0-7.9.0-2.3.1 installing attr-2.4.44-2.2 installing file-5.03-2.2 installing libacl-2.2.48-2.2 installing libreadline6-6.0-18.3 installing libzio-0.99-3.2 installing perl-5.10.0-72.5 installing acl-2.2.48-2.2 installing bash-4.0-18.3 installing build-compare-2009.10.14-2.2.3 installing brp-check-suse-1.0-23.2 installing build-2009.09.23-2.2 installing insserv-1.13.0-2.2 installing libcom_err2-1.41.9-3.1 installing libgcc44-4.4.1_20090817-2.3.4 installing libgomp44-4.4.1_20090817-2.3.4 installing libuuid1-2.16-4.5.1 installing bzip2-1.0.5-36.6 installing cracklib-2.8.13-2.2 installing libmpfr1-2.4.1-3.2 installing libopenssl0_9_8-0.9.8k-3.4 installing less-436-3.2 installing info-4.13a-3.2 installing libcom_err-devel-1.41.9-3.1 installing cpio-2.10-4.2 installing diffutils-2.8.7-145.2 installing findutils-4.4.0-46.2 installing gawk-3.1.6-26.2 installing gzip-1.3.12-100.4 installing libblkid1-2.16-4.5.1 installing libstdc++44-4.4.1_20090817-2.3.4 installing libtool-2.2.6-47.7 installing m4-1.4.13-2.2 installing make-3.81-130.2 installing sed-4.1.5-130.2 installing tar-1.21-4.2 installing binutils-2.19.51-10.26.4 installing grep-2.5.4-4.2 installing texinfo-4.13a-3.2 installing pam-1.1.0-3.2 installing login-3.40-2.1 installing autoconf-2.63-5.2 installing libgmpxx4-4.3.1-2.2 installing gettext-runtime-0.17-65.2 installing coreutils-7.1-3.2 installing linux-kernel-headers-2.6.31-3.4 post linux-kernel-headers-2.6.31-3.4 /var/tmp/rpm-tmp.w3dgsM 1 installing automake-1.11-6.2 installing sysvinit-2.86-215.2 installing timezone-2009p-1.1.1 WARNING: Not updating /etc/localtime with new zone file installing libppl7-0.10.2-5.2 installing cvs-1.12.12-155.2 installing cyrus-sasl-2.1.23-3.1 installing krb5-1.7-6.1 installing psmisc-22.7-8.2 installing groff-1.18.1.1-172.173.2 Updating etc/sysconfig/suseconfig... installing libldap-2_4-2-2.4.17-5.3 installing glibc-devel-2.10.1-10.4 installing gettext-tools-0.17-65.2 installing libppl_c2-0.10.2-5.2 installing man-2.5.2-22.2 Updating etc/sysconfig/cron... installing aaa_base-11.2-43.45.1 Updating etc/sysconfig/language... Updating etc/sysconfig/backup... Updating etc/sysconfig/boot... Updating etc/sysconfig/kernel... Updating etc/sysconfig/suseconfig... Updating etc/sysconfig/clock... Updating etc/sysconfig/proxy... Updating etc/sysconfig/windowmanager... Updating etc/sysconfig/sysctl... Updating etc/sysconfig/cron... Updating etc/sysconfig/news... Updating etc/sysconfig/shutdown... Updating etc/passwd...unchanged Updating etc/group...unchanged Updating etc/shadow...unchanged installing cyrus-sasl-devel-2.1.23-3.1 installing keyutils-devel-1.2-109.2 installing libbz2-devel-1.0.5-36.6 installing libstdc++44-devel-4.4.1_20090817-2.3.4 installing zlib-devel-1.2.3-140.2 installing libcloog0-0.15.7+ppl-2.2 installing netcfg-11.1-2.2 warning: /etc/HOSTNAME created as /etc/HOSTNAME.rpmnew installing permissions-2009.10.07.1653-2.1 Updating etc/sysconfig/security... installing libopenssl-devel-0.9.8k-3.4 installing krb5-devel-1.7-6.1 installing post-build-checks-1.0-66.1 installing cpp44-4.4.1_20090817-2.3.4 installing pam-modules-11.2-4.1 installing util-linux-2.16-4.5.1 installing rpm-4.7.1-6.7.3 Updating etc/sysconfig/services... installing cpp-4.4-4.2 installing openldap2-devel-2.4.17-5.3 installing rpmlint-mini-1.0-219.3 installing gcc44-4.4.1_20090817-2.3.4 installing rpmlint-Factory-1.0-51.1 installing gcc-4.4-4.2 installing gcc44-c++-4.4.1_20090817-2.3.4 installing gcc-c++-4.4-4.2 removing nis flags from //etc/nsswitch.conf... now finalizing build dir... Starting SuSEconfig, the SuSE Configuration Tool... Running in full featured mode. Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.groff... Executing /sbin/conf.d/SuSEconfig.permissions... Finished. ----------------------------------------------------------------- I have the following modifications for msktutil.spec: 4c4 < Release: 1 --- > Release: 43.1 ----------------------------------------------------------------- ----- building msktutil.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/home:dipe/openSUSE_11.2/b92ec11f13803a767e9d68f945…' /usr/src/packages/SOURCES/msktutil.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.vXH1X7 + umask 022 + cd /usr/src/packages/BUILD + cd /usr/src/packages/BUILD + rm -rf msktutil-0.4 + /usr/bin/bzip2 -dc /usr/src/packages/SOURCES/msktutil-0.4.tar.bz2 + /bin/tar -xvvf - /bin/tar: Record size = 8 blocks drwxr-xr-x jknight/jknight 0 2010-03-16 05:12 msktutil-0.4/ -rw-r--r-- jknight/jknight 6323 2010-03-16 05:12 msktutil-0.4/msktconf.cpp -rw-r--r-- jknight/jknight 10736 2010-03-16 05:12 msktutil-0.4/msktkrb5.cpp -rw-r--r-- jknight/jknight 5470 2010-03-16 05:12 msktutil-0.4/krb5wrap.h -rw-r--r-- jknight/jknight 18011 2010-03-16 05:12 msktutil-0.4/LICENSE -rw-r--r-- jknight/jknight 1894 2010-03-16 05:12 msktutil-0.4/README -rwxr-xr-x jknight/jknight 152439 2010-03-16 05:12 msktutil-0.4/configure -rw-r--r-- jknight/jknight 10414 2010-03-16 05:12 msktutil-0.4/msktutil.interactive -rw-r--r-- jknight/jknight 3274 2010-03-16 05:12 msktutil-0.4/configure.in drwxr-xr-x jknight/jknight 0 2010-03-16 05:12 msktutil-0.4/debian/ -rw-r--r-- jknight/jknight 648 2010-03-16 05:12 msktutil-0.4/debian/control -rwxr-xr-x jknight/jknight 2178 2010-03-16 05:12 msktutil-0.4/debian/rules -rw-r--r-- jknight/jknight 2009 2010-03-16 05:12 msktutil-0.4/debian/changelog -rw-r--r-- jknight/jknight 651 2010-03-16 05:12 msktutil-0.4/debian/postinst -rw-r--r-- jknight/jknight 340 2010-03-16 05:12 msktutil-0.4/debian/cron-daily.sh -rw-r--r-- jknight/jknight 643 2010-03-16 05:12 msktutil-0.4/debian/copyright -rw-r--r-- jknight/jknight 1197 2010-03-16 05:12 msktutil-0.4/Makefile.in -rw-r--r-- jknight/jknight 5931 2010-03-16 05:12 msktutil-0.4/msktname.cpp -rw-r--r-- jknight/jknight 25907 2010-03-16 05:12 msktutil-0.4/msktutil.cpp -rw-r--r-- jknight/jknight 2403 2010-03-16 05:12 msktutil-0.4/config.h.in -rw-r--r-- jknight/jknight 27478 2010-03-16 05:12 msktutil-0.4/msktldap.cpp -rw-r--r-- jknight/jknight 12406 2010-03-16 05:12 msktutil-0.4/msktutil.M -rw-r--r-- jknight/jknight 9043 2010-03-16 05:12 msktutil-0.4/msktutil.h -rw-r--r-- jknight/jknight 1330 2010-03-16 05:12 msktutil-0.4/INSTALL -rw-r--r-- jknight/jknight 2978 2010-03-16 05:12 msktutil-0.4/ChangeLog -rw-r--r-- jknight/jknight 7846 2010-03-16 05:12 msktutil-0.4/msktpass.cpp -rw-r--r-- jknight/jknight 6816 2010-03-16 05:12 msktutil-0.4/krb5wrap.cpp + STATUS=0 + '[' 0 -ne 0 ']' + cd msktutil-0.4 + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.eZpFOg + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /usr/src/packages/BUILDROOT/msktutil-0.4-43.1.x86_64 ++ dirname /usr/src/packages/BUILDROOT/msktutil-0.4-43.1.x86_64 + /bin/mkdir -p /usr/src/packages/BUILDROOT + /bin/mkdir /usr/src/packages/BUILDROOT/msktutil-0.4-43.1.x86_64 + cd msktutil-0.4 + CXXFLAGS=' -I/usr/include/et' + export CXXFLAGS + RPM_OPT_FLAGS='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -I/usr/include/et' + export RPM_OPT_FLAGS + CFLAGS='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables' + export CFLAGS + CXXFLAGS=' -I/usr/include/et' + export CXXFLAGS + FFLAGS='-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables' + export FFLAGS + ./configure --host=x86_64-unknown-linux-gnu --build=x86_64-unknown-linux-gnu --target=x86_64-suse-linux --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/lib --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info checking for x86_64-unknown-linux-gnu-g++... no checking for x86_64-unknown-linux-gnu-c++... no checking for x86_64-unknown-linux-gnu-gpp... no checking for x86_64-unknown-linux-gnu-aCC... no checking for x86_64-unknown-linux-gnu-CC... no checking for x86_64-unknown-linux-gnu-cxx... no checking for x86_64-unknown-linux-gnu-cc++... no checking for x86_64-unknown-linux-gnu-cl.exe... no checking for x86_64-unknown-linux-gnu-FCC... no checking for x86_64-unknown-linux-gnu-KCC... no checking for x86_64-unknown-linux-gnu-RCC... no checking for x86_64-unknown-linux-gnu-xlC_r... no checking for x86_64-unknown-linux-gnu-xlC... no checking for g++... g++ checking for C++ compiler default output file name... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for install... /usr/bin/install checking for cat... /bin/cat checking for rm... /bin/rm checking for cp... /bin/cp checking for echo... /bin/echo checking for sed... /usr/bin/sed checking for mkdir... /bin/mkdir checking how to run the C++ preprocessor... g++ -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking krb5.h usability... yes checking krb5.h presence... yes checking for krb5.h... yes checking com_err.h usability... yes checking com_err.h presence... no configure: WARNING: com_err.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: com_err.h: proceeding with the compiler's result checking for com_err.h... yes checking heim_err.h usability... no checking heim_err.h presence... no checking for heim_err.h... no checking heimdal/heim_err.h usability... no checking heimdal/heim_err.h presence... no checking for heimdal/heim_err.h... no checking sasl.h usability... no checking sasl.h presence... no checking for sasl.h... no checking sasl/sasl.h usability... yes checking sasl/sasl.h presence... yes checking for sasl/sasl.h... yes checking for krb5_init_context in -lkrb5... yes checking for ldap_initialize in -lldap... yes checking whether com_err.h needs extern "C"... configure: error: Couldn't get error_message to work. error: Bad exit status from /var/tmp/rpm-tmp.eZpFOg (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.eZpFOg (%build) System halted. On Fri, Apr 16, 2010 at 1:52 PM, Marcus Meissner <meissner(a)suse.de> wrote: > On Fri, Apr 16, 2010 at 08:19:22AM -0700, Di Pe wrote: >> ran it again but still the same error, >> >> any other ideas? > > Can you add a > cat config.log > > after the configure and mail me the full log? > > Ciao, Marcus > -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] Prefer vs Support vs Keep vs Substitute
by Jon Nelson 22 Mar '11

22 Mar '11

What is the difference between Support and Keep? Like, let's say I have a package FOO that I'd like to always be installed in the build environment, *if* it is available. If it is not available, block all other builds until it *is* available, but do not block FOO itself. How do I do that? Is there a way to configure a project with more than one repository with different configurations (such as, when using repo A, substitute foo for bar)? -- Jon -- 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] tar_scm blocked in "source update running"
by Cristian Morales Vega 01 Feb '11

01 Feb '11

dolphin-emu from home:RedDwarf:NonFree, that uses the new tar_scm source service, has been in "source update running" for more than an hour. Also, at least the tar_scm version I have installed from openSUSE:Tools seems to have a typo that makes --filename not work. Where it says FILE="$FILENAME" VERSION="$MYVERSION" it should say FILE="$MYFILENAME" VERSION="$MYVERSION" I would create a SR, but not sure what/where is upstream/devel project for the source services. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 12

[opensuse-buildservice] [PATCH] Notifications do not support multiple action requests
by Islam Amer 04 Dec '10

04 Dec '10

Hello, I was trying out multiple actions in one request and noticed that the notifications contain only the last action. I looked at the code and found this in /usr/lib/obs/server/BSNotify.pm line 82 : # FIXME: how to handle multiple actions in one request here ? # right now the last one just wins .... So here's a proposed fix : add an actions key in the reqinfo hash, that contains an ordered list of hashes that contain the details of the actions. The Data::Dumper of reqinfo produced by the attached patch looks like this : $VAR1 = { 'when' => '2010-09-30T00:12:13', 'actions' => [ { 'sourcerevision' => '1', 'sourceproject' => 'Foo:Devel:Personal', 'deletepackage' => undef, 'targetproject' => 'Foo:Trunk', 'sourcepackage' => 'libfoo', 'type' => 'submit', 'targetpackage' => 'libfoo', 'deleteproject' => undef }, { 'sourcerevision' => '1', 'sourceproject' => 'Foo:Devel:Personal', 'deletepackage' => undef, 'targetproject' => 'Foo:Trunk', 'sourcepackage' => 'bar', 'type' => 'submit', 'targetpackage' => 'bar', 'deleteproject' => undef } ], 'author' => 'bob', 'description' => 'Test', 'state' => 'new', 'comment' => undef, 'who' => 'bob', 'sender' => 'bob', 'id' => 32, 'type' => '' }; Is this change acceptable ? If so, I guess the notification plugins will have to be changed to accommodate this. Thanks, Islam Amer

3 7

[opensuse-buildservice] [PATCH] distinguish between local and worker builds
by Anas Nashif 29 Nov '10

29 Nov '10

Hi, Here is a tiny patch that define a macro when packages are built inside OBS so that special packages built locally can be treated differently. Anas diff --git a/src/backend/bs_worker b/src/backend/bs_worker index 948dd0b..2bbc838 100755 --- a/src/backend/bs_worker +++ b/src/backend/bs_worker @@ -1431,6 +1431,7 @@ sub dobuild { push @args, '--oldpackages', $oldpkgdir if $oldpkgdir && -d $oldpkgdir; push @args, '--norootforbuild' unless $BSConfig::norootexceptions && grep {"$projid/$packid" =~ /^$_$/} keys %$BSConfig::norootexceptions; push @args, '--baselibs-internal'; + push @args, '--define', "running_in_obs 1"; push @args, '--lint'; push @args, '--dist', "$buildroot/.build.config"; push @args, '--rpmlist', "$buildroot/.build.rpmlist";-- 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] ISO files and distributions
by Troy Telford 16 Nov '10

16 Nov '10

When building ISO images using kiwi, I have a question: It seems that I have no problems building ISO images for SUSE base distros (no surprise there). However, if I try to build an ISO image using something else (CentOS seems to be my example...), I get an unresolvable error: nothing provides kiwi, nothing provides kiwi-packagesmanager:instsource. So... does the ISO building in OBS require those package compiled for the target distribution? Or is kiwi independant of the OS the ISO image is being built for? -- Troy Telford -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 6

[opensuse-buildservice] openSUSE Build Service 2.1 Release
by Andreas Jaeger 08 Nov '10

08 Nov '10

The openSUSE Build Service - OBS - is now officially at release 2.1. We're delighted with the improvements in this release, including an enhanced web interface, integration with online code management systems and better access controls. OBS 2.1 Introduces New Features =========================== Enhanced web user interface This iteration has enhanced the web user interface of openSUSE Build Service with features that were previously only in the osc command line client. It now allows submitting of packages to other projects, showing a history of changes and who did them, with associated comments. This means that the full work flow needed to build packages, contribute them to projects and collaborate on them is available from the web interface. Integration with online source code management tools Users of the Build Service may now access a new concept called 'source services'. Source services allow, for example, the automatic checkout of source code for a package from a remote server via Git or Subversion, building a tar ball from these checked out sources, and using them for building a package. It also enables direct download of tar balls from remote sites. This allows packagers to work with external sources without downloading them to their own workstations, and makes it easy to rebuild packages after upstream changes with a single click. Better access controls The access controls have been enhanced so that read/write access to a project can be granted on an individual basis. This allows for tighter control of work flows where needed. You can for example ensure people don't have access to security updates while they are being tested. Using OBS ========= To use the Open Source Build Service, you can access the public instance on build.opensuse.org or install it on your own hardware to have a private Build Service. For local installations you can install from source, or use the ready-to-run appliance image, either directly or in a virtual machine. You can also obtain an installation image to install an openSUSE 11.3 system with the Build Service pre-installed. For details check http://en.opensuse.org/openSUSE:Build_Service_installations For more information about the Build Service, check http://en.opensuse.org/Portal:Build_Service. Thanks ====== This release of the OBS has received many contributions from other companies, community members and foundations, making this release a truly collaborative product. We would like to thank everyone who helped make the openSUSE Build Service 2.1 possible! Special thanks go to Martin Mohring and the OBS team at The Linux Foundation, who contributed the extended access handling. About the Build Service ================== The Build Service is an open package and distribution development platform providing a transparent infrastructure for developers to build packages for a variety of Linux distributions and hardware architectures. build.opensuse.org is a freely available service and can build packages for the most popular distributions besides openSUSE including SUSE Linux Enterprise, Debian, Fedora, Mandriva, Red Hat Enterprise Linux and Ubuntu. The Build Service aims to significantly reduce the costs and risks related to the distribution of applications, from building, providing and maintaining them. It does so by providing a convenient web and command-line interface, which developers can use to upload their code and build instructions. The Build Service will then create a clean, virtualized operating system, install any required build dependencies and create the package. This process will be repeated for each supported operating system. Once the build is finished, all packages will be made available in a set of repositories for easy distribution. The Build Service at build.opensuse.org currently builds about 100,000 packages from 25,000 users working on 15,000 different projects. Communities and companies using their own Build Service installation include the MeeGo Project, VLC team, Dell, Cray and many others. For more information about the Build Service, check http://en.opensuse.org/Portal:Build_Service. -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

7 10

[opensuse-buildservice] Ubuntu 10.10 Repository on build.opensuse.org
by Fritz Elfert 08 Nov '10

08 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Just a shot question: Are there any plans to add Ubuntu 10.10 to the list of available repositories? Thanks in advance -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMuQ83boM4mAMyprARAu2fAJ9/bfyJ237nm5kkcvokxwvEmNvpXwCeOYGl 6GTQd2EOxM5QTfx+P821JfM= =jHOs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 8

[opensuse-buildservice] I can't access my build service account who do I contact?
by Dave Plater 01 Nov '10

01 Nov '10

Hi, I get this message if I try to login to my build service projects :- OBS Web Interface Error: Permission denied The account that is logged into the system lacks proper permissions to perform the operation. Please contact the openSUSE admin to get proper permissions for the user account. Error Details: Errorcode: 403 Message: <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http Who can fix it, I can login to everything else. Thanks Dave Plater -- 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] CentOS:CentOS-5 prjconf
by Matwey V. Kornilov 31 Oct '10

31 Oct '10

Hi, I do have an assumption that line %kernel_module_package_buildreqs kernel-devel redhat-rpm-config is missed in Macros section of prjconf of CentOS:CentOS-5. Can someone fix it or explain me where I am wrong? -- 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] [api] [patch] RFC changes for model and exception for flag access in DbProject
by dl9pf＠gmx.de 29 Oct '10

29 Oct '10

Hi ! Early & often ... thus here're my current thoughts on how to start with the access flag in DbProject model. Feedback welcome ! Best, Jan-Simon -- 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] OBS 2.1.1 released
by Adrian Schröter 29 Oct '10

29 Oct '10

We just released OBS 2.1.1 maintenance und security fix release. Users of OBS 2.1.0 should update ASAP due to a critical security issue. OBS 2.0 and before is not affected by this. Apart from this we have also a number of bugfixes, find details below. Special thanks go to Vivian Zhang from Intel and David Greaves for their contributions to this release. It got released to the ususal places: Appliance: http://en.opensuse.org/openSUSE:Build_Service_Appliance Packages: http://download.opensuse.org/repositories/openSUSE:/Tools/ Git: http://www.gitorious.org/opensuse/build-service/commits/2.1 Changes: ======== * Default build target list got updated * Support for filtering user base when using LDAP database for authentification * LDAP support enforces the usage of SSL for authentification now for security reasons Bugfixes: ========= * api got fixes which allowed a cross side scripting attack to change a users password, if he is logged in and clicked on a crafted URL elsewhere. (Affected only OBS 2.1.0) * api handles request state "revoked" also as final state now * webui received multiple layout fixes and improvements esp. when handling sources. * webui is CC'ng now all bugowners if multiple are defined (#513167) * source service daemon has been fixed to support long running processes * worker code download is honoring proxy settings now (#630994) -- 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] OBS, MeeGo and the social desktop : Application information, feedback and rating
by David Greaves 28 Oct '10

28 Oct '10

This is more of an initial exploration than a concrete proposal :) I'll post this to both the opensuse-buildservice(a)opensuse.org and meego-dev(a)meego.com lists. MeeGo is going to be using the Open Collaboration Services (OCS) API. http://www.socialdesktop.org/ocs/ http://www.freedesktop.org/wiki/Specifications/open-collaboration-services One of the features of this is to provide feedback and ratings from the device/desktop to the application development team. MeeGo's community OBS will be used for developers to manage their applications and I was interested in the concept of using the OBS API to support this. The api already provides some rating services so it seems to fit in somewhere. https://api.obs.maemo.org/apidocs/#107 As I say, the use-case is something around providing feedback from the application launcher on the device; maybe an on-device popup that allows a star rating, comment etc that is linked back to the appropriate OBS package and team. So.... does this fit with the intended usage around the 'rating' type services already in the OBS? David cc'ed Bergie as he's not subscribed. -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- 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 packages through the API - Help?
by Dan Leinir Turthra Jensen 28 Oct '10

28 Oct '10

Hi! You may have heard of this funny little thing called Project Bretzn, which Frank Karlitschek announced at the openSuse conference last week[1]. I'm one of the people working on the connecting-the-dots bit for it, and as the subject hints at, I have now run into what seems like a bit of a problem: I cannot find any functions to actually create a new package using the web API. I can interact with existing ones perfectly fine (storing new information into _meta), but creating new ones seems to be missing. Can someone help me out here? I further assume that the same problem exists for creating sub-projects, and as such would like to request assistance with this as well - this is less important, but would be greatly appreciated if it is possible. In short, what i would like to request is: Pointers to which functions i will need to call to create a new package, and to create new sub-projects. Thank you in advance for your help! :) [1] For those who don't: http://news.opensuse.org/2010/10/26/from-the- developer-to-the-user-and-back-announcing-project-bretzn/ :) -- ..Dan // Leinir.. http://leinir.dk/ Co- existence or no existence - Piet Hein -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] Confusion
by Robert Schweikert 28 Oct '10

28 Oct '10

Hi, I am attempting to build a new package (and maybe this is really a packaging question) and now have an example that has hit on a rather long standing confusion of mine. Never having had a good example I was amiss of being able to properly formulate my lack of understanding (this is I believe a build-service question). I am trying to build euca2ools, which is implemented in Python and requires boto and m2crypto. M2crypto is found in the standard distribution, thus that does not pose a problem. However, boto (available as python-boto) is only found in the devel:languages:python project. Now, I can certainly make my project dependent on devel:languages:python and get what I need. That part I understand. However, what happens if/when I want to submit my work to the project. How do things end up in the right place, and where would for example Eucalyptus end up? Further, how would this dependency on devel:languages:python be resolved? Why would a package that is part of devel:langauges:ANYTHING not be part of the :standard project? Come to think of it, I do have another example. A while back I submitted perlcritic and it's dependent packages to the project and things are in devel:languages:perl. I made the assumption that from there it would eventually propagate up the tree and just be available in the distribution. However, as I just checked it is not. As far as I understand things, a devel project/repo is subject to have version changes at pretty much any given time. Thus, I am wondering why packages would not be in a more static place. I suppose this is where Contrib might come into play, however, how would we then separate packages from devel:languages:ANYTHING and put some of those into :contrib and others into :standard? For example what makes perl-razor-agents a special package to be part of :standard while a person wanting perlcritic would have to add devel:languages:perl as a repo. (Just using perlcritic as an example, not because I feel neglected but because it is easy for me to illustrate my confusion). Clarification is appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Software Engineer Consultant LINUX rschweikert(a)novell.com 781-464-8147 Novell Making IT Work As One -- 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] 1hour Scheduled Outage of build and mirror.opensuse.org
by Lars Vogdt 27 Oct '10

27 Oct '10

Hi openSUSE Users Tomorrow, Thu 28th from 09:00 AM CET to approx. 10:00 AM CET, we need some maintenance on the following hosts: http://build.opensuse.org http://software.opensuse.org http://widehat.opensuse.org/ http://tube.opensuse.org/ Apologies for inconveniencies this may cause. Please contact admin(a)opensuse.org with any queries. Your openSUSE Admins -- 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] passwords in /mounts/rdadm/Passwords
by Berthold Gunreben 27 Oct '10

27 Oct '10

Hi, I just created a suggestion how we could store the information about our current passwords. Please have a look at /mounts/rdadm/Passwords/MAP Berthold -- ------------------------------------------------------------------ Berthold Gunreben SUSE Linux GmbH -- Build Service mailto:bg@suse.de Maxfeldstr. 5 http://www.suse.de/ D-90409 Nuernberg, Germany SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- 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] "No Data" in obs 2.1 /monitor
by Carsten Hoeger 27 Oct '10

27 Oct '10

Hi, since I did an update from 2.0 to 2.1, all images in /monitor are showing "No Data". This is not critical but ugly. Any idea, what could be the reason? -- With best regards, Carsten Hoeger

1 0

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 26 Oct '10

26 Oct '10

present: speilicke, coolo, tschmidt, cwh, lrupp, bg, adrian Topics: ======= * Driver Build Status * OBS deployment * OBS 2.1.1 General reflection of openSUSE conference. Driver Build Status =================== cwh explained source service for kiwi DuD generation. He currently consideres to store package lists data in a seperate file with own format beside the source service file. OBS deployment ============== Discussion about our current deployment strategies and possible improvements. No defined result yet. OBS 2.1.1 ========= We have the need for a 2.1.1 release next week. A candidate should be ready end of this week. -- 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] bug in set_version service
by Jon Nelson 26 Oct '10

26 Oct '10

I noticed a bug in the set_version service. If the destination file is a specfile, then the file gets overwritten /twice/ - once with the new version, and once with 'Release: 0' which throws out the first (version) change. Here is my recommended fix: if [ "${FILE%.spec}" != "$FILE" ]; then # set release back to zero after version upgrade, will be increased by OBS during build sed -e "s,^Release:.*,Release: 0," -e "s,^Version:.*,Version: $MYVERSION," "$FILE" > "$MYOUTDIR/$FILE" || exit 1 else sed -e "s,^Version:.*,Version: $MYVERSION," "$FILE" > "$MYOUTDIR/$FILE" || exit 1 fi I generally prefer to see '-e' used whenever possible. -- Jon -- 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] Ubuntu 10.10 and our general approach for debian based chroots
by Stephan Kleine 25 Oct '10

25 Oct '10

Hi, I just looked at the 10.10 chroot and it doesn't start because procps can't run "start procps" in its post install script because it can't connect to Upstart (obviously). The problem, and its apparent solution, is documented in their release notes at https://wiki.ubuntu.com/MaverickMeerkat/ReleaseNotes - search for "Upstart jobs cannot be run in a chroot." Basically one just has to symlink /sbin/initctl to /bin/true but I have no idea how to inject custom commands into the chroot setup so I leave that to you. Also, regarding our general approach for creating debian based chroots: Why don't we simply use "debootstrap"? At least that is what the Ubuntu people wondered and, after giving it a try, I'm wondering too. It is a simple bash script (so the extracted debian package "just works" or it could easily get repackaged into a rpm) that takes the distro, architecture and wanted variant (minimal, with build tools, ...) as arguments and then automatically sets up a working chroot. So, how about we change the approach for debian based systems and simply use their debootstrap to create the initial chroot and then just install the dependencies of the to be build package afterwards? Besides being very easy to use and actually working (e.g. it already contains a fix / workaround for the change that is screwing us over with upstart on 10.10) it would also remove the "joy" to debug the stuff every few months when a new debian based thingy gets imported? Thoughts? regards, Stephan FWIW http://www.pastie.org/1245252 shows the output of creating a minbase chroot with debootstrap on 11.2 -- 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] OBS 2.1: Status of SuperH (sh4) support with QEMU
by Martin Mohring 24 Oct '10

24 Oct '10

Hi, with QEMU User Mode improving, we can now catch a couple of embedded architectures with OBS. The newest one in the family being SH4: http://lizards.opensuse.org/2010/10/24/obs-2-1-status-of-superh-sh4-support… Also, I had fixed the virtual machine builds (KVM, XEN should also work) if mixed with QEMU User mode for all the archs. This means now: we can do ARM, MIPS 32, PowerPC 32 and finally SH4 with OBS inside an emulator Martin OBS Maintainer -- 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] Workflow suggestions for working with nightly builds and full releases
by Matt Williams 21 Oct '10

21 Oct '10

Hi all, I'm hoping to get some suggestions from you guys about how to best handle a bunch of packages I'm maintaining. Basically I have a number of packages (the Falcon programming language, some extra modules and some tools). What I would like to do is have a OBS project (falcon:Unstable -- all under my home:Milliams personal project) where I build nightly versions of the packages, then I would also like to have a second project (home:Milliams:falcon) where I build only the officially released packages. Is there any way in which I can ease this cycle since on the whole, the spec files in the two projects will be almost identical. Can I perhaps maintain one as the main project and have the other one link against it with patches applied to change the version and the tarball? I will probably use the new 'source service' technique for the Unstable repo to fetch snapshots from Git and maybe for the release repo to to get the tarballs directly from the release website. Thanks in advance for any help you can provide, Matt Williams -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1