Re: CUPS printer problems - #!/bin/bash
On 29.11.2014 22:18, Duncan Patton a Campbell wrote:
On Sat, 29 Nov 2014 00:57:18 +0100
Antoine Jacoutot ajacou...@bsdfrog.org wrote:
Not that I can find, but what you're saying here is what I'm
seeing:
bash _was_ on the system for a short time a while back when it was
needed
to get grolog to run on OBSD64. Afterward it was removed. But
cups-foomatic is going out when it gets installed, and finding
some bashism,
preferentially configures for it. In newer versions of foom* this
becomes an explicitly configurable param.
If that were to be the case, it would have called
/usr/local/bin/bash, not /bin/bash...
I dunno. This thing sets up for /bin/bash iff it finds some kind of
bashism.
/usr/local/bin/bash was left over in shells, but that's not where
it got this from. In the openprinting code it makes reference to
bash as
a preferred shell or something, so I think something in the old
foom*
is finding .bash.history or some other cruft and automagically
selecting
Sorry for interrupting..isn't it this?
$ pwd
/usr/ports/print/cups-filters
$ egrep -ri bash *
Makefile: perl -pi -e 's,/bin/bash,/bin/ksh,g'
${WRKSRC}/filter/textonly
patches/patch-filter_foomatic-rip_foomaticrip_c:-char modern_shell[64]
= /bin/bash;
$
for it.
Dhu
--
Antoine
Re: CUPS printer problems - #!/bin/bash
Sorry for interrupting..isn't it this? We are explicitely patching so that it is *not* it... -- Antoine
Re: CUPS printer problems - #!/bin/bash
On Sat, 29 Nov 2014 00:57:18 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: Not that I can find, but what you're saying here is what I'm seeing: bash _was_ on the system for a short time a while back when it was needed to get grolog to run on OBSD64. Afterward it was removed. But cups-foomatic is going out when it gets installed, and finding some bashism, preferentially configures for it. In newer versions of foom* this becomes an explicitly configurable param. If that were to be the case, it would have called /usr/local/bin/bash, not /bin/bash... I dunno. This thing sets up for /bin/bash iff it finds some kind of bashism. /usr/local/bin/bash was left over in shells, but that's not where it got this from. In the openprinting code it makes reference to bash as a preferred shell or something, so I think something in the old foom* is finding .bash.history or some other cruft and automagically selecting for it. Dhu -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems - #!/bin/bash
On Fri, 28 Nov 2014 17:38:46 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Fri, Nov 28, 2014 at 09:23:41AM -0700, Duncan Patton a Campbell wrote: On Fri, 28 Nov 2014 11:15:26 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: On Thu, Nov 27, 2014 at 03:54:10PM -0700, Duncan Patton a Campbell wrote: On Thu, 27 Nov 2014 15:01:44 -0700 Duncan Patton a Campbell campb...@neotext.ca wrote: The kludge that killz (bugz;): # cd /bin # ln -s sh bash And now my printer works! Yes but the Print Self-Test Page does not. Cups claims it does but foomatic says something else (attached). The Shell sez bash but it's pointing to /bin/sh. The problem could some shell diff between ksh and bash, or something entirely else I don't see how bash ended up in the process... Foomatic was patched to use ksh. You sure you don't have an old foomatic configuration around? I just spotted a misused of bash in cups-filters actually, but it's for the textonly filter, so that does not concern that particular issue. bash has _been_ on the system before, so it must be going out and finding some dead config. I've been doing installs not upgrades on the system and then hooking up the user disks after the fact. Looking in the most recent foomatic code I find statements like 2003-12-21 Till Kamppeter till.kamppe...@gmx.net * Makefile.in: Fixed compatibility for non-bash systems: Used VAR=VALUE; export VAR instead of export VAR=VALUE (Thanks to Florian Diesch die...@spamfence.net). 2006-10-03 Till Kamppeter till.kamppe...@gmail.com * foomatic-rip.in: Fixed bashism. but also Unfortunately, this technique does not work for `CONFIG_SHELL' due to an Autoconf bug. Until the bug is fixed you can use this workaround: CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash Yeah but that has nothing to do with why your foomatic is trying to invoke /bin/bash. You are mixing apples and oranges here. I only used that to point out that there's bashisms thruout the codebase... but I'd guess that somewhere Fruitco is conflating apples and oranges into the round_fruit set (as distinct from long_fruit like bananas and pine cones). If I build foomatic from net sources I get # ./foomatic-rip -v foomatic rip version 4.0.12.246 man foomatic-rip for help. # # pkg_info| grep foom foomatic-db-4.0.20131218 Foomatic PPD data foomatic-db-engine-4.0.11 Foomatic PPD generator but that's NOT what the package installs: # foomatic-rip -v foomatic-rip of cups-filters version 1.0.54 man foomatic-rip for help. This is the version in the /tmp/foomatic*.log files. I just removed the /bin/bash - sh link and got the same log file: foomatic-rip version 1.0.54 running... ... Error: Executing /bin/bash So cups is installing old filtre code imported from foo-1.0.54 but the foo-packages think they're at 4.0.? Something is funky here, and it goes further than my machine. Dhu -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems - #!/bin/bash
I only used that to point out that there's bashisms thruout the codebase... but I'd guess that somewhere Fruitco is conflating apples and oranges into the round_fruit set (as distinct from long_fruit like bananas and pine cones). If I build foomatic from net sources I get What net sources? I am not interested about external non official sources. I am only interested in fixing out packages. The only official net source of foomatic-rip is cups-filters. The one from openprinting is not maintained anymore. $ pkglocate foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/bin/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/libexec/cups/filter/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/man/man1/foomatic-rip.1 Sorry but I will not help with locally compiled external softwares, only with official ports/packages. -- Antoine
Re: CUPS printer problems - #!/bin/bash
On Fri, 28 Nov 2014 19:34:35 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: I only used that to point out that there's bashisms thruout the codebase... but I'd guess that somewhere Fruitco is conflating apples and oranges into the round_fruit set (as distinct from long_fruit like bananas and pine cones). If I build foomatic from net sources I get What net sources? I am not interested about external non official sources. I am only interested in fixing out packages. The only official net source of foomatic-rip is cups-filters. The one from openprinting is not maintained anymore. I'm not running that code. As I pointed out the official openbsd foomatic packages are NAME/NUMBERED like like the openprinting version 4.012, but inside they are something else branched from a much older version: version 1.1 is from circa 2002. This is version 1.0.54 # which foomatic-rip /usr/local/bin/foomatic-rip l /usr/local/bin/foomatic-rip lrwxr-xr-x 1 root wheel 43 Nov 26 11:44 /usr/local/bin/foomatic-rip - /usr/local/libexec/cups/filter/foomatic-rip # l /usr/local/libexec/cups/filter/foomatic-rip -r-xr-xr-x 1 root bin 108536 Jul 31 07:06 /usr/local/libexec/cups/filter/foomatic-rip /usr/local/bin/foomatic-rip -v foomatic-rip of cups-filters version 1.0.54 man foomatic-rip for help. The code from openprinting returns foomatic rip version 4.0.12.246 $ pkglocate foomatic-rip that's netbsd. are these packages xcompiled? cups-filters-1.0.61p1:print/cups-filters:/usr/local/bin/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/libexec/cups/filter/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/man/man1/foomatic-rip.1 Sorry but I will not help with locally compiled external softwares, only with official ports/packages. It's the Official port/package that is CALLING BASH. # pkg_info | grep cups cups-1.7.4p2Common Unix Printing System cups-filters-1.0.54p2 OpenPrinting CUPS filters cups-libs-1.7.4 CUPS libraries and headers # pkg_info | grep foom foomatic-db-4.0.20131218 Foomatic PPD data foomatic-db-engine-4.0.11 Foomatic PPD generator Dhu -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems - #!/bin/bash
I'm not running that code. As I pointed out the official openbsd foomatic packages are NAME/NUMBERED like like the openprinting version 4.012, but inside they are something else branched from a much older version: version 1.1 is from circa 2002. This is version 1.0.54 # which foomatic-rip /usr/local/bin/foomatic-rip l /usr/local/bin/foomatic-rip lrwxr-xr-x 1 root wheel 43 Nov 26 11:44 /usr/local/bin/foomatic-rip - /usr/local/libexec/cups/filter/foomatic-rip # l /usr/local/libexec/cups/filter/foomatic-rip -r-xr-xr-x 1 root bin 108536 Jul 31 07:06 /usr/local/libexec/cups/filter/foomatic-rip /usr/local/bin/foomatic-rip -v foomatic-rip of cups-filters version 1.0.54 man foomatic-rip for help. The code from openprinting returns foomatic rip version 4.0.12.246 How is that relevant to the bash issue; you confuse me... did I miss something? $ pkglocate foomatic-rip that's netbsd. are these packages xcompiled? What do you mean that's netbsd? And what do you mean by xcompiled? cups-filters-1.0.61p1:print/cups-filters:/usr/local/bin/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/libexec/cups/filter/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/man/man1/foomatic-rip.1 Sorry but I will not help with locally compiled external softwares, only with official ports/packages. It's the Official port/package that is CALLING BASH. Nowhere in the installed cups-filters code I can see it calling bash... Just grep for it yourself and you'll see. So there must be something specific on your system. Did you make sure you don't have an old config laying around? -- Antoine
Re: CUPS printer problems - #!/bin/bash
On Sat, 29 Nov 2014 00:34:17 +0100 Antoine Jacoutot ajacou...@bsdfrog.org wrote: I'm not running that code. As I pointed out the official openbsd foomatic packages are NAME/NUMBERED like like the openprinting version 4.012, but inside they are something else branched from a much older version: version 1.1 is from circa 2002. This is version 1.0.54 # which foomatic-rip /usr/local/bin/foomatic-rip l /usr/local/bin/foomatic-rip lrwxr-xr-x 1 root wheel 43 Nov 26 11:44 /usr/local/bin/foomatic-rip - /usr/local/libexec/cups/filter/foomatic-rip # l /usr/local/libexec/cups/filter/foomatic-rip -r-xr-xr-x 1 root bin 108536 Jul 31 07:06 /usr/local/libexec/cups/filter/foomatic-rip /usr/local/bin/foomatic-rip -v foomatic-rip of cups-filters version 1.0.54 man foomatic-rip for help. The code from openprinting returns foomatic rip version 4.0.12.246 How is that relevant to the bash issue; you confuse me... did I miss something? $ pkglocate foomatic-rip that's netbsd. are these packages xcompiled? What do you mean that's netbsd? And what do you mean by xcompiled? pkglocate is a netbsd utility. I didn't know it had been ported. xcompiled == cross-compiled. cups-filters-1.0.61p1:print/cups-filters:/usr/local/bin/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/libexec/cups/filter/foomatic-rip cups-filters-1.0.61p1:print/cups-filters:/usr/local/man/man1/foomatic-rip.1 Sorry but I will not help with locally compiled external softwares, only with official ports/packages. It's the Official port/package that is CALLING BASH. Nowhere in the installed cups-filters code I can see it calling bash... Just grep for it yourself and you'll see. So there must be something specific on your system. Did you make sure you don't have an old config laying around? Not that I can find, but what you're saying here is what I'm seeing: bash _was_ on the system for a short time a while back when it was needed to get grolog to run on OBSD64. Afterward it was removed. But cups-foomatic is going out when it gets installed, and finding some bashism, preferentially configures for it. In newer versions of foom* this becomes an explicitly configurable param. Dhu -- Antoine -- Ne obliviscaris, vix ea nostra voco.
Re: CUPS printer problems - #!/bin/bash
Not that I can find, but what you're saying here is what I'm seeing: bash _was_ on the system for a short time a while back when it was needed to get grolog to run on OBSD64. Afterward it was removed. But cups-foomatic is going out when it gets installed, and finding some bashism, preferentially configures for it. In newer versions of foom* this becomes an explicitly configurable param. If that were to be the case, it would have called /usr/local/bin/bash, not /bin/bash... -- Antoine
