September 2014 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] After 13.2 Beta1 is before 13.2 RC1
by Stephan Kulow 22 Sep '14

22 Sep '14

Hi, I thought long how to keep 13.2 in sync with Factory without loosing the abilty to cherry-pick, i.e. leave too intrusive changes in Factory. So I wrote a little tool that will create submit and delete requests for Factory changes to 13.2. Those requests will not be reviewed, but tested in 13.2's staging projects. To keep you in the loop, I create the requests as coming from the devel project, but they specify the source revision currently in openSUSE:Factory. This way you can see if I decline or accept a request to 13.2 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 1

[opensuse-packaging] Any plan to submit npm to Factory?
by marguerite 20 Sep '14

20 Sep '14

Forgot to CC opensuse-packaging ML. Hi, Joachim, Can we submit npm w/ all its dependencies and related tools like gyp to Factory before Beta? npm is now a separate package, thus the nodejs in Factory is now not able to build anything nodejs. But there're packages in Factory seem to rely on npm to build. So we now face a mut-be-done choice: 1. fix the packages in Factory by the "manual copy" method to avoid using of npm 2. drop the packages (and even nodejs itself) from Factory, guide our users to use d:l:nodejs to develop their nodejs applications. 3. submit the splitted stuff to Factory, which will be ?50 packages, before Beta. BTW, I don't like the "manual copy" method, which is: 1. changeable over releases (if upstream add new files, your package will success anyway) 2. too much things needed to be judged by human-being (like which one to copy?) 3. it may needs a local test environment for the packager, which will force the packager to be a real nodejs developer. So it'll break our BURP way of packaging. and actually this method can be done by robots like things done by our perl CPAN robots. It undervalues human-being, or even challenges human-being because we are much more easy to get things wrong than a robot. But anyway this way is super fast, we can package 50 packages for one night. Anyway if we want to keep both ways of packaging ("manual copy" && "patch package.json") available, we still need to make a decision whether or not to submit those development tools to Factory. Marguerite

1 0

[opensuse-packaging] epstopdf in openSUSE:Factory issues
by Simon 20 Sep '14

20 Sep '14

Hi All, Just updated the efl (enlightenment foundation libraries) to the latest release and noticed that it is failing to build for factory but is building fine for 13.1 the error is below. [ 737s] sh: epstopdf: command not found [ 737s] error: Problems running epstopdf. Check your TeX installation! [ 737s] Makefile:1469: recipe for target 'doc' failed [ 737s] make[1]: *** [doc] Segmentation fault [ 737s] Makefile:2666: recipe for target 'doc' failed [ 737s] make: *** [doc] Error 2 I will probably disable the doc generation for now but does anyone know where the more simple fix is, a search for eppstopdf in build.opensuse.org doesn't return anything. Cheers Simon Lees Enlightenment Maintainer - openSUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 4

[opensuse-packaging] Handling of suggests
by Todd Rme 18 Sep '14

18 Sep '14

Recently, a bunch of recommends in python-matplotlib were changed to suggests: https://build.opensuse.org/request/show/249989 Does YaST2 have any mechanism in place to install suggests? If not, what practical role do they play? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] rpmlint failure on argus
by Shawn W Dunn 17 Sep '14

17 Sep '14

So I've got an rpmlint failure in home:sfalken:branches:security/argus as follows: RPMLINT report: [ 20s] =============== [ 21s] Traceback (most recent call last): [ 21s] File "rpmlint.py", line 384, in <module> [ 21s] File "rpmlint.py", line 169, in main [ 21s] File "rpmlint.py", line 231, in runChecks [ 21s] File "BinariesCheck.py", line 326, in check [ 21s] IOError: [Errno 2] No such file or directory: '/tmp/rpmlint.argus-server-3.0.8-0.x86_64.rpm.6x3txz/usr/share/doc/packages/argus-server/support/Startup/argus' [ 21s] 1 packages and 0 specfiles checked; 0 errors, 7 warnings. [ 21s] Anybody got any pointers on where I can start to track down what is causing this failure? (other than telling me that rpmlint can't find the file it's telling me it can't find? I got that part =P)

2 1

[opensuse-packaging] A Problem getting docbook.xsl from the net during package build
by Lee Duncan 17 Sep '14

17 Sep '14

I am trying to get drbd utilties to build under OBS, but I'm getting an error I don't understand. It looks like the build is having problems getting http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl when trying to build man pages. The command that is failing is (basically): | xsltproc --xinclude --stringparam variablelist.term.break.after 1 \ | http://docbook.sourceforge.net/release/xsl/current/manpages /docbook.xsl \ | drbdsetup.xml When run manually on my local system this command works fine. But when run during the OBS build, it gets this error: I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl Do I have to do something special in my spec file to get networking to work during the build? -- Lee Duncan SUSE Labs -- 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] rpmlint: OSError: no such file or firecroty
by Matwey V. Kornilov 17 Sep '14

17 Sep '14

Hi, Could you please help me, what I do wrong? In the log following, rpmlint fails with a traceback. https://build.opensuse.org/package/live_build_log/home:matwey:branches:scie… [ 1193s] RPMLINT report: [ 1193s] =============== [ 1244s] Traceback (most recent call last): [ 1244s] File "rpmlint.py", line 384, in <module> [ 1244s] File "rpmlint.py", line 169, in main [ 1244s] File "rpmlint.py", line 231, in runChecks [ 1244s] File "DuplicatesCheck.py", line 63, in check [ 1244s] OSError: [Errno 2] No such file or directory: '/tmp/rpmlint.eso-midas-doc-13SEPpl1.4-4.1.i586.rpm.rjnAwx//usr/share/doc/packages/eso-midas-doc/volb/img498.gif' [ 1245s] 3 packages and 0 specfiles checked; 2 errors, 488 warnings. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] PENAWARAN SOUVENIR PERUSAHAAN TANPA BRAND
by Marketing 9 16 Sep '14

16 Sep '14

Dear customer Kami menerima pesanan gift perusahaan untuk product tertentu seperti: 1.travel adapter, (min 100pcs) 2.usb flashdisk, (min 100pcs) 3.payung (berbagai macam ukuran / min 300pcs) 4.Kemeja promosi (min 100pcs) 5.Kaos krah / oblong (min 500pcs) 6.Mouse promosi (min 500pcs) 7.power bank (min 200pcs) 8.PEN (MIN 500PCS HARGA MULAI RP.5.000) semua product kami tanpa merek, dan dapat di printing / sablon sesuai permintaan anda untuk mendapatkan penawaran harga yang baik, silakan hubungi kami kembali hubungi kami untuk info lebih lengkap locanojakarta(a)yahoo.com PHONE: 0812 90 59 1689 http://locanousb.blogspot.com/

1 0

[opensuse-packaging] current tor package in openSUSE 12.3
by Lars Edman ＠ LinuxSuSE 16 Sep '14

16 Sep '14

Hi! Not certain if this packaging list is the best to subscribe to? But start here. I run an updated openSUSE 12.3 x86_64 with openssl-1.0.1i-1.64.1.x86_64 Current tor-0.2.4.23-2.12.1.x86_64 from openSUSE-update seems to be built against OpenSSL-1.0.1h and leaves the following warning msg: sep 14 12:01:58.258 [Varning] OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000108f: OpenSSL 1.0.1h 5 Jun 2014; running with 1000109f: OpenSSL 1.0.1i 6 Aug 2014). I've experienced the same problem (and the "weird crashes") in my Slackware server after upgrading OpenSSL, and rebuilt tor. Will you rebuild tor and make an update, or do I have to build it myself? Tor also leaves another warning msg concerning the build: sep 14 12:01:58.258 [Varning] Tor was compiled with the --enable-bufferevents option. This is still experimental, and might cause strange bugs. If you want a more stable Tor, be sure to build without --enable-bufferevents. And finally an ordinary message concering the build of openssl: sep 14 12:01:58.258 [Meddelande] We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently lacks accelerated support for the NIST P-224 and P-256 groups. Building openssl with such support (using the enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH much faster. Best regards Lars -- 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] update seamonkey to version seamonkey-2.29.x from 2.26.x
by doiggl＠velocitynet.com.au 14 Sep '14

14 Sep '14

Hello FYI update SeaMonkey to version seamonkey-2.29.x from 2.26.x https://build.opensuse.org/package/show/mozilla:Factory/seamonkey src: https://download.mozilla.org/?product=seamonkey-2.29&os=linux&lang=en-US --Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1