<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Add two new buildbots that build-only test on Debian stable and Ubuntu LTS"
href="https://bugs.webkit.org/show_bug.cgi?id=168321">168321</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[GTK] Add two new buildbots that build-only test on Debian stable and Ubuntu LTS
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>Tools / Tests
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>clopez@igalia.com
</td>
</tr>
<tr>
<th>CC</th>
<td>bugs-noreply@webkitgtk.org, lforschler@apple.com, mrobinson@webkit.org
</td>
</tr></table>
<p>
<div>
<pre>One of the problems we currently have is that we are using ancient versions of libraries in our JHBuild, and old versions of GCC on the bots.
One of the reasons we do this is to unintentionally avoid breaking the build on systems that require using this old versions of the libraries or the compiler.
However, a majority of our users are using distributions that ship the last version of this libraries or the compiler.
So we end testing WebKit with a different version of the dependencies than what the users end running. Not ideal.
The proposed solution is:
1) Add two new buildbots that buid-test WebKitGTK+ on the last Debian stable and Ubuntu LTS without using the internal JHBuild. This bots will build against the system libraries. This will ensure we don't unintentionally break our policy about dependency versions <a href="https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy">https://trac.webkit.org/wiki/WebKitGTK/DependenciesPolicy</a>
2) Then we will have complete freedom to raise the dependencies on the JHBuild without fearing unintentionally build breakage on older systems. Ideally we would like to keep the versions of the libraries on our jhbuild synced with the last GNOME modulesets. That way we can test WebKit with the version of libraries that most users will end using.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>