-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/04/11 16:01, Clint Byrum wrote:
Excerpts from James Hunt's message of Fri Apr 08 08:51:48 -0700 2011:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
As a precursor to pushing this update out to Natty next week, I've
updated my
On 11/04/11 16:01, Clint Byrum wrote:
Excerpts from James Hunt's message of Fri Apr 08 08:51:48 -0700 2011:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
As a precursor to pushing this update out to Natty next week, I've
updated my upstart-testing PPA with Upstart version
Excerpts from James Hunt's message of Fri Apr 15 09:57:07 -0700 2011:
This is likely because the dbus upstart job has a post-start that sends
USR1 to pid 1, which is supposed to tell it to re-connect to dbus.
I believe the bug is because the USR1 handler needs to ignore requests
to
Excerpts from James Hunt's message of Fri Apr 08 08:51:48 -0700 2011:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
As a precursor to pushing this update out to Natty next week, I've
updated my upstart-testing PPA with Upstart version 0.9.5-1ubuntu1:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
As a precursor to pushing this update out to Natty next week, I've
updated my upstart-testing PPA with Upstart version 0.9.5-1ubuntu1:
ppa:jamesodhunt/upstart-testing
Code is here:
On Friday, April 08, 2011 11:51:48 AM James Hunt wrote:
Hi All,
As a precursor to pushing this update out to Natty next week, I've
updated my upstart-testing PPA with Upstart version 0.9.5-1ubuntu1:
ppa:jamesodhunt/upstart-testing
Code is here: