It was an adventure, but I finally made a new foomatic-rip. It works!! Along the way, I picked up: rreitz@sheevaplug:~/cups-filters-1.0.43$ dpkg -l cups-filters Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================-===============-===============-=============================================== ii cups-filters 1.0.44-2 armel OpenPrinting CUPS Filters - Main Package
which does not work, but I guess you know that. I look forward to 1.0.44-3. Thanks, Randy On Feb 11, 2014, at 2:45 AM, Didier 'OdyX' Raboud <o...@debian.org> wrote: > Le lundi, 10 février 2014, 23.34:23 Till Kamppeter a écrit : >> I have fixed the problem upstream (BZR rev. 7159) now. I do not use >> PATH+MAX any more for strings which are used to hold a command line. >> Command lines have 65535 bytes now. >> >> Please test and tell whether it solves the problem. If so, I will >> release a new cups-filters version. > > At least it doesn't cause obvious regressions for me. > > Till: if you release a new version, can you include your fix for the > upstart job? > > Randy: can you recompile cups-filters on your platform with the attached > patch and confirm that it works? > > Cheers, > OdyX<foomatic-rip_Do_not_use_PATH_MAX_for_the_length_of_strings_which_are_supposed_to_hold_a_command_line.patch>