When will system-config-printer-gnome 1.5.9 be available in Ubuntu 16.04?

Asked by bastux on 2019-02-20

Currently only version 1.5.7 is available:
apt-cache policy system-config-printer-gnome
system-config-printer-gnome:
  Installiert: 1.5.7+20160212-0ubuntu2
  Installationskandidat: 1.5.7+20160212-0ubuntu2
  Versionstabelle:
 *** 1.5.7+20160212-0ubuntu2 500
        500 http://10.62.64.23/pool/TesatXenial ./ Packages
        500 http://de.archive.ubuntu.com/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status
(sources.list can be provided if needed)

But version 1.5.9 fixes the following bug:
error message "cups-waiting-for-job-completed" gets displayed, but there is no error present.
https://bugs.launchpad.net/ubuntu-mate/+bug/1656790

This was fixed on 2017-08-25, but still the package isn't present in the Ubuntu 16.04 repositories:
https://packages.ubuntu.com/search?keywords=system-config-printer-gnome

The following might be a little off topic:
Generally, when are new software releases moved to the official ubuntu repositories? Whats the process behind that? Because I thought an LTS-release would provide the latest software packages while it's under support.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu system-config-printer Edit question
Assignee:
No assignee Edit question
Solved by:
Manfred Hampl
Solved:
2019-02-20
Last query:
2019-02-20
Last reply:
2019-02-20
Manfred Hampl (m-hampl) said : #1

Manfred Hampl suggests this article as an answer to your question:
FAQ #3037: “no rolling release”.

Best Manfred Hampl (m-hampl) said : #2

Re: "I thought an LTS-release would provide the latest software packages"

No, on the contrary. LTS releases are focusing on stability, and consequently do not add new functionality during their support period. Just severe bugs are corrected.

If you think that bug 1656790 deserves being corrected also for Ubuntu 16.04, then please create a bug report or add a comment in an already-existing one.

bastux (bastux) said : #3

Thanks Manfred Hampl, that solved my question.

bastux (bastux) said : #4

I commented on the bug report, as you suggested. Thank you Manfred.