Your message dated Sun, 8 Jun 2025 10:26:50 +0000 with message-id <aEVlan57Xk4qcFG-@debian.org> and subject line Re: unblock: openrct2/0.4.23+ds-1 (pre-approval) has caused the Debian Bug report #1107459, regarding unblock: openrct2/0.4.23+ds-1 (pre-approval) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1107459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107459 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: unblock: openrct2/0.4.23+ds-1 (pre-approval)
- From: Mathias Gibbens <gibmat@debian.org>
- Date: Sat, 07 Jun 2025 20:52:46 +0000
- Message-id: <[🔎] 70bf6927609dd6220a0452d4c948e2fa85cc2eb5.camel@debian.org>
Package: release.debian.org Control: affects -1 + src:openrct2 User: release.debian.org@packages.debian.org Usertags: unblock X-Debbugs-Cc: Michał Janiszewski <janisozaur@gmail.com>, gibmat@debian.org Severity: normal Please unblock package openrct2 (pre-approval) [ Reason ] I received the following request from one of the OpenRCT2 developers today: On Sat, 2025-06-07 at 21:18 +0200, Michał Janiszewski wrote: > I'm one of the developers of OpenRCT2 and I wanted to ask if it would > be possible to update the package in trixie to 0.4.23, our latest > release? [snip] We have implemented a lot of performance-related > improvements and it would be great to see those in use, especially on > low-powered devices such as raspberry pi, when it eventually trickles > there. [ Impact ] Without the update, trixie will include an older version of OpenRCT2 that is missing out on various performance-related improvements. I do plan to provide backported versions of OpenRCT2 during trixie's lifetime, similar to how I've done for bookworm. [ Tests ] I have been uploading new releases of openrct2 to experimental since the soft freeze began and have installed them locally to verify the game operates as expected. [ Risks ] None; openrct2 is a leaf package in contrib and I've performed my normal play testing of the version uploaded to experimental. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing [ Other info ] No debdiff, since it would be huge when comparing against 0.4.21+ds-1 in testing. I've attached the relevant changelog entries for the two uploads to unstable. unblock openrct2/0.4.23+ds-1openrct2 (0.4.23+ds-1~exp1) experimental; urgency=medium * New upstream release - Rebase patches as needed -- Mathias Gibbens <gibmat@debian.org> Sat, 07 Jun 2025 14:57:57 +0000 openrct2 (0.4.22+ds-1~exp1) experimental; urgency=medium * New upstream release - Drop patch to disable version check and rely on new cmake flag - Rebase patches as needed -- Mathias Gibbens <gibmat@debian.org> Sun, 04 May 2025 19:37:24 +0000Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: Mathias Gibbens <gibmat@debian.org>
- Cc: 1107459-done@bugs.debian.org
- Subject: Re: unblock: openrct2/0.4.23+ds-1 (pre-approval)
- From: Ivo De Decker <ivodd@debian.org>
- Date: Sun, 8 Jun 2025 10:26:50 +0000
- Message-id: <aEVlan57Xk4qcFG-@debian.org>
- In-reply-to: <[🔎] 70bf6927609dd6220a0452d4c948e2fa85cc2eb5.camel@debian.org>
- References: <[🔎] 70bf6927609dd6220a0452d4c948e2fa85cc2eb5.camel@debian.org>
Hi, On Sat, Jun 07, 2025 at 08:52:46PM +0000, Mathias Gibbens wrote: > Please unblock package openrct2 (pre-approval) Please carefully read the freeze policy at https://release.debian.org/testing/freeze_policy.html > [ Other info ] > No debdiff, since it would be huge when comparing against 0.4.21+ds-1 > in testing. In that case, it's almost certain that your upload won't be in line with the freeze policy. So I'm closing this bug. Feel free to re-open if you want to upload targeted fixes that are in line with the freeze policy. Thanks, Ivo
--- End Message ---