Thank you for the repository access and the kind words. Knowing the history makes it much easier to pick up where you left off without repeating the same mistakes.
> First of all, thanks for stepping up and being ready to take over the > maintenance of Mono. I spent a lot of time improving its packaging from > the (very) poor state it reached over many years in an orphaned state, > and it feels good to know it is not going back to rot. Your improvements were substantial. The packaging is in genuinely good shape and the commit history makes the reasoning clear. It is a solid foundation to inherit. > To avoid confusion: the removal of this hook is part of an in-progress > removal of cli-common itself. For more details, see: > - https://bugs.debian.org/1079871 > - https://bugs.debian.org/1111276 Understood, and thank you for the correction. That reframes things entirely. I plan to send a wontfix reply to #1135240, withdraw the patch I submitted, and removed the block on #1133410. I notice two small cli-common remnants still present in ds2-2 that may be intentional - want to check: cli-common-dev in Build-Depends and the update-alternatives call for cli-gacutil in mono-runtime.postinst/prerm. My current ds2-3 commit is adoption-only and does not touch either. Would you like me to fold that cleanup into ds2-3 to give the upload a bit more substance, or would you prefer to keep ds2-3 minimal and defer it to ds2-4? Packages that relied on the cli-common registration path will need to migrate their own postinst scripts to call gacutil directly. > Before giving up on Debian, I was on my way to adopt libgdiplus as it > seems to be quite core to the Mono ecosystem. I would advise adopting > it in addition to Mono, see https://bugs.debian.org/1079870 Agreed. I will file the ITA against #1079870 once merge request !3 on the libgdiplus Salsa repository has had a chance to be reviewed or merged. Bastian's 6.1+dfsg-1.2 NMU in the meantime is helpful context for where the archive state sits. > Beware that "dotnet-team" is not a real thing. There is no Mono Team, > not for many years already. Noted. Could update wiki.debian.org/Teams/Mono to reflect solo maintenance. The Vcs-* fields in debian/control still point to salsa.debian.org/dotnet-team/mono, which *should* be fine since the repository is real; it is just the "team" framing that would need correcting in the wiki. > To be extra clear: I already see you as the sole maintainer of Mono, > so all I wrote above is mostly information about what I was doing in > the last years. Feel free to disregard parts or even all of it ;) I appreciate that. None of it is being disregarded - it has all been directly useful. My current ds2-3 commit is: sole Maintainer field, DM-Upload-Allowed: yes, Standards-Version 4.7.4, a gbp.conf encoding the branch/tag conventions, and Closes: #1133397 in the changelog. Lintian is clean. I was planning to push it to a feature branch (james/adopt-mono-6.14.1+ds2-3) for your review before anything touches debian/unstable. If you would prefer I push directly to debian/unstable, or have a different workflow preference, just say so. Since I do not yet have upload rights I will still need sponsorship for the actual upload. If you are willing to review and sponsor 6.14.1+ds2-3 I would be grateful. If you would rather point me toward another DD that is equally fine. > Oh, and please get in touch with Mono current upstream -- > https://gitlab.winehq.org/mono/mono as they seem to be very pleased at > the idea of a renewal of Debian maintenance: > https://gitlab.winehq.org/mono/mono/-/work_items/12 Will do. I plan to reach out once the adoption upload is in the archive so there is something concrete to point to. Regards, James
