Cups and printer conundrums

Hello All, I have an Canon LPB-5050N, old stock obviously as it is discontinued. I have the Canon CAPT software, version 2.30 which includes both RPM's and DEB's. The only problem is that the RPM's are both 32 and 64 bit, but the DEB is only 32 bit and I want to install on a 64 bit Debian system. Add to that the machine is (mostly) airgapped, and my 'net access is dialup. There are instructions in the archive, and I can consider using "alien" on the 64 bit RPM, but I would prefer to do it in a cleaner fashion. I would appreciate any comments. The appropriate two pieces of software have the source in the package, but I am not certain that computer has all the necessary development packages, yet. It is also that the deb scripts will put the appropriate files in the right places, and do a lot of the registering and configuring, which is why I am using Debian for the administration tools. Regards, Mark Trickett

On Sat, Jun 06, 2015 at 09:37:12PM +1000, Mark Trickett wrote:
I have an Canon LPB-5050N, old stock obviously as it is discontinued. I have the Canon CAPT software, version 2.30 which includes both RPM's and DEB's. The only problem is that the RPM's are both 32 and 64 bit, but the DEB is only 32 bit and I want to install on a 64 bit Debian system.
three thoughts come to mind: 1. have you tried just installing the 32-bit .deb package? you would need to add the i386 architecture (with 'dpkg --add-architecture i386') if you haven't already done so. you'd also need to install any i386 libraries and other packages depended upon by the 32-bit .deb (you can apt-get install them once you've added the i386 architecture)
I would appreciate any comments. The appropriate two pieces of software have the source in the package, but I am not certain that computer has all the necessary development packages,
2. check the source for debian build scripts etc. if they are included, look for the Build-Depends: line of the .../debian/control file and apt-get install the packages listed. you should then be able to build a 64-bit .deb 3. try a google search for the full filename of the package in double-quotes and amd64. e.g. '"foo.deb" amd64' - someone may have already gone to the trouble of compiling a 64-bit version and made it available somewhere. as usual when considering third-party packages, use your best judgement as to whether you trust the source of the binary package because by installing the package (and thus running the install scripts, if any) you are effectively giving them root access. unofficial packages by debian developers are likely to be safe. if you want to examine the package without installing it, you can extract the contents of a .deb package (including the pre and post install and rm scripts) into a temporary directory using 'dpkg-deb -x <filename.deb> <dir>' craig -- craig sanders <cas@taz.net.au>

Hello Craig, On Sat, 2015-06-06 at 22:33 +1000, Craig Sanders wrote:
On Sat, Jun 06, 2015 at 09:37:12PM +1000, Mark Trickett wrote:
I have an Canon LPB-5050N, old stock obviously as it is discontinued. I have the Canon CAPT software, version 2.30 which includes both RPM's and DEB's. The only problem is that the RPM's are both 32 and 64 bit, but the DEB is only 32 bit and I want to install on a 64 bit Debian system.
three thoughts come to mind:
1. have you tried just installing the 32-bit .deb package? you would need to add the i386 architecture (with 'dpkg --add-architecture i386') if you haven't already done so. you'd also need to install any i386 libraries and other packages depended upon by the 32-bit .deb (you can apt-get install them once you've added the i386 architecture)
Will need to sort out a 'net connection, even via sneakernet from my other laptop using a 56K analog modem. Your instructions are appreciated.
I would appreciate any comments. The appropriate two pieces of software have the source in the package, but I am not certain that computer has all the necessary development packages,
2. check the source for debian build scripts etc. if they are included, look for the Build-Depends: line of the .../debian/control file and apt-get install the packages listed. you should then be able to build a 64-bit .deb
3. try a google search for the full filename of the package in double-quotes and amd64. e.g. '"foo.deb" amd64' - someone may have already gone to the trouble of compiling a 64-bit version and made it available somewhere. as usual when considering third-party packages, use your best judgement as to whether you trust the source of the binary package because by installing the package (and thus running the install scripts, if any) you are effectively giving them root access.
unofficial packages by debian developers are likely to be safe.
if you want to examine the package without installing it, you can extract the contents of a .deb package (including the pre and post install and rm scripts) into a temporary directory using 'dpkg-deb -x <filename.deb> <dir>'
The package as I have is a .tar.gz with a lot in it, including the manual and there are also some helper programs that might help monitor things like toner levels. Such are not essential, but can be quite convenient. I a trying to look over code, and while each individual bit fits, I cannot assemble a mental structure of what is going on, yet. I do have a helper script from elsewhere, for the prior version, which it appears did have a Debian 64 bit version. If I can email you some details, would you be able to grab and put somewhere where I would be able to use wget to transfer? I am finding that the search engines are a mixed blessing on the dial up connection. When I can locate a resource, some of them do not respond well, and the download manager in FF has a bad "feature" of truncation and no way to resume or tell it that the transfer has more to go.
craig
Regards, Mark Trickett

Mark Trickett wrote:
When I can locate a resource, some of them do not respond well, and the download manager in FF has a bad "feature" of truncation and no way to resume or tell it that the transfer has more to go.
-- I have had this problem on dial-up. I try to solve it by getting the address of the download and using wget. I found it more reliable. And if the download is partial, you can complete it with the -c option rather than beginning again. I now mostly use midori rather that firefox. ben

Hello Ben, On Sun, 2015-06-07 at 18:34 -0700, bnis@fastmail.fm wrote:
Mark Trickett wrote:
When I can locate a resource, some of them do not respond well, and the download manager in FF has a bad "feature" of truncation and no way to resume or tell it that the transfer has more to go.
Had to copy and paste from email reader, your contribution followed two dashes at the start of a line, which Evolution took as the separator before a "SIG" and did not include in the reply.
I have had this problem on dial-up. I try to solve it by getting the address of the download and using wget. I found it more reliable. And if the download is partial, you can complete it with the -c option rather than beginning again. I now mostly use midori rather that firefox.
ben
I have a plugin for FF that will craft a wget command line, and I have used a "naked" wget with the URL and the -c and --no-proxy switches. I have yet to find the proxy on this PC, and have found necessary to bypass. This is how I manage to download my digital copy of Linux Journal, and grab some larger files here and there. I am trying to migrate to a fresh PC, and taking some of my data is not straightforward, I am on several learning curves and finding somewhat steep in conjunction with well past the 20's and a lot of physical work in meat space. Regards, Mark Trickett

On 08.06.15 20:17, Mark Trickett wrote:
Had to copy and paste from email reader, your contribution followed two dashes at the start of a line, which Evolution took as the separator before a "SIG" and did not include in the reply.
It was worse than that; bnis's reply followed a "-- ", i.e. a full kosher sig separator. Camouflaged as a sig, the reply had to be manually exposed here too, even though I use mutt. (t-prot supresses long quotes and sigs.) Erik
participants (4)
-
bnis@fastmail.fm
-
Craig Sanders
-
Erik Christiansen
-
Mark Trickett