[EN] Python 3 upgrade forces removal of hplip & friends

[dibl]

.
If you don't want to wait you can test the patch script on the iso live image in a couple of days.

The workaround that @Teriarch made, described in post #10 on this thread, is working perfectly for my HP LaserJet Pro p1606dn, for 2 siduction systems in my home.

[Teriarch]

Please,please check the script first on the live shine-on iso image before you proceed.

If something fails you can always restart and report the failure. Be sure to have sudo
configured for the current user and don't worry if the hplip packages will get removed in
the process, you will get them back in a blink of an eye even before the script ends.

Have fun!

Code: [Select]

#!/usr/bin/bash

pushd .
sudo apt-get update
mkdir /tmp/hplip
mkdir /tmp/hptmp
cd /tmp/hplip
sudo apt-get install python3 python3.12
apt-get download python3
dpkg-deb -x /tmp/hplip/python3_3.13.1-2_amd64.deb /tmp/hptmp
dpkg-deb --control python3_3.13.1-2_amd64.deb /tmp/hptmp/DEBIAN
sed -i -e 's/python3-profiler/python3 (= 3.12), python3-profiler/g' /tmp/hptmp/DEBIAN/control
sed -i -e 's/Version: 3.13.1-2/Version: 3.13.1-2b/g' /tmp/hptmp/DEBIAN/control
dpkg-deb --root-owner-group -b /tmp/hptmp /tmp/hplip/python3_3.13.1-2b_amd64.deb
rm /tmp/hplip/python3_3.13.1-2_amd64.deb
sudo dpkg -i /tmp/hplip/*.deb
cd /tmp
rm -rf /tmp/hptmp /tmp/hplip

sudo apt-get install hplip hplip-data hplip-gui
grep -r '#!/usr/bin/python3' /usr/share/hplip /usr/lib/cups/backend 2>/dev/null|sed -e 's/:#!\/usr\/bin\/python3//g'|xargs -n1 sudo sed -i -e 's/\#\!\/usr\/bin\/python3/\#\!\/usr\/bin\/python3.12/g'
# grep -r '#!/usr/bin/python3' /usr/share/hplip /usr/lib/cups/backend 2>/dev/null|sed -e 's/:#!\/usr\/bin\/python3.12//g'|xargs -n1 sudo sed -i -e 's/\#\!\/usr\/bin\/python3.12/\#\!\/usr\/bin\/python3/g'
/usr/bin/hp-systray -x&
popd



[Teriarch]

A minor improvement to get rid of the version tracking in case
Python3 is getting an update (and don't forget to chmod 755 the
script before execution):

Code: [Select]

#!/usr/bin/bash

pushd .
sudo apt-get update
mkdir /tmp/hplip
mkdir /tmp/hptmp
cd /tmp/hplip
sudo apt-get install python3 python3.12
apt-get download python3
py3tmp=$(ls /tmp/hplip/*.deb)
py3tmpb=$(ls /tmp/hplip/*.deb|sed -e 's/_amd/b_amd/g')
py3ver=$(ls /tmp/hplip/*.deb|sed -e 's/\/tmp\/hplip\/python3_//g'|sed -e 's/_amd64.deb//g')
py3verb=$(ls /tmp/hplip/*.deb|sed -e 's/\/tmp\/hplip\/python3_//g'|sed -e 's/_amd64.deb/b/g')
dpkg-deb -x $py3tmp /tmp/hptmp
dpkg-deb --control $py3tmp /tmp/hptmp/DEBIAN
sed -i -e 's/python3-profiler/python3 (= 3.12), python3-profiler/g' /tmp/hptmp/DEBIAN/control
sed -i -e 's/Version: '$py3ver'/Version: '$py3verb'/g' /tmp/hptmp/DEBIAN/control
dpkg-deb --root-owner-group -b /tmp/hptmp $py3tmpb
rm $py3tmp
sudo dpkg -i $py3tmpb
cd /tmp
rm -rf /tmp/hptmp /tmp/hplip

sudo apt-get install hplip hplip-data hplip-gui
grep -r '#!/usr/bin/python3' /usr/share/hplip /usr/lib/cups/backend 2>/dev/null|sed -e 's/:#!\/usr\/bin\/python3//g'|xargs -n1 sudo sed -i -e 's/\#\!\/usr\/bin\/python3/\#\!\/usr\/bin\/python3.12/g'
# grep -r '#!/usr/bin/python3' /usr/share/hplip /usr/lib/cups/backend 2>/dev/null|sed -e 's/:#!\/usr\/bin\/python3.12//g'|xargs -n1 sudo sed -i -e 's/\#\!\/usr\/bin\/python3.12/\#\!\/usr\/bin\/python3/g'
/usr/bin/hp-systray -x&
popd



[sidemmc]

Nice! I have fun.

[finotti]

A minor improvement to get rid of the version tracking in case
Python3 is getting an update (and don't forget to chmod 755 the
script before execution):

[snip]

How will this affect future updates?  Will the modified hplip be replaced by the new official version when it is released?  Do we need to remove anything later on or take any special actions in the future?

I've been trying to hold for an official fix, as it makes me worried to hack packages like this (since I am not familiar with how it all works), but it is taking so long...

[Teriarch]

@finotti
 
> [...], as it makes me worried to hack packages like this

To the less experienced the script might look a little scary, but I assure you:
There is nothing to be scared of (That's what they mean, when they say: "Minimally invasive").

> How will this affect future updates?

It won't. If hplip get's an update, so be it. The patched files will be replaced by the new ones (which
hopefully will work this time) and that's it. And the package manager is not aware of the previous
changes, since we patched after the install.

If python3 gets an update before hplip does, hplip will be removed in the process. But you can run
the script again to allow for another life cycle of ancient hplip (as long as python3 remains compatible
with python3.12 nothing happens).

> Will the modified hplip be replaced by the new official version when it is released?

Yes it will. As soon as there is a new release available. Not a single trace will remain.

> Do we need to remove anything later on or take any special actions in the future?

No, we don't. As soon as new releases will be available the old ones will be replaced
and the twilight disappears.

Rest assured that the main concern is always the regular course of events.

[finotti]

Thanks @Teriarch for the clarifications and reassurances.  (And, mostly, for the fix!)  I will try your script tomorrow morning.

[Teriarch]

@finotti

Lest the script get the user executed,
for all the love of Betsy I would suggest you give it
one more try on the life shine-on iso image until
you feel more uncomfortable with it for the final go, ;-)
 

[finotti]

@finotti

Lest the script get the user executed,
for all the love of Betsy I would suggest you give it
one more try on the life shine-on iso image until
you feel more uncomfortable with it for the final go, ;-)

FWIW: I ran the script yesterday, and so far, so good.  Thanks for your help!

[Teriarch]

Perfect! You're welcome.

[Biram]

I’ve run into the same problem before with updates breaking stuff like printers or specific packages I rely on. I had to hold off on upgrading a few things myself to keep my printer working, which is an old HP LaserJet. It’s frustrating, but holding packages back has been a good workaround for now. Hopefully, they’ll fix the dependency issue soon, but I agree—definitely something to watch out for if you’re relying on hplip.

[Teriarch]

@Biram

> , which is an old HP LaserJet.

I've got myself an old HP 2300 Laser Jet with almost 30k pages of output.
It's reliable as hell. These machines are indestructible. But nowadays they
don't build them like this anymore. Anyway, do you know about the advantage
of hplip over cups? My printer is running fine with cups. Is hplip worthwhile
considering?

[seasons]

For those of you who removed hplip, a fixed version is available today.

[debsid]

Just FYI. I am one of those who let hplip go, as the printer on my system had stopped working with my Linux laptop. I installed the fixed hplip a couple of days ago, but have noticed that my HP LaserJet still does not print on my laptop.