May 2011 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] how to I cd to correct location after /bin/tar -xf -
by doiggl＠velocitynet.com.au 04 May '11

04 May '11

Hello How this error be fixed [1] ? Spec file at [2] Full Log at [3] It needs to cd to the correct location #cd CodeAnalyst-2_13_2_0156-Public instead of #cd: CodeAnalyst-2_13_2_0156-Public.tar.gz: No such file or directory Thanks Glenn [1] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.h2OzIK + umask 022 + cd /usr/src/packages/BUILD + cd /usr/src/packages/BUILD + rm -rf CodeAnalyst-2_13_2_0156-Public.tar.gz + /usr/bin/gzip -dc /usr/src/packages/SOURCES/CodeAnalyst-2_13_2_0156-Public.tar.gz + /bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd CodeAnalyst-2_13_2_0156-Public.tar.gz /var/tmp/rpm-tmp.h2OzIK: line 32: cd: CodeAnalyst-2_13_2_0156-Public.tar.gz: No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.h2OzIK (%prep) [2] spec file https://build.opensuse.org/package/view_file?file=CA-test.spec&package=CA-t… [3] log https://build.opensuse.org/package/live_build_log?arch=x86_64&package=CA-te… [4] content of CodeAnalyst-2_13_2_0156-Public/ # ls CodeAnalyst-2_13_2_0156-Public AUTHORS COPYING INSTALL Makefile.am README autogen.sh careport.sh debian m4 mkNda.sh samples CAInstaller.sh ChangeLog INSTALLATION NEWS RELEASENOTES ca_manual_install.sh configure.in doc mkInternal.sh mkPublic.sh src -- 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] Need help: sed scripts
by Nelson Marques 04 May '11

04 May '11

Good people, As some people are aware I'm trying to get Unity going and there's a few itches in which I need some help. I've been paying a lot of attention to the packaging done by Ubuntu and they are currently are using a sed script to change a few values, the file is included on here[1] and it's named "compiz-keybindings.sed". What would be the best way (without making patch) to use it on OBS/RPM spec to change the values? NM -- Nelson Marques /* As cicatrizes lembram-nos de onde estivemos, mas não ditam para onde vamos */ -- 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] enabled openSUSE_Factory in devel projects
by Stephan Kulow 03 May '11

03 May '11

Hi, As factory-auto will reject packages that are build disabled in devel projects, I wrote a little check and found 368 factory packages still (from initial devel project setup) in build disabled. Those I enabled for "openSUSE_Factory". In case this a problem in your project, you should seriously rethink the devel project of the packages. This is not meant to be static forever, if it does not make sense, change it, but for a devel project I see 0 use cases of build disabled against Factory. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Build failures because of GNOME 3, and how to fix them
by Vincent Untz 03 May '11

03 May '11

Hi all, GNOME 3 should reach Factory soon as it got pushed this morning. Since that's a big change, it will likely have some impact in terms of build failures, and create some new ones in Factory. Here are the common cases that should help you fix those issues. If you hit something else, don't hesitate to ask the GNOME team for help. Common causes for build failures ================================ a) Some devel packages got renamed Because we have both gtk2 and gtk3 versions of some libraries, some devel packages have been renamed. For example, what used to be gtksourceview-devel in 11.4 is now gtksourceview2-devel. Same for libunique-devel (now libunique1-devel), libwnck-devel (now libwnck2-devel), and more. The solution here is to move to pkgconfig() BuildRequires: the devel package renaming won't have an impact anymore. This is available since openSUSE 11.3, if I'm not mistaken. For instance, instead of using BuildRequires: gtksourceview-devel you would use: BuildRequires: pkgconfig(gtksourceview-2.0) gtksourceview-2.0 is the basename (without the .pc extension) of the pkg-config file provided by the library. b) configure fails, complaining about a library that cannot be found It's obviously hard to know what the exact issue is, but it's possible that you were relying on the fact that one of your BuildRequires was requiring a package that should have been in your BuildRequires (a direct dependency of your package). So it was working before, but that was a bit lucky. The solution here is to explicitly list all the build dependencies as BuildRequires, instead of relying on another package to bring them in (unless some well-known cases, like glibc-devel, or the glib2-devel/pkgconfig(glib-2.0) when you have GTK+ as BuildRequires, etc.) c) NetworkManager API changed With the move to NetworkManager 0.9, some API got changed. I'm not aware of any good guideline on how to fix this; I'd advise to check upstream in git/svn if there's a fix for this. Else, ping us. But that shouldn't affect too many packages, hopefully. d) libnotify API changed A few functions were removed, and an argument to notify_notification_new() was removed. The solution for this issue is not too hard. The first thing to do is to check upstream if a fix got committed already. Else, a patch can be easily written. An example can be found at: https://build.opensuse.org/stage/package/view_file?file=tsclient-libnotify0… e) Package tries to build a gnome-panel applet Because of the port to GTK+ 3 and D-Bus, the libpanel-applet API has changed, and some porting is needed. This is not a trivial task, although it's definitely doable. It's unclear to me how many packages outside of GNOME:Apps/GNOME:Factory are affected. Note that it can affect some python apps that need the gnomeapplet module (which isn't built anymore). There are several solutions: + look what upstream did in git/svn, and: - if they removed it, just stop building the applet - if they ported it, take the patch and apply it + if nothing is done, ping me so I know how many packages are affected. I might invest time in writing a compatibility layer if it turns out to be needed. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 6

[opensuse-packaging] RPMLINT warning: W: non-etc-or-var-file-marked-as-conffile /srv/www/htdocs/*
by Ralf Lang 02 May '11

02 May '11

Hi folks, while packaging horde4 I noticed the rpmlint warning horde4.noarch: W: non-etc-or-var-file-marked-as-conffile /srv/www/htdocs/horde4/config/conf.php.dist If config files are allowed to live in /var (where web apps used to live in old times) why are they not allowed in /srv ? -- 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

5 12

[opensuse-packaging] FTLibrary.h not in ftgl-devel
by Javier Llorente 01 May '11

01 May '11

Hi list-mates, I'm trying to compile OpenCASCADE 6.5.0 and I'm getting ../../../src/OpenGl/OpenGl_FontMgr.cxx:4:23: fatal error: FTLibrary.h: No such file or directory compilation terminated. OpenCASCADE.spec has "BuildRequires: ftgl-devel." I have seen that that package doesn't provide FTLibrary.h. Is it a packaging bug? Thanks, -- Javier Llorente

2 3