Bug 2132772 - Editing a recurring event moves it forward in time
Summary: Editing a recurring event moves it forward in time
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-calendar
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F37FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2022-10-06 15:35 UTC by Kamil Páral
Modified: 2022-10-19 07:23 UTC (History)
7 users (show)

Fixed In Version: gnome-calendar-43.0-6.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-19 07:23:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-calendar issues 882 0 None opened Editing a recurring event moves it forward in time 2022-10-06 15:35:11 UTC

Description Kamil Páral 2022-10-06 15:35:11 UTC
This bug is just for blocker discussion. See the upstream description here:
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/882

Proposing for a blocker discussion.

Comment 1 Adam Williamson 2022-10-10 09:01:48 UTC
+5 in https://pagure.io/fedora-qa/blocker-review/issue/960 , marking accepted.

Comment 2 Ray Strode [halfline] 2022-10-11 19:40:02 UTC
The eds client api is very foreign to me, but I posted what I think is a fix here: https://gitlab.gnome.org/GNOME/gnome-calendar/-/merge_requests/262

Comment 3 Fedora Update System 2022-10-11 20:23:36 UTC
FEDORA-2022-d687a7f331 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d687a7f331

Comment 4 Fedora Update System 2022-10-12 09:38:43 UTC
FEDORA-2022-d687a7f331 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d687a7f331`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d687a7f331

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-10-12 16:23:42 UTC
FEDORA-2022-d687a7f331 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d687a7f331`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d687a7f331

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Kamil Páral 2022-10-13 08:52:09 UTC
(In reply to Fedora Update System from comment #5)
> You can provide feedback for this update here:
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-d687a7f331

This seems correctly fixed in gnome-calendar-43.0-5.fc37.x86_64. I found another problem though, I'll report it and link it in the upstream issue.

Comment 7 Adam Williamson 2022-10-17 22:04:13 UTC
Needs re-testing with the new build (43.0-6), so setting back to ON_QA.

Comment 8 Kamil Páral 2022-10-18 08:13:44 UTC
(In reply to Adam Williamson from comment #7)
> Needs re-testing with the new build (43.0-6), so setting back to ON_QA.

Seems to be fixed.

Comment 9 Fedora Update System 2022-10-18 12:40:52 UTC
FEDORA-2022-d687a7f331 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d687a7f331`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d687a7f331

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-10-19 07:23:39 UTC
FEDORA-2022-d687a7f331 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.