May 2011 - openSUSE Packaging - openSUSE Mailing Lists

Re: [opensuse-packaging] linker error - need help
by Philipp Thomas 28 May '11

28 May '11

On Sat, 28 May 2011 06:50:53 +0400, Ilya Chernykh <anixxsus(a)gmail.com> wrote: >still fails for older openSUSE releases: You can't have accepted my SR (from psmt) as otherwise you would have -lsqlite in that command line. Philipp -- 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] linker error - need help
by Ilya Chernykh 28 May '11

28 May '11

I have a package that fails at the link stage, reporting undefined references as follows, and the --no-as-needed option does not help :( /bin/sh ../libtool --silent --tag=CXX --mode=link g++ -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -L/opt/kde3/lib64 -L/usr/lib/qt3/lib64 -L/usr/lib64 -Wl,--no-as-needed -Wl,--enable-new-dtags -L../src/fs -Wl,-Bsymbolic-functions -o ktagebuch main.o -lkio library/ui/libktagebuchui.la library/libktagebuch.la -lfilesystem -lkdeui -lkdecore /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_exec' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_column_text' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_bind_blob' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_step' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_open' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_column_bytes' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_column_blob' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_prepare' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_close' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_mprintf' /usr/src/packages/BUILD/ktagebuch-0.74/src/fs/.libs/libfilesystem.so: undefined reference to `sqlite3_errmsg' build log link: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=ktage… -- 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] -devel package name constrained by shlib package name
by Atri 27 May '11

27 May '11

Hi! I am trying to package [1] the scientific visualisation and data plotting software Plplot. The intention is to push it to a devel project and then to Factory by the next Milestone. However, I am facing a few problems with the naming policy to be adhered to for the shared-library and *-devel sub-packages provided by plplot. I have gone through the guidelines for shared library package names [2] and have tried to strictly adhere to it (because I want this package to end up in factory later). However, this has lead to several sub-packages having awful names such as:- 1. libplplotqtd0 : provides the shared library libplplotqtd.so.0 (I have no problem with this name, though Fedora uses the prettier name plplot-qt for this) 2. plplotqtd-devel : -devel package that depends on the libplplotqtd0 shared library alone and thus apparently has to have such a name (otherwise RPMLint complains). If I wanted to name this package as plplot-qt-devel instead, would this be possible, without violating the guidelines? (Fedora uses plplot-qt-devel, and I think that's a better name for this package) Similarly for the sub-package plplottcltk-devel, which depends on the shlib libplplottcltk9.so.9. While I have no problem with the shlib package names themselves (as these packages will invariably be installed as dependencies and not by an user), to name the devel packages in accordance with the shlib package makes the name look awful and difficult for a user to search for the package. I would expect a user to search for the package plplot-qt-devel when he/she wants the qt development files for plplot. If someone could tell me if it possible for the -devel package depending on a single shlib package to have a different name instead of following the shlib package name closely, without getting rpmlint to throw warnings, it would be a big help. Thanks, and bye -- Atri [1] https://build.opensuse.org/package/show?package=plplot&project=home:badshah… [2] http://en.opensuse.org/openSUSE:Shared_library_packaging_policy -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] python 2.7.1
by Sascha Manns 27 May '11

27 May '11

Hello Mates, actual we have python 2.7 checked in into the repos. Sadly the new calibre needs python 2.7.1 (atm it isn't compatible with any 3.x version). So i just would like to ask, if anyone can update this package. Have a nice weekend Sascha -- Sincerely Yours Sascha Manns open-slx Community & Support Agent openSUSE Membership Comitee openSUSE Marketing Team Web: http://saigkill.homelinux.net German Community Portal: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 4

[opensuse-packaging] Preblem building against boost
by Ilya Chernykh 27 May '11

27 May '11

I receive the following error message: /usr/include/boost/filesystem/v2/operations.hpp:534:14: error: 'unnamed_Path' was not declared in this scope I wonder how it happens that the file included with boost has undeclared references? -- 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] What prevents this SR from being accepted?
by Ilya Chernykh 26 May '11

26 May '11

Hi! I want to know what prevents this submit request from being accepted? https://build.opensuse.org/request/show/66899 It has been submitted to 11.4:Uptade:Test already 6 weeks ago and still no response. It fixes this issue: https://bugzilla.novell.com/show_bug.cgi?id=686786 which is very critical for all KDE3 users. It is even more strange that the sr has been accepted to Factory but still is not accepted to 11.4:Update:Testing. As a temporary measure we included the fixed package in our KDE3 repository(and changed the dependencies accordingly) but this is not how the things should be as the package is not KDE3-specific. We received 100%-positive feedback on this fix. So how much we have to wait now? Until 11.5 is out? It seems some other requests in 11.4:Update:Test are waiting even longer, for two months and more. -- 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] Package does not build for 32-bit
by Ilya Chernykh 25 May '11

25 May '11

A package builds well for 64-bit architecture, but fails for 32-bit one with the following output: kallery.cpp:198:64: error: invalid conversion from 'long unsigned int*' to 'size_t*' What should I do to make it build well for both architectures? The package link: https://build.opensuse.org/package/show?package=kallery&project=home%3AAnsu… -- 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] Right usage of libexecdir?
by Vincent Untz 25 May '11

25 May '11

Hey, Dominique and I are currently wondering what to do wrt libexecdir for evolution-data-server. Should we leave it unchanged (so files will be in /usr/lib) or should we change it to /usr/lib/evolution-data-server? If the latter, is there any reason this is not done automatically? Also, hrm, would rpmlint have ways to warn about packages that put binaries in libdir instead of libexecdir? (I can find a few of them here with a grep) 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

6 9

[opensuse-packaging] Rpm-4.9.0 is in Factory
by Michael Schroeder 24 May '11

24 May '11

Hi Packagers, I've spent the last week to upgrade rpm from 4.8.0 to 4.9.0. The package was submitted to Factory yesterday and is already checked in. Besides some bug fixes and an update to a newer BerkeleyDB library rpm-4.9.0 contains plugin architecture for dependency generation. In older rpms, the internal dependency generator was pretty much hardcoded in C, so we always used the old external one to generate dependencies. With rpm-4.9.0, the internal generator has become flexible enough so that we can use it. This means for you, that rpm will no longer use the %__find_provides and %__find_requires macros. Some packages redefined those macros to be able to filter the generated dependencies. This will no longer work in rpm-4.9.0. Instead, support for dependency filtering was added to rpm. You can now use %define %__requires_exclude_from ^/foo.*bar to tell rpm to ignore files matching the regexp when generating requires (the $RPM_BUILD_ROOT is already stripped). You can use %define %__requires_exclude libfoo.* to remove a generated dependency. The same is possible for %__provides_ and %__supplements_. As the generator definitions are now pluggable, I'll migrate them from the rpm package into the corresponding packages in the next days, i.e. the mono plugin definition into the mono package. Have fun with rpm-4.9.0, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- 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] branding packages ?
by Nelson Marques 24 May '11

24 May '11

Hi all, I'm currently finishing the packaging of unity-2d and need to a small branding package (so that we have the icon of openSUSE and not the one of Ubuntu). Anyone can point documentation for this, or the best procedures to make this happen? NM -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4