On 08/22/2009 01:53 PM, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report which was
filed against the enlightenment package:
#541477: enlightenment: configuration lost in update to e16
It has been closed by Marco Rodrigues <[email protected]>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Marco Rodrigues
<[email protected]> by replying to this email.
It is indeed unsatisfactory.
You filled the bug http://bugs.debian.org/541477 in Debian BTS
against the package enlightenment. I'm closing it at *unstable*, but
it will remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/492508. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
As it happens, I had found that particular bug report myself in the last
few days. It does not seem to provide the reasons for the package being
removed (it simply states that that is the case), and the possible
replacement which it indirectly suggests - e16 - is not viable, for the
reasons I gave in my own bug report and which I elaborate on below.
I am aware that the enlightenment package has been removed from Debian;
that is precisely the problem, or at least part of it.
According to the bug report you linked to, the enlightenment package has
been replaced by the e16 package; however, according to what I have been
told in response to my own bug report, there is no upgrade path from
enlightenment to e16. It is therefore not viable to simply uninstall
enlightenment and install e16, as I would expect to be the procedure for
a "replacement" update; further configuration is needed. What's more, as
far as I was able to tell when I inadvertently made the experiment,
simply copying the ~/.enlightenment directory to ~/.e16 would not work;
at a glance, the directories and the files they contain seem to have
different formats.
It does not appear to be possible to upgrade cleanly from enlightenment
to e16 without losing configuration settings. e16 is stated to be the
replacement for enlightenment (though apparently this is not advertised
in ay way which would bring the fact to the attention of people who
might need to make the switch). This seems to me to be a very obvious
and very serious problem, which is in serious need of fixing before the
removal of enlightenment can be made truly final.
I understand if it is not possible (within the package guidelines) to
automatically convert ~/.foobar config settings between packages, for
technical and policy reasons. However, I would expect that if those
settings will be lost, there would at least be a prominent alert message
at install time (e.g. via apt-listchanges or simply the curses-based
configuration dialogs) that these settings will have to be migrated by
hand, with either an explanation of how to do so or a link to a place to
find such an explanation. That would not be truly satisfactory, but it
would be sufficient if no better solution is practical.
Thank you for your contribution to Debian.
You're quite welcome. I'd prefer to contribute more (and more
practically) than I have, but I haven't had much time, and what I have
has been taken up by other interests. Just because I'm less than happy
in this case shouldn't be taken to mean that I'm unhappy with Debian; I
like it very much, and that's precisely why it bothers me that a problem
like this is being dismissed the way this one seems to be.
--
The Wanderer
Warning: Simply because I argue an issue does not mean I agree with any
side of it.
Secrecy is the beginning of tyranny.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
