Hi, On Fri, 10 Apr 2020 at 11:42:18 +0200, Dominik George wrote: > In any case, the roundcube backport has been in production for two weeks > now, and so far noone found any issue with it. Unfortunately 1.4.3+dfsg.1-1~bpo10+1 is currently *uninstallable* (WTF?) without pulling php-masterminds-html5 from Bullseye :-( This is the missing dependency I was referring to in my (two IIRC) earlier messages as the only technical blocker for 1.4.3+dfsg.1-1~bpo10+1. (Concerns regarding the sustainability of the backport remain, but upstream development isn't as fast-paced as it used to some years ago, so my gut feeling is that keeping the backport in shape will be less painful than for jessie-backports.) AFAICT php-masterminds-html5 isn't lying in BACKPORTS-NEW either. I mailed its uploader (taffit) to ask his opinion regarding an upload to buster-backports. I can also take care the backport itself. In principle we could also demote it from Depends: to Recommends:, as IIRC roundcube will fallback to another parser (the former default) for HTML messages if Masterminds/HTML5 is missing; I'm quite reluctant to change upstream defaults though. And in any case the change would need to be made in sid first. > If you grant me access on Salsa, I will ofcourse import it into a git > branch, and commit to maintaining it there at least until the release of > bullseye. Speaking personally, I fear a “culture clash” in terms of communication, workflow and processes, so won't tweak the ACL. (Trimming the requests in my earlier replies was perhaps too subtle, so here is an explicit answer.) This is independent from the technical merit of your work or the fact that 1.4.3+dfsg.1-1~bpo10+1 isn't installable (shit happens). Cheers, -- Guilhem.
Attachment:
signature.asc
Description: PGP signature