wsexport project depend on xvfb-run and stopped to work after migration to stretch
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Install xauth on Toolforge Stretch instances | operations/puppet | production | +1 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | bd808 | T55704 Packages to be added to toollabs puppet | |||
| Resolved | Tpt | T215699 toolforge stretch: xvfb-run depend on xauth package but xauth is missing |
Event Timeline
Comment Actions
Change 496004 had a related patch set uploaded (by Tpt; owner: Tpt):
[operations/puppet@production] Install xauth on Toolforge Stretch instances
Comment Actions
Change 496004 merged by Bstorm:
[operations/puppet@production] Install xauth on Toolforge Stretch instances
Comment Actions
The package should roll out across the grid hosts over the course of the next 30 minutes or so.
$ sudo -i puppet agent -tv Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for tools-sgewebgrid-lighttpd-0922.tools.eqiad.wmflabs Notice: /Stage[main]/Base::Environment/Tidy[/var/tmp/core]: Tidying 0 files Info: Applying configuration version '1552430503' Notice: /Stage[main]/Profile::Toolforge::Grid::Exec_environ/Package[xauth]/ensure: created Notice: Applied catalog in 110.94 seconds $ xvfb-run -a ebook-convert Usage: ebook-convert input_file output_file [options] Convert an ebook from one format to another. input_file is the input and output_file is the output. Both must be specified as the first two arguments to the command. The output ebook format is guessed from the file extension of output_file. output_file can also be of the special format .EXT where EXT is the output file extension. In this case, the name of the output file is derived from the name of the input file. Note that the filenames must not start with a hyphen. Finally, if output_file has no extension, then it is treated as a directory and an "open ebook" (OEB) consisting of HTML files is written to that directory. These files are the files that would normally have been passed to the output plugin. After specifying the input and output file you can customize the conversion by specifying various options. The available options depend on the input and output file types. To get help on them specify the input and output file and then use the -h option. For full documentation of the conversion system see https://manual.calibre-ebook.com/conversion.html Whenever you pass arguments to ebook-convert that have spaces in them, enclose the arguments in quotation marks. For example "C:\some path with spaces" Options: --version show program's version number and exit -h, --help show this help message and exit --list-recipes List builtin recipe names. You can create an ebook from a builtin recipe like this: ebook-convert "Recipe Name.recipe" output.epub Created by Kovid Goyal <kovid@kovidgoyal.net>