<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - the version information embedded in LibreOffice for macOS are broken"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=122375">122375</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>the version information embedded in LibreOffice for macOS are broken
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Mac OS X (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>julian@corecode.io
</td>
</tr></table>
<p>
<div>
<pre>Description:
the version information embedded into LibreOffice on macOS is broken.
have a look at this image of a spreadsheet that contains the meta information
of the last two dozen releases:
<a href="https://ibb.co/PZMC7gM">https://ibb.co/PZMC7gM</a>
its immediately obvious that only the information in 'CFBundleGetInfoString' is
correct. which is funny, since this key has been deprecated for nearly 10
years, should be removed right now, and is certainly not the right place to
have version information.
the CFBundleShortVersionString and CFBundleVersion strings are broken in a
funny inconsistent way.
1.) for dot-zero (x.y.0.p) releases, they are always of a 3-number format, but
the last number is ALWAYS wrong:
consider the 6.1.0.3 release which is the 3rd and last build of the 6.1.0
releases. the CFBundleShortVersionString and CFBundleVersion keys should be
6.1.0.3. but it has been set to 6.1.3 which is obviously wrong. the 6.1.3
release didn't happen until 3 months later. not sure what the rationale is
here.
2.) for non-dot-zero (x.y.z!=0.p) releases, they are always of a 3-number
format, but the last number always contains 2 zeroes instead of the additional
point that should seperate the patch level.
consider the current 6.1.4.2 release which is the second build of the 6.1.4
releases. the CFBundleShortVersionString and CFBundleVersion keys should be
6.1.4.2 (or possibly 6.1.4 if you want to ignore the patch level in the short
version string). but it has been set to 6.1.4002 which doesn't make sense to
me. even if it did make sense, it should be applied consistently, which is the
single most important thing about any version number format. its not as
important how much sense it makes, but whether you apply it consistently. but
you consistently alternate between two different schemes, that in my opinion
are broken in different ways.
in summary, please remove the deprecated CFBundleGetInfoString key and add the
sane version numbers stores there to the CFBundleShortVersionString key and/or
the CFBundleVersion key. thanks
Steps to Reproduce:
download any and all LibreOffice releases and have a look at the version
numbers
Actual Results:
version numbers are not what you expect
Expected Results:
sane version numbers
Reproducible: Always
User Profile Reset: No
Additional Info:
i'll try to attach the full CSV with all version numbers if its possible</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>