Allow user created containers to co-exist with Puritine containers

Bug #1566391 reported by Christopher Townsend
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libertine
Status tracked in Devel
Devel
Fix Released
Medium
Christopher Townsend
Trunk
Fix Released
Medium
Christopher Townsend
Puritine
Invalid
Undecided
Unassigned
libertine (Ubuntu)
Fix Released
Medium
Christopher Townsend

Bug Description

Currently, the ContainerConfig.json file is a symlink to the one included in the Puritine click. If a user wants to create their own container on the device, it fails due to the symlink pointing to a read-only file.

There should be some sort of hook that can merge the Puritine ContainersConfig.json file with the one that resides in ~/.local/share/libertine.

Related branches

Changed in puritine:
status: New → Confirmed
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Christopher Townsend (townsend) wrote :

This probably something that we should put in the libertine-demo package...or something.

Changed in libertine (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

Fix committed into lp:libertine at revision 210, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Changed in puritine:
status: Triaged → Invalid
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Christopher Townsend (townsend)
Changed in puritine:
importance: Medium → Undecided
Changed in libertine (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.