I'm trying to update lilo to version 23.2, but I keep getting this
error:
cp lilo $DESTDIR/sbin/lilo
cp: cannot create regular file `/sbin/lilo': Permission denied
make[1]: *** [install] Error 1
make[1]: Leaving directory
`/usr/src/packages/BUILD/lilo-23.2/lilo-23.2/src'
make: *** [install] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.MMYvgO (%install)
What's going wrong here?
--
Per Jessen, Zürich (16.1°C)
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
There was a strange bug about missing graphics in our docs
(bnc#718743). It turned out inkscape was not able to convert SVGs to
PNGs because gnome-vfs2 lacked libfam. After adding
"BuildRequires: fam" it worked fine.
Is this the proper fix? Why is this needed?
"rpm -q --requires gnome-vfs2" lists libfam.so.0()(64bit), thus I'd
expect that libfam would get installed automatically?
--
Karl Eichwalder SUSE LINUX Products GmbH
R&D / Documentation Maxfeldstraße 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
Hi,
In the lyx package I specify the paths for the myspell dictionaries and
the mythes thesaurus files, so that spellingcontrol and thesaurus is
working out of the box without the need for the user to set the right
paths, but this is only usefull when there are dictionaries and
thesaurus files installed. Installation of lyx does not trigger this at
the moment. Using lyx I never noticed this, because I have libreoffice
installed, and thus the spellingdictionary and thesaurus file for my
language.
My question: what do I add to the spec file to trigger the installation
of the myspell dictionary and libreoffice-thesaurus in the right language?
Regards,
Cor
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hello Mates,
yesterday i've updated TeXmacs to the present version.
Now it builds for 11.3 and 11.4, but not for Factory. It gives me:
In file included from Guile/Glue/glue.hpp:19:0,
from ./Guile/Scheme/evaluate.cpp:17:
Guile/guile.hpp:54:22: fatal error: guile/gh.h: No such file or directory
compilation terminated.
The full bl can viewed there: http://bit.ly/qAijYd
As i'm understanding it needs guile, but guile is included in Factory and it
builds.
Maybe anyone has an Idea?
Have a nice day
Sascha
--
Sincereley yours
Sascha Manns
open-slx GmbH
Community & Support Agent
openSUSE Marketing Team
http://saigkill.homelinux.net
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi there,
- dunno if this is the right forum for such requests - if not, please
suggest a different/the right one ;-) -
can the Banshee/SLE_11_SP1 repo be re-established please? This
application is really superior to the other potential candidates (which
are mostly also not supported anymore).
TIA, cheers.
l8er
manfred
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
vuntz mentioned it might be good to inform people, though I doubt anyone
is going to read this..
As you may have noticed I am going through all factory packages to
implement a few of the specfile guidelines[1] in semi-automated fashion,
among them the following subtasks:
[1] http://en.opensuse.org/openSUSE:Specfile_guidelines
automated:
- removal of '# norootforbuild'
- removal of 'AutoReqProv: on' since this is default anyway
manual:
- removal of Authors list, no longer desired in factory
- removal of %clean section, no longer required
- removal of rm -Rf %buildroot in %install when spotted, [1]
- changing %{?%jobs:-j%jobs} to %_smp_mflags, [1]
- adding %{?_smp_mflags} whereever there is none, or
- tagging places more explicitly where parallel build does not work
by utilizing the grepable string "-j1" plus a comment if none exists
- replacing CFLAGS="$RPM_OPT_FLAGS" ./configure --bindir=%_bindir
--infodir=%_infodir ... (and similar) by %configure [shorter]
- shlib policy where it seems quick
- killing old %changelog (because it's in .changes already)
Keep in mind:
- obs-service-format_spec_file has been configured for a handful of
projects and is adding more line noise besides my actual changes
So far.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hey,
Here are some notes about the packaging guidelines BoF we had on
Wednesday, at the openSUSE Conference.
It'd be great to reflect what seems to have been agreed in our
documentation. Any volunteer for that?
Cheers,
Vincent
=====
Our packaging guidelines documentation
- lots of discussion about the effort that was started a while ago to
merge with Fedora
- rough agreement that we should try to push the parts we both agree on
(ie, most of the documentation) upstream, at rpm.org
- needs to be discussed with Fedora
Having a smaller set of groups
- possibly use the same set as Fedora
- improve spec-cleaner to do the automatic replacement
- need to drop the groups view in the yast software installer
Patch tags
- long discussion about the merits of tags in the .spec file and inline
description inside each patch
- Recommendation (not enforced): use patch tags in .spec file as it
makes things easier to review, and it's easier to jump in a package.
However, in the end, it's up to the maintainer to choose the way he
prefers
- Rule: choose at least one of tags in .spec file or inline
description, so that patches are described.
- Rule that should be enforced: whatever patch guideline is used by a
package, it should be applied consistently. This means: if you update
a package using one approach, please use the same approach.
Shared library packaging policy
- we have a whitelist of packages that don't have to move to SLPP.
That's blocking the enforcement of SLPP.
- robjo will update the whitelist so that it tracks a list of
packages/versions, instead of a list of packages; that means when a
new version of a whitelisted package arrives, SLPP should be applied.
- Reminder that it's wrong to obsolete an old version of the library:
libfoo2 should not obsolete libfoo1.
--
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!
I'm trying to build gtk3 application Xiphos [1] with webkit backend for
oS:Factory, but compilation fails with the following error:
[ 45/130] cxx: src/main/display.cc -> build/default/src/main/display_1.o
In file included from ../src/gui/debug_glib_null.h:36:0,
from ../src/backend/sword_main.cc:52:
../src/gui/gui.h:8:32: fatal error: gconf/gconf-client.h: No such file
or directory
compilation terminated.
Please help to fix this problem. gconf2-devel package is installed.
[1] https://build.opensuse.org/package/show?package=xiphos&project=home%
3Akkirill
--
Kirill Kirillov
<><
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
In build.opensuse.org/home:jengelh:dev/gf2x, I have a new package gf2x,
where I decided to call the shared library package "libgf2x-1" instead
of "libgf2x1" for purposes of clarity. Do Factory maintainers concur
with this stance? If so, the shlib-policy check of rpmlint may need to
be relaxed to allow the extra dash when $pkgname =~ /\d\w$/ (I don't
see it yet necessary for \d\w+).
libgf2x-1.x86_64: E: shlib-policy-name-error (Badness: 10000) libgf2x1
Your package contains a single shared library but is not named after its
SONAME.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
Is there an example or documentation related to integrating Systemd in
spec files showing how to install and activate service files if system
has systemd enabled.
Ideally I would like to support both systemd enabled and the traditional
init system in the spec.
Thanks
Togan
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org