Hi Matt, > From time-to-time we identify issues on our tracker which are best solved > downstream by the distros. Since the vast majority of our uses seem to be > using Debian-derived distros I would dearly like to get some engagement with > the Debian packagers over these, but at present I haven't identified a > useful mechanism to do so. I think you just did ;). This mailing list is for exactly that. > Good examples of these are #907878 which has been outstanding for a couple > of years, and #984782 which I raised myself a little recently. Firstly, all bugs that are not specific to Debian packaging should be fixed upstream. Unfortunately, xrdp 0.9.15 did not make it into bullseye in time. Situations like that could be improved if I weren't the only person working on the xrdp package. For now, we will have to wait for the bullseye release and then do backports for new versions and targeted fixes through stable-proposed-updates. I do not consider the mentioned bugs important enough to try testing-proposed-updates during the freeze. > At downstream, we're able to advise some users who stumble across these as > to fixes and workarounds. With "downstream", you mean Ubuntu? In any case, please always test on Debian, and do not report bugs to Debian that are not reproducible there. > To a point that's OK, but because we have no > engagement at present with Debian in particular, I can never be sure that > the fix I'm advising is optimal, or how I can propose it to Debian for > discussion at least. Simply e-mail it to the BTS, like you did with your bug report. > Is there a better mechanism for us to attempt an engagement other than > raising bugs? Should we maybe be proposing PRs in salsa too? I'm sure we can > find some effort to do that if it would be helpful to you and your users. Yes, if you have a patch that is Debian-specific, please propose it as MR on Salsa. If you find a bug that is Ubuntu-specific, please report it there. If you find a bug in xrdp upstream, and fix it, and think it should be fixed in Debian stable as well, please make a patch release based off of the version currently in Debian stable. The best option would be to synchronise Debian and xrdp, in a way that xrdp supports an LTS branch in parallel to the Debian stable lifecycle, where fixes for important bugs are backported to. We could simply track this branch in Debian stable then. For the current iteration, unfortunately this will mean to start with 0.9.12 (but I will provide the most recent version in bullseye-backports as soon as bullseye gets released) -nik
Attachment:
signature.asc
Description: PGP signature