February 2012 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Easy way to recognize software that use given library
by Josef Reidinger 23 Feb '12

23 Feb '12

Hi, It looks like we have some ancient libraries in games project, that probably noone use. Is there easy way how to recognize in OBS which packages depend on given one? I am unable to google it ( maybe just wrong search term ). thanks Josef -- Josef Reidinger Software Engineer Appliance Department SUSE LINUX, s. r. o. Lihovarska 1060/12 190 00 Praha 9 Czech Republic jreidinger(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

5 12

[opensuse-packaging] How is the "release" value in the specfile supposed to be set?
by Greg Freemyer 22 Feb '12

22 Feb '12

All, I've just been ignoring the release variable in my specfiles but I don't really understand the way it works out. I suspect its described on the wiki, but I couldn't find it. As an example, I maintain sleuthkit. Looking in 3 repos I see: sleuthkit | 3.2.3-10.1 | x86_64 | security sleuthkit | 3.2.3-3.5 | x86_64 | factory-oss sleuthkit | 3.2.3-2.1.3 | x86_64 | openSUSE Current OSS As of a few days ago, they all had "release: 0" in their respective specfiles. My understanding is that the number following the dash above is the release number, I really have 3 releases of 3.2.3 represented above. -2, -3, and -10. Is that right? If I push the code in security to factory, will it suddenly become -10 (or -11)? Do I ever need to set the release value in my specfiles to anything but 0? Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 7

Re: [opensuse-packaging] How is the "release" value in the specfile supposed to be set?
by Togan Muftuoglu 21 Feb '12

21 Feb '12

In-Reply-To: <CAGpXXZLUDH5mC+Ziby+HZR_5oWGKs3_y=pifWMCit5CtBnNZQg(a)mail.gmail.com> On 02/21/12 at 10:42am, Greg Freemyer wrote: > > sudo zypper in --force nikto-2.1.1-2.1 > > fyi: in this case I'm going to delete the package from my home > project. I only branched it to fix the simple bug you accepted, so i > definitely want to switch to the security version. > If you have branched the package, normally when your SR is accepted then your home:user:branch:BLABLA is deleted. Of course you can force to keep it but by default osc submitpac will cause the home:user:branch to be deleted Togan -- When there is will, there is a way -- 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] bluedevil and gnome-icon-theme
by Matwey V. Kornilov 21 Feb '12

21 Feb '12

Hi all, I am running opensuse 12.1 and I've found that bluedevil package requires gnome-icon-theme (through other dependencies). This must be fixed prior the next release. Installing another 60 MB of unneeded software only to run BlueTooth in KDE is quite odd. Unfortunately, I could not find the root of this evil, and I hope that maintainers will do that. -- 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] New build failures due to xorg-x11 reshuffle
by Stephan Kulow 21 Feb '12

21 Feb '12

Hi, As Marguerite Su already noted, xorg-x11 libraries were split, renamed and recreated as meta packages. For most packages this is no problem, but in some cases this creates a problem. The situation is this: vim.spec requires gtk2-devel, which in return requires pkgconfig(xft). Before the xorg libs split, this pkgconfig require dragged in all other XOrg libraries too and vim build was free to choose. Now there is only Xft and the libraries below it in the buildroot and vim fails. You have two options to fix the build, which both come down to: fix your build requires to require what you need to build. Either use the correct form (works on >= 11.4 afaik) BuildRequires: pkgconfig(xt) or simulate the old way in dragging all X libs in: BuildRequires: xorg-x11-devel The choice is yours - but what I'm most afraid of are packages that do not build fail, but simply disable X11 support. vim only fails because one binary is missing. If vim.spec had used %_bindir/* as many others do, it would have left unnoticed ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

7 11

[opensuse-packaging] Where to submit python3 packages?
by Vitaliy Tomin 21 Feb '12

21 Feb '12

I've built some python packages needed for my work with python3 https://build.opensuse.org/project/monitor?project=home%3AHighwayStar%3Abra… There are numpy, scipy, IPython and some dependencies built with python3 . Should I submit it to devel:languages:python? What current police about python3 packages? Should it be build with links packages as described http://en.opensuse.org/openSUSE:Packaging_Python#Building_Python2_And_Pytho… Also i found project devel:languages:python3 in buildservice, but it has no packages. What does it for? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 8

[opensuse-packaging] Unable to branch server:php:applications php5-pear-phpunit-PHP_CodeCoverage
by Robert Munteanu 20 Feb '12

20 Feb '12

Hi, I've recently deleted a branched package ( see subject ) since I was getting instructed to use osc pull to repair it, but that did not work ( sorry, did not save the messages ). I decided to start fresh and delete/branch the package . Here's a brief console log > osc branch server:php:applications php5-pear-phpunit-PHP_CodeCoverage Server returned an error: HTTP Error 400: Bad Request service source_validator failed: > osc up checking out new package php5-pear-phpunit-PHP_CodeCoverage A php5-pear-phpunit-PHP_CodeCoverage At revision None. > cd php5-pear-phpunit-PHP_CodeCoverage/ > osc status (no output) > osc up At revision None. > osc pull osc pull makes only sense with a detached head, did you mean osc up? I'm basically stuck with being unable to branch the package . Any ideas on how to get out of this situation would be appreciated. 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 5

[opensuse-packaging] Compilation Issue - grub-0.97-reiser4-20050808.tar
by doiggl＠velocitynet.com.au 20 Feb '12

20 Feb '12

Hello I have two questions. Q1. Have you a .spec file to compile this patched version of grub ? Q2. I am attempting to compile grub-0.97-reiser4-20050808.tar from [1] and get the following what needs to be installed to fix the error ? Thanks Glenn # ./configure configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for gcc... (cached) gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking dependency style of gcc... (cached) gcc3 checking for ranlib... ranlib checking whether optimization for size works... yes checking whether gcc has -fno-stack-protector... yes checking whether -Wundef works... yes checking whether -falign-loops works... yes checking for objcopy... objcopy checking if C symbols get an underscore after compilation... no checking whether objcopy works for absolute addresses... no configure: error: GRUB requires a working absolute objcopy; upgrade your binutils [1] http://ftp.icm.edu.pl/packages/linux-reiserfs/reiser4progs/grub-0.97-reiser… -- 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] Sorry: Sent reminder mails twice
by Stephan Kulow 18 Feb '12

18 Feb '12

Hi, Sorry for the trouble, but I managed to send some old mail content. The date is correct, so you should be able to spot the old mail easily - still sorry. Greetings, Stephan -- 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] Factory X11 Rename Issue
by Marguerite Su 18 Feb '12

18 Feb '12

why there's no notification for the rename of such an important series of packages: xorg-x11-* every dependency you picked up which depends on any X11 package while you do not call it directly will got an unresolvable. and they even can't be fixed by add suse version tag and call a single dependency like libX11-devel. about 30+ unresolvables drive me almost crazy. now there's two sets of X11 which almost the same content in Factory. you "have choice for"...what choice? by writing 100+ characters for each of them? will it be automatically resolved? it's really bad for no notification of "sensitive" change on basic system packages. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1