Hey,
Dominique and I are currently wondering what to do wrt libexecdir for
evolution-data-server. Should we leave it unchanged (so files will be in
/usr/lib) or should we change it to /usr/lib/evolution-data-server?
If the latter, is there any reason this is not done automatically?
Also, hrm, would rpmlint have ways to warn about packages that put
binaries in libdir instead of libexecdir? (I can find a few of them here
with a grep)
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
Hi everybody,
We know them all and some of us get frustrated by them:
lints and brp checks aborting our builds, even though make and make
install perfectly passed through (well, one correction here already:
APPARENTLY perfectly passed).
I do not argue against the checks at all and I think they are a good
thing (tm).
But sometimes they can be a little bit cryptic and most of the time
require work.
so I started a series of blog posts (2 so far) which try to address
them. Please bare with me, I'm no hard core crack coder, but I will
try to summarize the usual causes and solutions to a problem. Not in
every case will the provided solution fit and if you're not sure about
correctness in your package: discuss the matter with upstream. Anyway,
once you produce a patch, you should always make sure upstream gets it
too.
So what were the blog posts about so far?
Part 1: how to fix brp and rpmlint warnings ? today:
Expression compares a char* pointer with a string literal
http://dominique.leuenberger.net/blog/?p=151
Part 2: how to fix brp and rpmlint warnings ? today:
I: Program causes undefined operation
(likely same variable used twice and post/pre incremented in the same
expression)
http://dominique.leuenberger.net/blog/?p=178
As noted on the first entry, i will gladly take recommendations for
which errors you would like to see an entry. I will try to write them
up, likely 1 or 2 per week (I am actually not that much of a writer... 0
Hope the series is useful to you... If it saves you a few minutes here
and there, then it is.
Best regards,
Dominique
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
The licenses package is 300KB on the live cd and the only files
linked into are gpl licenses - in addition it's very unclear if links
to licenses are really ok. So I submitted a fix for all packages in
factory I could find using licenses - for some I had to include
a license.
The licenses package will soon disappear, so please review and
forward the requests.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
is there a maintenance window? Where was it announced (so that I could
subscribe to the feed)? How long will it take?
Generally there seems to be nothing like a status page for openSUSE
services. Would be genuinely useful.
--
Stefan Seyfried
"Dispatch war rocket Ajax to bring back his body!"
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi!
I have a question. I want to a package which heavily uses icons from another
one. But the OBS system does not allow to built it: it says "icon file not
installed" even though the dependency on a package that contains the
necessary icon is included. What can I do to successfully install this
package?
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
I'm busy fighting with the python3-base-3.2 build, which seems to be unpredictable atm, due to blender (against the protests of distro
packagers) switching to that version. The 11.4 x86_64 build fails in devel:languages:python:Factory but all the others succeed, I've had
varying build results by linking home:plater:blender python3-base to home:plater:blender python3 and devel:languages:python:Factory
python3, when linked to devel:languages:python:Factory python3 it mimics the devel build but when linked to home:plater:blender python3
I've had complete build failures and all x86_64 failures with i586 successes with a fresh untouched branched python3 after only adding a
fedora conditional for BuildRequires first. I understand that the build service servers aren't 100% in fact the connection was down again a
few moments ago and up again now, I don't know if this has any effect that can cause such build behaviour? It also builds differently on my
local x86_64 11.4 system using rpmbuild.
As it stands now, I've added a few build requirements which seemed to be missing and have experienced an i586 failure due to -pg and
-fomit-frame-pointer being incompatible and redefining $RPM_OPT_FLAGS omitting -fomit-frame-pointer (without diving into gcc) can this
cause problems?
It looks like I've a successful build atm but only after changing a few build options. Here is the diff with comments:
%build
# use rpm_opt_flags
+# Redefine opt flags due to error: -pg and -fomit-frame-pointer are incompatible
+export RPM_OPT_FLAGS="-fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g"
export OPT="$RPM_OPT_FLAGS"
#export OPT="-O0 -g"
@@ -201,10 +210,12 @@
--docdir=%{_docdir}/python \
--enable-ipv6 \
--with-fpectl \
- --enable-shared
+ --enable-shared \
+ --with-cxx-main=%{_bindir}/c++ configure started asking for a c++ compiler
LD_LIBRARY_PATH=.:$LD_LIBRARY_PATH \
- make %{?_smp_mflags} profile-opt
+ make %{?_smp_mflags} This is the change that had the most effect on the build
succeeding.
+# profile-opt
%check
# test_file fails in autobuild env - "stdin.seek(-1)" wrongly succeeds. probably an issue with autobuild's stdin
@@ -244,10 +255,10 @@
# cleanup parts that don't belong
for so in _md5 _sha1 _sha256 _sha512; do
- rm $RPM_BUILD_ROOT%{sitedir}/lib-dynload/$so.*
+ rm -f $RPM_BUILD_ROOT%{sitedir}/lib-dynload/$so.* _md5 and _sha1 don't exist, I haven't checked the others but when I see
things missing that existed before I get worried.
done
for dir in curses dbm sqlite3 tkinter; do
- rm -r $RPM_BUILD_ROOT%{sitedir}/$dir
+ rm -rf $RPM_BUILD_ROOT%{sitedir}/$dir
done
# install site-specific tweaks
@@ -277,7 +288,7 @@
# move idle config into /etc
install -d -m 755 ${RPM_BUILD_ROOT}/etc/idle3
-(
+(
cd ${RPM_BUILD_ROOT}/%{sitedir}/idlelib/
for file in *.def ; do
mv $file ${RPM_BUILD_ROOT}/etc/idle3/
I use kwrite for spec files and it saves in UTF8 also removes trailing white spaces.
I would appreciate expert help with this after which python3-3.2 could hopefully be ready for tumbleweed, blender is about to be 2.57 RC1
and will be released in about a month, the current blender in 11.4 is beta plus svn and would have been newer if the switch to python 3.2
hadn't happened. I think blender is the main consumer of python3 along with a couple of gnome apps.
Thanks
Dave P
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Donnerstag, 31. März 2011 sent speilicke :
> State of submit-request #65647 was changed by saschpe:
>
> new -> declined
>
> Comment:
> description is >400 lines, too long :-)
>
Where is a limit documented?
Greetings, Stephan
--
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 building a new branding package for kdebase4-workspace. Apparently
I managed to get it built but when I ask zypper to install it
I got a (obviously expected) conflict with
kdebase4-workspace-branding-(openSUSE|upstream).
The insteresting thing is zypper only provides one solution for the conflict:
Solution 1: do not install kdebase4-workspace-branding-IFBa-1.1-4.1.x86_64
Instead of both "do not install branding-IFBa" and "deinstallation of
kdebase4-workspace-branding-*"
spec file: http://pastebin.com/pV9ngFYT
build log: http://pastebin.com/b5uQ8kEf
I've built a copy of kdebase4-openSUSE in my home OBS repository and
the generated package is installed as expected (zypper presents both
solutions)
Any hint ?
Thanks in advance,
Sandro Andrade
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hello Mates,
atm i'm trying to update my openEMR Version.
But sadly he breaks. OSC says, that Folder "Documentation" can't found.
But it is present in the Source.
Maybe i have a mistake?
Greetings
Sascha
--
Sincerely Yours
Sascha Manns
open-slx Community & Support Agent
openSUSE Membership Comitee
openSUSE Marketing Team
Web: http://saigkill.homelinux.net
German Community Portal: http://community.open-slx.de
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
All,
I'm trying to package a CPAN package whose license statement at cpan is:
===
Copyright (C) 2004 Squirrel Consultancy
This library is free software; you can redistribute it and/or modify
it under the same terms as Perl itself, either Perl version 5.6.0 or,
at your option, any other version of Perl 5 you may have available.
===
What do I put in the specfile as a license?
Thanks
Greg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org