Re: Orphaning mu-editor, firmware-microbit-micropython, and their (build)-deps

2024-04-19 Thread Keith Packard
> Now Keith can rebase his changes unto that. My changes involve stripping the non-DFSG elements out of the package, and that requires shipping a non-upstream .tar.gz file for the source archive. Because of that, I'm using a pure git process and not bothering to generate pristine tar bits -- ther

Re: Orphaning mu-editor, firmware-microbit-micropython, and their (build)-deps

2024-04-19 Thread Alexandre Detiste
Hi, I did this upstream bump because I think that MR on upstream & pristine-tar brach should not be allowed. (the Games Team did received several such MR from XZ-hack "Hans Jansen" puppet socket) Now Keith can rebase his changes unto that. Greetings Le sam. 20 avr. 2024, 00:34, Nick Morrott >

Re: Orphaning mu-editor, firmware-microbit-micropython, and their (build)-deps

2024-04-19 Thread Nick Morrott
On Fri, 19 Apr 2024 at 16:34, Hans-Christoph Steiner wrote: > > Hey Nick, > > Thanks for maintaining mu-editor, my kids are just getting started with it. > So > I might be interested in taking it over. Are the updates a lot of work? I > see > the tarball is tagged with dfsg so there's that...

Re: Orphaning mu-editor, firmware-microbit-micropython, and their (build)-deps

2024-04-19 Thread Hans-Christoph Steiner
Hey Nick, Thanks for maintaining mu-editor, my kids are just getting started with it. So I might be interested in taking it over. Are the updates a lot of work? I see the tarball is tagged with dfsg so there's that... .hc Nick Morrott: Dear team, I intend to orphan two of my team main

Orphaning mu-editor, firmware-microbit-micropython, and their (build)-deps

2024-04-19 Thread Nick Morrott
Dear team, I intend to orphan two of my team maintained packages, and their several (build)-dependencies, that I originally packaged and have maintained (to varying degrees, it can be argued) since 2018. Thank you to team members who have contributed bug fixes and patches during this time. I've re