Update gnome-calendar to 43.1

Bug #1993308 reported by Jeremy Bícha
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-calendar (Ubuntu)
Fix Released
High
Unassigned
Kinetic
Fix Released
High
Unassigned

Bug Description

Impact
------
There is a new bugfix release in the stable 43 series.
https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS

This includes several fixes for recurring calendar events. These bugs were considered a release blocker for Fedora 37.

https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist

Test Case
---------
Complete the test case from

https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar

What Could Go Wrong
-------------------
GNOME Calendar is included by default only in the Ubuntu Desktop flavor.

If there are bugs in GNOME Calendar, Evolution (not installed by default) could be used instead.

GNOME Calendar can sync with Google or Microsoft online calendars. Therefore, bugs in editing calendar events can by synced to those services.

GNOME Calendar is part of GNOME Core and is included in the GNOME micro release exception

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

Jeremy Bícha (jbicha)
Changed in gnome-calendar (Ubuntu):
status: New → Incomplete
Jeremy Bícha (jbicha)
description: updated
Changed in gnome-calendar (Ubuntu):
status: Incomplete → In Progress
Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Jeremy, or anyone else affected,

Accepted gnome-calendar into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-calendar/43.1-0ubuntu1 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-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. 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 gnome-calendar (Ubuntu Kinetic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-kinetic
Revision history for this message
Jeremy Bícha (jbicha) wrote :

I installed gnome-calendar 43.1-0ubuntu1 and successfully completed the test case.

I noticed that dragging an event to a different time slot didn't save to the correct time, depending on the system timezone. I reported that issue to GNOME. I verified that the issue also affects Calendar 43.0 currently in Kinetic so this is not a regression. Therefore, I am marking this SRU as verified.

https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/903

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

This bug was fixed in the package gnome-calendar - 43.1-0ubuntu1

---------------
gnome-calendar (43.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1993308)
    - Fixes multiple issues with recurring events

 -- Jeremy Bicha <email address hidden> Tue, 18 Oct 2022 10:09:27 -0400

Changed in gnome-calendar (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
ccdisle (sim-blk) wrote :

Thanks. I'll have a look and get back to you. So far it's not visible on my update list.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-calendar - 43.1-0ubuntu1

---------------
gnome-calendar (43.1-0ubuntu1) kinetic; urgency=medium

  * New upstream release (LP: #1993308)
    - Fixes multiple issues with recurring events

 -- Jeremy Bicha <email address hidden> Tue, 18 Oct 2022 10:09:27 -0400

Changed in gnome-calendar (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for gnome-calendar 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.

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

Hi Jeremy, we keep getting users reporting bugs on 43.0 upstream. Why does 43.1 not show up in https://packages.ubuntu.com/search?keywords=gnome-calendar&searchon=names&suite=kinetic&section=all ?

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Look in 'kinetic-updates' instead of 'kinetic'.

'kinetic' is frozen on the day kinetic was released. Updates will then go to either 'kinetic-updates' or 'kinetic-security'.

'kinetic-updates' is enabled by default. It's possible for users to turn it off and only depend on security updates, but then they are going to have bugs that have already been fixed.

I use this page to look up version info instead of the packages.ubuntu.com page:
https://launchpad.net/ubuntu/+source/gnome-calendar

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Your comments might be missed if you comment on bugs that are already closed.

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.