Hi all,
just to notify you all, since quite some time you neither need to specify a
clean section nor a BuildRoot in your spec files. Official rpm.org rpm
(present in openSUSE) has reasonable defaults.
It happened recently that I already let a (games) package into Factory which
had no %clean setion. Whilst this was an accident, the question is on how we
want to handle this in the future.
You should be aware that this is not support on any SLE*. Generally, we
wouldn't care for Factory but if you want to build for SLE, you may want to
keep it. I was told that the games guys already started to convert their spec
files. So we need a decision.
--
Mit freundlichen Grüßen,
Sascha Peilicke
Hi, people! I have a following error when building a package:
application_ob.cpp:103:41: error: call of overloaded 'FormatFromExt(QString&)' is ambiguous
application_ob.cpp:103:41: note: candidates are:
/usr/include/openbabel-2.0/openbabel/obconversion.h:81:24: note: static OpenBabel::OBFormat* OpenBabel::OBConversion::FormatFromExt(const char*)
/usr/include/openbabel-2.0/openbabel/obconversion.h:84:24: note: static OpenBabel::OBFormat* OpenBabel::OBConversion::FormatFromExt(std::string)
Does anybody know how to fix it?
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
Lot of Java packages from JPackage/Fedora and other distros would build
"as is" on openSUSE/SLE except for a small "mess".
- SLE requires target bytecode set to 1.5. (because there is only 1.5
Java for all archs)
- This bytecode requirement is usually fixed by changing the ant call to
ant -Dant.build.javac.source=1.5 -Dant.build.javac.target=1.5.
However sometimes you need to pass similar options to javac or mvn-jpp
if they are invoked from the spec file.
- Even while SLE requires 1.5 bytecode, %{ant} evaluates to
"JAVA_HOME=/usr/lib64/jvm/java ant", the same as in openSUSE
- Some specs call %{ant}, but others just call ant.
I am tired of editing spec files only to add this SLE specific
requirement in order to keep packages building for all repositories. So
I am looking for a better solution for our Java:base repository.
One solution I was thinking was to create a helper package installing an
alias in /etc/profile.d so that ant becomes ant
-Dant.build.javac.source=1.5 -Dant.build.javac.target=1.5. Add this
package to the project config surrounded by if sle_version. A similar
alias would be added for mvn-jpp. However I could not get this to work
with rpm.
This would allow to build the packages that use "ant" or "mvn-jpp"
directly without touching the spec file. Fixing the spec files to use
%{ant} would still be possible in parallel, but is not worth while this
fixes do not go upstream and a similar macro would be needed for mvn-jpp.
I am open to hear more solutions. Another may be using source services
to "fix" the spec file, but that would require to add a _service per
package. Only have in mind that the goal is to not touch the spec file,
but either workaround it in the project setup, or to adapt SUSE
conventions so that other's packages become buildable.
And the ideal solution of course would be to fix all packages to use a
target macro, but this is only worth if these changes go upstream to
Fedora and JPackage.
--
Duncan Mac-Vicar P. - Novell® Making IT Work As One™
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix
Imendörffer, HRB 16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi everyone,
I'm wondering when OpenSuSE 11.4 will update Opera package to 11.50?
Or at least how to do it properly myself?
There were at least two security vulnerabilities fixed, they're not
critical but still...
--
Best regards,
Derek mailto:takeda@takeda.tk
How are we supposed to hack your system if it's always down!
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hello all,
openSUSE 12.1 Milestone 3 will be released next week, on
Thursday 14 July 2011.
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
hi there,
I'm still trying to package calibre >= 0.8 for opensuse.
Problems are:
1. calibre by now requires python 2.7.1 or higher but NOT python 3
2. the original author is about as cooperative and helpful as the german tax authorities on a
bad day. His general approach to any kind of support question is "If you're not running the
binaries from my website, go eff yourself."
...problem with that is, calibre is pretty much the only decent ebook reader management
software that is platform independent.
any ideas?
bye,
MH
--
Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 UWG und §823 I
BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede kommerzielle Nutzung der
übermittelten persönlichen Daten sowie deren Weitergabe an Dritte ist ausdrücklich untersagt!
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
On 06/30/2011 10:25 AM, Mathias Homann wrote:
> nope, my package works fine, I just don't know if the requirement "python>= 2.7.1" on
> calibre's website is just a quirk or actually justified...
I think the author actually meant "Don't use Python3". So please submit
updated calibre to Factory and we can move on :)
--
Ismail Dönmez - openSUSE Booster
SUSE LINUX Products GmbH
Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hallo list,
I am trying to build perl-5.10 für CentOS-5 64-Bit which fails. The
SLES-Version builds correctly. I got the package originally form
"opensuse_11.1-updates". I get several error-messages like these, when I
try to compile:
BEGIN failed--compilation aborted at
../../lib/ExtUtils/MakeMaker/Config.pm line 6.
Compilation failed in require at ../../lib/ExtUtils/MakeMaker.pm line 7.
BEGIN failed--compilation aborted at ../../lib/ExtUtils/MakeMaker.pm line 7.
Every line which is effected lookes like this:
use ExtUtils::MakeMaker::Config;
use Config ();
It seems that a Perl-Config-Module is missing in CentOS. I am no
Perl-expert, but I am wondering that a perl-module can be missing, when
I try to compile Perl from source.
You can have a look at my package here:
https://build.opensuse.org/package/show?package=perl&project=home%3Agrenzla…
Can anyone help to solve the problem?
Greetings
Grenzläufer
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org