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

Uninstall of template rpm package can remove invalid template if it was renamed #839

Closed
marmarek opened this Issue Mar 8, 2015 · 2 comments

Comments

Projects
None yet
1 participant
@marmarek
Member

marmarek commented Mar 8, 2015

Reported by marmarek on 30 Apr 2014 23:49 UTC
Steps to reproduce:

  1. Install the system
  2. Rename default template (say, to fedora-20-x64-orig)
  3. Restore backup, including the template (fedora-20-x64)
  4. Try to remove original template package (qubes-template-fedora-20-x64)

It will try to remove just restored template, not the renamed original one.

Migrated-From: https://wiki.qubes-os.org/ticket/839

@marmarek marmarek added this to the Release 2 milestone Mar 8, 2015

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Mar 8, 2015

Member

Comment by marmarek on 30 Apr 2014 23:54 UTC
One could say that you can remove original template package before restoring the backup (this is what you finally want by restoring default template from the backup), but it isn't so simple - you need some VM to restore the backup (backupvm or so). The alternative is connecting backup device directly to dom0, which we are trying to forbid at all. If the backup is stored on some NAS, it is not possible at all to restore the backup without the BackupVM (or at least NetVM).

I'm not sure if we even want to fix this. But some workaround would be helpful.

Member

marmarek commented Mar 8, 2015

Comment by marmarek on 30 Apr 2014 23:54 UTC
One could say that you can remove original template package before restoring the backup (this is what you finally want by restoring default template from the backup), but it isn't so simple - you need some VM to restore the backup (backupvm or so). The alternative is connecting backup device directly to dom0, which we are trying to forbid at all. If the backup is stored on some NAS, it is not possible at all to restore the backup without the BackupVM (or at least NetVM).

I'm not sure if we even want to fix this. But some workaround would be helpful.

@marmarek

This comment has been minimized.

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