<86>Mar 28 06:38:14 userdel[21260]: delete user 'rooter' <86>Mar 28 06:38:14 groupadd[21770]: group added to /etc/group: name=rooter, GID=699 <86>Mar 28 06:38:14 groupadd[21770]: group added to /etc/gshadow: name=rooter <86>Mar 28 06:38:14 groupadd[21770]: new group: name=rooter, GID=699 <86>Mar 28 06:38:14 useradd[22112]: new user: name=rooter, UID=699, GID=699, home=/root, shell=/bin/bash <86>Mar 28 06:38:14 userdel[22878]: delete user 'builder' <86>Mar 28 06:38:14 userdel[22878]: removed group 'builder' owned by 'builder' <86>Mar 28 06:38:14 userdel[22878]: removed shadow group 'builder' owned by 'builder' <86>Mar 28 06:38:14 groupadd[23519]: group added to /etc/group: name=builder, GID=700 <86>Mar 28 06:38:14 groupadd[23519]: group added to /etc/gshadow: name=builder <86>Mar 28 06:38:14 groupadd[23519]: new group: name=builder, GID=700 <86>Mar 28 06:38:14 useradd[23758]: new user: name=builder, UID=700, GID=700, home=/usr/src, shell=/bin/bash warning: user vitty does not exist - using root warning: group vitty does not exist - using root warning: user vitty does not exist - using root warning: group vitty does not exist - using root warning: user vitty does not exist - using root warning: group vitty does not exist - using root warning: line 22: Deprecated PreReq converted to Requires(pre,postun): PreReq: python = 2.7 warning: Macro %gconf2_install not found warning: Macro %gconf2_uninstall not found <13>Mar 28 06:38:20 rpmi: libexpat-2.2.4-alt1 1503305345 installed <13>Mar 28 06:38:20 rpmi: perl-HTTP-Date-6.02-alt1 1348645274 installed <13>Mar 28 06:38:20 rpmi: xml-utils-1:2.9.4.0.12.e905-alt1.1 1525115767 installed <13>Mar 28 06:38:20 rpmi: perl-LWP-MediaTypes-6.04-alt1 sisyphus+225468.100.1.1 1553186684 installed <13>Mar 28 06:38:20 rpmi: perl-libnet-1:3.11-alt1 1511423541 installed <13>Mar 28 06:38:20 rpmi: perl-Compress-Raw-Zlib-2.084-alt1.1 sisyphus+219907.700.1.1 1548343625 installed <13>Mar 28 06:38:20 rpmi: libICE-1.0.9-alt1 1409902721 installed <13>Mar 28 06:38:20 rpmi: libgdbm-1.8.3-alt10 1454943334 installed <13>Mar 28 06:38:20 rpmi: libSM-1.2.3-alt1 sisyphus.215747.100 1540812795 installed <13>Mar 28 06:38:20 rpmi: rpm-build-gir-0.7.2-alt4 1534675014 installed <13>Mar 28 06:38:20 rpmi: perl-File-Listing-6.04-alt1 1329758996 installed <13>Mar 28 06:38:20 rpmi: sgml-common-0.6.3-alt15 1423664786 installed <13>Mar 28 06:38:20 rpmi: docbook-dtds-4.5-alt1 1223476557 installed <13>Mar 28 06:38:21 rpmi: perl-Try-Tiny-0.30-alt1 1514318058 installed <13>Mar 28 06:38:21 rpmi: perl-IO-Socket-IP-0.39-alt1 1494508514 installed <13>Mar 28 06:38:21 rpmi: perl-HTML-Tagset-3.20-alt2 1317725093 installed <13>Mar 28 06:38:21 rpmi: perl-Filter-1.59-alt1.1 sisyphus+219907.400.1.1 1548343389 installed <13>Mar 28 06:38:21 rpmi: perl-Encode-3.01-alt1 sisyphus+224923.100.1.1 1552474122 installed <13>Mar 28 06:38:21 rpmi: perl-URI-1.76-alt1 sisyphus+220243.100.1.1 1548863244 installed <13>Mar 28 06:38:21 rpmi: perl-HTML-Parser-3.72-alt1.2 sisyphus+219907.600.1.1 1548343581 installed <13>Mar 28 06:38:21 rpmi: perl-WWW-RobotRules-6.02-alt1 1329756211 installed <13>Mar 28 06:38:21 rpmi: perl-Encode-Locale-1.05-alt1 1444608613 installed <13>Mar 28 06:38:21 rpmi: perl-IO-HTML-1.001-alt1 1404821752 installed <13>Mar 28 06:38:21 rpmi: perl-Term-ANSIColor-4.06-alt1 1479407083 installed <13>Mar 28 06:38:21 rpmi: perl-Data-Dump-1.23-alt1 1444601978 installed <13>Mar 28 06:38:21 rpmi: perl-Compress-Raw-Bzip2-2.084-alt1.1 sisyphus+219907.1000.1.1 1548343668 installed <13>Mar 28 06:38:21 rpmi: perl-IO-Compress-2.084-alt1 sisyphus+219744.100.2.1 1548168679 installed <13>Mar 28 06:38:21 rpmi: perl-HTTP-Message-6.18-alt1 1528288416 installed <13>Mar 28 06:38:21 rpmi: perl-HTTP-Cookies-6.04-alt1 1504116575 installed <13>Mar 28 06:38:21 rpmi: perl-HTTP-Negotiate-6.01-alt1 1329760563 installed <13>Mar 28 06:38:21 rpmi: perl-Net-HTTP-6.18-alt1 1526560501 installed <13>Mar 28 06:38:21 rpmi: perl-libwww-6.38-alt1 sisyphus+225751.100.1.1 1553679612 installed <13>Mar 28 06:38:21 rpmi: libX11-locales-3:1.6.7-alt1 sisyphus.214413.200 1539171080 installed <13>Mar 28 06:38:21 rpmi: libXdmcp-1.1.3-alt1 sisyphus+225206.600.1.2 1552949353 installed <13>Mar 28 06:38:21 rpmi: libXau-1.0.9-alt1 sisyphus+223149.200.2.1 1551268152 installed <13>Mar 28 06:38:21 rpmi: libxcb-1.13.1-alt1 sisyphus.214413.100 1539170896 installed <13>Mar 28 06:38:21 rpmi: libX11-3:1.6.7-alt1 sisyphus.214413.200 1539171143 installed <13>Mar 28 06:38:21 rpmi: shared-mime-info-1.12-alt1 sisyphus+219597.100.2.2 1548057005 installed <13>Mar 28 06:38:21 rpmi: gsettings-desktop-schemas-data-3.32.0-alt1 sisyphus+225059.300.3.2 1552843929 installed <13>Mar 28 06:38:21 rpmi: libgio-2.60.0-alt1 sisyphus+225059.100.3.2 1552843618 installed <13>Mar 28 06:38:21 rpmi: gsettings-desktop-schemas-3.32.0-alt1 sisyphus+225059.300.3.2 1552843980 installed <13>Mar 28 06:38:21 rpmi: liblz4-1:1.8.3-alt2 sisyphus+221902.4200.4.1 1550599659 installed <13>Mar 28 06:38:21 rpmi: libgpg-error-1.36-alt1 sisyphus+225621.300.1.1 1553521082 installed <13>Mar 28 06:38:21 rpmi: libgcrypt20-1.8.4-alt1 sisyphus+225621.500.1.1 1553521735 installed <13>Mar 28 06:38:21 rpmi: libsystemd-1:241-alt3 sisyphus+222052.100.2.1 1550681059 installed <13>Mar 28 06:38:21 rpmi: libdbus-1.12.12-alt2 sisyphus+221234.100.1.2 1549918047 installed <13>Mar 28 06:38:21 rpmi: libdbus-glib-1:0.106-alt1 1454672854 installed <13>Mar 28 06:38:21 rpmi: dbus-tools-1.12.12-alt2 sisyphus+221234.100.1.2 1549918047 installed <86>Mar 28 06:38:21 groupadd[54702]: group added to /etc/group: name=messagebus, GID=499 <86>Mar 28 06:38:21 groupadd[54702]: group added to /etc/gshadow: name=messagebus <86>Mar 28 06:38:21 groupadd[54702]: new group: name=messagebus, GID=499 <86>Mar 28 06:38:21 useradd[54959]: new user: name=messagebus, UID=499, GID=499, home=/run/dbus, shell=/dev/null <13>Mar 28 06:38:21 rpmi: dbus-1.12.12-alt2 sisyphus+221234.100.1.2 1549918047 installed <13>Mar 28 06:38:22 rpmi: dbus-tools-gui-1.12.12-alt2 sisyphus+221234.100.1.2 1549918047 installed <13>Mar 28 06:38:22 rpmi: libpolkit-0.115-alt5 sisyphus.219065.100 1547027030 installed <13>Mar 28 06:38:22 rpmi: libxslt-1.1.32-alt2 1517429984 installed <13>Mar 28 06:38:22 rpmi: xsltproc-1.1.32-alt2 1517429984 installed <13>Mar 28 06:38:22 rpmi: libtinfo-devel-6.1.20180407-alt2 sisyphus+222164.200.1.1 1550686226 installed <13>Mar 28 06:38:22 rpmi: libncurses-devel-6.1.20180407-alt2 sisyphus+222164.200.1.1 1550686226 installed <13>Mar 28 06:38:22 rpmi: python-modules-curses-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:22 rpmi: libverto-0.3.0-alt1_7 sisyphus+223221.100.1.1 1551348953 installed <13>Mar 28 06:38:22 rpmi: libkeyutils-1.6-alt2 sisyphus.217337.100 1544003161 installed <13>Mar 28 06:38:22 rpmi: libcom_err-1.44.6-alt1 sisyphus+224154.100.1.1 1552091678 installed <13>Mar 28 06:38:22 rpmi: libtasn1-4.13-alt2 1521133850 installed <13>Mar 28 06:38:22 rpmi: rpm-macros-alternatives-0.5.0-alt1 sisyphus+221902.300.4.1 1550587121 installed <13>Mar 28 06:38:22 rpmi: alternatives-0.5.0-alt1 sisyphus+221902.300.4.1 1550587121 installed <13>Mar 28 06:38:22 rpmi: libp11-kit-0.23.9-alt5 1525798298 installed <13>Mar 28 06:38:22 rpmi: ca-certificates-2019.02.01-alt1 sisyphus+220384.200.1.1 1549032756 installed <13>Mar 28 06:38:22 rpmi: ca-trust-0.1.1-alt2 1515595785 installed <13>Mar 28 06:38:22 rpmi: p11-kit-trust-0.23.9-alt5 1525798298 installed <13>Mar 28 06:38:22 rpmi: libcrypto1.1-1.1.1b-alt1 sisyphus+225327.200.2.1 1553099317 installed <13>Mar 28 06:38:22 rpmi: libssl1.1-1.1.1b-alt1 sisyphus+225327.200.2.1 1553099317 installed <13>Mar 28 06:38:22 rpmi: libpython3-3.6.8-alt1 sisyphus+220164.200.3.1 1548842636 installed <13>Mar 28 06:38:22 rpmi: python3-3.6.8-alt1 sisyphus+220164.200.3.1 1548842636 installed <13>Mar 28 06:38:23 rpmi: python3-base-3.6.8-alt1 sisyphus+220164.200.3.1 1548842636 installed <86>Mar 28 06:38:23 groupadd[60628]: group added to /etc/group: name=_keytab, GID=498 <86>Mar 28 06:38:23 groupadd[60628]: group added to /etc/gshadow: name=_keytab <86>Mar 28 06:38:23 groupadd[60628]: new group: name=_keytab, GID=498 <13>Mar 28 06:38:23 rpmi: libkrb5-1.16.3-alt1 sisyphus+223678.100.1.1 1551746516 installed <13>Mar 28 06:38:23 rpmi: libtirpc-1.0.3-alt1 1532008017 installed <13>Mar 28 06:38:23 rpmi: libnsl2-1.1.0-alt1_1 1511548749 installed <13>Mar 28 06:38:23 rpmi: python-modules-compiler-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:23 rpmi: python-modules-email-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:23 rpmi: python-modules-unittest-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:23 rpmi: python-modules-nis-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:23 rpmi: python-modules-encodings-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:23 rpmi: python-modules-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:23 rpmi: python-modules-xml-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:23 rpmi: python-modules-hotshot-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:23 rpmi: python-modules-bsddb-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:24 rpmi: python-modules-ctypes-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:24 rpmi: python-modules-multiprocessing-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:24 rpmi: python-modules-logging-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:24 rpmi: python-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:24 rpmi: python-modules-distutils-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:24 rpmi: libnsl2-devel-1.1.0-alt1_1 1511548749 installed <86>Mar 28 06:38:24 groupadd[62232]: group added to /etc/group: name=sasl, GID=497 <86>Mar 28 06:38:24 groupadd[62232]: new group: name=sasl, GID=497 <13>Mar 28 06:38:24 rpmi: libsasl2-3-2.1.27-alt1 sisyphus+223971.100.1.1 1551928460 installed <13>Mar 28 06:38:24 rpmi: libldap-2.4.46-alt1.1 sisyphus+219907.4400.1.1 1548349979 installed <13>Mar 28 06:38:24 rpmi: libGConf-3.2.6-alt3 1455932638 installed <13>Mar 28 06:38:24 rpmi: glib2-devel-2.60.0-alt1 sisyphus+225059.100.3.2 1552843618 installed <13>Mar 28 06:38:24 rpmi: libGConf-devel-3.2.6-alt3 1455932638 installed <13>Mar 28 06:38:25 rpmi: GConf-3.2.6-alt3 1455932638 installed <13>Mar 28 06:38:25 rpmi: python-dev-2.7.15-alt1 sisyphus.217364.100 1544022423 installed <13>Mar 28 06:38:25 rpmi: librarian-0.8.1-alt6 1384178687 installed <13>Mar 28 06:38:25 rpmi: perl-XML-Parser-2.44-alt2.2 sisyphus+219907.1300.1.1 1548343835 installed <13>Mar 28 06:38:25 rpmi: desktop-file-utils-0.23-alt1 sisyphus.214313.100 1539037620 installed warning: line 22: Deprecated PreReq converted to Requires(pre,postun): PreReq: python = 2.7 Building target platforms: i586 Building for target i586 Wrote: /usr/src/in/nosrpm/gnochm-0.9.11-alt1.2.qa1.1.nosrc.rpm warning: line 20: Deprecated PreReq converted to Requires(pre,postun): PreReq: python = 2.7 Installing gnochm-0.9.11-alt1.2.qa1.1.src.rpm Building target platforms: i586 Building for target i586 Executing(%prep): /bin/sh -e /usr/src/tmp/rpm-tmp.69641 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + rm -rf gnochm-0.9.11 + echo 'Source #0 (gnochm-0.9.11.tar.bz2):' Source #0 (gnochm-0.9.11.tar.bz2): + /bin/bzip2 -dc /usr/src/RPM/SOURCES/gnochm-0.9.11.tar.bz2 + /bin/tar -xf - + cd gnochm-0.9.11 + /bin/chmod -c -Rf u+rwX,go-w . + echo 'Patch #0 (gnochm-0.9.5.patch):' Patch #0 (gnochm-0.9.5.patch): + /usr/bin/patch -p0 patching file gnochm.py.in Hunk #1 succeeded at 49 (offset 1 line). + sed -i 's|$(SHAREDMIME_TOOL)|true $(SHAREDMIME_TOOL)|' data/Makefile.in + exit 0 Executing(%build): /bin/sh -e /usr/src/tmp/rpm-tmp.21049 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd gnochm-0.9.11 + CFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -march=i586 -mtune=generic' + export CFLAGS + CXXFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -march=i586 -mtune=generic' + export CXXFLAGS + FFLAGS='-pipe -frecord-gcc-switches -Wall -g -O2 -march=i586 -mtune=generic' + export FFLAGS + '[' -n '' ']' ++ sed -r 's/(^|[[:space:]]+)-[^m][^[:space:]]*//g' ++ printf %s '-pipe -frecord-gcc-switches -Wall -g -O2 -march=i586 -mtune=generic' + ASFLAGS=' -march=i586 -mtune=generic' + export ASFLAGS + export lt_cv_deplibs_check_method=pass_all + lt_cv_deplibs_check_method=pass_all + xargs -ri find '{}' -type f '(' -name config.sub -or -name config.guess ')' -printf '%h/\n' + xargs -rn1 install -pm755 -- /usr/share/gnu-config/config.sub /usr/share/gnu-config/config.guess + readlink -e -- ./configure + sort -u + xargs -ri dirname -- '{}' + ./configure --build=i586-alt-linux --host=i586-alt-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/lib --localstatedir=/var/lib --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --disable-dependency-tracking --without-included-gettext --disable-schemas-install checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for a BSD-compatible install... /bin/install -c checking for python... /usr/bin/python checking for version... 2.7 checking for platform... linux2 checking for gconftool-2... /usr/bin/gconftool-2 checking for scrollkeeper-config... /usr/bin/scrollkeeper-config checking for intltool >= 0.21... 0.30 found checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for iconv... /usr/bin/iconv checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... /usr/bin/msgmerge checking for xgettext... /usr/bin/xgettext Using config source xml:readwrite:/var/cache/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for style of include used by make... GNU checking for i586-alt-linux-gcc... i586-alt-linux-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i586-alt-linux-gcc accepts -g... yes checking for i586-alt-linux-gcc option to accept ANSI C... none needed checking dependency style of i586-alt-linux-gcc... none checking how to run the C preprocessor... i586-alt-linux-gcc -E checking for egrep... grep -E 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 locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... /usr/bin/msgfmt checking for dcgettext... yes checking for gmsgfmt... /usr/bin/msgfmt checking for xgettext... /usr/bin/xgettext checking for catalogs to be installed... be cs de el es fr hu it ja pl pt_BR ru sv tr vi zh_CN zh_TW checking for update-mime-database... /usr/bin/update-mime-database configure: creating ./config.status config.status: creating Makefile config.status: creating gnochm.lsm config.status: creating gnochm.py config.status: creating gnochm.spec config.status: creating pixmaps/Makefile config.status: creating glade/Makefile config.status: creating po/Makefile.in config.status: creating help/Makefile config.status: creating help/C/Makefile config.status: creating data/Makefile config.status: executing intltool commands config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing po/stamp-it commands + make make: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11' Making all in pixmaps make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' Making all in glade make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/glade' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/glade' Making all in po make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/po' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/po' Making all in help make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' Making all in C make[2]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' for file in gnochm-C.omf; do \ scrollkeeper-preinstall /usr/share/gnome/help/gnochm/C/gnochm.xml ./$file $file.out; \ done; \ touch omf_timestamp make[2]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[2]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[2]: Nothing to be done for 'all-am'. make[2]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' Making all in data make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/data' LC_ALL=C ../intltool-merge -d -u -c ../po/.intltool-merge-cache ../po gnochm.desktop.in gnochm.desktop Generating and caching the translation database WARNING: ../po/de.po is not in UTF-8 but iso-8859-1, converting... Merging translations into gnochm.desktop. LC_ALL=C ../intltool-merge -k -u -c ../po/.intltool-merge-cache ../po gnochm.keys.in gnochm.keys Found cached translation database Merging translations into gnochm.keys. LC_ALL=C ../intltool-merge -s -u -c ../po/.intltool-merge-cache ../po gnochm.schemas.in gnochm.schemas Found cached translation database Merging translations into gnochm.schemas. make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11' rm -f gnochm cp gnochm.py gnochm chmod +x gnochm make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11' make: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11' + exit 0 Executing(%install): /bin/sh -e /usr/src/tmp/rpm-tmp.24149 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + /bin/chmod -Rf u+rwX -- /usr/src/tmp/gnochm-buildroot + : + /bin/rm -rf -- /usr/src/tmp/gnochm-buildroot + cd gnochm-0.9.11 + /usr/bin/make 'INSTALL=/bin/install -p' prefix=/usr/src/tmp/gnochm-buildroot/usr exec_prefix=/usr/src/tmp/gnochm-buildroot/usr bindir=/usr/src/tmp/gnochm-buildroot/usr/bin sbindir=/usr/src/tmp/gnochm-buildroot/usr/sbin sysconfdir=/usr/src/tmp/gnochm-buildroot/etc datadir=/usr/src/tmp/gnochm-buildroot/usr/share includedir=/usr/src/tmp/gnochm-buildroot/usr/include libdir=/usr/src/tmp/gnochm-buildroot/usr/lib libexecdir=/usr/src/tmp/gnochm-buildroot/usr/lib localstatedir=/usr/src/tmp/gnochm-buildroot/var/lib sharedstatedir=/usr/src/tmp/gnochm-buildroot/var/lib mandir=/usr/src/tmp/gnochm-buildroot/usr/share/man infodir=/usr/src/tmp/gnochm-buildroot/usr/share/info install make: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11' Making install in pixmaps make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' make[2]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' make[2]: Nothing to be done for 'install-exec-am'. test -z "/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps" /bin/install -p -m 644 'chmfile.png' '/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps/chmfile.png' /bin/install -p -m 644 'gnochm.png' '/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps/gnochm.png' /bin/install -p -m 644 'gnochm_logo.png' '/usr/src/tmp/gnochm-buildroot/usr/share/pixmaps/gnochm_logo.png' make[2]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/pixmaps' Making install in glade make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/glade' make[2]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/glade' make[2]: Nothing to be done for 'install-exec-am'. test -z "/usr/src/tmp/gnochm-buildroot/usr/share/gnochm/glade" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/gnochm/glade" /bin/install -p -m 644 'gnochm.glade' '/usr/src/tmp/gnochm-buildroot/usr/share/gnochm/glade/gnochm.glade' /bin/install -p -m 644 'prefdialog.glade' '/usr/src/tmp/gnochm-buildroot/usr/share/gnochm/glade/prefdialog.glade' make[2]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/glade' make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/glade' Making install in po make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/po' if test -r ".././mkinstalldirs"; then \ .././mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share; \ else \ /bin/sh ../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share; \ fi mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/be/LC_MESSAGES installing be.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/be/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/cs/LC_MESSAGES installing cs.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/cs/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/de/LC_MESSAGES installing de.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/de/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/el/LC_MESSAGES installing el.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/el/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/es/LC_MESSAGES installing es.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/es/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/fr/LC_MESSAGES installing fr.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/fr/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/hu/LC_MESSAGES installing hu.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/hu/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/it/LC_MESSAGES installing it.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/it/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/ja/LC_MESSAGES installing ja.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/ja/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/pl/LC_MESSAGES installing pl.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/pl/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/pt_BR/LC_MESSAGES installing pt_BR.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/pt_BR/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/ru/LC_MESSAGES installing ru.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/ru/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/sv/LC_MESSAGES installing sv.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/sv/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/tr/LC_MESSAGES installing tr.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/tr/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/vi/LC_MESSAGES installing vi.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/vi/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/zh_CN/LC_MESSAGES installing zh_CN.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/zh_CN/LC_MESSAGES/gnochm.mo mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/locale/zh_TW/LC_MESSAGES installing zh_TW.gmo as /usr/src/tmp/gnochm-buildroot/usr/share/locale/zh_TW/LC_MESSAGES/gnochm.mo if test "gnochm" = "glib"; then \ if test -r ".././mkinstalldirs"; then \ .././mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/glib-2.0/gettext/po; \ else \ /bin/sh ../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/glib-2.0/gettext/po; \ fi; \ /bin/install -p -m 644 ./Makefile.in.in \ /usr/src/tmp/gnochm-buildroot/usr/share/glib-2.0/gettext/po/Makefile.in.in; \ else \ : ; \ fi make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/po' Making install in help make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' Making install in C make[2]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[3]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[3]: Nothing to be done for 'install-exec-am'. /bin/sh ../../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C for file in legal.xml gnochm.xml; do \ cp ./$file /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C; \ done if test ""; then \ /bin/sh ../../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C/; \ for file in .//*.png; do \ basefile=`echo $file | sed -e 's,^.*/,,'`; \ /bin/install -p -m 644 $file /usr/src/tmp/gnochm-buildroot/usr/share/gnome/help/gnochm/C//$basefile; \ done \ fi /usr/bin/make install-data-hook make[4]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' /bin/sh ../../mkinstalldirs /usr/src/tmp/gnochm-buildroot/usr/share/omf/gnochm mkdir -p -- /usr/src/tmp/gnochm-buildroot/usr/share/omf/gnochm for file in gnochm-C.omf; do \ /bin/install -p -m 644 $file.out /usr/src/tmp/gnochm-buildroot/usr/share/omf/gnochm/$file; \ done scrollkeeper-update -p /usr/src/tmp/gnochm-buildroot/var/lib/scrollkeeper -o /usr/src/tmp/gnochm-buildroot/usr/share/omf/gnochm make[4]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[3]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[2]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help/C' make[2]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[3]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[3]: Nothing to be done for 'install-exec-am'. make[3]: Nothing to be done for 'install-data-am'. make[3]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[2]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/help' Making install in data make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[2]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[2]: Nothing to be done for 'install-exec-am'. test -z "/usr/src/tmp/gnochm-buildroot/usr/share/application-registry" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/application-registry" /bin/install -p -m 644 'gnochm.applications' '/usr/src/tmp/gnochm-buildroot/usr/share/application-registry/gnochm.applications' if test -z "" ; then \ for p in gnochm.schemas ; do \ GCONF_CONFIG_SOURCE=xml:readwrite:/var/cache/gconf/gconf.xml.defaults /usr/bin/gconftool-2 --makefile-install-rule ./$p ; \ done \ fi Attached schema `/schemas/apps/gnochm/preferences/sync_page' to key `/apps/gnochm/preferences/sync_page' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/sync_page', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/sync_page', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/sync_page', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/sync_page', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/save_path' to key `/apps/gnochm/preferences/save_path' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/save_path', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/save_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/save_path', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/save_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/save_path', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/save_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/use_lcid' to key `/apps/gnochm/preferences/use_lcid' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/use_lcid', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/use_lcid', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/use_lcid', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/use_lcid', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/use_lcid', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/use_lcid', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/recent_size' to key `/apps/gnochm/preferences/recent_size' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/recent_size', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/recent_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/recent_size', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/recent_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/recent_size', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/recent_size', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/search_previous' to key `/apps/gnochm/preferences/search_previous' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/search_previous', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/search_previous', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/search_previous', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/search_previous', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/search_previous', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/search_previous', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/titles_only' to key `/apps/gnochm/preferences/titles_only' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/titles_only', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/titles_only', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/titles_only', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/titles_only', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/titles_only', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/titles_only', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/whole_words' to key `/apps/gnochm/preferences/whole_words' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/whole_words', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/whole_words', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/whole_words', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/whole_words', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/whole_words', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/whole_words', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/toolbar_enable' to key `/apps/gnochm/preferences/toolbar_enable' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/toolbar_enable', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_enable', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/toolbar_enable', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_enable', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/toolbar_enable', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_enable', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/toolbar_tooltips' to key `/apps/gnochm/preferences/toolbar_tooltips' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/toolbar_tooltips', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_tooltips', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/toolbar_tooltips', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_tooltips', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/toolbar_tooltips', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/toolbar_tooltips', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/tree_views' to key `/apps/gnochm/preferences/index_tree' Attached schema `/schemas/apps/gnochm/preferences/tree_views' to key `/apps/gnochm/preferences/contents_tree' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/tree_views', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/tree_views', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/tree_views', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/tree_views', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/tree_views', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/tree_views', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/html_bg_color' to key `/apps/gnochm/preferences/html_bg_color' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/html_bg_color', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/html_bg_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/html_bg_color', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/html_bg_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/html_bg_color', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/html_bg_color', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/chm_search_path' to key `/apps/gnochm/preferences/chm_search_path' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/chm_search_path', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/chm_search_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/chm_search_path', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/chm_search_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/chm_search_path', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/chm_search_path', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/http_support' to key `/apps/gnochm/preferences/http_support' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/http_support', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/http_support', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/http_support', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/http_support', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/http_support', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/http_support', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/new_browser_window' to key `/apps/gnochm/preferences/new_browser_window' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/new_browser_window', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/new_browser_window', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/new_browser_window', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/new_browser_window', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/new_browser_window', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/new_browser_window', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/auto_raise_window' to key `/apps/gnochm/preferences/auto_raise_window' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/auto_raise_window', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/auto_raise_window', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/auto_raise_window', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/auto_raise_window', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/auto_raise_window', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/auto_raise_window', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf Attached schema `/schemas/apps/gnochm/preferences/source_newwindow' to key `/apps/gnochm/preferences/source_newwindow' WARNING: failed to install schema `/schemas/apps/gnochm/preferences/source_newwindow', locale `C': Unable to store a value at key '/schemas/apps/gnochm/preferences/source_newwindow', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/source_newwindow', locale `it': Unable to store a value at key '/schemas/apps/gnochm/preferences/source_newwindow', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf WARNING: failed to install schema `/schemas/apps/gnochm/preferences/source_newwindow', locale `pt_BR': Unable to store a value at key '/schemas/apps/gnochm/preferences/source_newwindow', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf killall: /proc lacks process entries (not mounted ?) test -z "/usr/src/tmp/gnochm-buildroot/usr/share/applications" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/applications" /bin/install -p -m 644 'gnochm.desktop' '/usr/src/tmp/gnochm-buildroot/usr/share/applications/gnochm.desktop' test -z "/usr/src/tmp/gnochm-buildroot/usr/share/mime-info" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/mime-info" /bin/install -p -m 644 'gnochm.keys' '/usr/src/tmp/gnochm-buildroot/usr/share/mime-info/gnochm.keys' test -z "/usr/src/tmp/gnochm-buildroot/usr/share/mime-info" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/mime-info" /bin/install -p -m 644 'gnochm.mime' '/usr/src/tmp/gnochm-buildroot/usr/share/mime-info/gnochm.mime' test -z "/usr/src/tmp/gnochm-buildroot/etc/gconf/schemas" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/etc/gconf/schemas" /bin/install -p -m 644 'gnochm.schemas' '/usr/src/tmp/gnochm-buildroot/etc/gconf/schemas/gnochm.schemas' test -z "/usr/src/tmp/gnochm-buildroot/usr/share/mime/packages" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/share/mime/packages" /bin/install -p -m 644 'gnochm.xml' '/usr/src/tmp/gnochm-buildroot/usr/share/mime/packages/gnochm.xml' /usr/bin/make install-data-hook make[3]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11/data' if test "xtrue /usr/bin/update-mime-database" != "xno"; then \ true /usr/bin/update-mime-database /usr/src/tmp/gnochm-buildroot/usr/share/mime; \ fi make[3]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[2]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11/data' make[1]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11' make[2]: Entering directory '/usr/src/RPM/BUILD/gnochm-0.9.11' test -z "/usr/src/tmp/gnochm-buildroot/usr/bin" || mkdir -p -- "/usr/src/tmp/gnochm-buildroot/usr/bin" /bin/install -p 'gnochm' '/usr/src/tmp/gnochm-buildroot/usr/bin/gnochm' make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11' make[1]: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11' make: Leaving directory '/usr/src/RPM/BUILD/gnochm-0.9.11' + mv /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm.py + ln -s gnochm.py /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm + sed -i 's,/usr/bin/python,/usr/bin/env python,' /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm.py + /usr/lib/rpm/find-lang gnochm --with-gnome + rm -rf /usr/src/tmp/gnochm-buildroot/var/lib/scrollkeeper + desktop-file-install --dir /usr/src/tmp/gnochm-buildroot/usr/share/applications --remove-category=Utility --remove-category=Application --add-category=Office --add-category=Viewer /usr/src/tmp/gnochm-buildroot/usr/share/applications/gnochm.desktop /usr/src/tmp/gnochm-buildroot/usr/share/applications/gnochm.desktop: error: (will be fatal in the future): value "gnochm.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path + /usr/lib/rpm/brp-alt Cleaning files in /usr/src/tmp/gnochm-buildroot (auto) Verifying and fixing files in /usr/src/tmp/gnochm-buildroot (binconfig,pkgconfig,libtool,desktop) /usr/share/applications/gnochm.desktop: performed minor cleanup: 2d1 < Encoding=UTF-8 23c22 < Icon=gnochm.png --- > Icon=gnochm 28c27 < MimeType=application/x-chm --- > MimeType=application/x-chm; Checking contents of files in /usr/src/tmp/gnochm-buildroot/ (default) Compressing files in /usr/src/tmp/gnochm-buildroot (auto) Verifying ELF objects in /usr/src/tmp/gnochm-buildroot (arch=normal,fhs=normal,lfs=relaxed,lint=relaxed,rpath=normal,stack=normal,textrel=normal,unresolved=normal) Bytecompiling python modules in /usr/src/tmp/gnochm-buildroot using /usr/bin/python Can't list '/usr/src/tmp/gnochm-buildroot/usr/lib' Bytecompiling python modules with optimization in /usr/src/tmp/gnochm-buildroot using /usr/bin/python -O Can't list '/usr/src/tmp/gnochm-buildroot/usr/lib' Hardlinking identical .pyc and .pyo files Processing files: gnochm-0.9.11-alt1.2.qa1.1 Executing(%doc): /bin/sh -e /usr/src/tmp/rpm-tmp.71613 + umask 022 + /bin/mkdir -p /usr/src/RPM/BUILD + cd /usr/src/RPM/BUILD + cd gnochm-0.9.11 + DOCDIR=/usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + export DOCDIR + rm -rf /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + /bin/mkdir -p /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + cp -prL ABOUT-NLS AUTHORS ChangeLog NEWS README /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + chmod -R go-w /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + chmod -R a+rX /usr/src/tmp/gnochm-buildroot/usr/share/doc/gnochm-0.9.11 + exit 0 Finding Provides (using /usr/lib/rpm/find-provides) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.1vwWhm find-provides: running scripts (alternatives,debuginfo,gir,lib,pam,perl,pkgconfig,python,shell,typelib) Finding Requires (using /usr/lib/rpm/find-requires) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.TNAa4R find-requires: running scripts (cpp,debuginfo,files,gir-js,gir-python,gir,lib,pam,perl,pkgconfig,pkgconfiglib,python,rpmlib,shebang,shell,static,symlinks,typelib) python.req: /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm.py: skipping sys python.req: /usr/src/tmp/gnochm-buildroot/usr/bin/gnochm: skipping sys find-requires: FINDPACKAGE-COMMANDS: python Finding Requires(post) (using /usr/lib/rpm/find-scriptlet-requires) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.F33GDP Finding Requires(preun) (using /usr/lib/rpm/find-scriptlet-requires) Executing: /bin/sh -e /usr/src/tmp/rpm-tmp.n4K5d8 Requires: python2.7(libglade), python2.7(bonobo), /usr/bin/env, python-base, python-modules, python2.7(chm), python2.7(gconf), python2.7(gnome), python2.7(gobject), python2.7(gtk), python2.7(gtkhtml2), python2.7(mimetypes) Requires(interp): /bin/sh Requires(pre): python = 2.7 Requires(post): GConf2, scrollkeeper, desktop-file-utils, /bin/sh, /usr/sbin/gconf_install_schema Requires(preun): /bin/sh, /usr/sbin/gconf_uninstall_schema Requires(postun): python = 2.7, scrollkeeper, desktop-file-utils Wrote: /usr/src/RPM/RPMS/noarch/gnochm-0.9.11-alt1.2.qa1.1.noarch.rpm 5.39user 0.85system 0:17.24elapsed 36%CPU (0avgtext+0avgdata 18996maxresident)k 0inputs+0outputs (0major+495350minor)pagefaults 0swaps 13.98user 3.42system 0:39.60elapsed 43%CPU (0avgtext+0avgdata 116328maxresident)k 2312inputs+0outputs (0major+871401minor)pagefaults 0swaps --- gnochm-0.9.11-alt1.2.qa1.1.noarch.rpm.repo 2011-11-22 03:37:22.000000000 +0000 +++ gnochm-0.9.11-alt1.2.qa1.1.noarch.rpm.hasher 2019-03-28 06:38:51.389578509 +0000 @@ -51,11 +51,7 @@ Requires: /bin/sh -Requires: /bin/sh Requires: /usr/bin/env -Requires: /usr/bin/python -Requires: python2.7(ConfigParser) +Requires: python-base +Requires: python-modules Requires: python2.7(chm) -Requires: python2.7(codecs) Requires: python2.7(gconf) -Requires: python2.7(getopt) -Requires: python2.7(gettext) Requires: python2.7(gnome) @@ -64,13 +60,3 @@ Requires: python2.7(gtkhtml2) -Requires: python2.7(htmlentitydefs) -Requires: python2.7(locale) Requires: python2.7(mimetypes) -Requires: python2.7(os) -Requires: python2.7(pickle) -Requires: python2.7(re) -Requires: python2.7(sgmllib) -Requires: python2.7(string) -Requires: python2.7(urllib) -Requires: python2.7(urlparse) -Requires: python2.7(webbrowser) Requires: /usr/sbin/gconf_install_schema