Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 16:17

    redshiftzero on develop

    Removes xfail on the test_journ… swapped constants for magic num… Merge pull request #4987 from z… (compare)

  • 16:17
    redshiftzero closed #4987
  • 16:17
    redshiftzero closed #4978
  • 15:10
    rocodes synchronize #4991
  • 14:58
    redshiftzero commented #4992
  • 14:27
    zenmonkeykstop commented #4988
  • 14:26
    zenmonkeykstop commented #4764
  • 14:24
    emkll edited #4990
  • 14:23
    emkll opened #4992
  • 14:23
    emkll labeled #4992
  • 13:57

    emkll on docs-prune

    (compare)

  • 13:57

    emkll on master

    Remove obsolete README from pre… Merge pull request #335 from fr… (compare)

  • 13:57
    emkll closed #335
  • 12:49
    rocodes synchronize #4991
  • 07:57
    eloquence edited #335
  • 07:56
    eloquence labeled #335
  • 07:56
    eloquence opened #335
  • 07:56

    eloquence on docs-prune

    Remove obsolete README from pre… (compare)

  • 07:51
    eloquence labeled #334
  • 07:51
    eloquence labeled #334
Conor Schaefer
@conorsch
ETA for unsigned Release file ~45m...
Conor Schaefer
@conorsch
SD debs built, tor debs fetched, proceeding with upload to apt-qa...
Conor Schaefer
@conorsch
Uploading debs...
Conor Schaefer
@conorsch
Debs are up at https://apt-qa.freedom.press/ without a signed Release file. Before I pass the Release file over for signing, I'd appreciate a sanity-check on the packages exposed at that URL
(I'm requesting visual review via browser; apt installs won't work)
mickael e.
@emkll
debs on apt-qa lgtm
proceeding to sign the release file
Conor Schaefer
@conorsch
release file signature verified, uploading to apt-qa. stand by for preflight testing
Kushal Das
@kushaldas
yay
Conor Schaefer
@conorsch
Release file uploaded! Please proceed with preflight testing. Remember to use the prod SecureDrop Release Signing Key, but set the apt repo URL to https://apt-qa.freedom.press/
Kevin O'Gorman
@zenmonkeykstop
will nuke these nucs and test the fresh install
Conor Schaefer
@conorsch
roger, i'm testing an in-place upgrade on prod vms
mickael e.
@emkll
in-place upgrade successful, fancy new logo appears. Now testing the graphical updater upgrading to v3 onions
Conor Schaefer
@conorsch
i'm a bit behind on in-place upgrade testing—didn't have a full 0.14.0 environment in place, as i'd thought. resolving now, will continue from there
Conor Schaefer
@conorsch
in-place upgrade on servers went smoothly, confirming new design is displayed and furthermore quite spiffy. proceeding with graphical updater and migration to v3...
mickael e.
@emkll
I keep getting an incorrect admin password error when running the GUI updater in VMs
Kevin O'Gorman
@zenmonkeykstop
Fresh install of 1.0.0 with v3 in progress
Conor Schaefer
@conorsch
@emkll i got that once; when i reran it it was fine though. might have fat-fingered it...
David Huerta
@huertanix
Tails desktop shortcut ticket added: freedomofpress/securedrop#4837.
Erik Moeller
@eloquence
wonderful, we can definitely get that into 1.1.0
David Huerta
@huertanix
:cool:
Kushal Das
@kushaldas
I guess I will just crash
Conor Schaefer
@conorsch
In-place upgrade testing complete. Successful migration to v2&v3.
mickael e.
@emkll
i am running upgrade testing on mac minis right now, the upgrade was successful , migrating from v2-> v2+v3 over tor, it's taking a while
Conor Schaefer
@conorsch
:+1:
Kevin O'Gorman
@zenmonkeykstop
I got an error on the tails update phase of the GUI updater as well
Erik Moeller
@eloquence
oh noes
Conor Schaefer
@conorsch
drat, was it wrong password, @zenmonkeykstop ?
Kevin O'Gorman
@zenmonkeykstop
str:
  • git checkout 0.14.0
  • bounce network
  • clicked Update now
  • entered password when prompted
Conor Schaefer
@conorsch
i'll reset my tails env to dev, delete the 1.0.0 tag locally inside tails, reboot, and try again
thanks for STR!
Kevin O'Gorman
@zenmonkeykstop
Dunno, will retry
oh, one other thing, the ansible defaults change to apt-qa was still there.
success! with git reset --hard HEAD first
Conor Schaefer
@conorsch
ah-ha! so you had a dirty working copy
Kevin O'Gorman
@zenmonkeykstop
one annoying thing - because the securedrop_init.py script always bounces network, you now get the pop-up saying the updater is already running in the tailsconfig part of the process
Conor Schaefer
@conorsch
yeah i've seen that =( not ideal
that one's worth a follow-up issue, not a release blocker though
Kevin O'Gorman
@zenmonkeykstop
running it one more time with clean working copy, then wil lsee if i can recreate failure again
it's also not ideal that it doesn't give a useful message
Conor Schaefer
@conorsch
lgtm: after reboot, i was able to type in admin password in gui updater, and it took it the first time. i did see a failure afterward, during run of the tailsconfig step, but that's because i'd wiped the aths info from persistence out of habit, so tailsconfig couldn't find the necessary files (it did the first several times i ran it during initial migration)
Kevin O'Gorman
@zenmonkeykstop
haha that time it worked for me with the change in place
Conor Schaefer
@conorsch
looking good over here. @emkll, how fare you with graphical updater tests?
mickael e.
@emkll
Ok, that worked, I did indeed have a file that was left over from previous testing
:sweat_smile:
Conor Schaefer
@conorsch
woohoo! we just had the RM tap out due to timezones. what say you, DRM @emkll? (note: DRM = Deputy Release Manager)
mickael e.
@emkll
I'm almost done migrating a mac mini to v3 onion services, once that is complete and if/when @zenmonkeykstop is satisfied, i think we can proceed with the cutover
Conor Schaefer
@conorsch
roger that, standing by for dns cutover
Kevin O'Gorman
@zenmonkeykstop
preflights all working for me
mickael e.
@emkll
ok all preflights successful. Unless anyone has any objections, we can cut over