No upstart Docs + asshole Canonical Employees = Fail

I was in need of a means to disable upstart scripts in /etc/event.d via some means other than getting rid of the file. Since upstart has no documentation to speak of, I asked my buddy Google.

Google pointed me to the year old bug 94065 in launchpad. I added a quick ‘me too’ and subscribed to updates on the bug. This was back in March. Fast forward to last week and this arrives:

** Changed in: upstart
      Target: 0.5 => None

--
Add non-destructive means to disable a job

https://bugs.launchpad.net/bugs/94065

You received this bug notification because you are a direct subscriber
of the bug.

There is no mention of this change in bug meta-data on the launchpad site, or maybe I’m just not finding it since I lack the doctorate in navigating launchpad necessary to be able to use the site. This prompted an update from the original reporter on the bug asking for more information:

is there a disable method yet? i reported this initially over a year ago. (there may be, but since there’s no upstart manpage on hardy, it’s hard to know. :-)

Now for the asshole fail:

Scott James Remnant wrote on 2008-08-14: (permalink)

Does this bug report say that there is a disable method? Is it marked Fix Released?
No.

I’m not sure what Scott James Remnant <scott@canonical.com>’s roll at Canonical is but perhaps it should be modified to remove any tasks that involve interaction with the public?

This entry was posted in General and tagged , , , . Bookmark the permalink.

4 Responses to No upstart Docs + asshole Canonical Employees = Fail

  1. Matt Ryan says:

    That’s what you get when you have social inadequate geeks throughout your organisation. It’s no co-incidence a lot of them came from Debian which is most famous for developers who live in their parents basement trying to out do each other with more complicated semantic arguments about unimportant topics.

  2. paul says:

    thanks for the chuckle. your blog post just popped up in a google search for documentation on upstart. as the submitter of the bug in question, i can assure you that when i received that reply, my reaction was pretty much the same as yours. “wow.”

    and isn’t it ironic that two years after that bug, i’m still looking for documentation…

  3. Spud says:

    God, upstart is mega-fail at this point. No docs, what assholes.

  4. Jedediah Frey says:

    Move file from X.conf to X.conf.disabled.

    Upstart only loops through things named *.conf

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>