November 2012 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] systemd status in Factory : WAIT BEFORE UPGRADING TO CURRENT FACTORY
by Frederic Crozat 07 Nov '12

07 Nov '12

Hi all, as some people noticed, despite testing new systemd release in a Staging repository for some weeks, some bugs went into the upgrade. Those bugs are due to both systemd and udev being moved to /usr. What does it means for packagers : - systemd will continue to check its .service from /lib/systemd/system, in addition to /usr/lib/systemd/system (and /etc/systemd/system) but packagers should change their package to use the new location for Factory (an rpmlint rule to detect that will be enabled soon) - udev will only check /usr/lib/udev/rules.d. The udev package has been modified to migrate /lib/udev/ to /usr/lib/udev and replace /lib/udev by a symlink to /usr/lib/udev. So, packages installing rules in /lib/udev should still be ok but they should be fixed to use the new rules (I've fixed all known broken packages in Factory already). Again, an rpmlint rule for this will be enabled soon in Factory - RUN+="socket:..." rules are not longer supported by udev 195. The only remaining package using it is multipath and Hanne is fixing it. Current issues - filesystem upgrade: this one is still under investigation (fortunately, Robert has a VM exhibiting the bug so I'll be able to test this one). For M1, filesystem was reverted to its previous state and we'll see on re-doing the changes after M1 is out. - mkinitrd needed to be modified to correctly handle udev new path but unfortunately, I missed one directory in my patch to handle this. Fixed package should be pushed in Factory pretty soon. - udev was supposed to move /lib/udev to /usr/lib/udev but one test in the install script in udev package was wrong, which was preventing the /lib/udev move. This will be also fixed soon. Until all those issues are fixed (I'll sent a follow-up mail here), please DON'T UPGRADE YOUR FACTORY INSTALLATION. Thanks. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging]
by Cristian Morales Vega 05 Nov '12

05 Nov '12

The following packages have been failing to build on Factory for more than 30 days. This is a reminder for anybody that could be interested in any of them. Any package failing to build for more than 100 days will be dropped from openSUSE. - libgcj43 Fails for 277 days: undefined reference to `__cxa_call_unexpected' - elilo Fails for 92 days: undefined reference to `__stack_chk_fail_local' (New upstream version 3.14 available) - opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it - selinux-policy Fails for 74 days: error(s) encountered while parsing configuration (Different changes in devel project (since 6 months)) - libgcj41 Fails for 47 days: java test cases... - compiz Fails for 44 days: kwin changes - kdegraphics3 Fails for 42 days: gphoto update (Current sources were declined: request 138654) - xerces-j2-bootstrap Fails for 33 days: temporary failure - hawk Fails for 33 days: cannot load such file -- gettext/tools/rgettext (rails 2 vs rails 3?) - python-tagpy Fails for 33 days: taglib update - rubygem-webyast-time Fails for 31 days: Missing partial shared/online_help (Different changes in devel project (since 23 days)) - ccscript3 Fails for 30 days: undefined reference to `main' (Request 139531 to network:telephony) - iscsitarget Fails for 30 days: kernel 3.6 This is a test. Please give some feedback. Anything to improve? Did this email actually helped you? The email was sent BCC to the package maintainers I could identify. I couldn't identify one clear one for ccscript3 and sent it to the latest .changes entry. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 12

[opensuse-packaging] Packaging Policies - and how to change them: A proposal
by Andreas Jaeger 03 Nov '12

03 Nov '12

Looking at our packaging policies, I see nobody nobody currently taking care of it and no real process to change them and make those changes known. So, I'd like to propose the following: * Introduce a simple process for changing the policies, e.g.: - send an email to opensuse-packaging with a proposal for change - discuss change - if change gets accepted by packagers and reviewers: + update the wiki pages + send an email to opensuse-announce about the change (we can also collect a couple of smaller changes and only send this out once a while) * I suggest to form a small team that guides the process and decides if there is no consensus - and better formulates the process. Any better ideas? Who likes to join the team and help shaping the packaging policies? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 8

[opensuse-packaging] Help needed to figure out what is missing
by Togan Muftuoglu 03 Nov '12

03 Nov '12

Hi, For sometime I have been trying to get racket [1] to build and after a long fight I manage to get it building and working on openSUSE 12.1 and Factory but for some reason I can't figure out why it fails to build for openSUSE 12.2 Help is appreciated as I intent to submit it to devel:languages:misc and hopefully into factory Togan [1] <http://www.racket-lang.org/> -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 6

[opensuse-packaging] setting a system variable and compiler options
by Denny Beyer 03 Nov '12

03 Nov '12

Dear all, I could use some input for a progam I packaging at the moment, which requires two system variables to run. 1. path to binaries The documentation says, that /usr/local/program/bin/ needs to be in the PATH - variable. That shouldn't be needed, if those binaries are installed into "/usr/bin" by the package. If that doesn't work, I'll use links from "/usr/bin/" 2. path to libraries Looks like this is needed: MYLIBPATHVAR is required to point to the library of the program in "/usr/lib/program/lib/" or "/usr/share/program/lib/" How do I introduce a new system wide environment variable - available for all users? 3. Compiler options for optimization to improve the performance of the program, the compiler could get some performance settings like -O3 -mtune=corei7 -march=corei7 etc. to get the full capability for calculations (sse4.2). How does that effect the packaging? Do I need to splitt off a -SSE3/4 package and how does that work? Could somebody point me to some wiki page / sample package to see how to achieve that? You'll see the package in obs https://build.opensuse.org/package/show?package=radiance&project=home%3Alum… cheers, Denny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 4

[opensuse-packaging] libtorrent-rasterbar (0.16.5) examples fail to build with boost 1.49
by Mariusz Fik 03 Nov '12

03 Nov '12

Hi, I wanted to update libtorrent-rasterbar package in devel:libraries:c_c++. Libray is building fine but examples fail: [ 24s] Making all in examples [ 24s] make[1]: Entering directory `/home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples' [ 24s] g++ -DPACKAGE_NAME=\"libtorrent-rasterbar\" -DPACKAGE_TARNAME=\"libtorrent-rasterbar\" -DPACKAGE_VERSION=\"0.16.5\" -DPACKAGE_STRING=\"libtorrent-rasterbar\ 0.16.5\" -DPACKAGE_BUGREPORT=\"arvid(a)cs.umu.se\" -DPACKAGE_URL=\"http://www.libtorrent.org\" -DPACKAGE=\"libtorrent-rasterbar\" -DVERSION=\"0.16.5\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_PTHREAD=1 -DHAVE_BOOST=1 -DHAVE_BOOST_SYSTEM=1 -DHAVE_GETHOSTBYNAME=1 -DHAVE_GETHOSTBYNAME_R=1 -DGETHOSTBYNAME_R_RETURNS_INT=1 -DHAVE_LIBRT=1 -DNDEBUG=1 -DTORRENT_USE_OPENSSL=1 -DHAVE_PYTHON=\"2.7\" -DHAVE_BOOST_PYTHON=1 -DHAVE_LINUX_FIEMAP_H=1 -DBOOST_ASIO_HASH_MAP_BUCKETS=1021 -DBOOST_EXCEPTION_DISABLE=1 -DBOOST_ASIO_ENABLE_CANCELIO=1 -DBOOST_ASIO_DYN_LINK=1 -DTORRENT_BUILDING_SHARED=1 -I. -ftemplate-depth-50 -I../include -Os -I/usr/include -fmessage-length=0 -O2 - Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fvisibility=hidden -fno-strict-aliasing -fvisibility-inlines-hidden -c -o client_test.o client_test.cpp [ 24s] client_test.cpp: In function 'int main(int, char**)': [ 24s] client_test.cpp:1645:28: warning: ignoring return value of 'int scanf(const char*, ...)', declared with attribute warn_unused_result [-Wunused-result] [ 24s] client_test.cpp:1761:25: warning: ignoring return value of 'int scanf(const char*, ...)', declared with attribute warn_unused_result [-Wunused-result] [ 24s] /bin/sh ../libtool --tag=CXX --mode=link g++ -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fvisibility=hidden -fno-strict-aliasing -fvisibility-inlines-hidden -lboost_system-mt -L/usr/lib64 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -lrt -o client_test client_test.o ../src/libtorrent-rasterbar.la -lGeoIP -lrt -lpthread [ 24s] libtool: link: g++ -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fvisibility=hidden -fno-strict-aliasing -fvisibility-inlines-hidden -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -o .libs/client_test client_test.o -L/usr/lib64 ../src/.libs/libtorrent-rasterbar.so -lboost_system-mt -lssl -lcrypto -lGeoIP -lrt -lpthread -Wl,-rpath -Wl,/usr/lib64 [ 25s] client_test.o: In function `libtorrent::block_info::peer() const': [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/../include/libtorrent/torrent_handle.hpp:120: undefined reference to `boost::asio::ip::address_v4::address_v4(boost::array<unsigned char, 4ul> const&)' [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/../include/libtorrent/torrent_handle.hpp:120: undefined reference to `boost::asio::ip::address::address(boost::asio::ip::address_v4 const&)' [ 25s] client_test.o: In function `basic_endpoint': [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:91: undefined reference to `boost::asio::ip::detail::endpoint::endpoint(boost::asio::ip::address const&, unsigned short)' [ 25s] client_test.o: In function `libtorrent::block_info::peer() const': [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/../include/libtorrent/torrent_handle.hpp:117: undefined reference to `boost::asio::ip::address_v6::address_v6(boost::array<unsigned char, 16ul> const&, unsigned long)' [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/../include/libtorrent/torrent_handle.hpp:117: undefined reference to `boost::asio::ip::address::address(boost::asio::ip::address_v6 const&)' [ 25s] client_test.o: In function `basic_endpoint': [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:91: undefined reference to `boost::asio::ip::detail::endpoint::endpoint(boost::asio::ip::address const&, unsigned short)' [ 25s] client_test.o: In function `handle_alert(libtorrent::session&, libtorrent::alert*, std::multimap<std::string, libtorrent::torrent_handle, std::less<std::string>, std::allocator<std::pair<std::string const, libtorrent::torrent_handle> > >&, std::set<libtorrent::torrent_handle, std::less<libtorrent::torrent_handle>, std::allocator<libtorrent::torrent_handle> >&, int*, boost::unordered::unordered_set<libtorrent::torrent_status, boost::hash<libtorrent::torrent_status>, std::equal_to<libtorrent::torrent_status>, std::allocator<libtorrent::torrent_status> >&, std::vector<libtorrent::torrent_status const*, std::allocator<libtorrent::torrent_status const*> >&, bool&)': [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/client_test.cpp:949: undefined reference to `boost::asio::ip::address::from_string(char const*, boost::system::error_code&)' [ 25s] client_test.o: In function `basic_endpoint': [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:91: undefined reference to `boost::asio::ip::detail::endpoint::endpoint(boost::asio::ip::address const&, unsigned short)' [ 25s] client_test.o: In function `operator==': [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:193: undefined reference to `boost::asio::ip::detail::operator==(boost::asio::ip::detail::endpoint const&, boost::asio::ip::detail::endpoint const&)' [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:193: undefined reference to `boost::asio::ip::detail::operator==(boost::asio::ip::detail::endpoint const&, boost::asio::ip::detail::endpoint const&)' [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:193: undefined reference to `boost::asio::ip::detail::operator==(boost::asio::ip::detail::endpoint const&, boost::asio::ip::detail::endpoint const&)' [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:193: undefined reference to `boost::asio::ip::detail::operator==(boost::asio::ip::detail::endpoint const&, boost::asio::ip::detail::endpoint const&)' [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:193: undefined reference to `boost::asio::ip::detail::operator==(boost::asio::ip::detail::endpoint const&, boost::asio::ip::detail::endpoint const&)' [ 25s] client_test.o: In function `boost::asio::ip::basic_endpoint<boost::asio::ip::tcp>::address() const': [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:180: undefined reference to `boost::asio::ip::detail::endpoint::address() const' [ 25s] /usr/include/boost/asio/ip/basic_endpoint.hpp:180: undefined reference to `boost::asio::ip::detail::endpoint::address() const' [ 25s] client_test.o: In function `main': [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/client_test.cpp:1343: undefined reference to `boost::asio::ip::address::address(boost::asio::ip::address_v4 const&)' [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/client_test.cpp:1343: undefined reference to `boost::asio::ip::address::address(boost::asio::ip::address_v4 const&)' [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/client_test.cpp:1339: undefined reference to `boost::asio::ip::address_v4::address_v4(unsigned long)' [ 25s] /home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples/client_test.cpp:1340: undefined reference to `boost::asio::ip::address_v4::address_v4(unsigned long)' [ 25s] client_test.o: In function `__static_initialization_and_destruction_0': [ 25s] /usr/include/boost/asio/error.hpp:247: undefined reference to `boost::asio::error::get_netdb_category()' [ 25s] /usr/include/boost/asio/error.hpp:249: undefined reference to `boost::asio::error::get_addrinfo_category()' [ 25s] /usr/include/boost/asio/error.hpp:251: undefined reference to `boost::asio::error::get_misc_category()' [ 25s] client_test.o: In function `posix_tss_ptr': [ 25s] /usr/include/boost/asio/detail/posix_tss_ptr.hpp:42: undefined reference to `boost::asio::detail::posix_tss_ptr_create(unsigned int&)' [ 25s] collect2: error: ld returned 1 exit status [ 25s] make[1]: *** [client_test] Error 1 [ 25s] make[1]: Leaving directory `/home/abuild/rpmbuild/BUILD/libtorrent-rasterbar-0.16.5/examples' [ 25s] make: *** [all-recursive] Error 1 [ 25s] error: Bad exit status from /var/tmp/rpm-tmp.GFxL96 (%build) I'm not sure about the cause. Do we need first update boost to newer version? Any hints? -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

2 1

[opensuse-packaging] Is there a macro for both BuildRequires and Requires?
by Greg Freemyer 03 Nov '12

03 Nov '12

All, I think Requires and BuildRequires are disjoint / independent. I have a package that has about 20 Requires. I'd like to have a %check section for it, but I'll need all those requires at build time as well to do that. Is there a clean solution? Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Packaging guidelines: use Category "Packaging documentation"
by Andreas Jaeger 02 Nov '12

02 Nov '12

Looking at the wiki starting at http://en.opensuse.org/openSUSE:Packaging_guidelines, I see that not every packaging guideline is using the right category, I'm changing this now. If I miss anything or add the category wrongly, please help me and change the wiki. The line I'm adding is just the following at the end: [[Category:Packaging documentation]] All pages in this category are listed via: http://en.opensuse.org/Category:Packaging_documentation Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] RFC: Guidelines change for lua packaging
by Togan Muftuoglu 02 Nov '12

02 Nov '12

Hi, For background information, which describes the current packaging situation in build-service. please see the following mail <http://lists.opensuse.org/opensuse-buildservice/2012-09/msg00144.html> This is a revised version of a previously mailed RFC to this mailinglist <http://lists.opensuse.org/opensuse-packaging/2012-09/msg00214.html> and still needs refinement. Where appropriate, comments of other people are included in the main document, and where necessary comments are included within the ==NOTE== marks. Therefore contributions in enhancing the document is kindly requested. Thanks Togan 1) The main development should be taking place in devel:languages:lua and therefore devel:languages:misc should be droped as the devel repo for Factory. ==NOTE=== Dominique Leuenberger suggested this effort could be started by populating the packages (preferably as links to openSUSE:Factory, where they are already pushed). Any package that made it into devel:languages:lua should get a changedevelrequest to have the official devel repo follow the new package. ===================== 2) various lua packages that are scattered around the OBS should be developed in devel:languages:lua ==NOTE== That means contacting the maintainers of such packages and ask for moving there package(s) to devel:languages:lua project ========== * Guidelines for Lua packages * Macros are already defined by the lua and lua51 packages in devel:languages:lua # RPM macros for Lua # The major.minor version of Lua %lua_version %(lua -e 'print(_VERSION)' | cut -d ' ' -f 2) ==NOTE== In Ludwig Nussel suggested to compute this once at build time when installing the macros, rather then having rpm evaluate this macro every time ======= # compiled modules should go here %lua_archdir %{_libdir}/lua/%{lua_version} # pure Lua modules should go here %lua_noarchdir %{_datadir}/lua/%{lua_version} * Addon packages Lua add-on packages should generally follow the naming scheme of lua(version)-PKG_NAME -- e.g. Currently main lua packages provided by openSUSE are as follows lua ------ providing version 5.2 lua51 ------ providing version 5.1 lua50 ------ providing version 5.0 lua51-luafilesystem -- tobe used with lua version 5.1 lua-luafilesystem -- tobe used with lua version 5.2 ===NOTE== Unfortunately this itself brings the problem with the next version of lua coming into play say 5.3. Therefore a better way of naming the main lua packages is needed in order to prevent renaming process in the future ===== * Development Packages Some lua modules provide some C parts for extending the module should the user chooses to enhance the module. Hence the name development package, and these packages should have devel suffix added to the package name lua(version)-PKG_NAME-devel Example lua51-luafilesystem-devel * Documentation packages Taking account of the rpmlint warning regarding huge documentation, or the package is just documentation then naming should be lua(version)-PackageName-doc and should be installed to %_defaultdocdir /usr/share/doc/packages/lua-{PKG_NAME}-doc/* * Packaging tools * Many upstream Lua developers use LuaRocks to distribute their modules. Therefore we probably should be finding a way to integrate luarocks in our build system and possibly provide a packaging mechanism similar to py2pack of python -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

Fwd: [opensuse-packaging] How to detect package's version in specfile?
by Marguerite Su 02 Nov '12

02 Nov '12

在 2012-11-1 下午11:37，"Guido Berhoerster" <gber(a)opensuse.org>写道： > > PS: Guido, is "s|\\..*$||" regression? I asked around on gtalk, but no > > one knows such regex style...can you explain it a little bit? > > Not sure what you mean, it's just a BRE, the double backslash is > needed there because rpmbuild also interprets backslashes. What is BRE? I mean, the rpmquery gets a 16.0.1, and you used a pipe and sed s/// replacement to get 16. But \..*$ doesn't looks like the regex we normally use, the [0–9]\.[0-9]\. Stuff. So.I want to know how it works like regex. Eg I want to cut 2.8.9 to 9, how can I do that in your way? And why in spec you cant compare %if 16.0.1 == 16 (get a -1) but can compare %if 16 > 15? Why I have to cut it using sed or I have to use lua script to compare the full output? I think all the numbers here are treated as strings, but why some fails while some still works? Thanks Marguerite -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3