I just uploaded debootstrap 1.0.20~jaunty1 to jaunty-backports. Can you reproduce this bug with this version? My suspicion is that this change will have fixed it:
* For recent Ubuntu versions, move $TARGET/sbin/initctl aside in the same
way we do start-stop-daemon, so that attempts to control Upstart jobs
won't inadvertently affect jobs in the host system.
I just uploaded debootstrap 1.0.20~jaunty1 to jaunty-backports. Can you reproduce this bug with this version? My suspicion is that this change will have fixed it:
* For recent Ubuntu versions, move $TARGET/ sbin/initctl aside in the same
way we do start-stop-daemon, so that attempts to control Upstart jobs
won't inadvertently affect jobs in the host system.