Hi,
sajolida@??? wrote (22 Dec 2013 22:06:26 GMT) :
> I also had to propose several changes to the dialogs and error
> messages. So here they are. I hope it's clear which blob I'm
> referring to. I added some notes flagged XXX along the way.
> The title of the section should be the titles of the windows but
> I think that most of them were already ok.
Good!
When I write "applied" below, I'm talking of my local copy of
the code.
I'll notify this thread when I've prepared and tested a new version of
Tails-IUK with all these changes in.
> Not enough memory available
> ---------------------------
Applied, but I had to turn the bullet list into something else, and
</br> into newline, since zenity can't display these. This gives:
Not enough memory available to check for upgrades.
Make sure this system satisfies the requirements for running Tails.
See
file:///usr/share/doc/tails/website/doc/about/requirements/index.en.html.
Try to restart Tails and upgrade again.
Or do a manual upgrade.
See
https://tails.boum.org/doc/first_steps/upgrade#manual
> XXX: I get this error message when trying to do the upgrade from a VM
> with 1024MB. That's in contradiction with what is on the
> requirement page at the moment.
IIRC, I've seen that too when the web browser was open, but not
otherwise. Can you confirm this? Also, we're running many various
programs in parallel (and in the background) at login time, so the
results might be a little bit racy / random in this area.
Perhaps we should just merge feature/dont_autostart_iceweasel to
workaround this issue (IIRC that branch was only blocked by the broken
test suite, and it looks like, thanks to bertagaz, I might be able to
fix that in the next few days).
Anyway, the requirements page also says one can use Tails on a DVD,
and then one doesn't get incremental upgrades either, so personally
I'm not *that* concerned even if incremental upgrades require, say,
a bit more than 1GB of RAM. On the long run, I'll port all this stuff
from Moose to Moo, and we'll save some RAM — WIP (e.g. I've proposed
a patch upstream to port GnuPG::Interface to Moo today).
> Error while checking for upgrades
> ---------------------------------
Applied, but zenity does not support bold text AFAICT, so:
"Could not determine whether an upgrade is available from our website.\n\n".
"Check your network connection, and restart Tails to try upgrading again.\n\n".
"If the problem persists, go to file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html.",
> #1. Upgrade available
> ---------------------
Applied, but no bullet lists again, so:
"You should upgrade to %{name}s %{version}s.\n\n".
"For more information about this new version, go to %{details_url}s.\n\n".
"It is recommended to close all the open applications during the upgrade.\n".
"Downloading the upgrade might take a long time, from several minutes to a few hours.\n".
"The networking will be disabled after downloading the upgrade.\n\n".
"Download size: %{size}s\n\n".
"Do you want to upgrade now?"
> XXX: Round the download size.
Why not. Please create an "easy" ticket for that, making it clear to
which precision you think it should be rounded. Not a blocker IMHO.
> XXX: Use MB instead of MiB?
I think I remember reading that the sensible people around here are
migrating to the less ambiguous MiB (and friends), and trying to make
their units consistent system-wide. I may be wrong. Is it serious
enough that I should research this further, or?
Not a blocker anyway either IMO. Best case, that's a normal priority
"easy" ticket.
> XXX: The link shouldn't be clickable if you cannot click on it.
> People can do almost the same copy paste operation, or copy it
> manually.
I'm not totally convinced, as I do like to right-click -> copy link
address, but well, OK, applied :)
> #1. New version available
> -------------------------
Applied (as found on the blueprint).
> #2. Downloading upgrade
> -----------------------
Applied.
> Error while downloading the upgrade
> -----------------------------------
Applied.
> XXX: Does it make sense to add the URL in the debugging information as
> it might already be in the stderr?
Assuming you've actually checked it is in the stderr, I've applied the
proposed phrasing (without the URL).
> #3. Upgrading the system
> ------------------------
Applied.
> Error while installing the upgrade
> ----------------------------------
Applied.
> #4. Restart Tails
> -----------------
Applied.
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
