[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Enigma-devel] Loss of lifes in Debian 0.92.1-1 enigma releases
From: |
Ronald Lamprecht |
Subject: |
Re: [Enigma-devel] Loss of lifes in Debian 0.92.1-1 enigma releases |
Date: |
Thu, 19 Jan 2006 00:20:09 +0100 |
User-agent: |
Mozilla Thunderbird 1.0.7 (Windows/20050923) |
Hi Erich,
Erich Schubert wrote:
I just uploaded a new SVN checkout of enigma to Debian unstable.
I used the version number 0.92.2 for that, hoping that you'll stick to
using only two components. ;-)
I corrected the development trunk with patch r66 on January 1st. Please
apply this patch to the Debian release.
I recommended to integrate a single valuable patch to the Debian version.
Let me hope that you do not use the current r71 trunk version as 0.92.2
- with r61 we started Xerxes XML integration, with r71 we started
switching to XML. Even though we provide upgrade functionality from the
official 0.92 and earlier releases concerning options, scores and levels
there is no and there will be no upgrade functionality between different
trunk development releases!!
I can not recommend using any trunk revision >70 for playing Enigma. You
may loose all scorings you achieve with these versions!
Nevertheless we are thankfull for any reports from trunk-revision
testers - you can play the official release and test the trunk in
parallel without the danger of loss of data. (Of course you have to use
different install prefixes for Unix - /usr/local and /home/sweethome f.e.).
Since you seem to have enigma svn access, would you take a look at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343820
which is a swedish translation of the .po file.
(and maybe at the other open debian bugs, too, which are about specific
levels)
I scheduled the swedish translation when examinig 0.92.1. Sorry, the
level specific topics are currently of low priority as we started
fundamental code cleanups, updates and technology additions. We
currently do not have the manpower to provide a separate
0.92-maintainance repository branch. The fixes will end up anytime on
the trunk and may be not back portable to 0.92.
best regards,
Ronald