Bug#1028602: transition: gnustep-base, gnustep-gui
- To: Yavor Doganov <yavor@gnu.org>, 1028602@bugs.debian.org
- Subject: Bug#1028602: transition: gnustep-base, gnustep-gui
- From: Sebastian Ramacher <sramacher@debian.org>
- Date: Tue, 7 Feb 2023 21:53:03 +0100
- Message-id: <Y+K6L1b5r2HPRk1/@ramacher.at>
- Reply-to: Sebastian Ramacher <sramacher@debian.org>, 1028602@bugs.debian.org
- In-reply-to: <87sfftyehh.GNU's_not_UNIX!-yavor@gnu.org>
- References: <167361571055.1247157.13575129459169844921.reportbug@aneto> <Y9WXHTKrZIbfTKde@ramacher.at> <167361571055.1247157.13575129459169844921.reportbug@aneto> <87sfftyehh.GNU's_not_UNIX!-yavor@gnu.org> <167361571055.1247157.13575129459169844921.reportbug@aneto>
Control: tags -1 trixie
On 2023-01-29 09:41:30 +0200, Yavor Doganov wrote:
> Sebastian Ramacher wrote:
> > On 2023-01-13 15:15:10 +0200, Yavor Doganov wrote:
> > > I realise we are already late and in all likelihood we've missed
> > > the last bookworm train, which is rather unpleasant for us and
> > > GNUstep users but entirely our fault.
> >
> > I am not quite sure what you mean with unpleasant. What would be
> > unpleasant for GNUstep users?
>
> I meant that in case the transition is postponed to trixie, bookworm
> will ship with old releases of core GNUstep. It happened for bullseye
> when I missed to inform upstream about Debian's freeze/release
> schedule. This time the upstream releases were made in time but we
> failed to meet the deadline again.
That's unfortunate timing and it's too late. Let's do this transition
early in the trixie release cycle.
Cheers
--
Sebastian Ramacher
Reply to: