During the installation I got :
/var/tmp/pamac-build-yoda/python2/PKGBUILD: line 40: patch: command not found
==> ERROR: A failure occurred in prepare().
Aborting…
The complete text is :
Building python2…
==> Making package: python2 2.7.18-8 (Thu 26 Oct 2023 09:21:55 PM EDT)
==> Checking runtime dependencies…
==> Checking buildtime dependencies…
==> Retrieving sources…
→ Found Python-2.7.18.tar.xz
→ Found Python-2.7.18.tar.xz.asc
→ Found mtime-workaround.patch
→ Found python-gentoo-patches-2.7.18_p16.tar.xz
==> Validating source files with sha512sums…
Python-2.7.18.tar.xz … Passed
Python-2.7.18.tar.xz.asc … Skipped
mtime-workaround.patch … Passed
python-gentoo-patches-2.7.18_p16.tar.xz … Passed
==> Verifying source file signatures with gpg…
Python-2.7.18.tar.xz … Passed
==> Removing existing $srcdir/ directory…
==> Extracting sources…
→ Extracting Python-2.7.18.tar.xz with bsdtar
==> Starting prepare()…
bsdtar: Removing leading ‘/’ from member names
/var/tmp/pamac-build-yoda/python2/PKGBUILD: line 40: patch: command not found
==> ERROR: A failure occurred in prepare().
Aborting…
I am more used to Debian and I don’t have the knowledge to DEBUG that.
Yes I did uninstall and also had to kill some CUPS processed that were stucked and making my Desktop Fan go Crazy LOL
Tks for the 5.80 link !! I found something about that on a Chinese site but though I needed some Arch version of that… I lack some knowledge about CUPS and arch and what I can use “as is” from the Debian and/or manufacturer… will make some reading…
Opinion:- It’s unfortunate that Canon themselves don’t seem particularly interested in supporting Linux. From memory, there are a few aging (and useless) drivers for Debian, and nothing more.
I would love to help the next person to solve the problem but I tried " so many things".
The solution, that I tried 1st and it didn’t worked, now seem to have worked…
I must have did something for it to work but I’ll go with :
I didn’t download the package. Considering it was marked as the solution in the thread indicated (same printer), then it’s likely the one. Look under x64; though the install.sh script is probably smart enough to select the correct driver needed. Under Documents I’m guessing will be more useful information.
You might just as well stick with the current solution, if its working as expected. The option remains linked here for others to try if they wish to.