squid-deb-proxy is a python2 script
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
squid-deb-proxy (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bionic |
Invalid
|
Low
|
Unassigned |
Bug Description
[ IMPACT ]
squid-deb-proxy is a python2 script. I suggest to change the shebang to /usr/bin/python2 to reflect this. The script crashes for users who have made python3 the default in bionic. Anyone with python as python2 is fine (the default), but someone who likes to stay in bionic LTS yet program in python3 this results in an avoidable and easily fixable problem.
[ TEST CASE ]
Compare "python2 /usr/share/
[ REGRESSION POTENTIAL ]
There should not be (m)any. It just makes the implicit assumption that the script runs via python2 explicit.
The only time there could potentially be an issue is if python2 has been explicitly removed AND python pointed to python3. I have a hard time thinking why somebody would do that and such a setup would certainly break in a number of other situations.
Changed in squid-deb-proxy (Ubuntu): | |
status: | Expired → New |
Changed in squid-deb-proxy (Ubuntu): | |
importance: | Undecided → Low |
Changed in squid-deb-proxy (Ubuntu Bionic): | |
importance: | Undecided → Low |
Changed in squid-deb-proxy (Ubuntu): | |
status: | Confirmed → Fix Released |
description: | updated |
description: | updated |
Changed in squid-deb-proxy (Ubuntu Bionic): | |
status: | New → Incomplete |
status: | Incomplete → Opinion |
status: | Opinion → Invalid |
Which script do you mean, exactly? And on which ubuntu release?
/usr/share/ squid-deb- proxy-client/ apt-avahi- discover perhaps?