upstart to support "puritine-custom" container

Bug #1576356 reported by Kyle Nitzsche
6
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
libertine (Ubuntu)
Fix Released
Medium
Christopher Townsend

Bug Description

For bespoke projects, we want a different container than the standard "puritine" to avoid collision with com.ubuntu.puritine click in the store.

libertine upstart scripts should therefore add support for a container named "puritine-custom".

Related branches

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 217, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Revision history for this message
Christopher Townsend (townsend) wrote :

I'm actually making a change to include a "puritine" click hook which will do all of the linking and copying needed to support Puritine style click packages. With this, the Upstart job is no longer needed.

The only caveats are is that the Puritine click packages obviously need to have unique names, but more importantly, the container name used needs to be unique for each Puritine style click package, so care needs to be taken there.

Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Christopher Townsend (townsend)
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.