September 2013 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Hermes mail about failure [Fwd: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64]
by Bernhard Voelker 26 Sep '13

26 Sep '13

Hi *, I'm often receiving Hermes mails about build failures (like the following), but I can't see any problem in the log. Any hint? Thanks & have a nice day, Berny -------- Original Message -------- From: hermes(a)opensuse.org Subject: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64 X-Hermes-Msg-Type: OBS_BUILD_FAIL X-Mailer: openSUSE Notification System Date: Thu, 26 Sep 2013 04:20:31 +0000 Message-Id: <20130926042031.CB84723C6C(a)dhl.opensuse.org> Package coreutils-testsuite (version 8.21-216.26) of project Base:System failed to build for openSUSE_Factory / x86_64. Review the build log: osc remotebuildlog Base:System coreutils-testsuite openSUSE_Factory x86_64 | less Check out the package for editing: osc checkout Base:System coreutils-testsuite -- Hermes messaging (http://hermes.opensuse.org) openSUSE Build Service (https://build.opensuse.org/) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5

[opensuse-packaging] Can someone update this package ]from 1.3x to 1.4x please - https://build.opensuse.org/package/show/system:packagemanager/smart#
by doiggl＠velocitynet.com.au 25 Sep '13

25 Sep '13

Hello Can someone update this package [1]from 1.3x to 1.4x please. I am asking because I don’t see a package update/report update section. I am using the 1.4x version and it works. [2] see [2] for build details. Thank you Glenn source: http://launchpad.net/smart/trunk/1.4.1/+download/smart-1.4.1.tar.bz2 announcement: http://lists.labix.org/pipermail/smart-labix.org/2011-October/004210.html [1] https://build.opensuse.org/package/show/system:packagemanager/smart# openSUSE Build Service > Projects > system:packagemanager > smart [2] https://build.opensuse.org/package/show/home:doiggl/smart version 1.4x build details [ 125s] ... saving built statistics [ 125s] ... saving built packages [ 125s] /home/abuild/rpmbuild/RPMS/x86_64/smart-1.4.1-19.6.x86_64.rpm [ 125s] /home/abuild/rpmbuild/RPMS/x86_64/smart-debuginfo-1.4.1-19.6.x86_64.rpm [ 125s] /home/abuild/rpmbuild/RPMS/x86_64/smart-debugsource-1.4.1-19.6.x86_64.rpm [ 125s] /home/abuild/rpmbuild/RPMS/x86_64/smart-gui-gtk-1.4.1-19.6.x86_64.rpm [ 125s] /home/abuild/rpmbuild/RPMS/x86_64/smart-gui-qt3-1.4.1-19.6.x86_64.rpm [ 125s] /home/abuild/rpmbuild/RPMS/x86_64/smart-ksmarttray-1.4.1-19.6.x86_64.rpm [ 125s] /home/abuild/rpmbuild/RPMS/x86_64/smart-ksmarttray-debuginfo-1.4.1-19.6.x86_64.rpm [ 125s] /home/abuild/rpmbuild/SRPMS/smart-1.4.1-19.6.src.rpm [ 125s] /home/abuild/rpmbuild/OTHER/_statistics [ 125s] /home/abuild/rpmbuild/OTHER/rpmlint.log [ 125s] /home/abuild/rpmbuild/OTHER/smart-gui-gtk-appdata.xml [ 125s] /home/abuild/rpmbuild/OTHER/smart-gui-qt3-appdata.xml [ 125s] /home/abuild/rpmbuild/OTHER/smart-ksmarttray-appdata.xml [ 125s] [ 125s] cloud128 finished "build smart.spec" at Sun Sep 15 08:49:44 UTC 2013. [ 125s] [ 128s] [ 111.945064] SysRq : Power Off [ 128s] [ 111.956820] Power down. [ 128s] build: extracting built packages... [ 129s] smart-1.4.1-19.6.x86_64.rpm [ 129s] smart-debuginfo-1.4.1-19.6.x86_64.rpm [ 129s] smart-debugsource-1.4.1-19.6.x86_64.rpm [ 129s] smart-gui-gtk-1.4.1-19.6.x86_64.rpm [ 129s] smart-gui-qt3-1.4.1-19.6.x86_64.rpm [ 129s] smart-ksmarttray-1.4.1-19.6.x86_64.rpm [ 129s] smart-ksmarttray-debuginfo-1.4.1-19.6.x86_64.rpm [ 129s] smart-1.4.1-19.6.src.rpm [ 129s] _statistics [ 129s] rpmlint.log [ 129s] smart-gui-gtk-appdata.xml [ 129s] smart-gui-qt3-appdata.xml [ 129s] smart-ksmarttray-appdata.xml built rpms Architecture: i586 rpmlint.log smart-1.4.1-19.2.i586.rpm smart-1.4.1-19.2.src.rpm smart-debuginfo-1.4.1-19.2.i586.rpm smart-debugsource-1.4.1-19.2.i586.rpm smart-gui-gtk-1.4.1-19.2.i586.rpm smart-gui-gtk-appdata.xml smart-gui-qt3-1.4.1-19.2.i586.rpm smart-gui-qt3-appdata.xml smart-ksmarttray-1.4.1-19.2.i586.rpm smart-ksmarttray-appdata.xml smart-ksmarttray-debuginfo-1.4.1-19.2.i586.rpm Architecture: x86_64 rpmlint.log smart-1.4.1-19.2.src.rpm smart-1.4.1-19.2.x86_64.rpm smart-debuginfo-1.4.1-19.2.x86_64.rpm smart-debugsource-1.4.1-19.2.x86_64.rpm smart-gui-gtk-1.4.1-19.2.x86_64.rpm smart-gui-gtk-appdata.xml smart-gui-qt3-1.4.1-19.2.x86_64.rpm smart-gui-qt3-appdata.xml smart-ksmarttray-1.4.1-19.2.x86_64.rpm smart-ksmarttray-appdata.xml smart-ksmarttray-debuginfo-1.4.1-19.2.x86_64.rpm -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 6

[opensuse-packaging] ruby req/provs
by Matwey V. Kornilov 24 Sep '13

24 Sep '13

Hi, What is going on in devel:languages:ruby:extensions ? I am trying to install rubygem-vagrant which says that nothing provides rubygem(1.9.1:net-ssh:2.6) >= 2.6.6, net-ssh has been bumped to 2.7.0 version and provides rubygem(1.9.1:net-ssh:2.7). This should be auto-detected and reported to the maintainer. It is possible to run deps-resolver for every successfully built package, however, I think it is resource-consuming. Who need the repo providing not-installable packages. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 9

[opensuse-packaging] Broken i810 driver
by Felix Miata 23 Sep '13

23 Sep '13

Will the regression fix patch in http://lists.freedesktop.org/archives/intel-gfx/2013-September/033668.html once committed filter into 12.2 and 12.3 updates automatically? Will something more be necessary to make it happen? Does it qualify to happen at all? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- 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] scala packaging help needed
by Denny Beyer 17 Sep '13

17 Sep '13

Dear all, help is needed to package the latest scala version. Builds are broken for versions newer than v2.9.2. How you can help: 1) If you know how and have successfully build scala from source on opensuse, please provide some informations about setup / commandline build call with opts / required dependencies or 2) go directly to devel:languages:scala/scala and fix build issues. cheers, Denny -- 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] run-one-*
by Michael Riess 16 Sep '13

16 Sep '13

Hi packagers, are there any Scripts packaged like the run-one-* here: http://blog.dustinkirkland.com/2013/09/introducing-run-one-constantly-run-o… -- Michael Riess -- 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] packaging Perl modules with no hard Perl version dependency
by Adam Spiers 13 Sep '13

13 Sep '13

Adam Spiers (aspiers(a)suse.com) wrote to opensuse-factory: > Hi, > > Back in 2011 I became maintainer of GNU Stow, and since then have > built an package which lives in the OBS system:packagemanager project: > > https://build.opensuse.org/package/show/system:packagemanager/stow > > I would like it to be in Factory too, so I have submitted a request: > > https://build.opensuse.org/request/show/198646 During the review for this SR, I noticed this rpmlint warning: stow.noarch: W: no-dependency-on perl-base 5.18.1 It seems that currently my .spec results in the package containing files such as: /usr/lib/perl5/vendor_perl/5.18.1/Stow.pm which will only be found by the default @INC of a perl-5.18.1 package. However, I know for a fact that my non-binary modules will work with *any* Perl >= 5.6.1, and so would prefer to install them to a non-versioned directory, e.g. $ perl -V:vendorlib_stem vendorlib_stem='/usr/lib/perl5/vendor_perl'; However this is not on the default @INC. In contrast, sitelib_stem does seem to be, although my understanding is that "vendor" packages such as those from OBS should install to vendor* paths rather than site*. Is there a good reason for vendorlib_stem not being on @INC, and if so, is it OK for me to install to sitelib_stem instead? Thanks! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 8

[opensuse-packaging] run-one-*
by Michael Riess 12 Sep '13

12 Sep '13

Hi packagers, are there any Scripts packaged like the run-one-* here: http://blog.dustinkirkland.com/2013/09/introducing-run-one-constantly-run-o… -- Michael Riess -- 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] CMake and OBS
by Sankar P 11 Sep '13

11 Sep '13

Hi, Are there any best known methods to package CMake based projects using the open build service ? Specifically what I am looking forward to is a simplified way of: 1) Installing all the libraries that CMake generates to /usr/lib (or) /opt/<company>/lib 2) Installing all the binaries that CMake generates to /usr/bin (or) /opt/<company>/bin 3) Populate BuildRequires: based on the find_package inside the CMakeLists.txt( 4) Building only a small subset of all the targets supported by the CMake file in a project. To explain on this point. Assume that my project has 10 targets and I need only 5 targets (3 binaries and 2 libraries that they depend) to be shipped to the users. So, I want a way to generate a tarball with only these 3 binaries and their dependencies (2 libraries in our case), which can be used in a build-service project. If I am not using OBS for distributing the binaries, I can easily build the two binary targets alone and can ship the resultant binaries. But if I want to use CMake what is the best way for achieving this instead of creating a tarball with the sources for all the 10 targets ? I googled around a bit before asking here but could not find any relevant information. I see that CMake is used heavily in KDE and so some of the openSUSE packagers would have run into similar requirements and wanted to find out the best practices for using CMake in OBS. Thanks. Sankar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 7

[opensuse-packaging] Reminder: Beta checkin this friday
by Stephan Kulow 11 Sep '13

11 Sep '13

Hi, I want to remind you that this friday is the checkin for the Beta (some call it Beta 1, but that somewhat implies that there is going to be another one, which is not in the plan :) All features should be done by then and submitted to openSUSE:Factory. Having it in SCM or the devel project does not help the Beta. Everyone without features to finish, please help getting the current number of build failures down - we're over 100 again ;( After the Beta I'm going to branch off openSUSE:13.1 and will only cherry-pick from factory. Greetings, Stephan -- A real gentleman never takes bases unless he really has to. -- Overheard in an algebra lecture. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4