Firstly, Happy Holidays to everyone, we all hope that you have a nice festive season and that the New Years brings good fortune. But back to the business at hand…
The backport repositories exist so that we can provide updates to software that are needed by some users, or provide significant feature improvements but which are potentially disruptive to installed stable systems.
This is the case with the latest version of the HP printer and scanner software (hplip), which adds support for some new devices, but which our QA testing found to be incompatible with some existing devices.
Further details of the devices that are supported by hplip-3.15.11 can be found in the hplip release notes.
A list of HP printers and the required minimum version of hplip can be seen here and the new printers that are supported by this backport are listed here.
The new version of the hplip packages are now available in the Core Backports repository.
If you have a new HP printer or scanner which does not function properly with Mageia 5, you may require these packages.
Installing backports in Mageia is quite simple:
In rpmdrake, “Install & Remove Software”, select backports from the first drop-down filter. If a previous version is installed the available packages will be marked in the status column with a down arrow with a line above it in a red circle. Select and install the packages appropriate for your architecture.
It is NOT necessary to enable the Backports repository.
Do not forget to nginx
Pingback: Unser erster (eigener) Backport – HPLIP 3.15.11 | Mageia Blog (Deutsch)
Did i just read right ????? i must be sleeping and have a bad nightmare ?.
See for yourself, its really real
Yes i know it’s real,little joke as it take so long to open them.:D
Any chance that a more recent version of Firefox can be added to backports? I’m trying to convince my recent Linux converts that WebRTC is better than Skype but the Firefox ESR that ships with mga5 doesn’t have it. Unpacking tarballs and creating symlinks is easy for me but not them.
What version is required for WebRTC to work?
The ESR that we ship looks very close to being up to date so I’m wondering if this would require using the non esr branch?
Where that information is coming from ? according to this article it should be enabled in firefox 38.
Works fine here.
Perhaps Firefox Hello was enabled in 38 non-ESR but disabled in ESR 38.x (provided by Mageia). The Firefox Hello smiley face icon wasn’t visible and these confirm why not:
It may be possible to get it working by going to about:config, agree to dire warnings and change some settings. I decided to get a newer version straight from mozilla.org which has made several improvements to Hello that won’t be backported to ESR 38 plus it just works out-of-the-box.
shulltz kindly added my request to the Mageia dev mailing list. Their response was rather unfriendly. They consider the official releases at mozilla.org as unstable development versions and don’t even want them in backports. Its their choice but fortunately, I have choices too…
Firefox Hello (WebRTC) is intentionally deactivated in 38 ESR for backward compatibility reasons. Having an option to install a non-ESR firefox from Backports would be great. I noticed that Cauldron has non-ESR SRPMS available which (so far) build fine on mga5 so it seems do-able.
OK, I’ll bring this to the dev list and see what they say, but I’m fairly sure that this will come down to a mix of maintainer/security/can of worms issue.
Not sure if you would be willing to join and maintain or help to maintain firefox, any helps is always appreciated.
I was willing to help. I joined the dev list and offered as much in the thread you kindly started. I was wrongly accused of bringing this up before and told to stop beating the dead horse. It seemed rather hostile in there and the horse smells quite dead so I left with my feet. I thought the request seemed reasonable for backports but apparently not. Thanks for trying though.
The replies after you post on the ML expands on the issue and I should have been more aware of it. The packaging of FF is a pain as upstream use the dev channel as a release channel and force users onto that for the newest features as is the case here.
Its one of the reasons I stopped using FF years ago, if I had realised that the backport would require an updated set of libraries not just contained by FF I wouldn’t have suggested it as that is a whole different upgrade.
Pingback: İlk Backport’umuz – HPLIP 3.15.11 | Mageia Blog (Türkçe)
Pingback: Nosso primeiro Backport – HPLIP 3.15.11 | Mageia Blog (Português)
Pingback: Onze eerst backport – HPLIP 3.15.11 | Mageia Blog (Nederlands)