On Mon 09 Mar 2020 at 16:50:46 +0100, Frank B. Brokken wrote: > Dear Brian Potkin, you wrote: > > > > On Mon, Mar 09, 2020 at 01:48:58PM +0100, Frank Brokken wrote: > > > > > * What outcome did you expect instead? > > > > > > After the update I expected the print commands to continue working > > > > All present and future bugs in HPLIP can be avoided after reading > > > > https://wiki.debian.org/CUPSDriverlessPrinting > > > > I would use the driverless command and lpadmin to set up a queue. > > Hi Brian,
Hello Frank. Don't forget to send mail to the bug report. > Thanks for your reply. Unfortunately, now I'm left in a somewhat > confused state. It's possible that I overlooked some important update item, > but normally when updating programs continue to work, and if a reconfiguration > is necessary then that's clearly shown in, e.g., the changelog. You did not overlook anything. The behaviour is a bug. > If I correctly understand your (above) advice then you ask me to read a > document of some 20 sections, explaining the concept of > 'CUPSDriverlessPrinting'. It's a thorough document, but maybe a bit over the > top for users who would merely like to be able to continue printing? It was a suggestion and could prove useful to a user. > I've now downgraded hplip to the stable version, and all's working again. But > I think an upgrade to the version in 'testing' is preferable, since my > computer's normal distribution is 'testing'. Is there maybe some quick > (step-by-step) upgrading guide explaining how to upgrade from the > stable-release software to the testing-release software without encountering > print-failures? I think such a guide would be really useful. > > Please advise, The bug has been fixed upstream. Debian will have the fix when a new package is uploaded to unstable. The only way to avoid any bugs in testing is not to use it. I gave you the way to avoid bugs in HPLIP earlier. Cheers, Brian.
