[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

2016-11-29 Thread Rarylson Freitas
Hi, I'm sorry for don't response these questions in the last months. However, in the last days, I had some time and I understood better the situation. I'll split my post in three parts. 1 - Technical background 1.1 - Lack of documentation The `wait-for-start` job is not documented. Because

[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

2016-11-18 Thread Martin Pitt
Closing for now as there hasn't been a response in several months. Please reopen if you still want to go ahead with this as an SRU, and then please add a test case and a regression potential analysis. ** Changed in: upstart (Ubuntu Trusty) Status: Incomplete => Won't Fix -- You received

[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

2016-07-04 Thread Martin Pitt
Changing the default behaviour in 14.04 in our central init seems quite risky to me. Can you please explain in some more detail/with an example which packages are affected here? In particular, bug 1465382 has a patch which seems to be a more local workaround for this one, right? Or do these two

[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

2015-12-22 Thread Michael Terry
Moved the bug to be against Trusty, since current Ubuntus don't use a system upstart. ** Also affects: upstart (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: upstart (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: upstart (Ubuntu Trusty)

[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

2015-11-03 Thread Mathew Hodson
** Tags added: trusty ** Changed in: upstart (Ubuntu) Importance: Undecided => Medium ** Changed in: upstart (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in

[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

2015-10-19 Thread Rarylson Freitas
Of course. I actually only know two examples: - mounting-glusterfs.conf: The glusterfs-client package uses the command "wait-for-state WAIT_FOR=static-network-up WAITER=mounting-glusterfs" without passing "WAIT_STATE=running"; - So, this command doesn't works; - See:

[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

2015-10-01 Thread Serge Hallyn
Hi, could you please show a specific example which breaks currently? ** Changed in: upstart (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu.

[Touch-packages] [Bug 1465386] Re: Default values for WAIT_STATE are wrong in the upstart wait-for-state job

2015-06-15 Thread Ubuntu Foundations Team Bug Bot
The attachment wait-for-state.conf.patch seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by