Where communities thrive


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

    emkll on docs-backport-4900

    (compare)

  • 19:23

    emkll on 1.1.0

    Fix link to Tails update guide … Merge pull request #4906 from f… (compare)

  • 19:23
    emkll closed #4906
  • 18:48
    rmol commented #4887
  • 18:02

    emkll on backport_4892

    (compare)

  • 18:02

    emkll on 1.1.0

    Fix column/button alignment pro… Reduce the space between index … Merge pull request #4908 from f… (compare)

  • 18:02
    emkll closed #4908
  • 17:19

    emkll on 4848-tor-0.4.1.6

    (compare)

  • 17:02
    eloquence labeled #4909
  • 16:53
    emkll commented #4887
  • 16:53
    emkll commented #4887
  • 16:31
    emkll commented #4887
  • 16:31
    emkll commented #4887
  • 16:30
    emkll commented #4887
  • 16:29
    emkll commented #4887
  • 15:58
    eloquence unlabeled #4880
  • 15:58
    eloquence edited #4908
  • 15:34
    redshiftzero commented #4909
  • 15:29
    kushaldas commented #4909
  • 14:25
    emkll commented #4887
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
cc @conorsch
Conor Schaefer
@conorsch
no blockers to report here
proceeding with dns cutover
rmol
@rmol
here either.
Erik Moeller
@eloquence
\o/ :shipit:
Conor Schaefer
@conorsch
Proceeding with Nagios updates...
Erik Moeller
@eloquence
@conorsch I'm assuming docs branch and github release object are next on your list?
Conor Schaefer
@conorsch
thank for the reminder, one sec...
Conor Schaefer
@conorsch
@eloquence refresh my memory on the docs branch update step? i believe some action is required in ReadTheDocs—ensuring that release/1.0.0 maps to "stable", yes?
Erik Moeller
@eloquence
yes
"Make sure that the default branch of documentation is being built off the tip of the release branch."
so I think that's what you just said in different words :)
Conor Schaefer
@conorsch
still working on docs branch changes... i don't see the release/1.0.0 in there, so rebuilding from latest ad-hoc in an attempt to trigger a branch refresh
the webhook is still connected, i see successful deliveries from today
Erik Moeller
@eloquence
roger that, holding off on release announcement until then so we don't have to link to latest
Conor Schaefer
@conorsch
@eloquence should be good to go now, please check docs.securedrop.org and confirm you see 1.0.0
rmol
@rmol
Can confirm.
Erik Moeller
@eloquence
lgtm as well
Conor Schaefer
@conorsch
documented the steps here in the maintainer guide, since i couldn't find any pre-existing docs on updating the docs ("Yo, dawg...")
Erik Moeller
@eloquence
nice
posting release notes ...
nb, upgraded my instance via cron-apt and it seems to have worked fine, did have to shift+reload to clear out old stylesheets from cache
@conorsch could you poke at that backport docs PR?
Conor Schaefer
@conorsch
on it
Erik Moeller
@eloquence
will attempt to switch my longrunning instance over to v3 while bulk announce is running, in case of any issues not caught in QA for which it can serve as a canary
Erik Moeller
@eloquence
graphical updater worked, it did pop up an "updater already running" message briefly
Erik Moeller
@eloquence
getting my old friend "waiting for privilege escalation prompt" on playbook run