[Bug 1920567] Update Released

[Brian Murray]

The verification of the Stable Release Update for ply has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ply in Ubuntu.
https://bugs.launchpad.net/bugs/1920567

Title:
  Misbuilds on focal: virtual packages are not provided

Status in ply package in Ubuntu:
  Fix Released
Status in ply source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * If we (or a user) has to re-build ply, it misbuilds, silently.

  [Test Plan]

  Rebuild from source.
  apt show python3-ply | grep Provides

  Good:
  Provides: python3-ply-lex-3.10, python3-ply-yacc-3.10

  Bad:
  Empty output.

  [Where problems could occur]

   * Pretty minimal risk, no library code changes.
     Just getting things to build correctly, again.

  [Other Info]
   
   * The -4 upload included a port of the virtual package script to Python 3. Not backporting that, because it's a larger change.

  [Original Bug Report]
  Version: 3.11-3build1
  Ubuntu release: 20.04

  The python3-ply binary package should provide these virtual packages:
  python3-ply-lex-3.10, python3-ply-yacc-3.10, but it cannot provide
  them after a build in a fresh focal docker container.

  This is because the provided virtual package names are generated by
  the 'debian/virtual-packages.py' script, which uses a shebang with
  '/usr/bin/python'. By default there is no 'python' binary on ubuntu
  focal.

  One solution could be adding the 'python-is-python2' package as a
  build dependency. I have used this temporarily.

  Or the shebang could be more specific: '/usr/bin/python2' or
  '/usr/bin/env python2'.

  Or the script could be ported to python3 with a proper specific
  shebang.

  It would also be useful to raise a build error, when the script fails.

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