February 2011 - openSUSE Packaging - openSUSE Mailing Lists

Re: [opensuse-packaging] Need help with libname.
by Philipp Thomas 09 Feb '11

09 Feb '11

[Please, no extra copy via private mail as I do read the list] On Fri, 04 Feb 2011 23:22:45 +0200, Dave Plater <davejplater(a)gmail.com> wrote: >Am I correct in saying that a full stop "." isn't allowed to be in the >library name and needs to be replaced with an underscore "_" ? Yes, that' what the shared library policy tells you. >Meanwhile you wouldn't have an idea why libtool is naming the devel .so >link incorrectly. You can see it taking place in the makeinstall section >of the log? You tell me what project we're talking about and I'll have a look if time permits. I guess I have a few ideas why something like that can happen but I'd like to look first. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 15

[opensuse-packaging] How to extend OBS gpg key?
by Schlomo Schapiro 07 Feb '11

07 Feb '11

Hi, hope this is not too off topic, but how do I extend my build service key? $ osc signkey --extend home:sschapiro Server returned an error: HTTP Error 404: Not Found invalid_command And the web gui does not even mention gpg keys. My key expired in 2008 and Ubuntu won't install packages from a repo signed with an expired key. Kind Regards, Schlomo -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] Need help with prjconfig
by Dave Plater 07 Feb '11

07 Feb '11

Hi, I have a path to multimedia:libs in my home:plater factory repo, how do I make the builds prefer multimedia:libs over home:plater and still build against packages that aren't in mmlibs? Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 3

[opensuse-packaging] devel:languages:go - goinstall
by Graham Anderson 07 Feb '11

07 Feb '11

Besides compilers, linkers etc, the core Go[1] toolchain has several utility applications bundled with it. One of these is an app called goinstall[2] which facilitates the download, compilation and installation of third party libraries written in Go. Currently this utility doesn't work very well in the Go package[3] we are working on for the following reasons: 1) It scans the third party source for "Import" statements and treats these as hard dependancies which it will try to install first(from source). At the moment this includes any imports of any of the standard go libraries and looks for the source files. Although we have the goinstall utility in the main Go package, we don't install the standard library source by default. Our Go package currently only installs the library sources either from the .srpm or from the go-doc package (because the godoc utility replicates http://golang.org and generates API docs on the fly from the sources). 2) The goinstall utility is currently installed to /usr/bin (undesirable) It is desireable to have the goinstall utility working well as part of the core Go package, because we currently don't, and cannot, package all the third party libs; although I fully intend to grow the list of popular libs that we do package. Aside from hacking on the goinstall tool to improve it. I'd like to tweak the core Go package some more to make the goinstall tool work well in it's current form so I'd appreciate some feedback on which of the following options would be the most appropriate. 1) Add a "go-devel" to the .spec and bundle the standard library sources & the goinstall tool in this sub package. OR Install the standard library sources with the main Go package. 2) Install "goinstall" binary to /usr/sbin or /usr/local/sbin OR Leave it installed to /usr/bin because Go hackers may optionally have $GOROOT exported to a location in their $HOME. [1] http://golang.org [2] http://golang.org/cmd/goinstall/ [3] https://build.opensuse.org/package/show?package=go&project=devel:languages:… -- “What can be asserted without proof can be dismissed without proof.” - Christopher Hitchens -- 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] Need help with libname.
by Dave Plater 04 Feb '11

04 Feb '11

Hi, I split off all five of the libraries in the mjpegtools package (I shouldn't have because it would have been on its way to factory by now) and I'm having difficulty in getting the right shared library name for them. I've even taken one lib and dissected the name and followed step by step the reconstruction of the name following the guidlines. The libs all have a revision of 0.0.0 and follow the same naming pattern. This is the name of one liblavfile-1.99.so.0.0.0 which I have called it's package liblavfile-1.99-0 (maybe I should try 1_99-0 but I'm sure that was my first attempt) I've taken lib + name = liblavfile-1.99 and because the last letter of the name is really a digit -> 9 I've put in a dash after the 99- and then the sonumber 0. What am I doing wrong. I'm busy fixing a gstreamer blocker, I battled with a new libs subpackage name with gstreamer plugins bad as well but that ones numbers in the name had all underscores. This maybe has something to do with the fact that the tarball was named mjpegtools-2.0.0rc1 and I had to make the version 1.99.99 for the upgrade path but I don't see the specfile version being passed to the build anywhere and I took the version 1.99.99 from my head because the author stated on the website that the next version will be 2.0.0. The tarball decompresses to mjpegtools-2.0.0 Thanks Dave P -- 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 - gstreamer-0_10-plugins-bad has been broken by mjpegtools.
by Dave Plater 04 Feb '11

04 Feb '11

Hi, gstreamer-0_10-plugins-bad stopped building in factory, multimedia:libs and home:plater where I made the update. The present updated binaries in factory require libmjpegutils-1.9.so.0 and libmplex2-1.9.so.0 but mjpegutils are providing libmplex2-1.99.so.0 and libmjpegutils-1.99.so.0 but the devel package contains libmjpegutils.so and libmplex2.so. This will cause a blockage in zypper dup. I can try a quick workaround and just create the devel .so links but it's really better to get to the bottom of this. If you look in the spec file you will see a warning (I made it very hard to miss) about the pre checkin cripple script. I will solve the problem in the end but this problem needs solving fast! It's a good thing that one gst plugins bad plugin failed to build otherwise this could have gone unnoticed. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 1

Re: [opensuse-packaging] RPM how to change a directory to a link
by yersinia 03 Feb '11

03 Feb '11

> On Thu, Feb 3, 2011 at 12:58 PM, Johannes Meixner <jsmeix(a)suse.de> wrote: >> >> Hello, >> >> when there is in foo-1.rpm a directory /somewhere/foo/ but >> in foo-2.rpm it is a link /somewhere/foo -> /elsewhere/bar >> then "rpm --upgrade foo" fails with >> -------------------------------------------------------------- >> error: unpacking of archive failed on file /somewhere/foo: >> cpio: rename failed - Is a directory >> -------------------------------------------------------------- >> >> What is the officially blessed method to support such a change >> in the software in the RPM package of such a software? >> Well, strange enough the metod for doing this via lua and pretrans was never documentated but it is know today ( more or less) . Perhaps these link can help you https://bugzilla.redhat.com/show_bug.cgi?id=447156 https://bugs.launchpad.net/rpm/+bug/633636/comments/3 hth -- 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] pear error Parsing of package.xml from file "package.xml" failed only on SLE targets
by Ralf Lang 03 Feb '11

03 Feb '11

Hi, I've noticed some recent PHP pear packages fail only on SLE_* with an error in parsing the pear package.xml file. Take for example php5-pear-Crypt_Blowfish rlang@linux-ecfn:~/build/server:php:applications/php5-pear-Crypt_Blowfish> osc r openSUSE_11.1 x86_64 succeeded openSUSE_11.1 i586 succeeded openSUSE_11.2 x86_64 succeeded openSUSE_11.2 i586 succeeded openSUSE_11.3 x86_64 succeeded openSUSE_11.3 i586 succeeded openSUSE_Factory i586 succeeded openSUSE_Factory x86_64 succeeded SLE-10-SP2 i586 failed SLE-10-SP2 x86_64 failed SLE_11 x86_64 failed SLE_11 i586 failed SLE_11_SP1 i586 failed SLE_11_SP1 x86_64 failed The relevant error section is: + PHP_PEAR_PHP_BIN='/usr/bin/php -d memory_limit=50m' + /usr/bin/pear -v -d doc_dir=/doc -d bin_dir=/usr/bin -d data_dir=/usr/share/php5/PEAR/data install --offline --nodeps -R /var/tmp/php5-pear-Crypt_Blowfish-1.1.0RC2-build package.xml Parsing of package.xml from file "package.xml" failed Cannot download non-local package "package.xml" Package "package.xml" is not valid install failed How can I get a more verbose message of pear on SLE* why it thinks this xml is broken (as opposed to even openSUSE 11.1 which should roughly equal SLE_11)? -- 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

1 0

[opensuse-packaging] How do I submit a new rpm macro for inclusion?
by Dave Plater 02 Feb '11

02 Feb '11

Hi, I;ve been dealing with a lot of crippled sources and also build a few svn and git packages from time to time. I copied the contents of the %configure macro and substituted ./configure with ./autogen.sh. This would be ideal as a %autogen macro don't you think? Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5

[opensuse-packaging] problem with branched project
by Petr Cerny 02 Feb '11

02 Feb '11

Hi, I have a problem with branched package: the main package has been updated, so I did run "osc pull" to fix it. Apparently it has been "fixed" indeed when I now try to commit changes, I'm getting the following message: openssh-5.7p1.dif mentioned in spec file does not exist. ERROR: source_validator failed: None When I run "osc diff" on the package it doesn't show all changes, just some - it seems to compare wrong versions of .spec files, because "osc diff openssh.spec" shows correct diferences. Have you encountered something similar? Am I forgetting something or is it a known bug? Thanks Kind regards Petr Cerny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 5