August 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] usage of osc ls
by Kai-Uwe Behrmann 30 Aug '10

30 Aug '10

I would like to see all package names in a given distribution. Listing e.g. $ osc ls Mandriva:2009.1 -r standard gives no output. Even so I expected there is some. $ osc ls Mandriva:2009.1 -r standard -b | grep lcms lists several lcms packages but not lcms-devel. However lcms-devel is exactly used in BuildRequirements of the mandriva section of my spec files. Am I missing something essential? kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org -- 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] --prefer-pkgs option for osc build
by Zhang, Vivian 30 Aug '10

30 Aug '10

Hi, all I tried to use -prefer-pkgs options for osc build but failed: #osc build -p /var/tmp/buildcheck-atk/RPM --no-verify --clean standard i586 at-spi.spec Scanning the following dirs for local packages: /var/tmp/buildcheck-atk/RPM Getting buildinfo from server and store to /var/tmp/buildcheck-atk/Trunk:Testing/at-spi/.osc/_buildinfo-standard-i586.xml Server returned an error: HTTP Error 400: Bad Request Remote error: Can't use an undefined value as a HASH reference at build/Build.pm line 392. I checked the code and found that issue might be the wrong build_descr_data. if opts.prefer_pkgs: print 'Scanning the following dirs for local packages: %s' % ', '.join(opts.prefer_pkgs) prefer_pkgs, cpio = get_prefer_pkgs(opts.prefer_pkgs, arch, build_type) cpio.add(os.path.basename(build_descr), build_descr_data) build_descr_data = cpio.get() #print build_descr_data 07070100000000000081A400000000000000000000000000000000000002E3000000000000000000000000000000000000000500000000depsR:atk.i586-0/0/0: /sbin/ldconfig /sbin/ldconfig /sbin/ldconfig /sbin/ldconfig glib2 >= 2.0.0 libatk-1.0.so.0 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libglib-2.0.so.0 libgobject-2.0.so.0 libpthread.so.0 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 P:atk.i586-0/0/0: libatk-1.0.so.0 atk = 1.30.0-10.1 atk(x86-32) = 1.30.0-10.1 R:atk-devel.i586-0/0/0: /usr/bin/pkg-config atk = 1.30.0-10.1 glib2-devel >= 2.0.0 libatk-1.0.so.0 pkgconfig(gobject-2.0) rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(VersionedDependencies) <= 3.0.3-1 P:atk-devel.i586-0/0/0: pkgconfig(atk) = 1.30.0 atk-devel = 1.30.0-10.1 atk-devel(x86-32) = 1.30.0-10.107070100000000000081A40000000000000000000000000000000000001110000000000000000000000000000000000000000C00000000at-spi.spec%{!?python_sitearch: %define python_sitearch %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib(1)")} %define atk_version 1.29.2 %define gtk2_version 2.10.0 %define gail_version 1.9.0 %define libbonobo_version 2.4.0 %define orbit2_version 2.6.0 %define pango_version 1.2.0 Summary: Assistive Technology Service Provider Interface Name: at-spi Version: 1.30.0 Release: 1 URL: http://developer.gnome.org/projects/gap/ Source0: http://download.gnome.org/sources/at-spi/1.30/%{name}-%{version}.tar.bz2 License: LGPLv2+ Group: System/Libraries BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) ...... ...... %files python %defattr(-,root,root) %{python_sitearch}/pyatspi/ 07070100000000000081A40000000000000000000000000000000000000000000000000000000000000000000000000000000B00000000TRAILER!!! Then I make a workaround to comment out these two lines and it works ok. #cpio.add(os.path.basename(build_descr), build_descr_data) #build_descr_data = cpio.get() Does the output of build_descr_data above is expected and is it safe to comment out the code to not adding/checking the deps info Thanks vivian

4 6

[opensuse-buildservice] Admin password
by Matwey V. Kornilov 30 Aug '10

30 Aug '10

Hi, I forgot admin password for my local obs instance. How to change or reset it? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] expandpackages issue when using build tool locally
by Zhang, Vivian 29 Aug '10

29 Aug '10

Hi, I tried to use build tool (build -repo=xxxxx xxx.src.rpm) locally and found a issue . The source rpm package can be built successfully on the OBS but fail with build tool locally (the config file is the as the OBS server). I checked the issue and found the generated rpmlist is different with the server. The local build tool missed some build dependencies. Has anyone met this issue and any diff between these two methods to get the rpmlist for initializing build environment? Thanks vivian

1 0

[opensuse-buildservice] Error with buildservice twhen building patched Nautilus
by Valerio Mariani 27 Aug '10

27 Aug '10

Dear All, I have been trying to build a version on Nautilus-Elementary for OpenSuse, starting fromt he Mandriva packages available here: http://suse-art.org/content/show.php/Nautilus-Elementary+Mandriva+RPM?conte… Basically, I took the normal spec file of the SuSe nautilus package and added the lementary patch from the Mdv rpm (with almost no modifications). The resulting rpm builds and works perfectly on my system. However, when I tried to build the packages with the build service I get this error: E: nautilus 64bit-portability-issue nautilus-mime-actions.c:1480 SysRq : Power Off Power down. Now, my programming skills re not bad, but not so advanced. The problem lies in this function: void launch_gnome_app_install_mimetype(GdkScreen *screen, NautilusFile *file, char *uri) { char *qmimetype, *quri, *qduri, *command; if (!screen) screen = gdk_display_get_default_screen(gdk_display_get_default ()); qmimetype = g_shell_quote (nautilus_file_info_get_mime_type (file)); quri = g_shell_quote (uri); command = g_strconcat("gnome-app-install --mime-type=", qmimetype, " ", quri, (char*)0 /* NB NULL is wrong */); g_free (qmimetype); g_free (quri); g_free (qduri); //eel_gnome_shell_execute_on_screen (command, screen); gdk_spawn_command_line_on_screen (screen, command, NULL); g_free (command); } This line is causing the error: qmimetype = g_shell_quote (nautilus_file_info_get_mime_type (file)); Can someone please help me to debug it? Or at least explain to me the nature of the error? My goal is to create an OBS repo for the elementary stuff, and this is one of the last packages that I must build. BTW would there really be an interest in such a repository? I am doing it mainly for myself but I would feel encouraged if others are interested. Thanks in advance Valerio -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

Re: [opensuse-buildservice] Mandriva versions
by Oliver Burger 27 Aug '10

27 Aug '10

> > okay, I have briefly checked contrib and non-free and they contain stuff > > which is on our blacklist (due to license problems, patent problems and > > copyright issues). > > Hmm, contrib and main are similar, the only difference is level of > support from Mandriva. I thought so as well. Not having non-free is o.k., there are hardly any things we need to build against in it. Just some kernel modules and some proprietary software, no libs. Not having contrib makes obs unusable for building a lot of packages. And: as well as main, contrib does not contain any non-OSS packages, so I don't know, where you do find license problems. Oliver PS.: Hi Fred, nice to read you again -- MandrivaUser.de - die deutsche Mandriva-Community Oliver Burger MandrivaUser.de - RPM-Team Mandriva - German i18n group -- 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] Mandriva versions
by Oliver Burger 27 Aug '10

27 Aug '10

Hi there, on FrOSCon I was talking to some openSUse guys about the possibility to use the obs as build system for the German Mandriva community. Now "playing arround" a bit brought several items to my attention. On some places in the buildservice I found the Mandriva versions 2009.1 and 2010. Which 2010 release is this? 2010.0 or 2010.1? And why are there not both? The second thing I wonder is which branches of the Mandriva repos are included? All three? main, contrib and non-free? Or just main? Is there a way to include additional repos like plf? (Mandriva's equivalent of packman, I think, don't know that much about packman) And last but not least. After building a package Mandriva's "genhdlist2" should be run on the repo to create the files needed by Mandriva's package management. Thanks for your answers, Oliver -- Do not meddle in the affairs of packagers 'cause they are subtle and quick to anger! Oliver Burger MandrivaUser.de - RPM-Team Mandriva - German i18n group -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 9

[opensuse-buildservice] "OSError: Can's access the keyring now"
by Satoru Matsumoto 27 Aug '10

27 Aug '10

I've installed osc from openSUSE:/Tools and followed the instructions. http://en.opensuse.org/openSUSE:Build_Service_Tutorial#Step_One_-_Login_and… But when I executed 'osc checkout home:MY_USERNAME', I got the following error messages: ====================================================================== Your user account / password are not configured yet. You will be asked for them below, and they will be stored in /home/$USER/.oscrc for future use. Creating osc configuration file /home/$USER/.oscrc ... Username: MY_USERNAME Password: ******** Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/osc/babysitter.py", line 50, in run return prg.main() File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 300, in main self.postoptparse() File "/usr/lib/python2.6/site-packages/osc/commandline.py", line 127, in postoptparse conf.write_initial_config(e.file, config) File "/usr/lib/python2.6/site-packages/osc/conf.py", line 523, in write_initial_config keyring.set_password(host, config['user'], config['pass']) File "/usr/lib64/python2.6/site-packages/keyring/core.py", line 33, in set_password return _keyring_backend.set_password(service_name, username, password) File "/usr/lib64/python2.6/site-packages/keyring/backend.py", line 97, in set_password return self.keyring_impl.password_set(service, username, password) OSError: Can's access the keyring now > /usr/lib64/python2.6/site-packages/keyring/backend.py(97)set_password() -> return self.keyring_impl.password_set(service, username, password) (Pdb) ====================================================================== I've already created my HOME repo and built some packages via Web UI, and I'm using openSUSE 11.3 x86_64. How can I solve this problem ? -- _/_/ Satoru Matsumoto - openSUSE Member - Japan _/_/ _/_/ Marketing/Weekly News/openFATE Screening Team _/_/ _/_/ mail: helios_reds_at_gmx.net / irc: HeliosReds _/_/ _/_/ http://blog.zaq.ne.jp/opensuse/ _/_/ -- 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] new obs project - business - bugreport #634989
by Denny Beyer 27 Aug '10

27 Aug '10

Dear all, I would like to add a new project where business relevant software could be collected. This is mainly finance management, tax related software and online banking etc. Unfortunately, there are not a lot applications out there covering this area so we need to make those available even easier to access. One more thing: This could also be just a collection of links to other projects, so we don't duplicate work if those packages exist already in obs but still get the benefit of just having to add this repo only to get the software + updates. Any thoughts? cheers, /Denny -- 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 web interface / positioning of the link footer
by Thomas Spahni 26 Aug '10

26 Aug '10

Hi I hope anyone of the devs sees this here. Using seamonkey 1.1.19 to access the web interface for SUSE OBS. When in a project it displays the footer with the links and the sponsor to the right of the main content instead of below it. Firefox 3.5.11 shows the footer correctly below the contents. Thought I'd better report this. Regards, Tom -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2