The Document Foundation Redmine: Issueshttps://redmine.documentfoundation.org/https://redmine.documentfoundation.org/favicon.ico?16960560022023-06-12T09:11:36ZThe Document Foundation Redmine
Redmine Infrastructure - Task #3661 (Closed): Linkify cool#foo issueshttps://redmine.documentfoundation.org/issues/36612023-06-12T09:11:36ZXisco Fauli Tarazonaxiscofauli@libreoffice.orgInfrastructure - Task #3539 (Closed): Need to update the URL to ask.libreoffice.org (at least for...https://redmine.documentfoundation.org/issues/35392021-09-01T07:52:40ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Moved from <a class="external" href="https://bugs.documentfoundation.org/show_bug.cgi?id=143908">https://bugs.documentfoundation.org/show_bug.cgi?id=143908</a></p>
<p>Description:<br />Since the ask.libreoffice.org site changed this August, there could be some links to update.</p>
<p>Steps to Reproduce:<br />1. Go to <a class="external" href="https://es.libreoffice.org/">https://es.libreoffice.org/</a><br />2. Choose menu Obtén ayuda - Asistencia comunitaria (<a class="external" href="https://es.libreoffice.org/obten-ayuda/asistencia-comunitaria/">https://es.libreoffice.org/obten-ayuda/asistencia-comunitaria/</a>)<br />3. Choose Ask LibreOffice (<a class="external" href="https://ask.libreoffice.org/es">https://ask.libreoffice.org/es</a>)</p>
<p>Actual Results:<br />¡Ups! Esa página no existe o es privada.</p>
<p>Expected Results:<br /><a class="external" href="https://ask.libreoffice.org/c/spanish/10">https://ask.libreoffice.org/c/spanish/10</a><br />or<br /><a class="external" href="https://ask.libreoffice.org/">https://ask.libreoffice.org/</a></p>
<p>Reproducible: Always</p>
<p>User Profile Reset: No</p>
<p>Additional Info:<br />pt-br it is correct<br />it points to ask.libreoffice.org</p> Infrastructure - Task #3295 (Closed): Missing from download list on Website: New UI languages Fri...https://redmine.documentfoundation.org/issues/32952020-08-03T14:33:39ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>From <a class="external" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134875">https://bugs.documentfoundation.org/show_bug.cgi?id=134875</a></p>
<p>There are two new User Interface languages for LibreOffice 7.0:<br /> Brand-new UI translation into Central Kurdish / Soranî / سۆرانی (ckb)<br /> Brand-new UI translation into Friulian (fur)</p>
<p>The download packages for the localized UI exist [1],[2], but these two languages are simply still missing from the LibreOffice download website [3]. Please add these two languages to the list on the website.</p>
<p>[1] <a class="external" href="https://www.libreoffice.org/download/download/?type=deb-x86_64&version=7.0.0&lang=ckb">https://www.libreoffice.org/download/download/?type=deb-x86_64&version=7.0.0&lang=ckb</a><br />[2] <a class="external" href="https://www.libreoffice.org/download/download/?type=deb-x86_64&version=7.0.0&lang=fur">https://www.libreoffice.org/download/download/?type=deb-x86_64&version=7.0.0&lang=fur</a><br />[3] <a class="external" href="https://www.libreoffice.org/download/download/?type=deb-x86_64&version=7.0.0&lang=pick">https://www.libreoffice.org/download/download/?type=deb-x86_64&version=7.0.0&lang=pick</a></p> Infrastructure - Task #3187 (Rejected): CrashReport: Handshake failurehttps://redmine.documentfoundation.org/issues/31872020-04-16T17:27:16ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>When LibreOffice crashes in a release build, it asks the user to send a crashreport the next time LibreOffice is launched. Once the crashreport is sent, the dialog displays the crash's url. For a couple of months now, this url is never displayed in my case, although crashreports from other users are still sent to the server. Surprisingly, it works with an older version of LibreOffice ( version 5.3.7.2 ) but not with a more recent one ( version 6.4.2.2 ). I'm using Win 7 on virtualbox<br />Attach you can see the wireshark logs from both versions.</p> Infrastructure - Task #3152 (Closed): 6.4 RCS never appeared in https://www.libreoffice.org/down...https://redmine.documentfoundation.org/issues/31522020-03-26T16:48:30ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p><_rene_> noticed that for some past releases now, but...<br /><_rene_> <a class="external" href="https://www.libreoffice.org/download/pre-releases/">https://www.libreoffice.org/download/pre-releases/</a><br /><_rene_> contains 6.1(!), 6.2(!) and 6.3 but not 6.4<br /><_rene_> thus the 6.4 rcs never appear there</p> Infrastructure - Task #3065 (New): Update Impress Remote in Downloads Archive websitehttps://redmine.documentfoundation.org/issues/30652019-12-27T15:57:12ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Based on <a class="external" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129544">https://bugs.documentfoundation.org/show_bug.cgi?id=129544</a></p>
<p>Comment: Impress remote has version 2.4.0 in Google Play (<a class="external" href="https://play.google.com/store/apps/details?id=org.libreoffice.impressremote">https://play.google.com/store/apps/details?id=org.libreoffice.impressremote</a>) and 2.3.0 in Downloads Archive website (<a class="external" href="https://downloadarchive.documentfoundation.org/libreoffice/old/">https://downloadarchive.documentfoundation.org/libreoffice/old/</a>). Could you update it?</p> Infrastructure - Task #2995 (Closed): TDF-SSO: Add big red warning to gerrit about old login meth...https://redmine.documentfoundation.org/issues/29952019-10-10T11:07:36ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Suggestion from the ESC meeting:</p>
<ul>
<li>TDF-SSO for gerrit (cloph)<br /> + gerrit was updated to use TDF-accounts<br /> <a class="external" href="https://lists.freedesktop.org/archives/libreoffice/2019-September/083474.html">https://lists.freedesktop.org/archives/libreoffice/2019-September/083474.html</a><br /> + old login methods will be deprecated/switch to TDF-SSO is prerequisite<br /> for updating to current version of gerrit<br /> + please link accounts using Settings → Identities → Link Another Identity<br /> + Will be a hard requirement later this year<br /> + Big red warning on gerrit for the affected users would be great (Kendy)</li>
</ul> Release Engineering - Task #2943 (New): Announce pre-releases in the QA blog, Bugzilla, ReleaseNoteshttps://redmine.documentfoundation.org/issues/29432019-08-06T12:30:35ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>In order to get as much testing as possible, we announce pre-releases ( alpha1, beta1, beta1, RC1, RC2 and RC3 ) in the qa blog < <a class="external" href="https://qa.blog.documentfoundation.org/">https://qa.blog.documentfoundation.org/</a> >, Bugzilla, and the ReleaseNotes</p>
<p>Steps:<br />1. Create the release plan wiki page --> See <a class="external" href="https://redmine.documentfoundation.org/issues/2942#change-17290">https://redmine.documentfoundation.org/issues/2942#change-17290</a><br />2. Create the banner --> <a class="external" href="https://wiki.documentfoundation.org/QA/BugHuntingSession/Organization#LibreOffice_6.0_Testing_Series">https://wiki.documentfoundation.org/QA/BugHuntingSession/Organization#LibreOffice_6.0_Testing_Series</a>. E.g: <a class="external" href="https://wiki.documentfoundation.org/File:BHS_large_6.3_RC3.png">https://wiki.documentfoundation.org/File:BHS_large_6.3_RC3.png</a><br />3. Update <a class="external" href="https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases">https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases</a> with the correct links<br />4. Add [[File:BHS_large_6.3_RC3.png|600px|center|link=https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases]] to <a class="external" href="https://wiki.documentfoundation.org/ReleaseNotes/6.3">https://wiki.documentfoundation.org/ReleaseNotes/6.3</a> (Use versioning accordingly )<br />5. In Bugzilla, Go to "Administration - Parameters - General" and add</p>
<p><center><a href="<a class="external" href="https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases&quot;">https://wiki.documentfoundation.org/QA/GetInvolved#Test_Pre-releases&quot;</a>><br /><img border="0" src="<a class="external" href="https://wiki.documentfoundation.org/images/7/7f/BHS_large_6.3_RC3.png&quot;">https://wiki.documentfoundation.org/images/7/7f/BHS_large_6.3_RC3.png&quot;</a> width="500" height="125"></a></center></p>
<p>to announcehtml (Use versioning accordingly )<br />6. Write a blog post in the QA blog. E.g: <a class="external" href="https://qa.blog.documentfoundation.org/2019/07/09/libreoffice-6-3-rc1-ready-for-testing/">https://qa.blog.documentfoundation.org/2019/07/09/libreoffice-6-3-rc1-ready-for-testing/</a> (Use versioning accordingly )</p>
<p>Before the final release, remove the banner from Bugzilla and the ReleaseNotes wiki page</p> Release Engineering - Task #2942 (New): Create ReleasePlan wiki pages before they are releasedhttps://redmine.documentfoundation.org/issues/29422019-08-06T12:15:31ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Every time a new pre-release or final release is created, its wiki page needs to be created as well. For instance, see: <a class="external" href="https://wiki.documentfoundation.org/Releases/6.3.0/RC2">https://wiki.documentfoundation.org/Releases/6.3.0/RC2</a></p>
<p>How to do it ( taking <a class="external" href="https://wiki.documentfoundation.org/Releases/6.3.0/RC2">https://wiki.documentfoundation.org/Releases/6.3.0/RC2</a> as a example):<br />1. Copy content from <a class="external" href="https://wiki.documentfoundation.org/Releases/6.2.0/RC2">https://wiki.documentfoundation.org/Releases/6.2.0/RC2</a> to <a class="external" href="https://wiki.documentfoundation.org/Releases/6.3.0/RC2">https://wiki.documentfoundation.org/Releases/6.3.0/RC2</a><br />2. Replace all 6.2.0 with 6.3.0<br />3. Change [[Category:Release|6202]] to [[Category:Release|6302]]<br />4. Remove content from 'List of fixed bugs' section<br />5. Get the new content from <a class="external" href="https://dev-builds.libreoffice.org/pre-releases/src/">https://dev-builds.libreoffice.org/pre-releases/src/</a>' ( for 6.3.0 RC2 the file is called 'bugs-libreoffice-6-3-0-release-6.3.0.2.wiki' )</p>
if it doesn't exists, you can create it yourself.
<ol>
<li>Go to the local repository</li>
<li>./g pull -r</li>
<li>./g fetch --tags</li>
<li>mkdir outdir</li>
<li>cd outdir</li>
<li>bootstrapdir=/home/xisco/releases/</li>
<li>export lo_tag=6.3.0.2</li>
<li>export lo_tag_last=6.3.0.1</li>
<li>$bootstrapdir/bin/lo-commit-stat --cherry --commits --bugs --bugs-wiki --bugs-changelog --log-suffix=release-${vendor_use:+libreoffice-}$lo_tag $bootstrapdir libreoffice-$lo_tag_last libreoffice-$lo_tag</li>
<li>'bugs-libreoffice-6-3-0-release-6.3.0.2.wiki' will be created</li>
</ol>
<p>6. Update the link in the Translations section</p> Release Engineering - Task #2898 (Rejected): LibreOffice_6.1.3_Linux_x86-64_deb_helppack_en-US.ta...https://redmine.documentfoundation.org/issues/28982019-06-04T14:01:16ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Reported in <a class="external" href="https://bugs.documentfoundation.org/show_bug.cgi?id=121706">https://bugs.documentfoundation.org/show_bug.cgi?id=121706</a></p>
<p>Description:<br />The help file from <a class="external" href="http://www.nic.funet.fi/pub/mirrors/documentfoundation.org/libreoffice/stable/6.1.3/deb/x86_64/LibreOffice_6.1.3_Linux_x86-64_deb_helppack_en-US.tar.gz">http://www.nic.funet.fi/pub/mirrors/documentfoundation.org/libreoffice/stable/6.1.3/deb/x86_64/LibreOffice_6.1.3_Linux_x86-64_deb_helppack_en-US.tar.gz</a> does not match the sha256 checksum.</p>
<p>Steps to Reproduce:<br />1. Go to download page<br />2. If the download link points to <a class="external" href="http://www.nic.funet.fi/pub/mirrors/documentfoundation.org/libreoffice/stable/6.1.3/deb/x86_64/LibreOffice_6.1.3_Linux_x86-64_deb_helppack_en-US.tar.gz">http://www.nic.funet.fi/pub/mirrors/documentfoundation.org/libreoffice/stable/6.1.3/deb/x86_64/LibreOffice_6.1.3_Linux_x86-64_deb_helppack_en-US.tar.gz</a> , then you will end up downloading the bad file.<br />Alternatively just enter in the URL to that mirror and it will download the bad file.<br />3. perform a checksum with sha256 and notice that it does not match with the website's checksum of aefe906103156c14f36e892a69a3f208b44cf8d34ff757bed9d1900dadad8ffc. The checksum from the mirror is cf38b2047ad1ea0f0fafed916e019f4e84e47821eb4e6163ba2800ec90a56f89.</p>
<p>Actual Results:<br />mismatched sha256 checksum</p>
<p>Expected Results:<br />matching checksums</p>
<p>Reproducible: Always</p>
<p>User Profile Reset: No</p>
<p>Additional Info:<br />The web site should exclude the bad mirror. The mirror needs to be checked if it was compromised or if the LibreOffice accounts used to upload the file was compromised. The bad file can still be extracted from the gz file.</p> Infrastructure - Task #2895 (Closed): Change Additional information to Add info from Help-Abouthttps://redmine.documentfoundation.org/issues/28952019-05-28T15:45:41ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Make it clearer in <a class="external" href="https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided">https://bugs.documentfoundation.org/enter_bug.cgi?product=LibreOffice&format=guided</a><br />we want the info from Help - About LibreOffice</p> Infrastructure - Task #2868 (Closed): Duplicate websites of certified developershttps://redmine.documentfoundation.org/issues/28682019-05-09T16:31:01ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>Hi,<br />there are two different websites of Certified Developers<br />1. <a class="external" href="https://www.documentfoundation.org/gethelp/developers/">https://www.documentfoundation.org/gethelp/developers/</a><br />2. <a class="external" href="https://www.libreoffice.org/get-help/professional-support/">https://www.libreoffice.org/get-help/professional-support/</a></p>
<p>TDF's one seems more accurate and I see these problems in the LibreOffice's one:<br />- Luboš Luňák is listed as Unaffiliated, he should go into Collabora<br />- László Németh is listed as Collabora, he should go into Unaffiliated<br />- Dennis Francis, Pierre-Eric Pelloux-Prayer and Maxime de Roucy are not listed<br />- Justin Luth is listed as SIL, he should go into Collabora</p>
<p>Ideally both websites should be fed from the same info. Meanwhile, the inconsistencies listed above should be addressed</p> Infrastructure - Task #2836 (Closed): https://www.documentfoundation.org/contribution/ should red...https://redmine.documentfoundation.org/issues/28362019-03-18T20:02:31ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>It's used in <a class="external" href="https://wiki.documentfoundation.org/images/4/47/CG41-CalcGuideLO.pdf">https://wiki.documentfoundation.org/images/4/47/CG41-CalcGuideLO.pdf</a> ( page 12 ) and probably in other documents...</p>
<p>Report based on <a class="external" href="https://bugs.documentfoundation.org/show_bug.cgi?id=123149">https://bugs.documentfoundation.org/show_bug.cgi?id=123149</a></p> Infrastructure - Task #2709 (New): Webpage: Feed shows html tagshttps://redmine.documentfoundation.org/issues/27092019-01-09T14:54:42ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>See: <a class="external" href="https://bugs.documentfoundation.org/attachment.cgi?id=148122">https://bugs.documentfoundation.org/attachment.cgi?id=148122</a></p>
<p>if title contains HTML tags, they're displayed in the feed. E.g <a class="external" href="https://people.gnome.org/~michael/blog/2019-01-08-vendor-neutral-marketing-4.html">https://people.gnome.org/~michael/blog/2019-01-08-vendor-neutral-marketing-4.html</a></p>
<p>issue based on <a class="external" href="https://bugs.documentfoundation.org/show_bug.cgi?id=122558">https://bugs.documentfoundation.org/show_bug.cgi?id=122558</a></p> Infrastructure - Task #2663 (Closed): The professional support page hides information by default ...https://redmine.documentfoundation.org/issues/26632018-10-08T15:15:44ZXisco Fauli Tarazonaxiscofauli@libreoffice.org
<p>The professional support page ( <a class="external" href="https://www.libreoffice.org/get-help/professional-support/">https://www.libreoffice.org/get-help/professional-support/</a> ) is confusing if visited from a phone.<br />The description on top fits the screen's width, which is ok, however, if one scrolls down and goes to the list of certified professional, only the the affiliations are displayed, while the professionals are listed on the right without any indicator more information is on the right.<br />The list of professionals should be displayed in the same column, right after the affiliation.</p>