[Bug 1951678] Re: Sync micropython 1.17+ds-1.1 (universe) from Debian unstable (main)

[Hans Joachim Desserud]

Ok, fair enough.

I only saw that the Debian package listed etter pass or "not a
regression" for the autopkgtest runs. The latter sounded a bit strange,
but not directly bad. Though I suppose that were likely the
architectures where the package didn't build at all.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1951678

Title:
  Sync micropython 1.17+ds-1.1 (universe) from Debian unstable (main)

Status in micropython package in Ubuntu:
  Incomplete

Bug description:
  Please sync micropython 1.17+ds-1.1 (universe) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
    * Build with -Werror=maybe-uninitialized.
    * Build with -Werror=maybe-uninitialized.
    * Change subpkg_tried to a static variable to avoid clobbering by longjmp
      (LP: #1931955)
    * No-change rebuild against libffi8ubuntu1
    * No-change rebuild against libffi8ubuntu1
    * No-change rebuild against libffi8ubuntu1

  
  The extra -Werror=maybe-uninitialized build flag has been included in the Debian package.

  I am not sure about the other log entries mentioned above, since I
  cannot see them in the diff generated by
  https://patches.ubuntu.com/m/micropython/micropython_1.17+ds-1ubuntu1.patch

  Changelog entries since current jammy version 1.17+ds-1ubuntu1:

  micropython (1.17+ds-1.1) unstable; urgency=high

    * Non-maintainer upload.
    * debian/rules: Circumvent FTBFS with gcc 11 using
      -Wno-error=maybe-uninitialized cflag. (Closes: #994239)

   -- Boyuan Yang <byang at debian.org>  Wed, 10 Nov 2021 15:51:19 -0500

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/micropython/+bug/1951678/+subscriptions