Skip to content

Conversation

strugee
Copy link
Contributor

@strugee strugee commented Apr 8, 2020

This feels ugly because it doesn't fix the underlying bug, but
it's incredibly hard to trace down the root cause in this
situation and it causes updates to fail which is pretty
critical. So this is probably better than nothing.

Ref QubesOS/qubes-issues#5052

This feels ugly because it doesn't fix the underlying bug, but
it's incredibly hard to trace down the root cause in this
situation and it causes updates to fail which is pretty
critical. So this is probably better than nothing.

Ref QubesOS/qubes-issues#5052
@codecov
Copy link

codecov bot commented Apr 8, 2020

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.65%. Comparing base (b02dd6a) to head (dbc2d73).
Report is 851 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #225   +/-   ##
=======================================
  Coverage   72.65%   72.65%           
=======================================
  Files           3        3           
  Lines         512      512           
=======================================
  Hits          372      372           
  Misses        140      140           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@marmarek
Copy link
Member

marmarek commented Apr 8, 2020

IMO better than guessing, make the actual error easier to find. It should be written to /var/lib/qubes/updates/errors in dom0, so qubes-dom0-update script may check this file and show it to the user. If that still doesn't contain enough details, you can modify qubes-receive-updates script to save stderr of qfile-dom0-unpacker there too.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants