This bug was fixed in the package pyferret - 7.2-1
Sponsored for Simon Quigley (tsimonq2)
---------------
pyferret (7.2-1) unstable; urgency=medium
* Mew upstream release
* Patch from Simon Quigleyo ensure we are py3-version neutral.
Closes: #869235
* Add gbp.conf file
* __init__.py: Add default values for FER_PALETTE, etc.
-- Alastair McKinstry <[email protected]> Sat, 22 Jul 2017 16:43:34
+0100
pyferret (7.1.1.beta-1) unstable; urgency=medium
* New upstream release.
- remove obsolete py3 patches
- patch to fixup setup.py for py3 libname
* Ignore tests for this build
* Standards-Version: 4.0.0. No changes required
* Enable builds with python3.5, py3.6 simultaneously. Closes: #863004
-- Alastair McKinstry <[email protected]> Sun, 25 Jun 2017 11:05:57
+0100
pyferret (7.0.0-3) unstable; urgency=medium
* Move to DH_COMPAT=10
* Depend on python*-dev not python*-all-dev. Closes: #863994
-- Alastair McKinstry <[email protected]> Thu, 18 May 2017 07:06:22
+0100
** Changed in: pyferret (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705759
Title:
Merge 7.1.1.beta-1 from Debian Sid
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyferret/+bug/1705759/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
