Hi Mathias,
On 25/03/17 00:29, Mathias Behrle wrote:
* Ross Gammon: " [tryton-debian] Bug#785566: Removing pygoocanvas after Stretch
release" (Fri, 24 Mar 2017 17:47:47 +0100):
Hi Ross,
severity 785566 important
thanks
Hi,
I plan to ask for the removal of pygoocanvas after Stretch is released.
At that time, I will raise this bug's severity to serious.
Your message is in format for the control server, so didn't work. Which is kind
of fortunate, because I don't agree to raise the severity for the reasons below.
Thanks for spotting that - no problems. I will only raise the severity
for the other packages that haven't been as proactive as yourself. :-)
According to the upstream bug report, version 0.3 now supports the
latest goocanvas (2.0), so it should already be possible to depend on
gir1.2-goocanvas-2.0 instead of python-pygoocanvas.
As https://git.gnome.org/browse/goocanvas/log/ shows, the patches in
question were merged (2016-12-15), but not yet released.
The latest release of goocanvas in Debian dates from 11 Jun 2015
[2015-08-22] goocanvas-2.0 2.0.2-2 MIGRATED to testing
So the according changes are not available in Debian.
Please correct me if I am wrong (you are the maintainer of the package...;).
Otherwise please provide an updated goocanvas package.
Sorry about that - the upstream goocalender bug did not mention that the
changes were dependent on changes pushed to goocanvas, so I missed it. I
can see that goocanvas seem to be working towards a 3.0 release. I will
ask for their plans. One option might be to patch things in Debian so
that we have a path for goocalender before the next problem hits the
unmaintained pygoocanvas (in Debian and upstream).
Regards,
Ross
