Last modified: 2013-09-11 22:46:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48913, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46913 - "stdin: is not a tty" on first run
"stdin: is not a tty" on first run
Status: RESOLVED WONTFIX
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized minor
: ---
Assigned To: Nobody - You can work on this!
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-05 04:09 UTC by Ori Livneh
Modified: 2013-09-11 22:46 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ori Livneh 2013-04-05 04:09:45 UTC
Log output:

[default] Running provisioner: VagrantPlugins::Shell::Provisioner...
stdin: is not a tty

This used to happen at the start of every Puppet run, because of the line "mesg n" in /root/.profile. The shell provisioner is actually invoked to fix the problem by changing it to "tty -s && mesg n". This fixes the problem for every subsequent run. Still, I'd like to prevent it from appearing even once.
Comment 1 Ori Livneh 2013-04-09 16:56:28 UTC
I wasted an hour trying various ploys for working around this issue and none of them worked reliably. The error only appears once and the wording is not especially terrifying. I'll just add a note to the README saying it should be disregarded, and hope that Ubuntu fixes it upstream by adding a check to .profile.
Comment 2 Andre Klapper 2013-04-10 11:02:38 UTC
I've upstreamed it as https://bugs.launchpad.net/ubuntu/+bug/1167281
Comment 3 Andre Klapper 2013-09-11 22:46:05 UTC
[mass-moving from Tools>MediaWiki-Vagrant to separate product. See bug 54041. Filter bugmail on this comment.]

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links