[SRU] libreoffice 7.3.6 for jammy

Bug #1988744 reported by Rico Tzschichholz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libreoffice (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
High
Rico Tzschichholz

Bug Description

[Impact]

 * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line:
     https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release

 * Version 7.3.5 is currently released in jammy. For a list of fixed bugs compared to 7.3.5 see the list of bugs fixed in the release candidates of 7.3.6 (that's a total of 50 bugs):
     https://wiki.documentfoundation.org/Releases/7.3.6/RC1#List_of_fixed_bugs
     https://wiki.documentfoundation.org/Releases/7.3.6/RC2#List_of_fixed_bugs

 * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes.

[Testing]

 * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually).

  * A recent set of upstream's automated jenkins testing can be found here:
    https://ci.libreoffice.org/job/gerrit_73/1900/

  * More information about the upstream QA testing can be found here:
    * Automated tests
      https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
    * Automated UI tests
      https://wiki.documentfoundation.org/Development/UITests
    * Regression tests
      https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
    * Feature tests
      https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

 * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing.
    * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220903_204748_cb772@/log.gz
    * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220903_234903_5c5f9@/log.gz
    * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220903_221954_4437b@/log.gz
    * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220903_203030_f897a@/log.gz
    * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220903_202914_32e82@/log.gz
 * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

[Regression Potential]

 * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed.

 * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in.

Changed in libreoffice (Ubuntu):
status: New → Fix Released
Changed in libreoffice (Ubuntu Jammy):
status: New → In Progress
assignee: nobody → Rico Tzschichholz (ricotz)
importance: Undecided → High
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

While reviewing, I see that a new `libreoffice-common.preinst.in` maintscript has been added. The script itself seems to be sane, but can we add a test case to the test plan that would test the scenario of the preinst? Making sure that it works and also that it doesn't actually remove anything invalidly. Thanks!

Revision history for this message
Rico Tzschichholz (ricotz) wrote :

@sil2000: I will try to "break" or tweak an existing installation for verification of this specific issue.

I haven't ran into this problem myself and didn't see a report in Ubuntu. Apparently there were users in Debian suffering from this problem.

description: updated
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Rico, or anyone else affected,

Accepted libreoffice into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in libreoffice (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (libreoffice/1:7.3.6-0ubuntu0.22.04.1)

All autopkgtests for the newly accepted libreoffice (1:7.3.6-0ubuntu0.22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/1:7.3.6-0ubuntu0.22.04.1 (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#libreoffice

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Rico Tzschichholz (ricotz) wrote :

Upgraded libreoffice from 1:7.3.5-0ubuntu0.22.04.1 to 1:7.3.6-0ubuntu0.22.04.1 from jammy-proposed in a clean and up-to-date jammy amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libreoffice - 1:7.3.6-0ubuntu0.22.04.1

---------------
libreoffice (1:7.3.6-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream release (LP: #1988744)

  [ Rico Tzschichholz ]
  * Bump yaru source to "2022-08-15"
  * debian/patches/tdf-108560-horribly-slow-to-paste-many-lines-into-ed.patch:
    - Calc very slow to open/save documents with large cell contents

  [ Rene Engelhard ]
  * debian/libreoffice-common.preinst.in,debian/rules,
    debian/shell-lib-extensions.sh:
    - Broken libreoffice trigger and /usr/lib/libreoffice/share/extensions
      missing; libreoffice fails to start when last extension is removed
      (/usr/lib/libreoffice/share/extensions being a 0-byte file)

 -- Rico Tzschichholz <email address hidden> Mon, 05 Sep 2022 16:18:50 +0200

Changed in libreoffice (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.