<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Liberation fonts downgraded to 2.00.3 after LibreOffice 7.2 is installed"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=144443#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - Liberation fonts downgraded to 2.00.3 after LibreOffice 7.2 is installed"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=144443">bug 144443</a>
from <span class="vcard"><a class="email" href="mailto:fitojb@ubuntu.com" title="Adolfo Jayme <fitojb@ubuntu.com>"> <span class="fn">Adolfo Jayme</span></a>
</span></b>
<pre>(In reply to Volga from <a href="show_bug.cgi?id=144443#c8">comment #8</a>)
<span class="quote">> I think there is necessary to build a bulletin to track any changes for the
> dependencies, including libraries and fonts, once their developers made a
> new release, we could be noticed soon, and attempt to apply into future
> version of LibreOffice.</span >
Several solutions exist for dependency tracking. Investigating which one we
could integrate could be a work item for a member of the Engineering Steering
Comittee.</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>