[request-tracker-maintainers] RT5 and RT6 updates
Andrew Ruthven
andrew at etc.gen.nz
Tue Aug 12 13:42:36 BST 2025
Hey folks,
I just thought I'd give a quick update since trixie is now out the door.
I'm looking again at RT 5.0.8 and RT 6. I've just had the first successful
build of request-tracker6 using 6.0.1. I haven't tried installing it yet,
that'll be tomorrow's job.
5.0.8 is currently waiting on me adding libwebservice-dropbox-perl to Debian
(does anyone use Dropbox to externalise their attachments?!). It is
packaged, pending an upload to NEW.
6.0.1 needs these packages added (in addition to the one above):
- ckeditor5
- libselenium-remote-driver-perl
- libwww-mechanize-chrome-perl
The later is failing tests, so I'm working through those. libwww-mechanize-
chrome-perl is needed to include graphs in email reports, as RT 6 switches
to this from GD::Graph.
libwww-mechanize-chrome-perl also has a few dependencies that need to be
uploaded to NEW.
I don't have a resolution to no non-minified code for ckeditor5 yet, I asked
about it on debian-js@, but no progress. I sent another email yesterday
about it[0]. The good news with ckeditor5 though is that Best Practical are
no longer patching ckeditor, this means that we'll be able to use the
generic package once it is in Debian!
If we don't have a ckeditor5 package, do I just upload it with the minified
ckeditor5?
When do we drop RT4 from unstable? Yesterday?
I should contact DSA about upgrading rt.debian.org to RT 5...
Cheers,
Andrew
[0] https://lists.debian.org/debian-js/2025/08/msg00002.html
On Mon, 2025-04-14 at 00:54 +1200, Andrew Ruthven wrote:
> Hey,
>
> The first beta release of RT6 came out a few days ago. I've started to
> look
> at what'll be involved to update to it. The main sticking point at the
> moment seems to be ckeditor v5. Once again RT6 is shipping with a minified
> version. A difference this time is it is now the upstream files, not built
> by BP (you can now configure which extensions to use via config settings).
>
> I've looked at the upstream releases, it appears they only release it as
> minified code[0]. To create these, it appears to require either their web
> interface, or to use npm. ckbuilder which we've been using so far doesn't
> appear to support v5 and they're going to drop webpack support soon.
>
> I see that Best Practical are aware of this, and have engaged with the
> ckeditor devs on finding a path forward[1], unfortunately it doesn't look
> this has made it into 6.0.0beta1.
>
> I'm not sure at this stage how easy it is have the source for ckeditor5 in
> our packages, and build ckeditor5 offline. A naive search of Debian
> packages
> for files named "ckeditor" don't show any that look like v5, so I can't
> see
> any prior art yet. The "ckeditor" package is still v4.
>
> I'm loath to include only the minified files, but I'm not seeing much
> choice
> at the moment. Thoughts/opinions/etc?
>
> Cheers,
> Andrew
>
> [0]
> https://ckeditor.com/docs/ckeditor5/latest/getting-
> started/installation/self-hosted/quick-start.html#installing-ckeditor-5-
> from-a-zip-file
> [1] https://github.com/ckeditor/ckeditor5/issues/17779
>
--
Andrew Ruthven, Wellington, New Zealand
andrew at etc.gen.nz |
Catalyst Cloud: | This space intentionally left blank
https://catalystcloud.nz |
More information about the pkg-request-tracker-maintainers
mailing list