September 2010 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Bad file descriptor in log
by doiggl＠velocitynet.com.au 27 Sep '10

27 Sep '10

Hello, Fyi there are lots of errors in log [1] include a sample of them here. [1] https://build.opensuse.org/package/live_build_log?arch=x86_64&package=php5&… Glenn ../configure: line 27709: 6: Bad file descriptor ../configure: line 27831: s/[^a-zA-Z0-9]/_/g: No such file or directory ../configure: line 27852: 5: Bad file descriptor ../configure: line 27853: 6: Bad file descriptor ../configure: line 27879: ac_fn_c_try_run: command not found ../configure: line 27890: 5: Bad file descriptor ../configure: line 27891: 6: Bad file descriptor ../configure: line 27892: as_fn_error: command not found ../configure: line 27903: 5: Bad file descriptor ../configure: line 27904: 6: Bad file descriptor ../configure: line 28251: s/[^a-zA-Z0-9]/_/g: No such file or directory ../configure: line 28298: 5: Bad file descriptor ../configure: line 28299: 6: Bad file descriptor ../configure: line 28336: 5: Bad file descriptor ../configure: line 28337: 6: Bad file descriptor ../configure: line 28645: 5: Bad file descriptor ../configure: line 28646: 6: Bad file descriptor ../configure: line 28684: 5: Bad file descriptor ../configure: line 28685: 6: Bad file descriptor ../configure: line 29153: 5: Bad file descriptor ../configure: line 29154: 6: Bad file descriptor ../configure: line 29192: 5: Bad file descriptor ../configure: line 29193: 6: Bad file descriptor ../configure: line 29989: 5: Bad file descriptor ../configure: line 29990: 6: Bad file descriptor ../configure: line 30027: 5: Bad file descriptor ../configure: line 30028: 6: Bad file descriptor ../configure: line 30036: 5: Bad file descriptor ../configure: line 30037: 6: Bad file descriptor ../configure: line 30054: 5: Bad file descriptor ../configure: line 30055: 6: Bad file descriptor ../configure: line 30445: 5: Bad file descriptor -- 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] boinc-client to sale
by Sascha 'saigkill' Manns 23 Sep '10

23 Sep '10

Hello Mates, since a few years i'm serving as Maintainer of the BOINC Package. Sadly the last Versions can't driven correctly. So i would like to give the Maintainer Job another, better Person. Maybe we can place then a running Version into Factory. All needed Files (my latest Status) can seen under home:saigkill:boinc. cu Sascha -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.saschamanns.de Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) Open-SLX : Linux convenient, simple, secure and complete

1 0

[opensuse-packaging] Compiler Error
by Sascha 'saigkill' Manns 23 Sep '10

23 Sep '10

Hello Mates, i'm trying to build mixdtv in my home:saigkill. At the Moment it breaks: http://paste.opensuse.org/19510065 Can anyone see, why the build breaks? -- Sincerely yours Sascha Manns open-slx GmbH openSUSE Community & Support Agent openSUSE Marketing Team Blog: http://saigkill.wordpress.com Web: http://www.saschamanns.de Web: http://www.open-slx.de (openSUSE Box Support German) Web: http://www.open-slx.com (openSUSE Box Support English) Open-SLX : Linux convenient, simple, secure and complete

2 3

[opensuse-packaging] [reminder] openSUSE 11.4 Milestone 2 is next week
by openSUSE Roadmap Reminder 22 Sep '10

22 Sep '10

Hello all, openSUSE 11.4 Milestone 2 will be released next week, on Thursday 30 September 2010. Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday. For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap Thanks, -- openSUSE Roadmap Reminder -- 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] Packaging python3 modules
by Vincent Untz 18 Sep '10

18 Sep '10

Hi, Just checking: I'm starting to see some modules which have a python3 and a python2 version (python-cairo, for example). Is keeping python-cairo for python2 and creating python3-cairo the right thing to do? Will it stay this way in the long term, or will we switch to the opposite scheme (python2-cairo for python2 and python-cairo for python3)? Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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] Devel packages: Handling factory and older releases
by Andreas Jaeger 17 Sep '10

17 Sep '10

I've split up a devel package from sane-backends for openSUSE:Factory. I have added to packages needing the devel library the following: %if 0%{?suse_version} > 1130 BuildRequires: sane-backends-devel %else BuildRequires: sane-backends %endif This allows the package, e.g. xsane, to build in an original 11.3 environment. So, now the package works fine - unless sane-backends and the package are in the same devel project since the split was done unconditionally in sane- backends. Now the package xsane will not build for older releases since it has buildrequires on sane-backends but sane-backends in the same devel project has a separate devel package that would need to be required. So, how to solve this the best way? Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

7 10

[opensuse-packaging] Question about RIS (Repository Index Service)
by Vincent Untz 16 Sep '10

16 Sep '10

Hi, There's a feature in libzypp that we'd like to use to make it easier for people to use the GNOME:STABLE repositories. This is RIS: http://old-en.opensuse.org/Standards/Repository_Index_Service I played a bit with it, and it's all working fine. Except that there's this behavior: "Newly added repositories should be added as disabled." So we tell people to run "zypper as <url> <alias> && zypper refs", but it's not enough, and we have to tell them to manually enable the repos created by the service. It could be argued that it's not that much of an issue, but if we change the RIS index, then new repos have to be manually enabled again. Is there any way to make this just work? Or do other people using RIS have a suggestion to improve the workflow for the user? Note that I do understand that for security, we'd want the repos to be disabled by default. But, well, it kind of makes RIS less useful :/ Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- 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] Bringing SCPM back in the product
by Philippe Andersson 15 Sep '10

15 Sep '10

Hello list, I recently volunteered as maintainer for SCPM -- my goal is to bring it back into the official product by 11.4. Under the guidance of Vladimir Botka, I was able to successfully build SCPM for "Factory", and to install the resulting RPMs on a vanilla but fully updated OS 11.3 install. I also verified that the installed binary did accept to run. My repository is still unpublished at this stage. pan@kermit:~> osc r home:phandersson:branches:openSUSE:Dropped scpm openSUSE_Factory x86_64 succeeded (repository is unpublished) openSUSE_Factory i586 succeeded (repository is unpublished) Can any of you please advise as to what the next step should be ? Thanks in advance, Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan(a)iba-group.com <http://www.iba-worldwide.com>

2 6

[opensuse-packaging] syslog-ng library packaging
by Peter Czanik 14 Sep '10

14 Sep '10

Hello, With version 3.2, syslog-ng was modularized. I'm trying now to package the git version at https://build.opensuse.org/package/show?package=syslog-ng32&project=home%3A… and get the following error messages at the end of compilation: syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libafsocket-notls.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libdbparser.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libafsocket-tls.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libaffile.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/libsyslog-ng.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libdummy.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libsyslogformat.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libafprog.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libafuser.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libconfgen.so syslog-ng.i586: E: devel-file-in-non-devel-package (Badness: 50) /usr/lib/syslog-ng/libcsvparser.so A development file (usually source code) is located in a non-devel package. If you want to include source code in your package, be sure to create a development package. Obviously these files are not source code, and http://en.opensuse.org/openSUSE:Shared_library_packaging_policy says, that: "Shared libraries which are used solely and only by programs from the containing main package must be packaged into the main rpm, without a separate lib$NAME$NUM rpm. " So, what's wrong here? Note: by the time of writing, I still get "state is outdated" Note2: the package is far from finished, most of the libs should go to /lib/syslog-ng instead (except for those with dependencies to /usr), so they are available even if /usr is unaccessible. Bye, CzP -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] The history behind docdir?
by Cristian Morales Vega 14 Sep '10

14 Sep '10

Can someone explain me why doc dir is handled the way it is? I mean: - Why %configure sets every dir but docdir? - Why we put docs in /usr/share/doc/packages instead of /usr/share/doc/ (as Fedora does)? This way there doesn't seems to be any specified function for plain /usr/share/doc and it just includes documentation of (wrong?) packages. - %_defaultdocdir vs %_docdir? - %_docdir_fmt is %%{NAME} while in Fedora it also includes the version. Also, there is any way to use it in the %files section? I would expect to be able to do something like %configure --docdir=%{_docdir}/%_docdir_fmt ... %files %{_docdir}/%_docdir_fmt - When the build system installs documentation in %_datadir/%name, should it be moved to %_docdir? Thanks. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1