How to install new version?
Szlamka József
I was away for a while and now as I'm back I realised that a new version is available. I'd like to upgrade my Ghini installation to the new version.
According to the documentation (http://ghini.readthedocs.io/en/ghini-1.0-dev/building.html):
"... users will notice a new version available warning and can decide to ignore it, or to update."
However, when I start Ghini there is no notification about the new version. So my very basic question is:
How can I upgrade to the new version?
The "About" window of the application says that my currently installed version is "Ghini 1.0.75".
Let me also propose a small additional info into the "About" window: the date of the version.
Regards:
József Szlamka
szlajozs
mainly because of the Hungarian translation.
thanks @szlajozs !
Mario Frasca
Hi József and all,
I'm afraid the mistake was from my side, I will review what I precisely did... as described in the docs (which is a reminder to me and in general to the responsible for releasing versions), one publishes a new release making sure the set of commits contains a version bump. I'm sure I didn't check, I suspect the version bump commit isn't included. I will review it next week, or you can check yourself too.
I don't think we should add a timestamp in text, I'm afraid the
text would become too long and users don't read long texts, we
just click them away.
we could have a version publishing script, which could check if the version bumping commit is in place and warn the user if it is not there.
or we need be more careful than I was in my last version
publication. but this warning will not prevent similar errors in
the future. something that has a non-zero probability of happening
will eventually happen.
as said, I will have time next week, maybe some of you have wants
to write a nice version publishing script in the meanwhile?
ciao,
Mario
--
You received this message because you are subscribed to the Google Groups "ghini/bauble" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bauble+un...@googlegroups.com.
To post to this group, send email to bau...@googlegroups.com.
Visit this group at https://groups.google.com/group/bauble.
For more options, visit https://groups.google.com/d/optout.
Szlamka József
Thank you for the explanation of the missing version check.
Regarding the addition of the version timestamp text into the "About" window, let me argue for it. We are not talking about an annoying nag screen that users hate and click away. This is a window that users call intentionally because they want to see the information it contains. I do think that adding an additional line containing the version timestamp text between the version line with bold larger font size and the Copyright line with small font size would be useful.
For example let's see my particular case:
I'm a user very new to Ghini so I don't know the exact behaviour of the app yet. I got a notification email from Github about the availability of a new version, but this notification didn't contain any info about the exact release number, only "[Ghini/ghini.desktop] publish to 1.0 (#298)". According to the documentation I expected a notice about the new version at program start, but there was nothing. As I don't know the behaviour of the app, one possible explanation that came into my mind: "what if that there was an automatic upgrade to the new version, let's check the About window!" The only useful info I knew from the About window was that my installed version is 1.0.75. As the notification email from github doesn't contain the precise release number (or I didn't find it), I don't know whether my installed version of 1.0.75 is up to date or not. I only remember that I installed Ghini some time in November and the Ghini notification is dated 4th Dec. So this is why the version timestamp would be a very useful info on the "About" screen. (At least in this particular case ...)
Of course I understand if this request is not among the most important items of the todo list or development roadmap of Ghini.
Ciao,
József
Mario Frasca
Hi József,
thanks for the quite complete description of your particular case. it makes a very good issue, and it's really very little work, implementing it. do you want to open it on github? the only trouble with it is updating all corresponding translation strings.
I generally think of myself as quite paranoid too, which I think
is a good thing to have: some healthy paranoia, but I had not
considered this case. (you star the project, receive a "new
release" notification by email, you don't see it when starting up
the software.)
so... please open the issue on github, and even better propose a pull request that (partially) implements the solution to the issue.
I will have time next week.
ciao,
Mario
Mario Frasca
apparently we already have a 'publish' script, and I don't dare check, but I'm afraid it was me who wrote it.
yes, it was me, last year August.
and in the commit comment I also added that the script was "in perspective the place to put all the next steps, like publishing to pip and updating the Windows NSIS installer."
if I understand what Ross has been doing, this last part has to happen —necessarily— in Windows, so we can't put it here, but we can put here a kind reminder. publishing to pip, however, can be automated. we could have a look...
cheers, M
Szlamka József
My Ghini desktop version is "Ghini 1.0.75". At startup I noticed a
warning about an available new version. I exited and ran from commandline:
~/bin/ghini -u
That downloaded a lot of stuff and completed without error. Then I
started Ghini again. According to the header of the statup window my
version is still 1.0.75. The startup warning changed a bit and now it is
saying:
(translated back to English from Hungarian):
"New version 1.0.80 is available. You have to exit in order to update."
I tried to re-run "~/bin/ghini -u" but nothing changed, and my installed
version is still 1.0.75.
What shall I do in order to get upgraded?
Regards:
József
Mario Frasca
give me some time, I'm the middle of something else, in the meanwhile
see if you manage to gather more information, about the location of the
files you're activating. if you have only one installed ghini, or you
have a global, and a local one. the documentation should mention
something about `ghini -u`, installed in the administrator's `~/bin`, or
in `/usr/local/bin`, maybe it helps, or maybe it needs reviewing in
order to help.
I'll come back to you within a couple of days.
you're not using ghini.pocket, are you?
cheers,
Mario
Mario Frasca
On 03/10/2018 12:54 PM, Szlamka József wrote:
> ~/bin/ghini -u
> Then I started Ghini again
could it be that you're using two different ghini.desktop instances?
like: the one you start from the command line using ~/bin/ghini (and
which you now updated), and the one which got integrated in your graphic
user interface is, say, /usr/local/bin/ghini? and they aren't the
same? like one is in a virtual environment, the other in a different one?
I would try starting ghini from the command line, using ~/bin/ghini.
how can you otherwise update and still get the old one... ?
or you missed an error message while updating? this sounds less likely.
let me know,
cheers,
Mario
Szlamka József
I don't think I have two different ghini.desktop instances. The commandline behind the Ghini menu item in my graphic ui is:
/usr/local/bin/ghini
Starting this brings up the following window:
And here is the window that starts when i run ~/bin/ghini from a terminal window:
I think both calls start the same ghini.desktop instance.
Cheers: József
Mario Frasca
forgot to include the list in the cc.
-------- Forwarded Message --------
| Subject: | Re: How to install new version? |
|---|---|
| Date: | Sun, 11 Mar 2018 20:13:12 -0500 |
| From: | Mario Frasca <ma...@anche.no> |
| To: | Szlamka József <szla...@gmail.com> |
Hi Jószef,
looks like update was not successful after all,
can you confirm by invoking again `~/bin/ghini -u`, and checking the log?
maybe you want to do it this way:
~/bin/ghini -u 2>&1 | tee /tmp/logfile.txt
let me know,
ciao,
Mario
Mario Frasca
this sounds so weird, I don't know what to think,
you could...
- check in `/home/szlajozs/.virtualenvs`, and see how many virtualenvs you have, that can be related to ghini-1.0
- confirm you only have one ghini.desktop package installed, it should be this one: /home/szlajozs/.virtualenvs/ghide/lib/python2.7/site-packages/ghini.desktop-1.0.80-py2.7.egg
- open `/home/szlajozs/.virtualenvs/ghide/bin/ghini` and verify that it mentions 1.0.80
but how do you get in this situation, and how can we detect, avoid, correct, I still do not know...
I'm afraid we need more logging, could you open an issue and
request that the log (~/.bauble/bauble.log) should start with
stating the version and the location of the ghini installation?
that would only help in future cases.
ciao,
M
Szlamka József
Many thanks for the hints. Unfortunately I don't have any Python experience, so concerning your first hint
(>- check in `/home/szlajozs/.virtualenvs`, and see how many virtualenvs you have, that can be related to ghini-1.0))
I don't know how to check how many ghini-related virtualenvs I have.
>- confirm you only have one ghini.desktop package installed, it should be this one: /home/szlajozs/.virtualenvs/ghide/lib/python2.7/site-packages/ghini.desktop-1.0.80-py2.7.egg
>- open `/home/szlajozs/.virtualenvs/ghide/bin/ghini` and verify that it mentions 1.0.80
#!/home/szlajozs/.virtualenvs/ghide/bin/python
# EASY-INSTALL-SCRIPT: 'ghini.desktop==1.0.80','ghini'
__requires__ = 'ghini.desktop==1.0.80'
__import__('pkg_resources').run_script('ghini.desktop==1.0.80', 'ghini')
>but how do you get in this situation, and how can we detect, avoid, correct, I still do not know...
>I'm afraid we need more logging, could you open an issue and request that the log (~/.bauble/bauble.log) should start with stating the version and the location of the ghini installation?
How do you see, did the above info give you any further clue?
Ciao,
József
Mario Frasca
On 03/12/2018 12:36 PM, Szlamka József wrote:
> >- confirm you only have one ghini.desktop package installed, it
> should be this one:
> /home/szlajozs/.virtualenvs/ghide/lib/python2.7/site-packages/ghini.desktop-1.0.80-py2.7.egg
> In /home/szlajozs/.virtualenvs/ghide/lib/python2.7/site-packages/ I
> have a subfolder "bauble-1.0.75-py2.7.egg" and also
> "ghini.desktop-1.0.80-py2.7.egg". Is that OK?
indeed the source of the problem. did I possibly change the way ghini
identifies itself? passing from bauble to ghini.desktop? I am not sure,
I will check.
you should be able to safely remove the one with 'bauble' in the name:
rm -fr
/home/szlajozs/.virtualenvs/ghide/lib/python2.7/site-packages/ghini.desktop-1.0.80-py2.7.egg
but really, the installation procedure should take care of this by itself.
thank you for opening the issue about logging.
let me know if removing that bauble 1.0.75 helps
ciao
Mario
Szlamka József
Many, many thanks, it is working now!!!!
As you suggested, I removed the subfolder "bauble-1.0.75-py2.7.egg", and
after that I launched Ghini from the graphical UI menu and the good
version started. Running ~/bin/ghini from the commandline also launches
the good version (1.0.80).
Thank you for your guidence!
And this is also a very special moment for me. This new version contains
the Hungarian translations I made several weeks ago, and now this is the
first time I can see them in live environment.
Ciao,
József
Mario Frasca
On 03/12/2018 04:45 PM, Szlamka József wrote:
> And this is also a very special moment for me
nice, I'm glad we had you again up and running.
I will try to replicate your situation here, and avoid it a next time.
ciao
M
Mario Frasca
here Ross changed the name of the 'egg' to 'ghini.desktop', this is not the name of the module:
299dd2a18 (RossD 2016-09-05 23:53:38 +1000 456) setuptools.setup(name="ghini.desktop",
the module is still called 'bauble', since you still import it with 'import bauble',
I suppose we should roll it back (and you will need to manually again remove the 'egg' named 'ghini.desktop'),
or we have to change the installation script.
I think much easier rolling it back.
but we need unit tests, to avoid this to happen again. I need to open an issue, but not right now, too late at night people make mistakes.
M
On Monday, 12 March 2018 16:45:51 UTC-5, Szlamka József wrote:
Hi Mario,
Many, many thanks, it is working now!!!!
As you suggested, I removed the subfolder "bauble-1.0.75-py2.7.egg", and