May 2013 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] brp-25-symlink
by Matwey V. Kornilov 03 May '13

03 May '13

Hi, I am experiencing strange issue at science eso-midas Factory. brp-25-symlink want to relink my links in a quite strange manner. here is log: [ 446s] INFO: relinking /opt/eso-midas/12FEBpl1.3/context/*.ctx -> ../applic/general/etc/*.ctx ../gui/XAlice/etc/alice.ctx ../contrib /astromet/etc/astromet.ctx ../contrib/baches/etc/baches.ctx ../stdred/ccdred/etc/ccdred.ctx ../stdred/ccdtest/etc/ccdtest.ctx ../contr ib/cloud/etc/cloud.ctx ../contrib/daophot/etc/daophot.ctx ../stdred/do/etc/do.ctx ../stdred/echelle/etc/echelle.ctx ../contrib/esolv/e tc/esolv.ctx ../stdred/feros/etc/feros.ctx ../contrib/geotest/etc/geotest.ctx ../contrib/imres/etc/imres.ctx ../contrib/invent/etc/inv ent.ctx ../stdred/irac2/etc/irac2.ctx ../stdred/irspec/etc/irspec.ctx ../contrib/iue/etc/iue.ctx ../stdred/long/etc/long.ctx ../contri b/lyman/etc/lyman.ctx ../stdred/mos/etc/mos.ctx ../stdred/optopus/etc/optopus.ctx ../contrib/pepsys/etc/pepsys.ctx ../stdred/pisco/etc /pisco.ctx ../stdred/qc/etc/qc.ctx ../contrib/romafot/etc/romafot.ctx ../stdred/spec/etc/spec.ctx ../applic/statist/etc/statist.ctx .. /contrib/surfphot/etc/surfphot.ctx ../contrib/template/etc/template.ctx ../contrib/tsa/etc/tsa.ctx ../contrib/wavelet/etc/wavelet.ctx (was ../applic/general/etc/*.ctx [ 446s] ../gui/XAlice/etc/alice.ctx [ 446s] ../contrib/astromet/etc/astromet.ctx [ 446s] ../contrib/baches/etc/baches.ctx [ 446s] ../stdred/ccdred/etc/ccdred.ctx [ 446s] ../stdred/ccdtest/etc/ccdtest.ctx [ 446s] ../contrib/cloud/etc/cloud.ctx [ 446s] ../contrib/daophot/etc/daophot.ctx [ 446s] ../stdred/do/etc/do.ctx [ 446s] ../stdred/echelle/etc/echelle.ctx [ 446s] ../contrib/esolv/etc/esolv.ctx [ 446s] ../stdred/feros/etc/feros.ctx [ 446s] ../contrib/geotest/etc/geotest.ctx [ 446s] ../contrib/imres/etc/imres.ctx [ 446s] ../contrib/invent/etc/invent.ctx [ 446s] ../stdred/irac2/etc/irac2.ctx [ 446s] ../stdred/irspec/etc/irspec.ctx [ 446s] ../contrib/iue/etc/iue.ctx [ 446s] ../stdred/long/etc/long.ctx [ 446s] ../contrib/lyman/etc/lyman.ctx [ 446s] ../stdred/mos/etc/mos.ctx [ 446s] ../stdred/optopus/etc/optopus.ctx [ 446s] ../contrib/pepsys/etc/pepsys.ctx [ 446s] ../stdred/pisco/etc/pisco.ctx [ 446s] ../stdred/qc/etc/qc.ctx [ 446s] ../contrib/romafot/etc/romafot.ctx [ 446s] ../stdred/spec/etc/spec.ctx [ 446s] ../applic/statist/etc/statist.ctx [ 446s] ../contrib/surfphot/etc/surfphot.ctx [ 446s] ../contrib/template/etc/template.ctx [ 446s] ../contrib/tsa/etc/tsa.ctx [ 446s] ../contrib/wavelet/etc/wavelet.ctx) [ 446s] ln: target './/opt/eso-midas/12FEBpl1.3/context/*.ctx' is not a directory It looks like $new_link_dest and $orig_link_dest should be the paths or files, but brp-25-synlink uses expanded globs instead. This leads to wrong ln command and breaks my package :) -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 9

[opensuse-packaging] devel:languages:erlang project news
by Matwey V. Kornilov 03 May '13

03 May '13

Hi, I've just linked erlang against openSUSE:Facory erlang. Now, we have devel:languages:erlang:Factory subproject where erlang is developed and this package is now devel for openSUSE:Factory, and we have erlang at devel:languages:erlang for compatibility. We are planning to remove erlang from devel:languages:erlang as soon as 12.3 will be discontinued (for people, who added the repo to their boxes nothing should change). However, lots of people and projects link erlang from devel:languages:erlang, and I would like to collect here some points for this people. Probably, I also have to send delete requests to all this packages with link to this message in order to notify that from now they link probably something wrong. 1. erlang is developed at devel:languages:erlang:Factory, please send your submitrequest to appropriate project. No sr will be accepted at devel:languages:erlang/erlang. 2. Why do you need bleeding-edge erlang in your project? openSUSE 12.2 and 12.3 provide erlang in oss-repo. Maybe it is enough. You also possibly create shadowing problem for people, masking erlang from distro with your bleeding-edge link. 3. If you do really need up-to-date erlang, please, consider linking from openSUSE:Factory, where it is probably little bit stable than in devel project where It can be occasionally broken. 4. Thank you for cooperation. -- With best regards, Matwey V. Kornilov http://0x2207.blogspot.com xmpp:0x2207@jabber.ru -- 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] Mixed case package names for php and python packages
by Johannes Weberhofer 03 May '13

03 May '13

Dear all, I'm currently packaging several python packages, and found that there are several packages available in mixed case notation (E.g. python-PyYAML or python-Sphinx). There is al global rule documented in http://en.opensuse.org/openSUSE:Package_naming_guidelines#Case_Sensitivity , saying whenever possible lowercase package-names should be used. I have found lots of packages (like php5-pear-Horde*) in the php section and also many others in the python section. Shouldn't that be cleaned up (as a long-term-target)? For cross-distribution projects it makes things a bit difficult, as e.g. Fedora uses the lower-case filenames of several python projects. 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

4 5

[opensuse-packaging] Howto protect files from removing after uninstall of a rpm?
by Meike Stone 02 May '13

02 May '13

Hello, I try to build a RPM. All is working fine. But I need that after uninstall of the rpm two files always should be left on disk. If the package is updated, file should be replaced with the file from new rpm and replaced renamed as .rpmsave. Is there a way to do this in the spec file? Thanks Meike -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 11

[opensuse-packaging] Recommended packages
by Dmitry Roshchin 02 May '13

02 May '13

It seems number of recommended packages is limited to 10. If there are 11 or more recommended packages in spec file, resulting rpm doesn't have recommendations. Is it normal? -- 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] glibmm and sigc static packages
by Sankar P 01 May '13

01 May '13

Hi, I am trying to build a static binary of https://github.com/i-rinat/fragview I patched the cmake file as: +SET (CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -static") to build a static binary. Now during the make phase, I get the following errors: /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld: cannot find -lglibmm-2.4 /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld: cannot find -lsigc-2.0 I got the above error for "-lm" too which went away after installing the libc-devel-static rpm. However I could not find either a glibmm-devel-static rpm or a sigc-devel-static rpm. Now what is the easiest way to get the static rpm of these packages so as to get the static binary generated ? Which buildservice packages should I fork and tweak ? I do not have much experience in building and so wanted to ask here before proceeding, to know if I am going in the right path. I need a static binary as I want to run this tool in some old SLE boxes where the latest GTK, glibmm packages are not available, and so I cannot compile the fragview tool from the source in those machines. On a side note, The earlier RPM search under software.opensuse.org/search will list the rpms (instead of the projects) and it was easier to find if there were any rpms in home projects etc. in just one page. Now, the search interface is kind of complex, and makes us click a lot more. Does anyone else apart from me, feel that this can be reported as an usability issue ? Thanks. Sankar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3