[Backport Request] tuxpaint, tuxpaint-config from Intrepid to Hardy

[Aaron Pickett]

tuxpaint 1:0.9.20-2ubuntu1 and tuxpaint-config 0.0.10-1 are available in Intrepid. Please backport to Hardy LTS.

The current version in Hardy blocks monitor screensaver/power-saving mode. The new version gives the option of allowing power management, as well as adding drawing tools and other features listed at: http://www.tuxpaint.org/docs/CHANGES.txt

My young children often forget to close the program when finished, so this is a helpful feature. Please, think of the children! (And the electricity usage of their old CRT monitor.)

[Chris Coulson (chrisccoulson)]

Just a thought - if the current Hardy version inhibits power management with no way of changing this behaviour, then perhaps it should be considered for fixing via a SRU (if the change isn't too big). Has anyone reported a bug for this behaviour yet?

[Aaron Pickett (aaron-d-pickett)]

Here's the original request to get tuxpaint updated in Ubuntu, but it only made it as far as adding the new package to Intrepid.
https://bugs.launchpad.net/ubuntu/+source/tuxpaint/+bug/173293

The responsible POC said that backporting would be a separate issue.

[Aaron Pickett (aaron-d-pickett)]

With regard to the SRU issue, this doesn't seem to fit the criteria at https://wiki.ubuntu.com/StableReleaseUpdates

Even the tuxpaint change log treats this like a feature addition rather than a bug fix:
* Added "--allowscreensaver" option, which prevents Tux Paint from disabling
  the screensaver or monitor power management while running.

So, this would appear to be a backport issue rather than a SRU. However, I will understand if this isn't a high priority for the backports team. Beyond simply resolving this tuxpaint issue, this is a chance for me to get familiar with Launchpad and contributing to the Ubuntu community.

[Evan Broder (broder)]

It looks like this bug requests a backport from Ubuntu 8.10 (Intrepid
Ibex). However, as Intrepid is no longer supported, such a backport is
no longer possible.

This bug is being set to "Won't Fix". If you would still like to move
forward with this backport request, please re-open the bug and adjust
it to request a backport from a current release.

(This change is being made by an automated bot run by Evan Broder, who
is now subscribed to the bug; if you think the change was made in
error, please feel free to re-open the bug)