Bug 1592524 - Upgrade Gutenprint to 5.2.14
Summary: Upgrade Gutenprint to 5.2.14
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gutenprint
Version: 28
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-18 18:34 UTC by Robert Krawitz
Modified: 2019-05-13 09:56 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-13 09:56:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Krawitz 2018-06-18 18:34:04 UTC
Description of problem: Fedora 28 Gutenprint is a 5.2.14 pre-release that is out of date (in particular, it does not have full support for color laser printers).


Version-Release number of selected component (if applicable): 5.2.14-pre2


How reproducible: dnf install gutenprint


Steps to Reproduce:
1. dnf install gutenprint
2.
3.

Actual results: 5.2.14-pre2 is installed


Expected results: 5.2.14 is installed


Additional info:

Gutenprint 5.2.14 is a major release that adds full support for most color laser printers.  5.2.14-pre2 has incomplete support, and as a pre-release is not supported by the Gutenprint team.

I am upstream project lead for Gutenprint.

Comment 1 Solomon Peachy 2018-06-28 13:19:02 UTC
Just FYI, this should have been reported against 'gutenprint' not 'printer-filters'

Comment 2 Zdenek Dohnal 2018-06-28 13:40:04 UTC
Hi Robert and Solomon,

sorry for the delay, I'll rebase gutenprint in F28 and rawhide.

Comment 3 Solomon Peachy 2018-06-28 17:23:58 UTC
(In reply to Zdenek Dohnal from comment #2)
> sorry for the delay, I'll rebase gutenprint in F28 and rawhide.

Thank you!

I'd personally like to see 5.2.14 go into F27 as well, due to the substantial improvements in printer support over 5.2.13.

And RHEL too, while we're at it -- RHEL6 and RHEL7 are still on 5.2.5 and 5.2.9, released eight and six years ago, respectively.

It doesn't go over well when we have to tell folks they need to upgrade or switch their entire OS (or walk them through recompiling gutenprint from source) in order to use their printers.

Comment 5 Zdenek Dohnal 2018-06-29 10:14:16 UTC
(In reply to Solomon Peachy from comment #3)
> (In reply to Zdenek Dohnal from comment #2)
> > sorry for the delay, I'll rebase gutenprint in F28 and rawhide.
> 
> Thank you!
> 
> I'd personally like to see 5.2.14 go into F27 as well, due to the
> substantial improvements in printer support over 5.2.13.

I'll consider it - generally I don't like putting new version onto stable Fedora releases, because it can suddenly break a use case for user.  

> 
> And RHEL too, while we're at it -- RHEL6 and RHEL7 are still on 5.2.5 and
> 5.2.9, released eight and six years ago, respectively.

I'm sorry, that's can't be done.
Our preference in RH is to maintain compatibility between minor releases, so we usually backport bugfixes and features to older releases. And RHEL 6 is in production phase 3, in which we don't do any rebases.

> 
> It doesn't go over well when we have to tell folks they need to upgrade or
> switch their entire OS (or walk them through recompiling gutenprint from
> source) in order to use their printers.

Would you mind telling them to contact our support at access.redhat.com (for RHEL cases, if they have subscription) or file a bugzilla? If they do such things, then we have information the customer wants a new feature and I can look into the code if it is possible to backport it (or rebase the package in difficult cases).

Comment 7 Solomon Peachy 2018-06-29 13:42:25 UTC
> I'll consider it - generally I don't like putting new version onto stable
> Fedora releases, because it can suddenly break a use case for user.  

Gutenprint takes great pains to maintain backwards compatibility across a release series, to the point where any user-visible changes (including any change in output for a given printer) is considered a regression and has to be proven/justified lest it be reverted.

> I'm sorry, that's can't be done.

I didn't have high expectations, but I figured it wouldn't hurt to ask!

> Our preference in RH is to maintain compatibility between minor releases, so
> we usually backport bugfixes and features to older releases. And RHEL 6 is
> in production phase 3, in which we don't do any rebases.

Gutenprint 5.x.y+1 is fully backwards compatible [*] with 5.x.y. "backporting bugfixes and features" to an older release in the series would yield essentially the same results as just rebasing to a newer release, albeit in a far riskier manner.

[*] With one noticeable exception -- 5.2.12 dropped support for foomatic and ijs as it was becoming an increasing maintenance burden, and IIRC the final straw was the discovery of a major bug that went unnoticed for years because everyone had long since switched to CUPS.

> Would you mind telling them to contact our support at access.redhat.com (for
> RHEL cases, if they have subscription) or file a bugzilla? If they do such
> things, then we have information the customer wants a new feature and I can
> look into the code if it is possible to backport it (or rebase the package
> in difficult cases).

Most of my headaches come from fairly technically illiterate folks using Debian (on underpowered Arm systems) but the ones using "EL" have to my knowledge all done their mass deployments on CentOS rather than RHEL.

I personally consider RHEL6 too obsolete to care about any more, but if RHEL7/CentOS7 pops back up I'll probably just respin the fedora packages instead.

Comment 9 Robert Krawitz 2018-07-02 15:04:55 UTC
(In reply to Zdenek Dohnal from comment #5)
> (In reply to Solomon Peachy from comment #3)
> > (In reply to Zdenek Dohnal from comment #2)
> > > sorry for the delay, I'll rebase gutenprint in F28 and rawhide.
> > 
> > Thank you!
> > 
> > I'd personally like to see 5.2.14 go into F27 as well, due to the
> > substantial improvements in printer support over 5.2.13.
> 
> I'll consider it - generally I don't like putting new version onto stable
> Fedora releases, because it can suddenly break a use case for user.  

Fedora 27 is already using a pre-release version of 5.2.13, so it's not an official release (of Gutenprint) to begin with and we can't respond to any issues unless they are reproduced on an official release.

There is one change in 5.2.14 over 5.2.12-5.2.13 that does change color; it really fixes what we decided was a bug in 5.2.12.  If you want to unrevert it, you could cherrypick change bfe1cdda9201a70375f5b6baed490d4fbb68f662 out.  We had a lot of debate over whether to make that change; we *really* don't like incompatible changes between releases!

Comment 10 Fedora Update System 2018-07-10 13:55:20 UTC
gutenprint-5.2.14-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-4b13d90f0e

Comment 11 Fedora Update System 2018-07-11 23:42:41 UTC
gutenprint-5.2.14-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-4b13d90f0e

Comment 12 Fedora Update System 2018-07-18 18:30:32 UTC
gutenprint-5.2.14-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 13 Andrew Wasielewski 2018-12-20 10:04:17 UTC
It would be good to have Gutenprint updated on RHEL7 itself.  My home router/firewall runs on ClearOS, which is based on CentOS 7 and thus RHEL7.  In order to share our Canon PIXMA iP7250 connected directly via USB I had to manually install the Fedora 29 Gutenprint packages.  It works fine, but not ideal installing Fedora pacjages on Centos.  Gutenprint 5.3.1 is also now available.

Comment 14 Ben Cotton 2019-05-02 19:17:09 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Ben Cotton 2019-05-02 20:06:28 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Zdenek Dohnal 2019-05-13 09:56:01 UTC
Actually, it is in stable now - the bug is not closed due error in bodhi - bugzilla communication.


Note You need to log in before you can comment on or make changes to this bug.