Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

signal-desktop: bumps for 19.03 #61886

Merged
merged 5 commits into from May 22, 2019
Merged

Conversation

flokli
Copy link
Contributor

@flokli flokli commented May 22, 2019

Motivation for this change

signal-desktop on 19.03 complains about the version being expired, and asking to upgrade, so let's do that!

We should probably always backport signal-desktop version bumps to the stable release.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

(cherry picked from commit 078de9c)
(cherry picked from commit ff7d16f)
(cherry picked from commit cbeea59)
(cherry picked from commit e98c2c8)
(cherry picked from commit fab6d81)
@flokli flokli requested a review from primeos May 22, 2019 14:11
@schmittlauch
Copy link
Member

I just ran nix-review on this and can confirm it's working fine.

@flokli flokli changed the title signal-desktop: bumps for 19.03 [19.03] signal-desktop: 1.22.0 -> 1.24.1 May 22, 2019
@flokli flokli changed the title [19.03] signal-desktop: 1.22.0 -> 1.24.1 signal-desktop: bumps for 19.03 May 22, 2019
@flokli flokli merged commit a45bc20 into NixOS:release-19.03 May 22, 2019
@flokli flokli deleted the signal-desktop-19.03 branch May 22, 2019 15:17
@primeos
Copy link
Member

primeos commented May 22, 2019

@flokli thanks for the backport :)

We should probably always backport signal-desktop version bumps to the stable release.

Yes, that was a bit unfortunate... :o Normally I backport a bunch of updates ~30 days before the version on the stable channel expires (can e.g. be extracted from libexec/resources/app.asar -> {"buildExpiration":1563316653000} -> date --date="@1563316653" -> Wed Jul 17 00:37:33 CEST 2019). But it seems like I forgot to add a reminder to my calendar after the last backport (probably because there was no backport for 19.03 yet).

Backporting every update individually would unfortunately significantly increase my workload as I don't use a stable channel and have to use VMs for testing (I'm not sure if there was ever a problem, but I don't want to risk it and skip testing). If someone has time for it that would be great, if not I would continue as before and give my best to not miss any backports (could probably add a periodic reminder after that branch-offs as well to add a new reminder for the stable channel).

@flokli
Copy link
Contributor Author

flokli commented May 22, 2019

@primeos no worries. Thanks for maintaining :-)

I wasn't aware signal-desktop clients have an expiration date. Maybe we should add this in a comment in the derivation somewhere.

I added a nixos vm test in #61916, that does OCR on the "Link your phone to Signal Desktop" message

Assuming you already tested basic functionality on unstable and the vm test on 19.03 passed, I'd consider it highly unlikely this will break in other major ways. But whatever workflow works for you best :-)

@primeos
Copy link
Member

primeos commented May 23, 2019

I wasn't aware signal-desktop clients have an expiration date. Maybe we should add this in a comment in the derivation somewhere.

Good idea. I'll have a look at this for the next update (maybe I could automate it and use it for reminders as well).

I added a nixos vm test in #61916, that does OCR on the "Link your phone to Signal Desktop" message

Thanks :)

Assuming you already tested basic functionality on unstable and the vm test on 19.03 passed, I'd consider it highly unlikely this will break in other major ways. But whatever workflow works for you best :-)

I also think that it's safe to assume that the backport works, if it doesn't crash during the launch due to incompatible dependencies or other problems.

@flokli
Copy link
Contributor Author

flokli commented May 24, 2019

I backported to signal test to 19.03 too, so checking should be pretty simple :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants