/qubes-issues

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

Broken symlink cause the whole backup to fail #1515

Closed
marmarek opened this Issue Dec 15, 2015 · 3 comments

Comments

Assignees

@marmarek marmarek

Labels
Projects
None yet
Milestone
  Release 3.1
1 participant
@marmarek
@marmarek

@marmarek marmarek added bug C: core P: major labels Dec 15, 2015

@marmarek marmarek added this to the Release 3.1 milestone Dec 15, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Dec 15, 2015

Member

Generally it's probably better to not follow symlinks in dom0 home.
Member

marmarek commented Dec 15, 2015

Generally it's probably better to not follow symlinks in dom0 home.

@marmarek marmarek self-assigned this Jan 6, 2016

@marmarek marmarek referenced this issue Jan 6, 2016

Open

"ERROR: Failed to perform backup: error in addproc" around 75% complete #1588

@marmarek marmarek closed this in marmarek/old-qubes-core-admin@ba3b908 Jan 7, 2016

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue Jan 7, 2016

@marmarek
tests: add a simple dom0 backup test 
Regression test for:
QubesOS/qubes-issues#1515

It assumes existing broken symlink in user dom0 home. Thanks for systemd
it is the case (`~/.local/share/systemd/user`).
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
24ad20c
@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 7, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.9-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update
Member

marmarek commented Jan 7, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.9-1.fc20 has been pushed to the r3.1 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek marmarek added the r3.1-dom0-cur-test label Jan 7, 2016

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jan 12, 2016

Member

Automated announcement from builder-github

The package qubes-core-dom0-3.1.10-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update
Member

marmarek commented Jan 12, 2016

Automated announcement from builder-github

The package qubes-core-dom0-3.1.10-1.fc20 has been pushed to the r3.1 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@marmarek marmarek added r3.1-dom0-stable and removed r3.1-dom0-cur-test labels Jan 12, 2016

marmarek added a commit to QubesOS/qubes-core-admin that referenced this issue Jan 15, 2016

@marmarek
tests: add a simple dom0 backup test 
Regression test for:
QubesOS/qubes-issues#1515

It assumes existing broken symlink in user dom0 home. Thanks for systemd
it is the case (`~/.local/share/systemd/user`).

(cherry picked from commit 24ad20c)
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
40104e9

@mfc mfc referenced this issue Feb 22, 2016

Open

Copy/generate VM icon instead of using symlink #1770

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