January 2012 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] build.opensuse.org OBS binary backend is down
by Adrian Schröter 17 Jan '12

17 Jan '12

The SAN array of the backend server server seems to have lost 3 hard disk at once now :/ That means the array is broken atm. We can not fix this before monday. Since not all binary parts of the projects are in backup it means that we will need to rebuild some of them afterwards. Sources and project configurations shall not be affected by this. It is sunshine out there, have fun :) sorry adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 2

[opensuse-packaging] Where to put headers of python extension modules
by Michal Vyskocil 16 Jan '12

16 Jan '12

Hi all, I have found that we don't have any standard location where to install the header files of python (C/C++) extension modules. There are several approaches 1.) install it into /usr/include dbus-1-python-devel, python-cairo-devel, etc 2.) /usr/include/python${py_ver}/ python-greenlet-devel 3.) ${libdir}/python${py_ver}/${module} python-egenix-mx-base, python-numpy-devel It seems that our distutils expects the variant 2.), so all packages have to be fixed to use this path. However I did not see anything like that in our Python packaging policy, so I would like to ask here first BTW: variant 1 should be considered as a bug as you can't install python and python3 package in parallel (python-gobject2-devel and python3-gobject-devel). [1] http://en.opensuse.org/openSUSE:Packaging_Python Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Breaking the loop with pkg-config 0.26
by Vincent Untz 13 Jan '12

13 Jan '12

Hi, A while ago, pkg-config 0.26 got released and the main change in there is that it depends on an external glib (instead of an internal copy). We can easily drop the pkg-config BuildRequires in glib by setting some environment variable so that glib knows how to use pcre & friends. (Of course, we lose the automatic pkgconfig() Provides/Requires, but okay, let's ignore that). However, things get ugly: + if we want glib2 to build with the external pcre library, we need pcre-devel to be installed + pcre-devel has a Requires for /usr/bin/pkg-config, and hence on the pkg-config package (automatically added at the same time as the pkgconfig() Provides, I guess) => to build pkg-config, I need glib2, for which I still need pkg-config. Loops are fun. The issue here is that to fix the loop, we'd need to eradicate the pkg-config dependency on everything that is below glib2. This includes at least libffi-devel, libselinux-devel, pcre-devel and zlib-devel. And libraries that might be below those. This sounds annoying, as it's easy to re-introduce a build loop. On the other hand, I don't really see what else we can do. Any opinion? Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 7

[opensuse-packaging] Licence issue with the Projects > security > nikto package
by Johannes Weberhofer 11 Jan '12

11 Jan '12

Working on a w3af packe, I have recognized, that the nikto package have a possible license issue. The plugins have the following licence lines: ####################################################################### # Source: http://cirt.net # This file may only be distributed and used with the full Nikto package. # This file may not be used with any software product without written permission from CIRT, Inc. # (c) 2007 CIRT, Inc., All Rights Reserved. # # NOTE: By sending any database updates to CIRT, Inc., it is assumed that you # grant CIRT, Inc., the unlimited, non-exclusive right to reuse, modify and relicense the changes. ####################################################################### # Notes: # NiktoDB 1.00 ####################################################################### While distribution seem to be ok within the full package, a proprietary license is used. Is this license ok for opensuse? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] don't understand the new licenses
by Sascha Manns 10 Jan '12

10 Jan '12

Hello mates, i'm trying to build a new packageversion. The old Licenses Field was "GPLv3 or later". If i'm going to: http://license.opensuse.org/ and place GPLv3 there, the Site proposes to use "GPL-3". If i'm placing this into the Licenses Field i become: kvirustotal-lang.noarch: W: invalid-license GPL-3 kvirustotal.x86_64: W: invalid-license GPL-3 kvirustotal.src: W: invalid-license GPL-3 The specified license string is not recognized. Please refer to http://license.opensuse.org/ for the list of known licences and their exact spelling. But why this false? Does anyone knows more? Wish all a happy X-Mas Sascha -- Sincerly yours Sascha Manns Community &Support Agent open-slx GmbH http://www.open-slx.de (Business) http://saigkill.homelinux.net (Private) This mail is written with Balsam Professional 12.1

5 6

[opensuse-packaging] Is there a quick way to test all Requires are in factory?
by Greg Freemyer 10 Jan '12

10 Jan '12

All, More than once I have submitted something to factory that didn't have all the requires and buildrequires pieces already there. Is there a simple test I can run on the package to verify that before I submit a new package? In this specific case, I want to submit security -- log2timeline. I've been slowly submitting all the pre-reqs and I think I finally have everything in factory. Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

12 21

[opensuse-packaging] generic provides for MPI environments
by todd rme 07 Jan '12

07 Jan '12

There are currently at least 3 MPI (message passing interface) environments provided by openSUSE: lam, mpich, and openmpi. Packages related to MPI, like mpi-selector, and python-pypar, require an MPI environment be installed, but do not care which it is as long as it is compliant with the MPI standard. There is no easy way to specify this in the requires, however. What does everyone think about having a generic provides for MPI environments, such as pkconfig(MPI), that each of these can provide and that other packages could require in order to be MPI environment-agnostic? If so, what would be the best name for it? -Todd -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] libexiv2.so.9 needed by rawstudio-2.0-1.2.i586
by Mariusz Fik 06 Jan '12

06 Jan '12

Hi, I just added graphics repository on openSUSE 12.1 and I tried to install rawstudio but got following error: |Problem: nothing provides libexiv2.so.9 needed by rawstudio-2.0-1.2.i586 | Solution 1: do not install rawstudio-2.0-1.2.i586 | Solution 2: break rawstudio by ignoring some of its dependencies -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

2 1

[opensuse-packaging] Submitting multiple changes against phpunit packages
by Robert Munteanu 05 Jan '12

05 Jan '12

Hi, I've branched server:php:applications to https://build.opensuse.org/project/packages?project=home%3Arobert_munteanu%… and updated a couple of packages, fixing https://bugzilla.novell.com/show_bug.cgi?id=734936 . These packages are in a dependency tree, and I'm not sure how to submit requests for them. Should I start with the leaves and once they are accepted submit the parents, or should I submit them all at once and mention that they should be reviewed/merged together? Thanks, Robert -- Sent from my (old) computer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] enable some build repos for clisp
by Ruediger Meier 04 Jan '12

04 Jan '12

Hi, Could anybody with power please enable building clisp in devel:languages:misc for SLE* and Tumbleweed repos? cu, Rudi -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1