Bug 94479 - Eterm: Warning: Config file is designed for a newer version of Eterm
|
Bug#:
94479
|
Product: Gentoo Linux
|
Version: 2005.0
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: vapier@gentoo.org
|
Reported By: nt@divzero.at
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: Eterm: Warning: Config file is designed for a newer version of Eterm
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-05-30 03:33 0000
|
this warning appears whenever i open an Eterm (on the console of course) and i
just don't understand that, because i get those warnings with the same version
of Eterm i created the config files with. if i delete the theme.conf and
user.conf in ~/.Eterm the warngins are gone, as are my user configs...
well you didnt really provide much info ...
what version of libast/eterm are you using ? what does your config file look like ?
* x11-terms/eterm
Latest version available: 0.9.3-r4
Latest version installed: 0.9.3-r4
* x11-libs/libast
Latest version available: 0.6.1
Latest version installed: 0.6.1
root@eNTi # emerge info
Portage 2.0.51.22-r1 (default-linux/amd64/2005.0, gcc-3.4.3-20050110,
glibc-2.3.5-r0, 2.6.11-gentoo-r8 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r8 x86_64 AMD Athlon(tm) 64 Processor 3500+
Gentoo Base System version 1.6.12
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.3 [enabled]
dev-lang/python: 2.3.5
sys-apps/sandbox: 1.2.8
sys-devel/autoconf: 2.13, 2.59-r6
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils: 2.16-r1
sys-devel/libtool: 1.5.18
virtual/os-headers: 2.6.11-r1
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d"
CXXFLAGS="-march=k8 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache digest distlocks fixpackages sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.inode.at/
http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/
http://mir.zyrianes.net/gentoo/
ftp://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/
ftp://mir.zyrianes.net/gentoo/
http://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/
ftp://ftp.ntua.gr/pub/linux/gentoo/
http://ftp.snt.utwente.nl/pub/os/linux/gentoo
http://ftp.ntua.gr/pub/linux/gentoo/ ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 16bit X a52 aalib acpi acpi4linux alsa apache2 audiofile
bash-completion berkdb bitmap-fonts bzip2 bzlib c++ cdb cdda cddb cdinstall
cdparanoia chroot crypt ctype cups curl dga dio dts dvb dvd dvdr dvdread
emul-linux encode ethereal fam flac font-server foomaticdb freetype ftp gdbm gif
gkrellm gmp gphoto2 gpm gtk gtk2 icq imagemagick imlib imlib2 ipv6 java
javascript jikes jp2 jpeg junit lesstif libmikmod libwww lua lzw lzw-tiff mad
maildir matroska mcal mikmod motif moznocompose moznoirc moznomail mp3 mpeg
mplayer ncurses net nethack nls nvidia offensive ogg oggvorbis openal opengl pam
pdflib perl png ppds print procmail python qt readline samba sdl ssl svg sysvipc
tcltk tcpd tetex tga threads tiff timidity transcode truetype truetype-fonts
type1 type1-fonts usb userlocales utf8 v4l v4l2 videos vim vim-with-x vorbis
xchatdccserver xine xml2 xmms xosd xpm xrandr xv xvid zlib userland_GNU
kernel_linux elibc_glibc"
Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
it's just the version string you have at the top ...
i just use the same one i used with 0.9.2, so the top of my file says:
<Eterm-0.9.2>
which works fine with Eterm-0.9.3 ... oddly enough, if i change the version to
0.9.3, i start getting the warnings like you :)
ah, it's already been fixed in upstream CVS
i grabbed the changes from cvs and added to 0.6.1-r1
