Install Go-oo from Testing or AUR?

I just noticed that Go-oo is in the testing repo. I'm not running a testing system. Does it make sense to install Go-oo (if I want to try it) from the testing repo, if I'm not using any other packages from testing? Or would it be better to use the version in AUR?
I guess I'm wondering both which would produce a better working version of Go-oo in my system and which package is being upgraded more consistently?
Also is there any prognosis on when Go-oo might be ready for the extra repo?
Thanks.
Last edited by cb474 (2009-04-27 09:45:00)

AndyRTR wrote:For localization just use the vanilla langpack PGBUILDs as proto and change the install path. That should work.
Thank you, that worked like a charm! :-)
If someone also wants to localize go-openoffice, here is my PKGBUILD:
pkgname=go-openoffice-de
pkgver=3.0.1
pkgrel=1
pkgdesc="OpenOffice.org - german language files for go-oo.org"
arch=('i686' 'x86_64')
license=('LGPL')
url="http://www.openoffice.org"
makedepends=('rpmextract')
depends=('go-openoffice')
source=(http://ftp-1.gwdg.de/pub/openoffice/extended/3.1.0rc2/OOo_3.1.0rc2_20090427_LinuxIntel_langpack_de.tar.gz)
md5sums=('43151ce886665ef794a939c765ac7d3f')
build() {
cd ${srcdir}/*native_packed*/RPMS
for i in *.rpm
do rpmextract.sh $i
done
# install openoffice language files
mkdir -p ${pkgdir}/usr/lib/go-openoffice-3.0.99.6/basis-link
cp -R opt/openoffice.org/basis3.1/* ${pkgdir}/usr/lib/go-openoffice-3.0.99.6/basis-link
cp -R opt/openoffice.org3/* ${pkgdir}/usr/lib/go-openoffice-3.0.99.6/basis-link
chown root:root -R ${pkgdir}/usr/lib/go-openoffice-3.0.99.6/
I just altered the name, pkgdesc, depends, source (there's a newer file online now, the old one doesn't exist anymore), md5sums and the install part of course
I don't know if the pkgver is correct (since it is 3.1.0 RC2) but hey, it works!
If someone wants to localize it for another language the only thing you have to do is to change the pkgname, source¹ and md5sums line.
¹: Choose your langpack .tar.gz file from here: http://ftp-1.gwdg.de/pub/openoffice/extended/3.1.0rc2/
Just like the vanilla openoffice you have to install the spell and grammar checker afterwards. The file is located here: /usr/lib/go-openoffice-3.0.99.6/share/extension/install
Thank you very much again Andy. I don't go back to vanilla openoffice
EDIT: I also don't really care if you split the mono and gstreamer dependencies into other packages (if that is possible). I would install them anyway
But I don't really get the point why Arch should do this? Openoffice is a fat package, everyone who wants to install knows this... One or two dependencies more don't hurt much in my opinion. So what is bad about mono and/or gstreamer?
I'm very happy with the features like video support since the Java Media Framework (JMF) isn't available for x86_64 :-(
Also vanilla openoffice could be placed in AUR so there's a way you can install it without those dependencies.
Last edited by darie (2009-04-27 23:18:27)

Similar Messages

  • Install single package from testing

    I just switched to Arch from Gentoo, and so far it's been mostly great. What I want to do right now is install 1 package from testing, and only that one. Is there an easy way to do this, besides uncommenting the testing repo, installing xorg-server, and commenting testing again? Basically (if you're familiar with Gentoo and emerge), I want to know what pacman's equivalent to /etc/portage/package.keywords is. Alternatively, if there's a way to make kde4 not absurdly slow with a relatively new ultra-low-end nvidia card (9300m), then I'm up for that as well. Additional background for this question is that I was hoping the newest (beta) drivers might alleviate this issue, but they depend on an xorg-server version that only exists in testing. I don't want to run testing, but if the new drivers help, then I'd be willing to run them (along with any reasonable, if unstable, dependencies). Thanks in advance.

    shimage wrote:I just switched to Arch from Gentoo, and so far it's been mostly great. What I want to do right now is install 1 package from testing, and only that one. Is there an easy way to do this, besides uncommenting the testing repo, installing xorg-server, and commenting testing again? Basically (if you're familiar with Gentoo and emerge), I want to know what pacman's equivalent to /etc/portage/package.keywords is. Alternatively, if there's a way to make kde4 not absurdly slow with a relatively new ultra-low-end nvidia card (9300m), then I'm up for that as well. Additional background for this question is that I was hoping the newest (beta) drivers might alleviate this issue, but they depend on an xorg-server version that only exists in testing. I don't want to run testing, but if the new drivers help, then I'd be willing to run them (along with any reasonable, if unstable, dependencies). Thanks in advance.
    Welcome to the forums.
    If you upgrade only xorg-server, you're going to have problems. There are other packages designed to be used with it.
    With that being said, you can always put testing as the last repo in /etc/pacman.conf. Then if you want to upgrade one package, you explicitly call it with pacman -S testing/<package_name>.

  • Install some packages from [testing] repository

    Hello Guys,
    Could you suggest me how can I install and update from time to time only several packages from testing but not all of that repository?
    Have a nice day,
    Stas

    bangkok_manouel wrote:
    There are completely valid scenarii where you can use only few packages from testing (see above, the linux kernel for example). Also, using different libs versions is not a heresy (simlinking is) so there are very few comments in this thread that would have been much more constructive without the condescending tone. Or should we, from now on, consider our fellow users as all dumb in opposition to competent linux users [1] as it has always been ?
    [1] http://www.archlinux.org/about/
    It is NOT safe to assume that ALL readers are competent. Just browse through the forums every once in a while. Hence care should be taken in giving advise.
    This is not a private club, things posted here are read by many competent Arch users and some incompetent as well. Results show up in a Google search. Even though its perfectly valid for me to wash my motherboard in water to get rid of dust, I wouldn't post that advise here without big WARNING tags. This isn't an indication that I assume all users are idiots, but simply that I know there are some who will not understand the 'ifs' associated with such a thing.

  • Installing only perl from testing

    Hello,
    I wanted to upgrade my perl installation to v5.12 (the one in testing).
    However, i don't want to use testing for anything else... Is this doable? I asked in another thread why the [core] perl was out-of-date but was told that there was a way to install specific [testing] packages (and also was. Would this work for something as perl?
    If so, can anyone point me in the right direction?
    Sorry if for some reason this isn't the right place to post this question.

    pedro-kun wrote:
    Ari'osika wrote:Aw man, I'm a little late. My suggestion was to download perl's source code and compile it. (That's I what I did, simply because I'm a wee-bit afraid of the testing-repo's haha).
    But if you install it from source, and some app has perl as one of its dependencies, how does pacman know that perl is installed? Don't you have to make a PKGBUILD for that?
    It doesn't, which was my intention for doing so.. As a proficient "perl hacker", i like to write scripts that are cross-version compatible because sometimes an update such as 5.10 to 5.12 eliminate a particular function in favor of other similar, but different, function.
    ..And now I just realized; I forgot to mention why I did what I did in my previous post. Sorry
    In other words; ignore my suggestion.
    EDIT: forgot something important.
    Last edited by Ari'osika (2010-07-31 23:30:37)

  • I am not able to install screen-git from the aur

    So yeah, i cant install screen-git from the aur. Im using yaourt.
    ┌─[yamifrankc]──(~)
    └─| % > aur -S screen-git
    ==> Resuming previous build
    ==> Downloading screen-git PKGBUILD from AUR...
    tar: Record size = 13 blocks
    ==> Last 5 comments ordered by date (asc):
    Comment by: dolby on Tue, 16 Jun 2009 15:02:25 +0000
    GNU screen shouldnt depend on libelf. Package in extra now doesnt.
    See http://bugs.archlinux.org/task/14700
    Comment by: dolby on Tue, 16 Jun 2009 15:03:08 +0000
    Oh yeah, gpm isnt a dependency either.
    Comment by: nihathrael on Tue, 16 Jun 2009 16:23:56 +0000
    Thanks for the pointers. Package updated.
    Comment by: firecat53 on Tue, 16 Jun 2009 23:19:28 +0000
    At least for x86_64, libelf seems to be a dependency. Throws an error about libelf.so.0 when starting screen if it's not installed.
    Comment by: Ranguvar on Sun, 11 Oct 2009 04:00:10 +0000
    The three lines at the end of the install scriplet are unnecessary now and can cause problems apparently, please remove :)
    Also, I cannot confirm libelf dependency, both by using ldd and trying removing libelf, so it should be kept out.
    First Submitted: Sun, 09 Nov 2008 15:43:42 +0000
    screen-git 20090616-1 : GNU Screen from GIT repository. Provides vertical splitting.
    ( Unsupported package: Potentally dangerous ! )
    ==> Edit the PKGBUILD (highly recommended for security reasons) ? [Y/n]("A" to abort)
    ==> ----------------------------------------------
    ==>n
    ==> screen-git dependencies:
    - ncurses (already installed)
    - shadow (already installed)
    - git (already installed)
    - automake (already installed)
    - autoconf (already installed)
    ==> WARNING: This PKGBUILD contains install file that can be dangerous.
    screen.install
    ==> Edit screen.install (highly recommended for security reasons) ? [Y/n] ("A" to abort)
    ==> ----------------------------------------------
    ==>y
    Please add EDITOR to your environment variables
    for example:
    ==> Edit PKGBUILD with:(replace gvim with your favorite editor)
    ==> Edit screen.install with:vim
    ==> WARNING: This PKGBUILD contains install file that can be dangerous.
    screen.install
    ==> Edit screen.install (highly recommended for security reasons) ? [Y/n] ("A" to abort)
    ==> ----------------------------------------------
    ==>n
    ==> Continue the building of screen-git ? [Y/n]
    ==> ----------------------------------------------
    ==>y
    ==> Install or build missing dependencies for screen-git:
    ==> Building and installing package
    mkdir: cannot create directory `/var/abs': Permission denied
    ==> WARNING: Unable to write in /var/abs/local/yaourtbuild/screen-git directory. Using /tmp directory
    ==> screen-git dependencies:
    - ncurses (already installed)
    - shadow (already installed)
    - git (already installed)
    - automake (already installed)
    - autoconf (already installed)
    ==> Determining latest git revision...
    -> Version found: 20091204
    ==> Making package: screen-git 20091204-1 i686 (Fri Dec 4 07:43:16 CST 2009)
    ==> Checking Runtime Dependencies...
    ==> Checking Buildtime Dependencies...
    ==> Retrieving Sources...
    -> Found screen.pam in build dir
    ==> Validating source files with md5sums...
    screen.pam ... Passed
    ==> Extracting Sources...
    ==> Removing existing pkg/ directory...
    ==> Entering fakeroot environment...
    ==> Starting build()...
    ==> Connecting to GIT server....
    Already up-to-date.
    ==> The local files are updated.
    ==> GIT checkout done or server timeout
    ==> Starting make...
    autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
    autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
    autoheader: WARNING: is deprecated and discouraged.
    autoheader:
    autoheader: WARNING: Using the third argument of `AC_DEFINE' and
    autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template without
    autoheader: WARNING: `acconfig.h':
    autoheader:
    autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
    autoheader: [Define if a function `main' is needed.])
    autoheader:
    autoheader: WARNING: More sophisticated templates can also be produced, see the
    autoheader: WARNING: documentation.
    configure: WARNING: unrecognized options: --with-sys-screenrc
    this is screen version 4.1.0
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking how to run the C preprocessor... gcc -E
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking whether gcc needs -traditional... no
    checking for library containing strerror... none required
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking minix/config.h usability... no
    checking minix/config.h presence... no
    checking for minix/config.h... no
    checking whether it is safe to define __EXTENSIONS__... yes
    checking for gawk... gawk
    checking for a BSD-compatible install... /bin/install -c
    configure: checking for buggy tools...
    - sh is 'GNU bash, version 4.0.35(2)-release (i686-pc-linux-gnu)'.
    - sed is 'GNU sed version 4.2.1'.
    checking if a system-wide socket dir should be used... yes
    checking for the socket dir... (eff_uid ? "/tmp/uscreens" : "/tmp/screens")
    configure: checking for MIPS...
    configure: checking for Ultrix...
    configure: checking for butterfly...
    configure: checking for POSIX.1...
    - you have a POSIX system
    configure: checking for System V...
    configure: checking for sequent/ptx...
    configure: checking SVR4...
    checking stropts.h usability... yes
    checking stropts.h presence... yes
    checking for stropts.h... yes
    checking for string.h... (cached) yes
    checking for strings.h... (cached) yes
    configure: checking for Solaris 2.x...
    configure: checking BSD job jontrol...
    - you have jobcontrol
    configure: checking setresuid...
    configure: checking setreuid...
    configure: checking seteuid...
    configure: checking select...
    configure: checking fifos...
    - your fifos are usable
    configure: checking for broken fifo implementation...
    - your implementation is ok
    configure: checking sockets...
    - your sockets are usable
    configure: checking socket implementation...
    - you are normal
    - both sockets and fifos usable. let's take sockets.
    configure: checking select return value...
    - select is ok
    configure: checking for tgetent...
    configure: checking libcurses...
    - you use the terminfo database
    configure: checking ospeed...
    configure: checking for /dev/ptc...
    configure: checking for SVR4 ptys...
    checking for getpt... yes
    configure: checking for ptyranges...
    configure: checking default tty permissions/group...
    checking for write... /usr/bin/write
    checking for xterm... /usr/bin/xterm
    - pty mode: 0620, group: 0
    configure: checking getutent...
    configure: checking ut_host...
    checking utempter.h usability... no
    checking utempter.h presence... no
    checking for utempter.h... no
    configure: checking for libutil(s)...
    configure: checking getloadavg...
    assuming posix signal definition
    configure: checking for crypt and sec libraries...
    configure: checking crypt...
    configure: checking IRIX sun library...
    configure: checking syslog...
    configure: checking wait union...
    configure: checking for termio or termios...
    configure: checking getspnam...
    configure: checking getttyent...
    configure: checking fdwalk...
    configure: checking whether memcpy/memmove/bcopy handles overlapping arguments...
    checking for long file names... yes
    checking for vsprintf... yes
    checking for dirent.h that defines DIR... yes
    checking for library containing opendir... none required
    checking for setenv... checking for nl_langinfo(CODESET)... yes
    checking for library containing gethostname... none required
    checking for rename... yes
    checking for fchmod... yes
    checking for fchown... yes
    checking for strerror... yes
    checking for lstat... yes
    checking for _exit... yes
    checking for utimes... yes
    checking for vsnprintf... yes
    checking for getcwd... yes
    checking for setlocale... yes
    checking for strftime... yes
    checking for PAM support... yes
    configure: creating ./config.status
    config.status: creating Makefile
    config.status: creating doc/Makefile
    config.status: creating config.h
    config.status: config.h is unchanged
    config.status: executing default commands
    configure: WARNING: unrecognized options: --with-sys-screenrc
    Now please check the pathnames in the Makefile and in the user
    configuration section in config.h.
    Then type 'make' to make screen. Good luck.
    CPP="gcc -E -DETCSCREENRC='"/usr/etc/screenrc"' -DSCREENENCODINGS='"/usr/share/screen/utf8encodings"'" srcdir=. sh ./osdef.sh
    AWK=gawk CC="gcc -march=i686 -mtune=generic -O2 -pipe" srcdir=. sh ./comm.sh
    gcc -c -I. -I. -DETCSCREENRC='"/usr/etc/screenrc"' -DSCREENENCODINGS='"/usr/share/screen/utf8encodings"' -DHAVE_CONFIG_H -DGIT_REV=\""`git describe --always 2>/dev/null`"\" \
    -march=i686 -mtune=generic -O2 -pipe screen.c
    gcc -c -I. -I. -DETCSCREENRC='"/usr/etc/screenrc"' -DSCREENENCODINGS='"/usr/share/screen/utf8encodings"' -DHAVE_CONFIG_H -DGIT_REV=\""`git describe --always 2>/dev/null`"\" \
    -march=i686 -mtune=generic -O2 -pipe ansi.c
    gcc -c -I. -I. -DETCSCREENRC='"/usr/etc/screenrc"' -DSCREENENCODINGS='"/usr/share/screen/utf8encodings"' -DHAVE_CONFIG_H -DGIT_REV=\""`git describe --always 2>/dev/null`"\" \
    -march=i686 -mtune=generic -O2 -pipe fileio.c
    gcc -c -I. -I. -DETCSCREENRC='"/usr/etc/screenrc"' -DSCREENENCODINGS='"/usr/share/screen/utf8encodings"' -DHAVE_CONFIG_H -DGIT_REV=\""`git describe --always 2>/dev/null`"\" \
    -march=i686 -mtune=generic -O2 -pipe mark.c
    gcc -c -I. -I. -DETCSCREENRC='"/usr/etc/screenrc"' -DSCREENENCODINGS='"/usr/share/screen/utf8encodings"' -DHAVE_CONFIG_H -DGIT_REV=\""`git describe --always 2>/dev/null`"\" \
    -march=i686 -mtune=generic -O2 -pipe misc.c
    gcc -c -I. -I. -DETCSCREENRC='"/usr/etc/screenrc"' -DSCREENENCODINGS='"/usr/share/screen/utf8encodings"' -DHAVE_CONFIG_H -DGIT_REV=\""`git describe --always 2>/dev/null`"\" \
    -march=i686 -mtune=generic -O2 -pipe resize.c
    gcc -c -I. -I. -DETCSCREENRC='"/usr/etc/screenrc"' -DSCREENENCODINGS='"/usr/share/screen/utf8encodings"' -DHAVE_CONFIG_H -DGIT_REV=\""`git describe --always 2>/dev/null`"\" \
    -march=i686 -mtune=generic -O2 -pipe socket.c
    In file included from socket.c:51:
    extern.h:159: error: conflicting types for 'execvpe'
    /usr/include/unistd.h:585: note: previous declaration of 'execvpe' was here
    make: *** [socket.o] Error 1
    ==> ERROR: Build Failed.
    Aborting...
    Error: Makepkg was unable to build screen-git package
    Vertical split is ftw! What can i do to build it?

    yeah, i also got that message.
    for vertical split you can go for screen-vs package. this is screen with the vs patch.
    http://aur.archlinux.org/packages.php?ID=6006

  • [Solved] Error installing Flash 64bit from AUR

    I tried installing the 64bit flash from here :http://aur.archlinux.org/packages.php?ID=21601, using 'yaourt -S flashplugin-alpha-64 10.0.d20.7-3'
    It will say:
    Downloading 10.0.d20.7-3 PKGBUILD from AUR
    Error: 10.0.d20.7-3 not found in AUR.
    So i tried another method by downloading this tar file from http://download.macromedia.com/pub/labs … .so.tar.gz
    Then i untarred the file and on the desktop it shows 'libflashplayer.so'
    So next i went to terminal, tried doing 'cd Desktop', followed by 'pacman -S libflashplayer.so', but it says i need to be root to do that. So i do 'su - ', and then 'cd Desktop', but it says '-bash: cd: Desktop: No such file or directory.'
    How am i suppose to install flash64 bit? Thanks.
    Last edited by Chance (2008-12-18 15:19:46)

    Chance wrote:
    I tried installing the 64bit flash from here :http://aur.archlinux.org/packages.php?ID=21601, using 'yaourt -S flashplugin-alpha-64 10.0.d20.7-3'
    It will say:
    Downloading 10.0.d20.7-3 PKGBUILD from AUR
    Error: 10.0.d20.7-3 not found in AUR.
    should be just "yaourt -S flashplugin-alpha-64" no version needed
    the error is telling you it cant find 10.0.d20.7-3 which is not a package.  did you get another error with the first part? or did  you see it building the package?
    i like building it by hand, so i usually (in a folder on my /home) i do
    mkdir flashplugin-alpha-64
    cd flashplugin-alpha-64
    yaourt -G flashplugin-alpha-64 (to get pKGBUILD and other files)
    makepkg  (to build)
    then install with yaourt -U [full package filename]
    makes me feel like i'm in control
    Last edited by toxygen (2008-12-18 04:56:50)

  • Need package from testing, How can I install?[solved]

    Hi
    I must install the i81 Driver from testing, but what must I edit in the pacman.conf?
    I have try it with
    Incoming = /etc/packman.d/testing
    this don't work.

    Remove that line from pacman.conf - it's completely incorrect. "Incoming=" means nothing to pacman, and if you look in /etc/pacman.d, there is no file called testing.
    Here's the right way. Uncomment these two lines in pacman.conf:
    #[testing]
    #Server = ftp://ftp.archlinux.org/testing/os/i686
    Then do
    pacman -Sy testing/xf86-video-i810
    If you don't need any other packages from testing, re-comment the lines in pacman.conf - if you want to be able to get selected packages from testing, move the lines to the end of pacman.conf, after all other repos.

  • Searching and installing packages from testing w/o editing pacman.conf

    Is this possible?

    tomk wrote:Installing individual packages from the testing repo is not recommended as they are likely to depend on testing versions of other packages. The only supported way of using the testing repo is to enable it at the top of the list in pacman.conf.
    I don't understand why that is true.
    If I enable the testing repo and update a package (pacman -S package), and if the dependencies are set correctly, the dependencies from testing needed should also be installed/updated, right?

  • Severely ugly fonts in openjdk6 from testing

    I have been using icedtea6 from AUR for months now and I just replaced it with openjdk6 from testing. icedtea6 had ugly fonts, but openjdk6 has severely ugly fonts. It's not too horrible with regular fonts, but it is with bold. A good test is the Font2DTest:
    java -jar /usr/lib/jvm/java-1.6.0-openjdk/demo/jfc/Font2DTest/Font2DTest.jar
    Does anyone know whether it's possible yet to get good fonts in openjdk6? If so, how?
    Last edited by skottish (2008-08-04 18:30:19)

    Problem is still here in openjdk6, not in jre/jdk.
    I think it is related to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495988
    Our fontconfig.properties.src is correct, but we have no compilefontconfig.jar, so I cannot try what the bug reporter mentioned, "java -jar compilefontconfig.jar fontconfig.config fontconfig.bfc".
    In Ubuntu, they added that file in 6b10-1: "* Install compilefontconfig.jar in openjdk-6-jre-lib package."
    Should we have that file?

  • KDE from testing

    I tried to install KDE from testing and I got:
    checking for file conflicts...
    error: the following file conflicts were found:
      kdenetwork: /opt/kde/bin/winpopup-install.sh: exists in filesystem
      kdenetwork: /opt/kde/bin/winpopup-send.sh: exists in filesystem
      kdenetwork: /opt/kde/include/kopete/kopetepicture.h: exists in filesystem
      kdenetwork: /opt/kde/include/kopete/kopeteprefs.h: exists in filesystem
      kdenetwork: /opt/kde/include/kopete/ui/addressbooklinkwidget.h: exists in filesystem
      kdenetwork: /opt/kde/include/kopete/webcamwidget.h: exists in filesystem
      kdenetwork: /opt/kde/lib/kde3/kopete_wp.la: exists in filesystem
      kdenetwork: /opt/kde/lib/kde3/kopete_wp.so: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/128x128/apps/wp_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/16x16/actions/wp_away.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/16x16/actions/yahoo_stealthed.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/16x16/apps/wp_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/22x22/actions/yahoo_stealthed.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/32x32/actions/yahoo_stealthed.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/32x32/apps/wp_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/48x48/apps/wp_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/icons/crystalsvg/64x64/apps/wp_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Footer.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Header.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Incoming/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Incoming/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Incoming/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Outgoing/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Outgoing/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Outgoing/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/Status.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/images/action.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/images/important.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/images/internal.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clean/Contents/Resources/main.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Footer.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Header.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Incoming/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Incoming/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Incoming/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Incoming/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Outgoing/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Outgoing/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Outgoing/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Outgoing/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/Status.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-background.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-inbound-arrow.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-inbound-avatar.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-inbound-background.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-inbound-left.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-inbound-right.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-outbound-arrow.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-outbound-avatar.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-outbound-left.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/body-outbound-right.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/footer-inbound-background.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/footer-inbound-left.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/footer-inbound-right.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/footer-outbound-background.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/footer-outbound-left.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/footer-outbound-right.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/header-inbound-background.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/header-inbound-left.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/header-inbound-right.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/header-outbound-background.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/header-outbound-left.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/header-outbound-right.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/icon-action.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/icon-highlighted.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/icon-internal.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/icon-me.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/icon-time.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/images/icon-you.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Clear/Contents/Resources/main.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Footer.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Header.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Incoming/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Incoming/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Incoming/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Outgoing/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Outgoing/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Outgoing/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Status.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Variants/Contact-Colors.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Variants/Name-Colors.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Variants/No-Colors.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/Variants/Status-Colors.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Gaim/Contents/Resources/main.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/COPYRIGHT: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Info.plist: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Footer.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Header.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Incoming/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Incoming/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Incoming/Context.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Incoming/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Incoming/NextContext.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Incoming/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Outgoing/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Outgoing/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Outgoing/Context.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Outgoing/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Outgoing/NextContext.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Outgoing/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Status.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Variants/Dark-Noback.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Variants/Dark.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Variants/Dark2-Noback.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Variants/Dark2.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Variants/Light-Noback.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Variants/Light.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Variants/Light2-Noback.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/Variants/Light2.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/images/background.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/images/background2.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/images/kopete.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/Contents/Resources/main.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/README: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Hacker/gpl.txt: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Footer.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Header.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Incoming/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Incoming/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Incoming/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Outgoing/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Outgoing/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Outgoing/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Status.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/Side_blue.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/Side_blue_moon.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/Side_blue_moon_without_transparency.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/Side_blue_without_transparency.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/Side_green.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/Side_green_without_trans.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/Side_green_without_transparency.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/cadre1.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/cadre2.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/cadre3.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/cadre4.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/cadre5.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/cadre6.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/konqui-blue.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/konqui-green.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/Variants/konqui/konqui-moon.jpg: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/main.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Konqi/Contents/Resources/puce.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Footer.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Header.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Incoming/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Incoming/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Incoming/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Incoming/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Outgoing/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Outgoing/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Outgoing/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Outgoing/buddy_icon.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Status.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Variants/Big_pictures.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/Variants/Contact_color.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/images/action.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/images/important.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/images/system.png: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Kopete/Contents/Resources/main.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Footer.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Header.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Incoming/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Incoming/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Incoming/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Outgoing/Action.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Outgoing/Content.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Outgoing/NextContent.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/Status.html: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete/styles/Retropete/Contents/Resources/main.css: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete_jabber/jabberchatui.rc: exists in filesystem
      kdenetwork: /opt/kde/share/apps/kopete_yahoo/yahooconferenceui.rc: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/128x128/actions/voicecall.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/128x128/actions/webcamreceive.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/128x128/actions/webcamsend.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/account_offline_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/add_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/contact_away_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/contact_busy_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/contact_food_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/contact_invisible_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/contact_phone_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/contact_xa_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/delete_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/edit_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/emoticon.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_away.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_chatty.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_connecting.mng: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_group.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_invisible.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_na.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_offline.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_online.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_original.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_raw.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_serv_off.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_serv_on.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/jabber_xa.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/kopeteavailable.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/kopeteaway.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/kopeteeditstatusmessage.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/kopetestatusmessage.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/metacontact_away.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/metacontact_offline.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/metacontact_online.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/metacontact_unknown.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/newmsg.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/search_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/show_offliners.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/status_unknown.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/status_unknown_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/voicecall.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/webcamreceive.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/actions/webcamsend.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_aim.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_gadu.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_http/ws.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_icq.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_irc.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_msn.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_qq.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_sms.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_smtp.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_tlen.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_gateway_yahoo.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/16x16/apps/jabber_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/account_offline_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/add_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/delete_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/edit_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/kopeteavailable.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/kopeteaway.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/kopeteeditstatusmessage.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/search_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/show_offliners.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/voicecall.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/webcamreceive.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/22x22/actions/webcamsend.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/account_offline_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/add_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/delete_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/edit_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/kopeteavailable.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/kopeteaway.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/kopeteeditstatusmessage.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/metacontact_away.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/metacontact_offline.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/metacontact_online.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/metacontact_unknown.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/newmessage.mng: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/newmsg.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/search_user.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/show_offliners.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/voicecall.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/webcamreceive.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/actions/webcamsend.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/32x32/apps/jabber_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/actions/kopeteavailable.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/actions/kopeteaway.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/actions/metacontact_away.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/actions/metacontact_offline.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/actions/metacontact_online.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/actions/voicecall.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/actions/webcamreceive.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/actions/webcamsend.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/48x48/apps/jabber_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/64x64/actions/voicecall.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/64x64/actions/webcamreceive.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/64x64/actions/webcamsend.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/crystalsvg/scalable/actions/account_offline_overlay.svgz: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/emoticon.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_away.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_chatty.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_connecting.mng: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_group.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_invisible.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_na.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_offline.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_online.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_original.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_raw.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_serv_off.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_serv_on.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/jabber_xa.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/kopeteavailable.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/kopeteaway.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/newmsg.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/status_unknown.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/actions/status_unknown_overlay.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/16x16/apps/jabber_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/22x22/actions/kopeteavailable.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/22x22/actions/kopeteaway.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/32x32/actions/kopeteavailable.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/32x32/actions/kopeteaway.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/32x32/actions/newmessage.mng: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/32x32/apps/jabber_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/48x48/actions/kopeteavailable.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/48x48/actions/kopeteaway.png: exists in filesystem
      kdenetwork: /opt/kde/share/icons/hicolor/48x48/apps/jabber_protocol.png: exists in filesystem
      kdenetwork: /opt/kde/share/services/kopete_wp.desktop: exists in filesystem
    errors occurred, no packages were upgraded.

    Snowman wrote:Did you installed the kopete package from AUR? If yes, remove it as it conflicts with kdenetwork.
    Thank you very much . Yes, I had kopete from AUR.

  • Steps for Go Live for Webtools moving from Test to Production

    Further to the useful checklist in the wiki recently supplied by Bryce can I ask for some minor gaps to be filled ( perhaps by inserting a few additional steps in that document)
    I have yet to hit the issues created by a go live implementation but this is only a matter of time...
    I am trying to work out what needs  to occur between having :
    a) a test B1 database successfully synching to a test WT site and db set up
    and
    b) the Production B1 database initially synched to the the live WT live WT db ready to accept the first live transactions.
    1) Copy WT site from test to live location
    2) Change Server config, settings and Tables tabs in Synch Manager click on 'Install Plugin' to add custom fields to Production B1 database
    3) ......
    I am stuck as to what needs to be done to "reset"  the WT back end db and how one goes about this.
    Coupled with this and probably part of the answer is the 'Initialise Synch' button. It would be useful to understand exactly what this does in terms of data  - presumably it is only transactional data - but which tables are affected?
    Also if there's anything else that I might have overlooked in terms of potential pitfalls I'd be grateful for advice - the recent posts regarding product trees and images come to mind.
    Thanks

    First thing is to plan for some downtime in your B1 databases. Nothing more frustrating than having new data come into b1 when you're trying to set this up. So perhaps do this at night or on a weekend when no one is using B1.
    Install Plugin operation adds UDF's, edits the stored proc in b1 db, and creates the queue table, PRX_Transaction_Queue
    Initialize synch runs upgrade scripts(if applicable), deletes all data that has synched from B1 previously(or would synch from Wt to B1, like a test order created in Wt) and inserts all relevant data into the queue table in B1 db. Also the synchid's are reset. It's pretty much the same list as is displayed on the Settings page of the Synch Manager. Please someone correct me if I'm missing something here!
    Pre-requisites:
    - Name the Wt db relevant to its position in the environment. B1Webtools is not the greatest name, it's meant to be a jumping off point. Rename your Wt db in the way that you would for B1. ie WebtoolsLive, WebtoolsTest. Makes things easier
    Two options:
    1) Presuming you have a test Wt db and a test b1 db or even a test Wt db and a production(live) B1 db, you could duplicate the test Wt db and change the synch manager config to point to the B1 live db. Install the "plugin" on the new B1 live db and enter your table mappings. Initialize synch will delete all the data that has synched from B1 test db to Wt db(now live db) and reset the synch id's to zero. These will be populated during the synch. Then Run Synch.
    Caveat: This option is fine if your synch takes a "short" period of time. Short being an hour. If you have say 20,000 business partners with 3 years of order history and 300 lines per order... expect several hours.
    2) Create a test synch profile and a live synch profile in tandem and update only the live synch profile with data. Also, have two web tools websites but work primarily in the live one. The synch manager will auto synch both profiles every time the service runs(set by you)
    When it's go time, copy the live db's over the test db's so you have a test environment exactly matching your live environment.  Now, obviously as soon as new data goes into the live db it's out of synch, but this way you have a test system you can break or use to test upgrades, etc.
    As you might guess, there are a number of ways to go with this. It really does depend on a) how comfortable you are with moving data around in SQL and b) what your setup entails.
    I think the best thing you can do is make it as simple as possible. Don't overthink things and make sure you have a backup of everything before you start.
    Good luck!

  • X + XFCE using a lot of RAM (Xorg 7.3 from testing)

    First off, I didn't know where to put it, so feel free to move it.
    I recently got a new laptop - HP 6510b (T7300, 2 GB RAM, X3100 onboard Intel GPU). Installed Arch on it, like on my other boxen. However, memory usage jumps through the roof once i run XFCE. I grabbed Xorg 7.3 from testing since that one has the Intel driver (xf86-video-intel) for my GPU.
    Some stats:
    Memory usage in runlevel 3:
    total used free shared buffers cached
    Mem: 2019 48 1970 0 4 19
    -/+ buffers/cache: 25 1993
    Swap: 282 0 282
    Memory usage in runlevel 5 (logged in to XFCE, empty desktop, except for aDesklets and Conky):
    total used free shared buffers cached
    Mem: 2019 190 1828 0 7 53
    -/+ buffers/cache: 129 1890
    Swap: 282 0 282
    Usually I boot into XFCE using 60 MB RAM with a similar configuration (even heavier, since I haven't got all the services running yet as I do normally - CUPS etc.). Now, that is obviously not the case. As mentioned above I have 2 GB of RAM, of which the onboard GPU should take max. 256 MB. Free does not seem to show that if I am correct (on my old laptop I could see 800+ MB of RAM, because 128 MB was reserved for the ATi GPU). Is this normal?
    If I run htop and sort on memory usage I see X + XFCE using more memory than usual (60 MB total, without aDesklets & Conky). Normally the graphical layer only adds like 40 MB more (if not less, since it used to be 60 MB).
    This is a screenshot of the memory-sorted active applications
    Does anyone have any pointers, or experience similar behaviour with Xorg 7.3?
    Last edited by B (2007-09-16 18:28:57)

    I was just wondering where the big difference came from. If it has to do with the inner workings of the driver, I'm afraid I can't do anything about then. I know I got plenty of RAM, I'm just a bit obsessed with stuff lingering around for nothing (bloat, you know ), and I suspected that might be the case here, which is not so, apparently .
    Shining: I used to think one of the great advantages of Linux was that, with a slim environment, it could be very light on resources (especially RAM). At this moment the difference with a stripped XP is not that big anymore . Memory usage on an onboard ATi GPU, 1280x800, 16bit was 60 MB. I suppose that was with 24 bit colour depth too (it was not set explicitly in Xorg.conf but after defining it & restarting X RAM usage was the same).
    I'd like to point out also there is nowhere in the BIOS i can set the amount of memory allocated to the X3100. It can have up to 384 MB according to Intel's docs, but I still got the full 2 GB RAM according to free. And the GPU has to get his memory in some way...
    Last edited by B (2007-09-17 15:51:30)

  • Help. Installed the program from adobe in the trial under the same ID.

    Help. Installed the program from adobe in the trial under the same ID. After the expiration of 30 days, our company has registered for acquisition programs. We have introduced a new ID for a trial test, and adobe programs from running. Test time is exhausted. How to run the program under the new ID in a trial.
    Помогите. Установил пакет програм от адобе в триал под одним ID. После истечения 30 дней наша компания зарегистрировалась для приобретения программ. Мы ввели новый ИД для триал теста, а адоб программы не запускаются. Пробное время исчерпано. Как запустить программы под новым ИД в триале.

    Perhaps extend trial adobe product if 30 days is exhausted? If I go under a different ID that shows 0 days.
    Возможно продлить триал продукта адобе если 30 дней исчерпано? Если я захожу под другим ИД то показывает 0 дней.

  • Replace devfsd with udev from "testing"? [Y/n]

    pacman -Syu keeps asking me this:
    :: Replace devfsd with udev from "testing"? [Y/n] n
    but im already using udev. why?

    um, again please? you mean i should just say yes? but why is pacman -Syu insisting on installing udev from testing (i have testing enabled but not prioritized in pacman.conf). this arch install of mine started from 0.72 (gimmick) so it is using udev (from current) by default.

  • Install BI Content on Test and Transport

    Hi,
    how do you make sure that something that works on your testsystem will also work on the
    production system? For example if I install some objects from BI Content, and everything works fine on the test system, and now I transport these few installed objects on production system how do I know if everything else was transported before?
    I mean I can compare both systems, but then I have to check each object on test and production system
    to know if everything was transported before...Am I wrong?
    Thanks
    alto

    Hi,
    If it is already live system then you have to compare each object with production system .
    Regards,
    Satya

Maybe you are looking for

  • Floating Licence

    Does Adobe Acrobat offer any type of floating licence? We are trying to incorporate digital signatures that can only be done in reader if the pdf is saved in Acrobat with the "extend features in adobe reader" function turned on. We don't/aren't going

  • How to transport Minor changes in BPC 7.0 to other client

    Hi, I am very new to BPC and got an ticket to do a minor change in script logic. We are in BPC 7.0. I am not sure how I can transport this minor change from Dev to other client. My question is: 1. Do we need to make system offline while making change

  • Need Help Using DateFields...

    whenever i invoke the method getDate(), the DateField resets to its initial value and i don't want that to happen... here's my code: class DateInputForm extends Form implements CommandListener{      private final SalesMIDlet m;      public Date curre

  • Question in regular expressions

    Hi, I have this string (abdcerpabdcerpabdcerpaabdcerpabdcerp) and i want to this string abdcerp and may be followed by one or more a's So i want to get these results: abdcerp abdcerp abdcerpa abdcerp abdcerp I know regular expressions very well but i

  • Has the Process Version changed in LR 5.5?

    I have downloaded LR5.5 and have gone through a final selection of images for printing; most of these I had modified using LR 5.4. With 5.5 a fair number of the images showed a considerable degree of highlight clipping which was not apparent when pro