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
Hello
I am trying to compile project called wflogs.
Project ->
https://build.opensuse.org/package/show?package=wflogs&project=home%3Adoiggl
Last log ->
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=wflog…
spec file ->
https://build.opensuse.org/package/view_file?file=wflogs.spec&package=wflog…
I have a link to another project called wfnetobjs too (no wfnetobjs rpm
installed yet)
Last set of wflog errors:
configure: error: wfnetobjs-incdir: no directory found, use configure
option
error: Bad exit status from /var/tmp/rpm-tmp.w8AYXU (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.w8AYXU (%build)
System halted.
Can someone assist me to compile this package please.
1. I think Ive got to install wfnetobjs rpm but dont know to set that in
the spec file.
2. Also I got to do the configure bit with a call like (but unsure how to
set in the spec file)
# ./configure --with-wfnetobjs-libdir=/usr/include/wallfire/
help appreciated.
Cheers Glenn
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
Many pure perl packages are not noarch just because of that
.packlist file in %perl_vendorarch. Is that file good for anything
in an rpm managed system? Ie could it be savely omitted from
packages?
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
I am not very happy with naming of nrpe and its sub-pkg.
we have nagios-nrpe-client, nagios-nrpe-server
While seeing the client pkg I'll be misled to install this pkg on the
remote box and vice versa. But the "client" pkg has to be installed on
the nagios box.
That's why I am thinking of:
- nagios-nrpe
it is the package to be installed on the remote box.
- nagios-nrpe-plugin or nagios-plugins-nrpe
just the name will let you associate to install this pkg on the nagios box.
What do you think ?
Any recommendations are welcome
Kind Regards
Chris
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi Dirk,
this single test actively hinders to correctly release an important package
(for me): hylafax+. Yup, one could argue, that using + in project names is
somewhat silly, but it's exactly, what is needed here. HylaFAX is
effectively forked by HylaFAX+. Now, the situation is unfortunate: hylafax
is released with major version 4 and 6, while hylafax+ is released as 5.
Keeping the name hylafax will replace the + version with the 6th version on
certain occasions, and those, who follow both developments will agree, that
this is the least desired. Either use one or the other but don't replace
them vice versa, please.
You will find my packages here:
https://build.opensuse.org/project/show?project=home%3Afrispete%3Ahylafax
What I would like to do is letting my hylafax+ package:
Provides: hylafax fax_daemon
Conflicts: hylafax sendfax
Obsoletes: hylafax
and all is well, up to 13-check-invalid-provides: the test boils down to:
$ echo hylafax | grep -E "^hylafax+[[:space:]]*$"
hylafax
$
while this is desired here:
$ echo hylafax | grep -G "^hylafax+[[:space:]]*$"
$
Using basic regex provide exactly the means of the unversioned package name
check, while not tripping over the '+'. According to the man page, only ?,
+, {, |, (, and ) lose their special meaning, thus:
$ echo hylafax+ | grep -G "^hylafax+[[:space:]]*$"
hylafax+
$
the + is matched literally, which is desired.
I agree, this case is pathologic, but I can't imagine any ill side effects
on this change, do you? It's a real pity to not being able to tag this
package correctly, e.g. allowing for a clean package replacement.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi, I've started getting the following build failure on lilypond factory
standard :-
|rm -f ./out/spacing-spanner.dep; DEPENDENCIES_OUTPUT="./out/spacing-spanner.dep ./out/spacing-spanner.o" g++ -c -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -ggdb -Woverloaded-virtual -I/usr/include/python2.6 -I/usr/include/python2.6 -fno-strict-aliasing -fmessage-length=0 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fwrapv -DHAVE_CONFIG_H -DNDEBUG -I./include -I./out -I../flower/include -I../flower/./out -I../flower/include -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -ggdb -O2 -finline-functions -g -pipe -pthread -I/usr/include/freetype2 -pthread -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -Wno-pmf-conversions -W -Wall -Wconversion -o out/spacing-spanner.o spacing-spanner.cc
spacing-spanner.cc: In static member function 'static std::vector<Grob*> Spacing_spanner::get_columns(Grob*)':
spacing-spanner.cc:41:35: error: expected primary-expression before '*' token
spacing-spanner.cc:41:36: error: expected primary-expression before '>' token
make[1]: *** [out/spacing-spanner.o] Error 1
Relating to the following line in ||spacing-spanner.cc :-
all = vector<Grob*>::vector<Grob*> (all.begin () + start,
The whole picture :-
vector<Grob*>
Spacing_spanner::get_columns (Grob *me_grob)
{
Spanner *me = dynamic_cast<Spanner*> (me_grob);
vector<Grob*> all (get_root_system (me)->used_columns ());
vsize start = binary_search (all, (Grob*)me->get_bound (LEFT),
&Paper_column::less_than);
vsize end = binary_search (all, (Grob*) me->get_bound (RIGHT),
&Paper_column::less_than);
all = vector<Grob*>::vector<Grob*> (all.begin () + start,
all.begin () + end + 1);
return all;
}
The "*>" doesn't give an error in the line "||Spanner *me =
dynamic_cast<Spanner*> (me_grob);" can somebody explain what to look for
in this error because I will most probably find a lot of these errors
after this one is fixed.
Thanks
Dave P
|
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi list,
I would like to make update of libpng to 1.4 branch. Today we have
package libpng12-0 in factory, for which
# rpm -q libpng12-0
libpng12-0-1.2.41-2.5.x86_64
# rpm -ql libpng12-0
/usr/lib64/libpng12.so.0
/usr/lib64/libpng12.so.0.41.0
But for 1.4 branch I get
/usr/lib64/libpng14.so.14
/usr/lib64/libpng14.so.14.0.0
Therefore, the name of new package should be libpng14-14?
Petr
Hi, I've packaged the DSSI plugin xsynth-dssi, the reason for doing this
was that it is needed for some example files that are packaged with
rosegarden, which I maintain. It is a very simple package which works
well and although there hasn't been a new version since 2004 the reason
for this that I got from Chris Cannam the main rosegarden developer in
the plugin department is that it just works.
It will live in multimedia:libs along with the other dssi plugins and of
course I will be happy to maintain it.
The package is in home:plater xsynth-dssi. The sources are found at :
http://dssi.sourceforge.net/download.html#Xsynth-DSSI
Thanks
Dave P
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
All,
I have a KPM package in my home directory that I created yesterday:
Package ohsm-ext4-v1.2-kmp (Project home:gregfreemyer:OHSM:OHSM_v1.2)
It's building for OpenSuse fine. Is there a way to build kernel
packages for other distros?
Thanks
Greg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org