Bug#901461: Packaging mu for Debian
On 25 August 2018 at 07:44, Petter Reinholdtsen <pere@hungry.com> wrote:
> [Nick Morrott]
>> This update tags the packages for non-free/{python,docs} - the
>> embedded pre-compiled Micropython firmware for the micro:bit doesn't
>> leave an alternative AFAICT at the moment).
>
> Is the Micropython implementation free software, and possible to build
> using free software? Is it possible to place it into its own package
> and build the firmware in Debian? Should it be split into a separate
> package to be shared between mu and uflash?
Discussion about the upstream MicroPython runtime is taking place at
https://github.com/ntoll/uflash/issues/54.
Upstream have confirmed that there are no non-free sources included in
the firmware, However, whether it is possible to build the firmware
locally with yotta without requiring an ARM mbed account *and* network
connection remains to be clarified.
The yotta build tool is not packaged in Debian.
>> The packaging would benefit from review and is currently without a
>> sponsor - I'll post an RFS to debian-python separately,
>
> Several lintian issues to address. Are you looking into those?
Aside from ever-changing Standards versions, there are 2 non-overridden issues:
testsuite-autopkgtest-missing
debian-watch-does-not-check-gpg-signature
I am looking into addressing the first issue, as I add build testing using xvfb.
> Feel free to contact me on IRC if you want me to sponsor the package.
Thanks. I am also pinging #debian-python for suggestions - the outcome
of the MicroPython runtime build steps seems like it will dictate how
to binary packages are organised.
Reply to: