Bug 17186 - The availlable Hplip package is outdated, hplip-3.15.11 supports many more printers
Summary: The availlable Hplip package is outdated, hplip-3.15.11 supports many more pr...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 5
Hardware: All Linux
Priority: Low enhancement
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA5-32-OK mga5-64-ok
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-20 18:11 CET by Benjamin Leduc
Modified: 2015-12-10 10:57 CET (History)
8 users (show)

See Also:
Source RPM: hplip-3.14.6-8.1mga5, hplip-3.15.7-1.mga6
CVE:
Status comment:


Attachments

Description Benjamin Leduc 2015-11-20 18:11:28 CET
Dear Mageia team, 

While purchassing a new printer; HP Envy 4520, correctecly recognized in the CUPS, I failed to print out the test page. 
This printer is supposed to be correctly recognized with hplip 3.15.11, but the repo only have 3.14.6

Can you please package a newer version?

Best regards

Benjamin 

Reproducible: 

Steps to Reproduce:
Comment 1 Marja Van Waes 2015-11-21 21:25:12 CET
Support for quite a lot more new printers has been added.

We still have hplip-3.15.7 instead of 3.15.11 in cauldron and 
5/core/backports_testing, too, and there is no maintainer, so assigning to pkg-bugs ml

CC: (none) => marja11
Version: 5 => Cauldron
Assignee: bugsquad => pkg-bugs
Summary: The availlable Hplip package is outdated => The availlable Hplip package is outdated, hplip-3.15.11 supports many more printers
Source RPM: hplip 3.14.6 8.1mga5 => hplip-3.14.6-8.1mga5, hplip-3.15.7-1.mga6
Whiteboard: (none) => MGA5TOO

David Walser 2015-11-24 15:20:05 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=15266

Comment 2 Thomas Spuhler 2015-11-29 00:53:46 CET
resolved in cauldron

Status: NEW => ASSIGNED
CC: (none) => thomas
Assignee: pkg-bugs => thomas

Comment 3 Thomas Spuhler 2015-11-30 23:58:11 CET
resolved in mga5 by updating backports_testing to version 3.15.11
The following packages are now in mga5/backport_testing:

hplip-3.15.11-1.mga6.src.rpm
hplip-3.15.11-1.mga6.x86_64.rpm
lib64hpip0-3.15.11-1.mga6.x86_64.rpm
lib64hpip0-devel-3.15.11-1.mga6.x86_64.rpm
lib64sane-hpaio1-3.15.11-1.mga6.x86_64.rpm
hplip-model-data-3.15.11-1.mga6.x86_64.rpm
hplip-gui-3.15.11-1.mga6.x86_64.rpm
hplip-hpijs-3.15.11-1.mga6.x86_64.rpm
hplip-hpijs-ppds-3.15.11-1.mga6.x86_64.rpm
hplip-doc-3.15.11-1.mga6.x86_64.rpm
hplip-debuginfo-3.15.11-1.mga6.x86_64.rpm

and corresponding i586 packages

assigning back to QA

Assignee: thomas => qa-bugs

Comment 4 claire robinson 2015-12-01 01:09:30 CET
We are currently unable to push backports.
See also bug 15266

Priority: Normal => Low
Component: RPM Packages => Backports
Version: Cauldron => 5
Whiteboard: MGA5TOO => feedback
Severity: normal => enhancement

Comment 5 claire robinson 2015-12-01 01:10:56 CET
Was it decided that this should be pushed through Updates instead?

If so then please rebuild into updates testing instead.

Thanks
Comment 6 Thomas Spuhler 2015-12-02 19:14:08 CET
no, backports is the correct location.
We did push it to updates_testing earlier (version 3.15.7) and it was reversed since some folks had problems with their older printers using 3.15.7

Whiteboard: feedback => (none)

Comment 7 Herman Viaene 2015-12-04 12:09:14 CET
MGA5-32 on Acer D620 Xfce
No installation issues.
Removed my HP Officejet Pro 8100 (as network printer) from MCC, restarted MCC and the printer was dertected and configured properly. OK for me.
The printer is about 2 years old, worked OK with previous versions of HPLIP.

CC: (none) => herman.viaene

Herman Viaene 2015-12-04 12:09:29 CET

Whiteboard: (none) => MGA5-32-OK

Comment 8 Herman Viaene 2015-12-04 15:21:13 CET
Note: I could not find the hplip-debuginfo-3.15.11-1.mga6.x86_64.rpm in MCC.
Comment 9 Luke Jones 2015-12-04 22:23:31 CET
Was there any indication of the age of the non-working printers given?
If they are very old, then it would make much more sense to push this to Updates, and the older drivers to backports.

Logically, many more people are going to have newer printers rather than old printers, and from a UX point of view, it would be users would expect new equipment to work.

It's the same thing with gfx cards.

CC: (none) => luke.nukem.jones

Comment 10 Dave Hodgins 2015-12-05 04:47:47 CET
Very few people will have the backports repos enabled. I agree with Luke, that it
would make more sense to push this as an update, and have a backport of the
older version so those who do have problems can still use their printers.
Hopefully there will be a lot less people impacted by this, then the number of
people who can use the new printer definitions.

CC: (none) => davidwhodgins

Comment 11 Thomas Spuhler 2015-12-05 23:47:38 CET
I was in favor of pushing it to updates, but as far as I recall the resistance came from QA
See http://svnweb.mageia.org/packages?view=revision&revision=872637 for the actual reversion.
Claire, I think you were in strong favor of putting it into backports.
Comment 12 Thomas Backlund 2015-12-06 00:23:02 CET
NO. 

We have an established policy to not push updates that knowingly break stuff for users of stable releases.

and only newer stuff go to backports. end of discussion.

CC: (none) => tmb

Comment 13 Luke Jones 2015-12-06 01:44:22 CET
Ah, my apologies everyone, I had thought this was for Cauldron in which case I would strongly suggest the newer version take priority. However since this is for mga5, the policy is good and should stand for stable releases, I agree.

If there were an extremely high percentage of users who required the newer version, then I would put up another argument for it, but this does not appear to be the case.

/mageia_newbie out.
Comment 14 Benjamin Leduc 2015-12-06 02:49:34 CET
It is more than needed.... 
The availlable driver does not work for any printer availlable in stores...
Comment 15 claire robinson 2015-12-06 10:33:12 CET
Please enable Core Backports Testing then Benjamin and install the packages listed in comment 3, leave feedback here whether they work or not and which arch (i586 or x86_64) you tested.

Thanks.
Comment 16 Thomas Spuhler 2015-12-06 18:44:52 CET
(In reply to Luke Jones from comment #13)
> Ah, my apologies everyone, I had thought this was for Cauldron in which case
> I would strongly suggest the newer version take priority. However since this
> is for mga5, the policy is good and should stand for stable releases, I
> agree.
> 
> If there were an extremely high percentage of users who required the newer
> version, then I would put up another argument for it, but this does not
> appear to be the case.
> 
> /mageia_newbie out.

I think there are good arguments for both ways. Before the end of life of mga5 there are probably more printers that will not work with the version in the release than printers that work.
But it's the current policy not to update packages for new features. Also those who buy a new printer are probably more open to upgrade from backports than those whose printer suddenly doesn't work anymore after a normal update from updates.
Comment 17 claire robinson 2015-12-07 16:45:27 CET
Did you have a chance to test this yet Benjamin?
Comment 18 Thomas Spuhler 2015-12-08 00:17:45 CET
Where are we with testing? See new bug report #17293
I am changing priority and severity.

Priority: Low => High
Severity: enhancement => major

Comment 19 claire robinson 2015-12-08 09:42:31 CET
Backports are always lowest priority.

It seems Richard tested it x86_64 in bug 17293. Benjamin is not responding, however we can validate this now.

Unfortunately, as stated previously, we don't have infrastructure in place yet to support pushing and it will have to be done manually.

I don't want to add "validated_updated" keyword until the process is sorted out, as it could include it in the list of packages to push to updates and cause that process to fail.

Sysadmins, please manually push from 5 Core Backports Testing to Core Backports.

Thanks

Priority: High => Low
CC: (none) => sysadmin-bugs
Whiteboard: MGA5-32-OK => MGA5-32-OK mga5-64-ok
Severity: major => enhancement

Comment 20 claire robinson 2015-12-08 09:45:41 CET
------------------
Core Backports Testing
hplip-3.15.11-1.mga5
------------------
Core Release
hplip-3.14.6-8.mga5
------------------
Core Updates
hplip-3.14.6-8.1.mga5
------------------
Comment 21 Pascal Terjan 2015-12-10 10:57:09 CET
Done:

[mga-advisories@valstar ~]$ mga-adv-move-pkg --sync --backport 5/core/hplip
The following SRPMs (and their corresponding binaries) will be moved:
- hplip-3.15.11-1.mga5.src.rpm

Are you sure? [Y/n] 

Moving binary and source rpms:
- i586:
    hplip-3.15.11-1.mga5.i586.rpm
    hplip-doc-3.15.11-1.mga5.i586.rpm
    hplip-gui-3.15.11-1.mga5.i586.rpm
    hplip-hpijs-3.15.11-1.mga5.i586.rpm
    hplip-hpijs-ppds-3.15.11-1.mga5.i586.rpm
    hplip-model-data-3.15.11-1.mga5.i586.rpm
    libhpip0-3.15.11-1.mga5.i586.rpm
    libhpip0-devel-3.15.11-1.mga5.i586.rpm
    libsane-hpaio1-3.15.11-1.mga5.i586.rpm
    hplip-debuginfo-3.15.11-1.mga5.i586.rpm
- x86_64:
    hplip-3.15.11-1.mga5.x86_64.rpm
    hplip-doc-3.15.11-1.mga5.x86_64.rpm
    hplip-gui-3.15.11-1.mga5.x86_64.rpm
    hplip-hpijs-3.15.11-1.mga5.x86_64.rpm
    hplip-hpijs-ppds-3.15.11-1.mga5.x86_64.rpm
    hplip-model-data-3.15.11-1.mga5.x86_64.rpm
    lib64hpip0-3.15.11-1.mga5.x86_64.rpm
    lib64hpip0-devel-3.15.11-1.mga5.x86_64.rpm
    lib64sane-hpaio1-3.15.11-1.mga5.x86_64.rpm
    hplip-debuginfo-3.15.11-1.mga5.x86_64.rpm
- source:
    hplip-3.15.11-1.mga5.src.rpm

Status: ASSIGNED => RESOLVED
CC: (none) => pterjan
Resolution: (none) => FIXED


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