openSUSE Packaging March 2014

packaging@lists.opensuse.org

40 participants
20 discussions

Packaging PHP: composer slowly kills PEAR as a base

by Ralf Lang

Hi folks, recently, a lot of PHP packages have been either converted from PEAR format to composer or offered in both format. Some new software has been composer-only right from the start. As far as I know, we only have tools for automatically dealing with PEAR format packages. This is going to get worse as the most widely used 3rd party pear server software, pirum, has been deprecated in favor of composer. This renders more and more pear based installations useless. http://pirum.sensiolabs.org/ https://twitter.com/fabpot/status/434256189258735616 Do you know how other distributions handle this? Is there any effort for (semi)automatic composer->rpm conversion tools? -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

6 years, 4 months

Re: [opensuse-packaging] How to set mpi as dependency?

by Pengfei Hao

This is how hdf5 did export CC="%{_libdir}/mpi/gcc/$mpi/bin/mpicc" export FC="%{_libdir}/mpi/gcc/$mpi/bin/mpif90" export F77="%{_libdir}/mpi/gcc/$mpi/bin/mpif77" export LD_LIBRARY_PATH="%{_libdir}/mpi/gcc/$mpi/%_lib" Make some assumptions and do an environment export seems the only way until now. 2014-03-21 9:47 GMT-05:00 Pengfei Hao <intijk(a)gmail.com>: > This is how hdf5 did > > export CC="%{_libdir}/mpi/gcc/$mpi/bin/mpicc" > export FC="%{_libdir}/mpi/gcc/$mpi/bin/mpif90" > export F77="%{_libdir}/mpi/gcc/$mpi/bin/mpif77" > export LD_LIBRARY_PATH="%{_libdir}/mpi/gcc/$mpi/%_lib" > > > Make some assumptions and do an environment export seems the only way until > now. > > > 2014-03-20 9:58 GMT-05:00 Alin Marin Elena <alinm.elena(a)gmail.com>: > >> have a loot at the usage of mpi-selector... >> intalling openmpi or mpich will not automatically set you the correct >> mpi.. as >> you expected... >> by the way mpirun shall not be of any concern in the compile/link process. >> >> regards, >> Alin >> >> On Thu 20 Mar 2014 15:51:29 Ruediger Meier wrote: >> > On Thursday 20 March 2014, Pengfei Hao wrote: >> > > Maybe I didn't make it clear. What I want is to have mpicc and mpirun >> > > command to compile MPI written code, it is kind like a compiler(But >> > > only script point to gcc). Even added the BuildRequires of openmpi >> > > and openmpi-devel , the mpicc and mpirun command is not ready. >> > >> > Thats why I've mentioned to look into the hdf5 package. Of course they >> > do something with the %_mpi define from my first email: >> > >> > for mpi in %_mpi; >> > do >> > mkdir $mpi >> > ln -s ../configure $mpi >> > cd $mpi >> > export CC="%{_libdir}/mpi/gcc/$mpi/bin/mpicc" >> > export FC="%{_libdir}/mpi/gcc/$mpi/bin/mpif90" >> > export F77="%{_libdir}/mpi/gcc/$mpi/bin/mpif77" >> > export LD_LIBRARY_PATH="%{_libdir}/mpi/gcc/$mpi/%_lib" >> > %configure \ >> > --docdir=%{_docdir}/%{name} \ >> > --prefix=%{_libdir}/mpi/gcc/$mpi \ >> > --exec-prefix=%{_libdir}/mpi/gcc/$mpi \ >> > --bindir=%{_libdir}/mpi/gcc/$mpi/bin \ >> > --libdir=%{_libdir}/mpi/gcc/$mpi/%_lib \ >> > --datadir=%{_libdir}/mpi/gcc/$mpi/share \ >> > --includedir=%{_libdir}/mpi/gcc/$mpi/include \ >> > --disable-dependency-tracking \ >> > %if 0%{?suse_version} > 1140 >> > --enable-fortran \ >> > %endif >> > --enable-hl \ >> > --enable-shared \ >> > --enable-parallel \ >> > --with-pthread >> > >> > make %{?_smp_mflags} >> > cd .. >> > done >> > >> > But better look at the original hdf5.spec. >> > >> > cu, >> > Rudi >> >> -- >> Without Questions there are no Answers! >> ______________________________________________________________________ >> Dr. Alin Marin ELENA >> http://alin.elenaworld.net/ >> ______________________________________________________________________ >> >> -- >> To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org >> > -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 7 months

project "vdr", repository "SLES11 SP3" has empty RPM_BUILD_ROOT?

by Stefan Seyfried

see $SUBJECT, vdr/dtv-scan-tables fails on SLES11, apparently because RPM_BUILD_ROOT is not set. Of course I could work around this in the spec file, but I find it is a rather strange thing to happen. Can someone enlighten me what the issue is and how to solve it properly? thanks, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 8 months

insserv-compat could be noarch

by Jean Delvare

Hi Ludwig, I see no reason why the insserv-compat package is built separately on each architecture. It only contains perl and shell code. Can we please turn it into a noarch package? Thanks, -- Jean Delvare SUSE L3 Support -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 8 months

need help to unpack and build package

by doiggl＠velocitynet.com.au

Hello, I need help to unpack and build package. How can this error be fixed ? Thanks Glenn project: https://build.opensuse.org/package/show/home:doiggl/cacti spec file: https://build.opensuse.org/package/view_file/home:doiggl/cacti/cacti.spec?e… Log shows: https://build.opensuse.org/package/live_build_log/home:doiggl/cacti/openSUS… [ 48s] ----------------------------------------------------------------- [ 48s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/home:doiggl/openSUSE_13.1/c64e8feb8dd54cb5cc2dd3c1…' /home/abuild/rpmbuild/SOURCES/cacti.spec [ 49s] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.8nrDDU [ 49s] + umask 022 [ 49s] + cd /home/abuild/rpmbuild/BUILD [ 49s] + cd /home/abuild/rpmbuild/BUILD [ 49s] + rm -rf cacti-0.8.9 [ 49s] + /usr/bin/gzip -dc /home/abuild/rpmbuild/SOURCES/cacti-0.8.9.tgz [ 49s] + /bin/tar -xf - [ 49s] + STATUS=0 [ 49s] + '[' 0 -ne 0 ']' [ 49s] + cd cacti-0.8.9 [ 49s] /var/tmp/rpm-tmp.8nrDDU: line 34: cd: cacti-0.8.9: No such file or directory [ 49s] error: Bad exit status from /var/tmp/rpm-tmp.8nrDDU (%prep) [ 49s] [ 49s] [ 49s] RPM build errors: [ 49s] Bad exit status from /var/tmp/rpm-tmp.8nrDDU (%prep) [ 52s] /.build/build: line 373: 205 Killed background_monitor_process [ 54s] [ 39.090123] SysRq : Power Off [ 54s] [ 39.307890] Power down. Partial file list shows: ######################## # tar -ztvf cacti-0.8.9.tgz drwxrwxr-x reinhard/reinhard 0 2013-08-07 05:09 cacti089/ -rw-r--r-- reinhard/reinhard 5934 2013-08-07 05:09 cacti089/about.php -rw-rw-r-- reinhard/reinhard 28824 2013-08-07 05:09 cacti089/graphs.php -rw-r--r-- reinhard/reinhard 5851 2013-08-07 05:09 cacti089/templates_import.php drwxr-xr-x reinhard/reinhard 0 2013-08-07 05:09 cacti089/install/ -rw-r--r-- reinhard/reinhard 1590 2013-08-07 05:09 cacti089/install/0_8_7e_to_0_8_7f.php -rw-r--r-- reinhard/reinhard 1723 2013-08-07 05:09 cacti089/install/0_8_2_to_0_8_2a.php -rw-r--r-- reinhard/reinhard 353 2013-08-07 05:09 cacti089/install/install_finish.gif -rw-r--r-- reinhard/reinhard 5783 2013-08-07 05:09 cacti089/install/0_8_4_to_0_8_5.php -rw-r--r-- reinhard/reinhard 6416 2013-08-07 05:09 cacti089/install/0_8_7i_to_0_8_8.php -rw-r--r-- reinhard/reinhard 5544 2013-08-07 05:09 cacti089/install/0_8_7b_to_0_8_7c.php -rw-r--r-- reinhard/reinhard 5790 2013-08-07 05:09 cacti089/install/0_8_6_to_0_8_6a.php -rw-r--r-- reinhard/reinhard 3473 2013-08-07 05:09 cacti089/install/0_8_6h_to_0_8_6i.php -rw-rw-r-- reinhard/reinhard 1590 2013-08-07 05:09 cacti089/install/0_8_8_to_0_8_8b.php -rw-r--r-- reinhard/reinhard 6588 2013-08-07 05:09 cacti089/install/0_8_6d_to_0_8_6e.php -rw-r--r-- reinhard/reinhard 9900 2013-08-07 05:09 cacti089/install/0_8_5a_to_0_8_6.php -rw-r--r-- reinhard/reinhard 4088 2013-08-07 05:09 cacti089/install/0_8_7g_to_0_8_7h.php -rw-r--r-- reinhard/reinhard 2250 2013-08-07 05:09 cacti089/install/0_8_6f_to_0_8_6g.php -rw-r--r-- reinhard/reinhard 1590 2013-08-07 05:09 cacti089/install/0_8_7c_to_0_8_7d.php -rw-r--r-- reinhard/reinhard 51368 2013-08-07 05:09 cacti089/install/0_8_8a_to_0_8_9.php -rw-r--r-- reinhard/reinhard 2656 2013-08-07 05:09 cacti089/install/0_8_1_to_0_8_2.php -rw-r--r-- reinhard/reinhard 2007 2013-08-07 05:09 cacti089/install/0_8_7_to_0_8_7a.php -rw-r--r-- reinhard/reinhard 1590 2013-08-07 05:09 cacti089/install/0_8_7d_to_0_8_7e.php -rw-r--r-- reinhard/reinhard 1591 2013-08-07 05:09 cacti089/install/0_8_7h_to_0_8_7i.php -rw-r--r-- reinhard/reinhard 1976 2013-08-07 05:09 cacti089/install/0_8_6c_to_0_8_6d.php -rw-r--r-- reinhard/reinhard 1590 2013-08-07 05:09 cacti089/install/0_8_7f_to_0_8_7g.php -rw-r--r-- reinhard/reinhard 5443 2013-08-07 05:09 cacti089/install/0_8_2a_to_0_8_3.php -rw-r--r-- reinhard/reinhard 1859 2013-08-07 05:09 cacti089/install/0_8_7a_to_0_8_7b.php -rw-r--r-- reinhard/reinhard 13095 2013-08-07 05:09 cacti089/install/0_8_6j_to_0_8_7.php -rw-r--r-- reinhard/reinhard 74608 2013-08-07 05:09 cacti089/install/0_8_3_to_0_8_4.php -rw-r--r-- reinhard/reinhard 413 2013-08-07 05:09 cacti089/install/install_next.gif -rw-rw-r-- reinhard/reinhard 26737 2013-08-07 05:09 cacti089/install/index.php -rw-r--r-- reinhard/reinhard 2406 2013-08-07 05:09 cacti089/install/0_8_to_0_8_1.php -rw-r--r-- reinhard/reinhard 1590 2013-08-07 05:09 cacti089/install/0_8_8_to_0_8_8a.php -rw-r--r-- reinhard/reinhard 2451 2013-08-07 05:09 cacti089/install/0_8_6g_to_0_8_6h.php -rw-r--r-- reinhard/reinhard 6038 2013-08-07 05:09 cacti089/graph_xport.php -rw-r--r-- reinhard/reinhard 26575 2013-08-07 05:09 cacti089/cmd.php -rw-r--r-- reinhard/reinhard 5340 2013-08-07 05:09 cacti089/auth_changepassword.php -rw-r--r-- reinhard/reinhard 14238 2013-08-07 05:09 cacti089/auth_login.php -rw-r--r-- reinhard/reinhard 9208 2013-08-07 05:09 cacti089/graph_settings.php -rw-rw-r-- reinhard/reinhard 65369 2013-08-07 05:09 cacti089/host.php -rw-rw-r-- reinhard/reinhard 18393 2013-08-07 05:09 cacti089/poller.php -rw-r--r-- reinhard/reinhard 6974 2013-08-07 05:09 cacti089/color.php -rw-r--r-- reinhard/reinhard 48 2013-08-07 05:09 cacti089/README -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 8 months

Which file does this go into into

by doiggl＠velocitynet.com.au

Hello, Which file does this go into in opensuse, its part of a lamp application [database part] --Glenn $database_type = "mysql"; $database_default = "dbname"; $database_hostname = "localhost"; $database_username = "user"; $database_password = "passwd"; $database_port = "3306"; -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 8 months

Call for Reviewers

by Stephan Kulow

Hi, The opensuse-review-team is likely the most important part of the Factory development process as without them our packaging guidelines are just words. They take what the openSUSE packaging community accepted as guidelines, and make sure they are implemented consistently. You can read about their work on the wiki: http://en.opensuse.org/openSUSE:OpenSUSE_review_team http://en.opensuse.org/openSUSE:Factory_review Now the problem is the ever increasing amount of reviews to do. Most of you will not be aware of it, but they do between 400 and 600 reviews *EVERY WEEK*, so the whole Factory development gets in trouble if one of the current review team is on vacation and that's just not how it should be. So before I call the tributes of openSUSE (sorry to everyone who doesn't know the book :), I would like to have an open call for volunteers. There has been one around half year ago, but it didn't really work out too well, so I would like to give it another round. Unfortunately the requirements didn't change since last time, so we just have to have better luck this time. So what is expected from the perfect reviewer? Foremost he needs to be a friendly guy, who can still say no. This sounds easy, but one of the hardest task in review is returning a 'yes, but' instead of 'no'. It can be very tiresome to explain the 20th packager that week about a policy (change), but if you declined 19, the 20th still deserves an answer. It happens that submitters don't accept the no and want to discuss, so some willingness to talk to people is also important, including the other reviewers. And it surely you need to have some expertise with openSUSE packaging, but reviewers don't have to be packaging superheros - they will become one fast enough when looking at dozens of requests a week. A good common sense to start with is better than a good knowledge of the latest bash tricks. My goal is to roughly double the number in the review team, so it's less work for everyone - or more time per review, but you shouldn't volunteer unless you really want to take your part of the 400 to 600 reviews a week. Which brings me a last requirement: you need to have extra time to spare. I know I'm asking for a lot, but I'm also offering a lot of responsibility for openSUSE to share. And I hope everyone agrees that the we're in pretty good shape generally if our biggest problem are too many submissions to review - so let's fix that too by embracing the team that did it so well in the past. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 8 months

How to set mpi as dependency?

by Pengfei Hao

I am packaging a package whcih need mpi environment, but default installation of OpenMPI will set nothing. So I don't have mpicc, mpirun .. etc. commands. I could export PATH= .... but I think this adhoc solution is not right. Could anyone told me how to the standard way to set mpi as dependency? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 8 months

Submitting a single maintenance request containing two packages

by Robert Munteanu

Hi, I want to submit a mr for 13.1 which would contain two packages. The guide at [1] only covers updates for a single package. How can I submit two package updates in a single mr? Thanks, Robert [1]: http://en.opensuse.org/openSUSE:Package_maintenance#Find_the_package_that_y… -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 8 months

sorting out duplicates help

by Robert Schweikert

Hi, Working on a package that creates a -doc package and includes the files in docdir via: %files doc %defattr(-,root,root) %doc %{docdir} I'd like to get the LICENSE file from the source into the main package via %files %doc LICENSE But when I do this I get complaints about the doc files being packaged twice. How do I solve this puzzle? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX SUSE-IBM Software Integration Center Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 years, 8 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging March 2014