Last modified: 2013-11-20 13:58:36 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 T58720, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56720 - Install some Qt related packages and doxygen
Install some Qt related packages and doxygen
Status: RESOLVED WONTFIX
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: High enhancement
: ---
Assigned To: Marc A. Pelletier
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-07 15:32 UTC by Peter Bena
Modified: 2013-11-20 13:58 UTC (History)
2 users (show)

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


Attachments

Description Peter Bena 2013-11-07 15:32:27 UTC
Per http://lists.wikimedia.org/pipermail/labs-l/2013-November/001798.html it's not easily possible to verify if some packages are supported or present on exec nodes. So I am requesting these packages to be installed:

make
gcc
g++
libqt4-core
libqt4-dev
libqt4-dev-bin
libqt4-gui
libqt4-opengl-dev
libqt4-webkit
libqt5opengl5-dev
libqt5qml-quickcontrols
libqt5v8-5-dev
libqt5v8-5-private-dev
libqt5webkit5-dev
libqtwebkit-dev
libqwt5-qt4
libsmokeqt3support4-3
libsmokeqtcore4-3
libsmokeqtdbus4-3
libsmokeqtdeclarative4-3
libsmokeqtgui4-3
libsmokeqthelp4-3
libsmokeqtnetwork4-3
libsmokeqtopengl4-3
libsmokeqtscript4-3
libsmokeqtsql4-3
libsmokeqtsvg4-3
libsmokeqttest4-3
libsmokeqtuitools4-3
libsmokeqtwebkit4-3
libsmokeqtxml4-3
libsmokeqtxmlpatterns4-3
qdbus-qt5
qt4-dev-tools
qt4-linguist-tools
qt4-qmake
qt4-qmlviewer
qt4-qtconfig
qt5-default
qt5-qmake
qtbase5-dev
qtbase5-dev-tools
qtcore4-l10n
qtquick1-5-dev
qtquick1-5-dev-tools

Some of these may be already installed, either using puppet or as part of default ubuntu image for some of the nodes, however I need to make sure these will be present in future images as well
Comment 1 Marc A. Pelletier 2013-11-07 15:38:09 UTC
The obvious question this list raises would be "why do you need development tools on execution nodes"?
Comment 2 Peter Bena 2013-11-07 16:06:25 UTC
Also doxygen 1.8.1.2-2 or newer
Comment 3 Peter Bena 2013-11-07 16:06:59 UTC
(In reply to comment #1)
> The obvious question this list raises would be "why do you need development
> tools on execution nodes"?

To perform periodical unit tests for huggle (which are now running on tools-dev in cron)
Comment 4 Peter Bena 2013-11-07 16:08:36 UTC
(In reply to comment #3)
> (In reply to comment #1)
> > The obvious question this list raises would be "why do you need development
> > tools on execution nodes"?
> 
> To perform periodical unit tests for huggle (which are now running on
> tools-dev
> in cron)

If it's problem to perform unit tests on tool labs, I can install them to our hugglewiki instance, that's no problem, but having at least doxygen would be cool as well
Comment 5 Marc A. Pelletier 2013-11-07 16:27:43 UTC
I think CI tasks are best left to some other project.

I know some effort has been spent getting a nice Jenkins-based setup in labs for it you might be able to leverage?
Comment 6 Peter Bena 2013-11-07 17:00:02 UTC
ok in that case at least install doxygen, we really need some reliable webserver for doxy

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


Navigation
Links