Your message dated Mon, 31 Mar 2025 23:21:42 +0200
with message-id <[email protected]>
and subject line Re: Bug#1032857: please consider adding the jgrpp patches
has caused the Debian Bug report #1032857,
regarding please consider adding the jgrpp patches
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 [email protected]
immediately.)
--
1032857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032857
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openttd
Version: 13.0-2
Severity: wishlist
Tags: upstream
Hi,
please consider packaging the jgrpp patches, too.
https://github.com/JGRennison/OpenTTD-patches
Thank you,
Toni
-- System Information:
Debian Release: 11.6
APT prefers stable-security
APT policy: (990, 'stable-security'), (990, 'stable'), (500,
'stable-updates'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-21-amd64 (SMP w/12 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages openttd depends on:
ii libc6 2.31-13+deb11u5
pn libfluidsynth3 <none>
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1+deb11u1
ii libgcc-s1 10.2.1-6
ii libicu67 67.1-7
pn libicu72 <none>
ii liblzma5 5.2.5-2.1~deb11u1
ii liblzo2-2 2.10-2
ii libpng16-16 1.6.37-3
ii libsdl2-2.0-0 2.0.14+dfsg2-3+deb11u1
ii libstdc++6 10.2.1-6
ii libxdg-basedir1 1.2.0-2+b1
pn openttd-data <none>
ii zlib1g 1:1.2.11.dfsg-2+deb11u2
Versions of packages openttd recommends:
ii openttd-opengfx 0.6.0-1
pn openttd-openmsx <none>
pn openttd-opensfx <none>
pn timidity <none>
Versions of packages openttd suggests:
pn openttd-opensfx <none>
pn timidity <none>
--- End Message ---
--- Begin Message ---
tags 1032857 +wontfix
thanks
Hey Toni,
I'm cleaning up my bug report backlog and noticed this bug was still
open and I did not reply to your previous mail, apologies for that (for
the bug report log: that was a private message sent by Toni).
I've taken another look at the jgrpp patches, which really are not just
a few patches, but it is effectively a fork with over a hundred patches
or features integrated. It does seem the fork is kept up-to-date with
upstream (which is quite impressive for such a long list of changes).
It does have completely separate versioning and is released from its own
repository, meaning the only reasonable way to package this would be in
its own Debian source package, alongside the openttd package.
I am not opposed to this, but I a not willing to take on maintainership
of this package (especially seeing the package has releases quite
often). If anyone else comes along that wants to do this, I'm happy to
collaborate on the packaging needed.
Given all that, I'll close this as wontfix for this package.
Gr.
Matthijs
On Sun, Apr 30, 2023 at 09:23:59PM +0100, Toni Mueller wrote:
>
> Hey Matthijs,
>
> On Sun, Apr 30, 2023 at 11:21:19AM +0200, Matthijs Kooijman wrote:
> > Thanks for your suggestion. What did you have in mind exactly?
>
> I thought that the patched package would replace the unpatched package.
>
> > I won't include third-party patches in the main build, since that
> > affects multiplayer compatibility (i.e. a patched build will be
> > incompatible with other people playing unpatched builds).
>
> Ok. I was unaware of that, but this patch adds a lot of flexibility and
> parallelism to the game, making it much more realistic to play.
>
> > I could consider including a non-patched and a patched build
> > side-to-side (i.e. in two different binary packages), but I'm not sure
> > I want to go down this path either (this is just one set of patches, but
> > I'm pretty sure there's others and before we know it we'll be packaging
> > a dozen of different patch sets...).
>
> I do understand the general argument, but am not aware of other patches
> for this game. And in any case, you could still have these two packages
> and then look at popcon to see which one has more traction.
>
> > IMHO the right path to making these patches more accessible, is to
> > submit them for inclusion upstream (possibly after improving the patch
> > quality).
>
> I think I'll look into why it hasn't yet been included into upstream.
>
> > So I'm inclined to close this as wontfix.
>
> That's a fair call, too, if you would still be receptive to my
> submitting a patch.
>
>
> Thanks,
> Toni
signature.asc
Description: PGP signature
--- End Message ---
