Hi Ville, Sorry it took so long to respond. I had just set up an anti-spam system which mails the reply-to address for verification. Having added google.com to my white-list did not help for the group mail, which comes from googlegroups.com. I just noticed your reply now, when I saw it in my queue of mails awaiting verification.
I'll answer as specifically as possible below, but my point was about improving the packaging procedure, which would lower the number of support issues with new installs. Please do consider the benefits of the approach I suggested. It would help no matter what packaging system is used, whether Debian, RPM, tgz, something on Microsoft, whatever. These issues exist whatever one is using (even Foresight Linux ;-) > > * The first hurdle was an incomplete install, which I was unable > > to remove or purge. > > What was the error message about? I did not at that time take copious notes, but it complained about some Python files, which I found strange, as apt should have sorted that out. Leo itself was installed, in that it was on the system, and in the path, but it would not launch without the extra Python stuff. That's when I tried to purge leo, but couldn't. > > * I then took the file list from the .deb package and removed all > > the top-level directories. [I know, there are better ways, but this is > > what I did.] > > > * Thinking that maybe it's an issue with the latest, I tried to > > install via the repositories, and got a complaint about some python-qt > > stuff (sorry, I did not keep notes) which I had to get installed via > > "apt-get -f install", which I did. > > > * Upon running leo, however, I received a Python usage complaint. > > Can you be more specific about this? It'd be much easier for me to fix > (I am to blame for all the .deb problems). It was a Python script complaining about something being called incorrectly. The exact text I cannot recall. It was at that stage that I concluded that it expected something that a previous version installed. > > It looks like the latest version expects stuff from previous versions > > to be in place. That doesn't help someone with no previous versions. I > > This is unlikely. When you upgrade, all the old files are removed, and > the packaging hasn't changed at all b/w 4.6.1 and 4.6.2. There are > other problems afoot. mm. Well, the fact remains that the following took place on my machine: 1. Latest version of Leo fails to install. 2. Latest version of Leo fails to UNinstall. 3. Latest version of Leo removed manually. 4. Immediately prior version of Leo installs. 5. Successfully upgraded (via .deb) to latest version of Leo. My guess is that it has nothing to do with Leo directly, but rather with an intermediate state in one of the libraries upon which it depends. I am here referring to the regular case of running something like "apt-get install one_package_name", then getting a screen full of other stuff installed as well. A regression in any of Leo's dependencies could have caused this. The approach I recommend will definitely deal with that, and make it extremely easy to generate automatically a list of true dependencies. Thanks again for taking time on this. I have yet to use Leo properly, and it's already blowing me away! ~8-) John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
