Hi all,
as you know I wrote a post about Fedora Packaging Guidelines [1]. I was
working on it during last three weeks (but a little, so it takes a long time
:)) and nowadays I'm ready to import a Fedora's content to en.opensuse.org
wiki. Now it is on pack.suse.cz [2]. I also checked that none of that page
conflicts with an existing content on openSUSE wiki, so it can be imported
easily.
Tom Callaway [3] from RedHat confirms me that a Guidelines are under Open
Publication License [4] and we can use it for SUSE without restrictions. He
was also interested on future collaboration and offers some meeting on
LinuxTag - it would be nice if anyone from SUSE will be ready to start a
discussion.
Before import I'd like to ask:
Which pages should be excluded for openSUSE? Some pages seems that they are
not interesting for SUSE (like Packaging:OldJPackagePolicy [5],
Packaging:SugarActivities [6]). Import it, or don't?
Second one is how to edit the text and adapt it for SUSE? Change the existing
text or leave it and add a SUSE specifics to the beginning or end of page (as
suggests Vladimir)? The second way should help us with synchronizing of
changes.
After that I'll add a warning [7] on the beginning of every page to prevent
that some users will use those guidelines and ask for help with editing ;-)
[1] http://lists.opensuse.org/opensuse-packaging/2009-02/msg00043.html
[2] http://pack.suse.cz/mvyskocil/fedora-packaging-guidelines/
[3] https://fedoraproject.org/wiki/TomCallaway
[4] http://fedoraproject.org/wiki/Legal/Licenses/OPL
[5] http://fedoraproject.org/wiki/Packaging:OldJPackagePolicy
[6] http://fedoraproject.org/wiki/Packaging:SugarActivityGuidelines
[7] http://en.opensuse.org/Template:Warning1
Best regards
Michal Vyskocil
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
the new module-init-tools, which will appear in Factory soon, deprecated
/etc/modprobe.conf(.local) and only uses /etc/modprobe.d/*.conf
configuration files (files without the .conf suffix are still read, but
cause a warning). I tried to find and fix packages that install modprobe
config files, but in case I missed some, the fix is simple:
change /etc/modprobe.d/$name to /etc/modprobe.d/50-$name.conf.
Also, mkinitrd should be updated to not copy /etc/modprobe.conf* if it's
not there.
Michal
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear fellow packagers,
for 11.2 i plan to drop the package python-numeric.
Reasons? Well, it's long abandoned original version of a project that is
now called NumPy. NumPy is not source compatible with Numeric, so it
lives in its own package called python-numpy. New(er) projects that used
to depend on Numeric now depend on NumPy.
If your package depends on python-numeric, please review it. It's likely
that you will be able to either remove the dependency, or painlessly
switch to python-numpy.
If not, say so now or be silent forever ;e)
PDB says that there's an explicit dependency on python-numeric in these
packages:
package-lists-openSUSE-KDE-cd
package-lists-openSUSE
package-lists-openSUSE-GNOME-cd
package-lists-openSUSE-images
(i assume that it's because of some of the following)
dia
fonttools
python-wxGTK-examples
python-gtk
pythoncad
python-gnome-extras
python-gnome
inkscape
python-gtk and python-gnome are mine, i'll handle them; i'm Ccing
maintainers of the others.
regards
m.
- --
(if you have any comments, please CC me in the reply, otherwise my
replies will break threads. that is a bug in my way of using the
mailinglist, which is not yet fixed)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAknSFkIACgkQjBrWA+AvBr93aACgh5a2Q2cI4UC8MKaBxEyDtDXU
W6AAoK1rL/RugrjRHmsfXzZ1KkkNWKR1
=TIbW
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hello Mates,
actualy i'm try to build skrooge. But in the CMakeLists.txt is the
following:
########### install files ###############
INSTALL(TARGETS skrooge DESTINATION ${BIN_INSTALL_DIR} )
INSTALL(FILES ${PROJECT_BINARY_DIR}/skrooge.desktop DESTINATION
${XDG_APPS_INSTALL_DIR} )
#INSTALL(FILES ${PROJECT_BINARY_DIR}/skrooge.desktop DESTINATION
${XDG_APPS_INSTALL_DIR}/../kde/ ) #CORRECTION BUG 2256687 on ubuntu
8.04
INSTALL(FILES ${PROJECT_BINARY_DIR}/x-skg.desktop DESTINATION
${MIME_INSTALL_DIR}/application/ )
INSTALL(DIRECTORY theme DESTINATION ${DATA_INSTALL_DIR}/skrooge
FILES_MATCHING PATTERN "*.css" PATTERN ".svn" EXCLUDE PATTERN
"CMakeFiles" EXCLUDE)
kde4_install_icons( ${ICON_INSTALL_DIR} )
That means, that i have 2 *.desktop Files (skrooge.desktop and x-
skg.desktop).
So i have placed in the Spec: %suse_update_desktop_file skrooge Finance
But now comes the Error: + /usr/lib/rpm/suse_update_desktop_file.sh --
project 'home:saigkill / openSUSE_Factory' --project home:saigkill --
basedir /usr/src/packages/SRPMS skrooge Finance
+ /usr/lib/rpm/suse_update_desktop_file.sh --project 'home:saigkill /
openSUSE_Factory' --project home:saigkill --basedir
/usr/src/packages/SRPMS -i skrooge Office Finance
`/usr/src/packages/BUILD/skrooge-0.2.6/skrooge/skrooge.desktop' ->
`/var/tmp/kde4-skrooge-0.2.6-
build/usr/share/applications/skrooge.desktop'
ERROR: suse_update_desktop_file: skrooge has multiple desktop files
I the last Version i have comment out the desktop Files in
CMakeLists.txt and create my own skrooge.desktop.
But i think it is not good that x-skg.desktop is missing.
Is it possible to fix this?
--
Sincereley yours
Sascha Manns
openSUSE Marketing Team
openSUSE Build Service
openSUSE Features Screening Team
Web: http://saschamanns.gulli.to
Project-Blog: http://lizards.opensuse.org/author/saigkill
Private-Blog: http://saschasbacktrace.blogspot.com
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
How is the games group supposed to be used?
Tower Toppler want to set itself in the games group with setgid set so
it can write on a global hiscore file also set at games group. It
seems ok to me, but rpmlint complains about the setgid.
Should I ignore rpmlint or it is correct and users able to play games
are supposed to be in the games group to start with? If my memory
doesn't fails in openSUSE, by default, users aren't in the games
group... since an user that plays games hasn't to know about users and
groups that would be a bug.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hi,
what is the proposed way to mirror SLE11 Updates?
yup is not included in SLE11, 11.1 and factory. And the SLE10 yup does not
do it.
--
Mit freundlichen Gruessen,
Andreas Vetter
Informations- und Kommunikationstechnik
Fakultaet fuer Physik und Astronomie
Universitaet Wuerzburg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Hello,
I would like to add a license to some repositories, similarly like the main
oss repository has (in order to provide some information about the repository
users should know). Looking at the oss repo I found out this is handled by the
license.tar.gz file in the root repo directory, but I have't managed to find
out any details about it. While I can guess the format for it, I have no idea
how to actually add such a file to a repository in the OBS. Can somebody
provide me some information about this?
Thanks
--
Lubos Lunak
KDE developer
--------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: l.lunak(a)suse.cz , l.lunak(a)kde.org
Lihovarska 1060/12 tel: +420 284 028 972
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Project: home:saigkill
Package: libdbus++
Hello Mates,
after upgrading to Version 0.6.1 i become the following Errors:
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../src -fmessage-
length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
-fasynchronous-unwind-tables -Wall -Wctor-dtor-privacy -Wnon-virtual-
dtor -Woverloaded-virtual -Wno-deprecated -Wunused-parameter -Wunused-
variable -Wunused-value -Wunused-function -I/usr/include/dbus-1.0 -
I/usr/lib64/dbus-1.0/include -DDBUSPP_WITH_THREAD -I../../include -
fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -
funwind-tables -fasynchronous-unwind-tables -MT dbus.lo -MD -MP -MF
..deps/dbus.Tpo -c ../dbus.cpp -fPIC -DPIC -o .libs/dbus.o
In file included from ../../include/dbus++/service.hpp:27,
from ../../include/dbus++/server.hpp:26,
from ../../include/dbus++/dbus.hpp:26,
from ../dbus.cpp:22:
.../../include/dbus++/detail/connection.hpp:64: error: 'condition' in
namespace 'boost' does not name a type
In file included from ../../include/dbus++/dbus.hpp:30,
from ../dbus.cpp:22:
.../../include/dbus++/detail/timer.hpp:63: error: 'condition' in
namespace 'boost' does not name a type
make[3]: *** [dbus.lo] Error 1
Does anyone know what th error is?
--
Sincereley yours
Sascha Manns
openSUSE Marketing Team
openSUSE Build Service
openSUSE Features Screening Team
Web: http://saschamanns.gulli.to
Project-Blog: http://lizards.opensuse.org/author/saigkill
Private-Blog: http://saschasbacktrace.blogspot.com
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
Project: home:saigkill
Package: libdbus++
Hello Mates,
i have an Question about my libdbus++ Build.
After autoreconf i get:
+ cd libdbus++-0.6.0
+ autoreconf -fi
src/debug/Makefile.am:9: Libtool library used but `LIBTOOL' is undefined
src/debug/Makefile.am:9: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
src/debug/Makefile.am:9: to `configure.in' and run `aclocal' and
`autoconf' again.
src/debug/Makefile.am:9: If `AC_PROG_LIBTOOL' is in `configure.in', make
sure
src/debug/Makefile.am:9: its definition is in aclocal's search path.
src/release/Makefile.am:7: Libtool library used but `LIBTOOL' is
undefined
src/release/Makefile.am:7: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
src/release/Makefile.am:7: to `configure.in' and run `aclocal' and
`autoconf' again.
src/release/Makefile.am:7: If `AC_PROG_LIBTOOL' is in `configure.in',
make sure
src/release/Makefile.am:7: its definition is in aclocal's search path.
src/thread/Makefile.am:9: Libtool library used but `LIBTOOL' is
undefined
src/thread/Makefile.am:9: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
src/thread/Makefile.am:9: to `configure.in' and run `aclocal' and
`autoconf' again.
src/thread/Makefile.am:9: If `AC_PROG_LIBTOOL' is in `configure.in',
make sure
src/thread/Makefile.am:9: its definition is in aclocal's search path.
src/threadd/Makefile.am:10: Libtool library used but `LIBTOOL' is
undefined
src/threadd/Makefile.am:10: The usual way to define `LIBTOOL' is to add
`AC_PROG_LIBTOOL'
src/threadd/Makefile.am:10: to `configure.in' and run `aclocal' and
`autoconf' again.
src/threadd/Makefile.am:10: If `AC_PROG_LIBTOOL' is in `configure.in',
make sure
src/threadd/Makefile.am:10: its definition is in aclocal's search path.
Have anyone an idea, how to fix this?
--
Sincereley yours
Sascha Manns
openSUSE Marketing Team
openSUSE Build Service
openSUSE Features Screening Team
Web: http://saschamanns.gulli.to
Project-Blog: http://lizards.opensuse.org/author/saigkill
Private-Blog: http://saschasbacktrace.blogspot.com
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org
