1. 17 Aug, 2020 9 commits
    • intrigeri's avatar
      Install Electrum and its dependencies from Bullseye (testing) instead of sid · 0a16c52d
      intrigeri authored
      Right now this is a no-op as the exact same versions are in testing and sid.
      But Electrum updates in sid tend to break stuff (e.g. #17828) on Buster,
      so let's at least avoid RC bugs from breaking Tails.
    • intrigeri's avatar
      Install trezor and python3-trezor 0.12.1 from Bullseye · 5739cdf7
      intrigeri authored
      According to
      #17461 (comment 151109), "Upcoming version of Electrum (4.0) requires python-trezor 0.12. This version of python-trezor is also required for the newest Trezor firmware update!"
      Folks on #17461 are reporting WIP about having python3-trezor in
      buster-backports, so let's hope this is temporary, because the risk
      python3-trezor/sid becomes uninstallable on Buster is too high for my taste.
      Still, in the meantime, let's avoid breaking TREZOR support in Tails 4.10.
      refs #17461
    • intrigeri's avatar
      Edit configuration in "offline" mode when starting Electrum · a895eb5b
      intrigeri authored
      Otherwise this command fails because "Daemon not running",
      and thus we abort our wrapper script and Electrum won't start.
      refs #17828
    • intrigeri's avatar
      Install python3-attr from buster-backports · 1c1fd0d8
      intrigeri authored
      Otherwise, Electrum aborts on startup with an exception:
          ValueError: Non keyword-only attributes are not allowed after
          a keyword-only attribute.
      I've reported to Debian the fact this dependency should be versioned:
      refs #17828
    • intrigeri's avatar
      Install python3-cryptography, otherwise Electrum 4.0.2-0.1 won't start · 14acdd12
      intrigeri authored
      I've mentioned this upstream on https://bugs.debian.org/968563,
      without filing a proper bug report as I did not test on sid.
      refs #17828
    • intrigeri's avatar
      Test suite: improve robustness of cloning a Git repository · 003a5a45
      intrigeri authored
      On a fast system, I've seen the "I clone the Git repository […]" scenario fail
      because "test -d '/home/amnesia/testing/.git" returned 1. This check was done
      just a few milliseconds after "Unpacking objects: 100%" appeared in the
      Terminal. My hypothesis here is that Git takes a a little bit of time, after
      displaying "Unpacking objects: 100%", until it actually puts the cloned files
      into place.
    • intrigeri's avatar
      Rubocop: target Ruby 2.5 (Buster) · 7b7cbcbe
      intrigeri authored
      Initially I had set this to 2.3 (Stretch), because most of the code we're
      analyzing is meant to be run on our Jenkins isobuilders or isotesters, that
      currently run Stretch.
      But Rubocop 0.81+ don't support analyzing code targeted at Ruby 2.3,
      so let's bump this to 2.5 (Buster), so that at least Rubocop can run.
      Rubocop 0.88.0 detects 58 offenses, but that'll be for another day.
    • intrigeri's avatar
    • intrigeri's avatar
      Test suite: improve robustness · b9a32d12
      intrigeri authored
      I've seen the "Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt
      volume with a keyfile" scenario fail with "cannot find
      GnomeDisksUnlockDialogKeyfileComboBox.png on the screen (FindFailed)".
      The video shows that the previous steps happened super quickly via Dogtail,
      while the dialog box was not fully rendered on screen yet, so I understand the
      keyfiles combo box was not visible yet when we tried to click on it. Let's wait
      a bit for it to appear.
      Note that this can go away in Tails 5.0, which will have GNOME Disks ≥ 3.35.2,
      which fixes #15952 ⇒ we can use Dogtail for interacting with the keyfiles
      combo box too.
  2. 16 Aug, 2020 10 commits
  3. 14 Aug, 2020 21 commits