Re: [Tails-dev] Please review draft documentation for IUK
intrigeri: Hi, sajol...@pimienta.org wrote (08 Jan 2014 11:36:08 GMT) : 1. Tails was not started from a writable device. Which cases does this refer to? when starting from a DVD? a read-only USB stick? what else? We happily delegate to bilibop the decision regarding whether the boot medium is writable. This of course includes DVD, and I believe one of the latest bilibop releases (that we're installing in feature/wheezy only) also detects the read-only switches on SD cards and USB sticks. Then what about: Tails was started from a DVD or a read-only device. I know that a DVD is a read-only device, but I bet this phrasing will be less problematic for some people. 4. There is not enough free space on the Tails system partition (a bit too technical, but how to express that without having tons of people nagging user support because, oh well, they have space left on their persistent volume?) Then, what can I do to get out of this? Reinstall? Yes, manual (full) upgrade. That's already what we tell them to do in this case anyway. Sure, that works. signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
sajol...@pimienta.org wrote (09 Jan 2014 10:19:15 GMT) : intrigeri: sajol...@pimienta.org wrote (08 Jan 2014 11:36:08 GMT) : 1. Tails was not started from a writable device. Which cases does this refer to? when starting from a DVD? a read-only USB stick? what else? We happily delegate to bilibop the decision regarding whether the boot medium is writable. This of course includes DVD, and I believe one of the latest bilibop releases (that we're installing in feature/wheezy only) also detects the read-only switches on SD cards and USB sticks. Then what about: Tails was started from a DVD or a read-only device. I know that a DVD is a read-only device, but I bet this phrasing will be less problematic for some people. OK. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri: I'm unconvinced (especially given we have to close #5735 first) that this can land into 0.22.1, but I'd be glad to see this improved for a future iteration. Filed #6575 as a subtask of #6508 (incremental upgrades: complete phase four), targetted at Tails 0.23. Let's do that. I've quickly had the code above save the reason why an incremental upgrade is not possible. The checks that are done, and the corresponding codenames for that reason, are (in chronological order): 1. non-writable-device 2. not-installed-with-tails-installer 3. no-incremental-upgrade-path 4. not-enough-free-space 5. not-enough-free-memory If one check does not pass, the others are not performed; in practice, there might be multiple reasons why an incremental upgrade is not possible, but we're only saving one. I think this should be enough to substantially improve UX, though. So, when advising the user to do a manual (full) upgrade, we can now insert a sentence that's specific to the primary reason why we cannot do an incremental upgrade, e.g.: 1. Tails was not started from a writable device. Which cases does this refer to? when starting from a DVD? a read-only USB stick? what else? 2. The device Tails is running from was not created using Tails Installer. 3. The Tails project does not provide an incremental upgrade to this version. (e.g. will be the case for 1.1, most likely) In the online doc I said: « No automatic upgrade is available from our website for this version. » I never used incremental in the end. 4. There is not enough free space on the Tails system partition (a bit too technical, but how to express that without having tons of people nagging user support because, oh well, they have space left on their persistent volume?) Then, what can I do to get out of this? Reinstall? 5. Not enough memory is available on this system. signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
Hi, sajol...@pimienta.org wrote (08 Jan 2014 11:36:08 GMT) : 1. Tails was not started from a writable device. Which cases does this refer to? when starting from a DVD? a read-only USB stick? what else? We happily delegate to bilibop the decision regarding whether the boot medium is writable. This of course includes DVD, and I believe one of the latest bilibop releases (that we're installing in feature/wheezy only) also detects the read-only switches on SD cards and USB sticks. 2. The device Tails is running from was not created using Tails Installer. 3. The Tails project does not provide an incremental upgrade to this version. (e.g. will be the case for 1.1, most likely) In the online doc I said: « No automatic upgrade is available from our website for this version. » I never used incremental in the end. OK, good. 4. There is not enough free space on the Tails system partition (a bit too technical, but how to express that without having tons of people nagging user support because, oh well, they have space left on their persistent volume?) Then, what can I do to get out of this? Reinstall? Yes, manual (full) upgrade. That's already what we tell them to do in this case anyway. 5. Not enough memory is available on this system. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
sajol...@pimienta.org wrote (02 Jan 2014 15:02:13 GMT) : 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 :) I'm not against right-click but I'm really against the link pretending being clickable when it is not. OK, fair enough. 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). Yes, it was in the stderr I got. Thank you for confirming. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri wrote (26 Dec 2013 13:34:43 GMT) :
intrigeri wrote (25 Dec 2013 18:54:12 GMT) :
#1. New version available
-
Applied (as found on the blueprint).
So, this reads:
You should manually upgrade to %{name}s
%{version}s.\n\n.
For more information about this new version, go to
%{details_url}s.\n\n.
Note that it is not possible to do an automatic upgrade
.
on your system. Automatic upgrades are only possible on
.
a Tails device installed using Tails Installer.\n\n.
To learn how to manually upgrade, go to .
https://tails.boum.org/doc/first_steps/upgrade/#manual;,
I find this confusing for users who would be pointed to the manual
upgrade despite they have installed Tails with our installer,
e.g. because there isn't enough free space on the system partition, or
not enough free memory to apply the incremental upgrade.
What do you think?
Did I miss your reply on that one?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri:
intrigeri wrote (26 Dec 2013 13:34:43 GMT) :
intrigeri wrote (25 Dec 2013 18:54:12 GMT) :
#1. New version available
-
Applied (as found on the blueprint).
So, this reads:
You should manually upgrade to %{name}s
%{version}s.\n\n.
For more information about this new version, go to
%{details_url}s.\n\n.
Note that it is not possible to do an automatic upgrade
.
on your system. Automatic upgrades are only possible on
.
a Tails device installed using Tails Installer.\n\n.
To learn how to manually upgrade, go to .
https://tails.boum.org/doc/first_steps/upgrade/#manual;,
I find this confusing for users who would be pointed to the manual
upgrade despite they have installed Tails with our installer,
e.g. because there isn't enough free space on the system partition, or
not enough free memory to apply the incremental upgrade.
What do you think?
Did I miss your reply on that one?
Actually, I'm the one who missed your question.
You are right, the reasons to force a manual upgrade can be many. I
tried to fix that with commit b0e9acb4 on the blueprint.
It's a shame that we don't provide more information on why it is not
possible to do an automatic upgrade. The resulting dialog is a bit
mysterious but the different reasons are explain in the documentation. I
think that's how far we can get for the moment.
I let you think about how hard it would be to be a bit more informative
inside that same dialog, and decide on how much you feel like improving
on that.
I also added commit c417569 on feature/incremental-upgrades-integration.
signature.asc
Description: OpenPGP digital signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
Hi, sajol...@pimienta.org wrote (07 Jan 2014 17:38:01 GMT) : You are right, the reasons to force a manual upgrade can be many. I tried to fix that with commit b0e9acb4 on the blueprint. Applied, thanks. It's a shame that we don't provide more information on why it is not possible to do an automatic upgrade. The resulting dialog is a bit mysterious but the different reasons are explain in the documentation. I think that's how far we can get for the moment. I let you think about how hard it would be to be a bit more informative inside that same dialog, and decide on how much you feel like improving on that. I'm unconvinced (especially given we have to close #5735 first) that this can land into 0.22.1, but I'd be glad to see this improved for a future iteration. Filed #6575 as a subtask of #6508 (incremental upgrades: complete phase four), targetted at Tails 0.23. I've quickly had the code above save the reason why an incremental upgrade is not possible. The checks that are done, and the corresponding codenames for that reason, are (in chronological order): 1. non-writable-device 2. not-installed-with-tails-installer 3. no-incremental-upgrade-path 4. not-enough-free-space 5. not-enough-free-memory If one check does not pass, the others are not performed; in practice, there might be multiple reasons why an incremental upgrade is not possible, but we're only saving one. I think this should be enough to substantially improve UX, though. So, when advising the user to do a manual (full) upgrade, we can now insert a sentence that's specific to the primary reason why we cannot do an incremental upgrade, e.g.: 1. Tails was not started from a writable device. 2. The device Tails is running from was not created using Tails Installer. 3. The Tails project does not provide an incremental upgrade to this version. (e.g. will be the case for 1.1, most likely) 4. There is not enough free space on the Tails system partition (a bit too technical, but how to express that without having tons of people nagging user support because, oh well, they have space left on their persistent volume?) 5. Not enough memory is available on this system. Improvements are welcome. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri:
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
Too bad. But your solution is fine...
#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.
Will do.
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?
Absolutely not. I was surprised by this unit but if you think that's the
way forward. Then I'm fine with that.
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 :)
I'm not against right-click but I'm really against the link pretending
being clickable when it is not.
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).
Yes, it was in the stderr I got.
signature.asc
Description: OpenPGP digital signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri wrote (25 Dec 2013 18:54:12 GMT) : 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. Actually, upgrade again seems suboptimal: first, it suggests that the user has something specific to do, which is wrong; second, this is not about upgrading, but merely about checking for upgrades. 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). Re-thinking of it a bit, this might be a bit more serious than I thought initially. I still hold the position that it's fine if applying an incremental upgrade requires a bit more than 1GB of RAM. However, *checking* for available upgrades should work with the minimal recommended amount of RAM. So, *if* it's enough to close the web browser to make this work (which I believe, and will try to confirm later today - #6535), then I'll mark this as blocked by #5735 (dont autostart iceweasel) and will work on completing that one too. Worst case, if even closing the browser is not enough, then I'll have to find another solution or workaround. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri wrote (25 Dec 2013 18:54:12 GMT) :
#1. New version available
-
Applied (as found on the blueprint).
So, this reads:
You should manually upgrade to %{name}s %{version}s.\n\n.
For more information about this new version, go to
%{details_url}s.\n\n.
Note that it is not possible to do an automatic upgrade .
on your system. Automatic upgrades are only possible on .
a Tails device installed using Tails Installer.\n\n.
To learn how to manually upgrade, go to .
https://tails.boum.org/doc/first_steps/upgrade/#manual;,
I find this confusing for users who would be pointed to the manual
upgrade despite they have installed Tails with our installer,
e.g. because there isn't enough free space on the system partition, or
not enough free memory to apply the incremental upgrade.
What do you think?
Cheers,
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri wrote (25 Dec 2013 18:54:12 GMT) : Applied, but zenity does not support bold text AFAICT, so: I was wrong, and am reintroducing all the bold text that sajolida proposed. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri wrote (26 Dec 2013 13:30:53 GMT) : However, *checking* for available upgrades should work with the minimal recommended amount of RAM. So, *if* it's enough to close the web browser to make this work (which I believe, and will try to confirm later today - #6535), then I'll mark this as blocked by #5735 (dont autostart iceweasel) and will work on completing that one too. In my tests, everything works fine with 1GB of RAM, see details on #6535, even when leaving the browser open. sajolida, please tell me how I can reproduce this issue. E.g. were you running the incremental upgrader multiple times in the same session, or using APT, or running other apps at the same time, or what? Reassigned #6535 to sajolida for more info. In the meantime, I'll consider this as not something I can do anything about. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
Hi, sajol...@pimienta.org wrote (22 Dec 2013 22:06:26 GMT) : http://git.tails.boum.org/tails/tree/wiki/src/doc/first_steps/upgrade.mdwn?h=feature/incremental-upgrades-integration As always, think about the structure of the doc, the workflow, and the content first, then go into the phrasing if you want. I'll do the markup later on. First, I'm confused. You wanted me (with pretty good reasons) to rename Tails Upgrader to Tails Incremental Upgrader, so I did that a few weeks ago (and, well, it was quite painful). And now the doc refers to Tails Upgrader everywhere. What's wrong? If you use Tails from a DVD or if your Tails device was not installed using Tails Installer, it is not possible to upgrade and you need to follow our [[installing instructions|download#media]] again with the new ISO image. s/installing/installation/ ? - If an error occurs while checking for available upgrades:br/ [[file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html|upgrade/error/check]] - If an error occurs while download the upgrade:br/ [[file:///usr/share/doc/tails/website/doc/upgrade/error/download.en.html|upgrade/error/download]] - If an error occurs while installing the upgrade:br/ [[file:///usr/share/doc/tails/website/doc/upgrade/error/install.en.html|upgrade/error/install]] Links to file:///, really? This won't work for those who read this page online, outside of Tails. In that case, span class=applicationTails Installer/span allows you to manually upgrade a USB stick or SD card to a newer version of Tails. - [[Upgrade by cloning from another device|upgrade#clone]] which already runs a newer version of Tails - [[Upgrade from an ISO image|upgrade#from_iso]] of a newer version of Tails Needs some linking words between the first sentence and the bullet list, maybe? In doc/upgrade/error, I read Check your network connection, and restart Tails to try upgrading again. but this is not really about upgrading, as most likely there is no upgrade available. Checking for available upgrades, instead? Other than this, all this seems very good to me, congrats! I also had to propose several changes to the dialogs and error messages. Thanks -- I'll look at it later, probably tomorrow. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
Hi,
sajol...@pimienta.org 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
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
Hi, #1. New version available - *You should manually upgrade to Tails 0.22.* For more information, go to https://tails.boum.org/news/version_0.22/. Note that it is not possible to do an automatic upgrade on your system. Automatic upgrades are only possible on a Tails device installed using Tails Installer. Download size: 916 MB Do you want to download the ISO image now? [Cancel] [Download] XXX: I get an error when clicking on Download: (gksudo:4338): GLib-CRITICAL **: g_str_has_prefix: assertion `str != NULL' failed localuser:tails-upgrade-frontend being removed from access control list This was known to be broken (#6509), that's why it is not an option anymore since tails-iuk 0.12. So, it looks very much like you used an older version of tails-iuk than the one my Last steps toward enabling incremental upgrades by default email asked to use: I've just released Tails-IUK 0.13, that fixes all coding tasks left for phase three. I'm giving it a manual testing session as we speak. Please use this version (or later) for any further testing, documentation work and comments. If I'm correct, could you please check if using the recommended version impacts other suggestions or documentation of yours? I'd like this point to be clarified before I dive into the rest, as the dialog titles, buttons and more have changed since the version you might have been testing. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review draft documentation for IUK
intrigeri: Hi, #1. New version available - *You should manually upgrade to Tails 0.22.* For more information, go to https://tails.boum.org/news/version_0.22/. Note that it is not possible to do an automatic upgrade on your system. Automatic upgrades are only possible on a Tails device installed using Tails Installer. Download size: 916 MB Do you want to download the ISO image now? [Cancel] [Download] XXX: I get an error when clicking on Download: (gksudo:4338): GLib-CRITICAL **: g_str_has_prefix: assertion `str != NULL' failed localuser:tails-upgrade-frontend being removed from access control list This was known to be broken (#6509), that's why it is not an option anymore since tails-iuk 0.12. So, it looks very much like you used an older version of tails-iuk than the one my Last steps toward enabling incremental upgrades by default email asked to use: I've just released Tails-IUK 0.13, that fixes all coding tasks left for phase three. I'm giving it a manual testing session as we speak. Please use this version (or later) for any further testing, documentation work and comments. If I'm correct, could you please check if using the recommended version impacts other suggestions or documentation of yours? I'd like this point to be clarified before I dive into the rest, as the dialog titles, buttons and more have changed since the version you might have been testing. Yes, that was already clear to me. But in the middle all those tests, this precise one from my VM was not done using tails-iuk 0.13 obviously. The other ones should be. I tried again the bug I got when trying to upgrade in a VM with 1GB of RAM and I still get it with 0.13. So I adapter a tiny bit the corresponding dialog. And as we might work on them incrementally, I also added them to the blueprint, so we can have all the advantages of Git :) https://tails.boum.org/blueprint/incremental_upgrades/#index4h2 signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
[Tails-dev] Please review draft documentation for IUK
I pushed the draft documentation for IUK to feature/incremental-upgrades-integration, see eee4313..5f3f56b. The main course is: http://git.tails.boum.org/tails/tree/wiki/src/doc/first_steps/upgrade.mdwn?h=feature/incremental-upgrades-integration As always, think about the structure of the doc, the workflow, and the content first, then go into the phrasing if you want. I'll do the markup later on. 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. Not enough memory available --- *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.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. Error while checking for upgrades - *Could not determine whether an upgrade is available from our website.* Check your network connection, and restart Tails to try upgrading again. If the problem persists, go to file:///usr/share/doc/tails/website/doc/upgrade/error/check.en.html. *Debugging information* ... #1. Upgrade available - *You should upgrade to Tails 0.22.* For more information, go to https://tails.boum.org/news/version_0.22/. Note that: - It is recommended to close all the open applications during the upgrade. - Downloading the upgrade might take a long time, from several minutes to a few hours. - The networking will be disabled after downloading the upgrade. Download size: 201 MB Do you want to upgrade now? [Upgrade later] [Upgrade now] XXX: Round the download size. XXX: Use MB instead of MiB? 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. #1. New version available - *You should manually upgrade to Tails 0.22.* For more information, go to https://tails.boum.org/news/version_0.22/. Note that it is not possible to do an automatic upgrade on your system. Automatic upgrades are only possible on a Tails device installed using Tails Installer. Download size: 916 MB Do you want to download the ISO image now? [Cancel] [Download] XXX: I get an error when clicking on Download: (gksudo:4338): GLib-CRITICAL **: g_str_has_prefix: assertion `str != NULL' failed localuser:tails-upgrade-frontend being removed from access control list #2. Downloading upgrade --- Downloading the upgrade to Tails 0.22... XXX: Use upgrade to XXX: Don't use please, as we are not to blame if the download is slow Error while downloading the upgrade --- *The upgrade could not be downloaded.* Check your network connection, and restart Tails to try upgrading again. If the problem persists, go to file:///usr/share/doc/tails/website/doc/upgrade/error/download.en.html. *Debugging information* ... XXX: Does it make sense to add the URL in the debugging information as it might already be in the stderr? #3. Upgrading the system *Your Tails device is being upgraded...* For security reasons, the networking is now disabled. Error while installing the upgrade -- *An error occured while installing the upgrade.* Your Tails device needs to be repaired and might be unable to restart. Please follow the instructions at file:///usr/share/doc/tails/website/doc/upgrade/error/install.en.html *Debugging information* ... #4. Restart Tails - *Your Tails device was successfully upgraded.* Some security features were temporarily disabled. You should restart Tails on the new version as soon as possible. Do you want to restart now? [Restart later] [Restart now] signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
