dom0 update issue: Domain sys-firewall sent unexpected file

[eloquence]

@ninavizz experienced the following update failure during a dom0 update (the SecureDrop Workstation preflight updater failed, after which I encouraged her to try using Qubes' own updater):

This seems to be a very unusual error, a Google search turns up only the code which generates it. Tracking in our repo for now until we understand it better.

[ninavizz]

Erik advised I reboot and try again, and I got the same result. This is a screenie of the resulting logs... :(

[conorsch]

turns up only the code which generates it

The code in question: https://github.com/QubesOS/qubes-core-admin-linux/blob/a3098d517f9f85af4ec02db4077ecf2192f340a5/dom0-updates/qubes-receive-updates#L83-L85

See discussion in #540 (comment). We recently uploaded an rpm to the staging yum repo with a tilde in the filename—which fails the regex validation in qubes-receive-updates, even though it's technically a valid rpm. Immediate fix is removing that problematic rc file from the dom0 repo. Then, in #540, we'll discuss solutions to the naming pragma.

[conorsch]

Changes in freedomofpress/securedrop-yum-test#9 should have resolved, running updater in "staging" env now to confirm resolved...

[conorsch]

Confirmed successful update via SD graphical updater on login, using dedicated test-only hardware running the "staging" env for the Workstation. We still have outstanding work regarding the rc, see #540 for details.

[conorsch]

Confirming that graphical updater in "staging" env successfully upgraded to 0.3.0 rc1, after merge of:

• Updates rc naming convention in RPM spec #554
• SecureDrop Workstation 0.3.0 rc1 rpm package securedrop-yum-test#10

Haven't performed functional testing, but clearly we've resolved the installation problems originally documented in this ticket. We'll continue with QA following #548