Hi Robert,

Le 20-05-21 à 17 h 31, Robert Hardy a écrit :
>
> Working with Debian is a nut I've yet to crack. I haven't got further
> than my own PPAs.
> I've tried before but it seems a lot more complicated than it needs to be.
> When I hear about a year long process to become a Debian developer and
> the need for mentoring I tend to glaze over...
> I'll have to try at some point but my time is expensive and I don't
> have a lot of time for games, especially when it's pro bono...
>
<DD hat>I totally understand the feeling, however please don't be
discouraged. There's no need to apply for Debian Developper status to
contribute to Debian, packaging or otherwise. But in any case, I can
assure you that the vast majority of applicants are able to complete the
process in a couple of weeks. But anyways, let's not hijack this thread
to talk about Debian, feel free to contact me if you have questions
about getting involved in Debian!</DD hat>

>
> You didn't read my message. The existing packages of freerdp2 inside
> Ubuntu are ancient pre-release development git snapshots from February
> 2019.
> There have been major changes to fix all sorts of problems. There are
> 2663 closed issues on github.
> It's hard to map exactly how many came after that snapshot in February
> 2019 with the UI in front of me but it's a lot of them.
> It also includes fixes to address significant 14 security vulnerabilities.
>
It's true that the version of freerdp in Debian/Ubuntu isn't quite up to
date but I can confirm that the packaging team is working on it. If you
look at the git repository for freerdp2-dev, you'll see that the sources
have been updated to freerdp-2.1.0 just a few days ago:
https://salsa.debian.org/debian-remote-team/freerdp2/-/blob/master/debian/changelog

Therefore it seems very likely that the next Debian stable release will
include a reasonably recent version of freerdp2.

-- Jerome


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to