January 2011 - openSUSE Packaging - openSUSE Mailing Lists

Re: [opensuse-packaging] Illegal char '~' in python-pyside specfile
by Carlos Gonçalves 28 Jan '11

28 Jan '11

On Thu, Jan 27, 2011 at 10:54 AM, Frederic Crozat <fcrozat(a)novell.com> wrote: > Le jeudi 27 janvier 2011 à 10:13 +0000, Carlos Gonçalves a écrit : >> Hi all, >> >> I'm maintaining PySide packages in home:cgoncalves:pyside:shiboken and >> am struggling to figure out why the heck builds on openSUSE >=11.3 and >> SLE11 fail due to an error in python-pyside specfile: "error: line >> 191: Illegal char '~' in: - initial package (version 0.3.0)". Any >> suggestions? >> >> I've the same kind of specfile for >> home:cgoncalves:pyside:shiboken/shiboken (which is also similar to >> python-pyside's), but builds don't fail there. > > This requires a rpm patch we don't have in openSUSE : > > http://rpm.org/ticket/56 Then how did shiboken manage to be built successfully? It also contains tildes. Thanks, Carlos Gonçalves -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 1

[opensuse-packaging] recent security breaches of open-source sites
by Thomas Biege 28 Jan '11

28 Jan '11

Dear community members and contributors, in the last few month we saw security breaches at gnu.org[1], at sourceforge.net[2] and at fedora[3]. Even if it is believed that the integrity of the hosted projects was not affected I want to take the opportunity to remind you to always verify the cryptographic checksums of downloaded archive files, review patches and keep a healthy relationship/communication to the upstream authors. It is good practise to change your password from time to time and make it hard to guess[4][5]. Take extra care using public wifi hotspots, crowded places[6], like trains, and other peoples computer etc. Cheers, Thomas [1] http://blog.sucuri.net/2010/11/savannah-gnu-org-hacked-and-currently-offlin… [2] http://sourceforge.net/apps/wordpress/sourceforge/2011/01/27/service-downti… [3] http://lists.fedoraproject.org/pipermail/announce/2011-January/002911.html [4] http://en.wikipedia.org/wiki/Password_strength [5] http://sourceforge.net/projects/pwgen/ [6] http://en.wikipedia.org/wiki/Shoulder_surfing_%28computer_security%29 -- Thomas Biege <thomas(a)suse.de>, SUSE LINUX, Security Support & Auditing SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- Wer aufhoert besser werden zu wollen, hoert auf gut zu sein. -- Marie von Ebner-Eschenbach -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] OpenNebula
by Jaime Melis 27 Jan '11

27 Jan '11

Hello, I'm an OpenNebula [1] developer, and we would like to include OpenNebula in mainstream openSUSE. OpenNebula has already been accepted in Debian sid and in Ubuntu. Is there anyone interested in becoming the package maintainer for this project? We already have a working spec file so there's no need to start from scratch. The main challenge I see it that OpenNebula depends on xmlrpc-c libraries which aren't directly available on openSUSE. Nevertheless these packages are provided by the hamradio project [2], in particular packages: xmlrpc-c and libxmlrpc-c-devel. Regards, Jaime Melis [1] http://www.opennebula.org [2] https://build.opensuse.org/project/show?project=hamradio -- Jaime Melis, Cloud Technology Engineer/Researcher DSA Research Group: web http://dsa-research.org and blog http://blog.dsa-research.org OpenNebula Open Source Toolkit for Cloud Computing: http://www.OpenNebula.org -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 8

[opensuse-packaging] Creating server:php:applications:pear and moving pear packages there?
by Ralf Lang 27 Jan '11

27 Jan '11

Hi packagers, are there any objections to moving pear packages (which are quite a lot) from server:php:applications to a new sub project server:php:applications:pear ? -- Ralf Lang Linux Consultant / Developer B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 6

[opensuse-packaging] Illegal char '~' in python-pyside specfile
by Carlos Gonçalves 27 Jan '11

27 Jan '11

Hi all, I'm maintaining PySide packages in home:cgoncalves:pyside:shiboken and am struggling to figure out why the heck builds on openSUSE >=11.3 and SLE11 fail due to an error in python-pyside specfile: "error: line 191: Illegal char '~' in: - initial package (version 0.3.0)". Any suggestions? I've the same kind of specfile for home:cgoncalves:pyside:shiboken/shiboken (which is also similar to python-pyside's), but builds don't fail there. Cheers, Carlos Gonçalves -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Virtualization:Cloud re-org
by Robert Schweikert 27 Jan '11

27 Jan '11

Hi, As we add more cloud fabric packages the Virtualization:Cloud was getting a bit crowded and confusing. Therefore, I created three sub-projects: Virtualization:Cloud:Eucalyptus Virtualization:Cloud:OpenNebula Virtualization:Cloud:OpenStack Each of the sub-projects contains the packages for the named cloud fabric. Packages that are shared between 2 or more cloud fabrics are maintained in Virtualization:Cloud. Just started on Virtualization:Cloud:OpenStack today, thus this will take a while to be ready. 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-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] Help needed - resolving ambiguity
by Robert Schweikert 26 Jan '11

26 Jan '11

Hi, I've linked python-nose and python-tempita into Virtualization:CLoud:OpenStack from devel:languages:python as these are needed to build one of the OpenStack components. Now I get the following message: unresolvable: have choice for python-setuptools needed by python-nose: python-distribute python-setuptools, have choice for python-setuptools needed by python-tempita: python-distribute python-setuptools How do I break this ambiguity? 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-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4

[opensuse-packaging] Help with stupid link error
by Robert Schweikert 26 Jan '11

26 Jan '11

Hi, Working on packaging OpenStack as part of my Hackweek 6 endeavor. Nova (one part of OpenStack) needs a newer version of redis than is available in OBS, thus I am sticking a copy into Virtualization:Cloud:OpenStack for now. I have run into a stupid link error that makes no sense to me, thus help is much appreciated. /usr/src/packages/BUILD/redis-2.0.4/redis.c:9293: undefined reference to `log' The math library is on the link line: cc -o redis-server -std=c99 -pedantic -O2 -Wall -W -fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -lm -pthread -fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -rdynamic -ggdb adlist.o ae.o anet.o dict.o redis.o sds.o zmalloc.o lzf_c.o lzf_d.o pqsort.o zipmap.o sha1.o This happens when building locally and in the build service. A log file can be found here: https://build.opensuse.org/package/live_build_log?arch=i586&package=redis&p… The offending source line is: return (double)age*log(1+asize); don't see anything wrong wit that. This produces -> nm -Bg /var/tmp/build-root/usr/src/packages/BUILD/redis-2.0.4/redis.o | grep log U log in the object file and of course: -> nm -Bg /var/tmp/build-root//lib64/libm.so.6 | grep log 000000000001a520 T __clog10 0000000000027ca0 T __clog10f 0000000000030410 T __clog10l 0000000000019020 W clog 000000000001a520 W clog10 0000000000027ca0 W clog10f 0000000000030410 W clog10l 00000000000263c0 W clogf 000000000002eb50 W clogl 0000000000010670 W ilogb 000000000001fb20 W ilogbf 000000000002c140 W ilogbl 0000000000014230 W log 00000000000146c0 W log10 0000000000022fb0 W log10f 000000000002d5e0 W log10l 0000000000010720 W log1p 000000000001fb90 W log1pf 000000000002c170 W log1pl 000000000001aaa0 W log2 0000000000028100 W log2f 00000000000307b0 W log2l 0000000000010ad0 W logb 000000000001feb0 W logbf 000000000002c1b0 W logbl 0000000000022bf0 W logf 000000000002d530 W logl shows that log is defined in the math library. As a weak symbol, but never the less that should be good enough at link time. Help is much 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-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

[opensuse-packaging] Need help for Unity with cmake
by Nelson Marques 23 Jan '11

23 Jan '11

Hi, Compiz is one of the packages[1] I needed to redo for Unity due to a so called 'glib main loop' branch. This package requires a couple of patches from Ubuntu in order to build the unity window decorator. The cmake installer resulting from this patches isn't working properly. >From the log[2] it seems that it's trying to install the unity decorator ignoring the DESTDIR prefix. I need to fix this. Anyone could point some good examples or tutorials that can help on this issue? NM [1] - https://build.opensuse.org/package/show?package=compiz&project=home:ketheri… [2] - https://build.opensuse.org/package/live_build_log?arch=i586&package=compiz&… -- nelson marques nmo.marques(a)gmail.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4

[opensuse-packaging] Looking for help and advice
by Nelson Marques 21 Jan '11

21 Jan '11

Dear all, As I'm giving the last steps before start polishing the packaging on the packages required for Unity and Ayatana Indicators, I have some doubts regarding mono, gtk-sharp packaging and package splitting. This package, libappindicator[1] does provide an example for all the other cases where I need to act. Could anyone please take a look into it and check if it's properly splitted and make some advice on it for the bad things? From this example I should be able to workout all the other packages in the same condition, so I can start cleaning up and polishing. Also any interesting documentation on openSUSE mono packaging will be most welcome. [1] - https://build.opensuse.org/package/show?package=libappindicator&project=hom… Thanks in advance, NM -- nelson marques nmo.marques(a)gmail.com -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3