Menu
▾
▴
gimp-print-devel
|
From: Steve L. <sle...@ya...> - 2019-07-25 01:41:13
|
I have replaced the file with a new build. The long name you mention is because it is embedded in the configure script. I could hand edit it. Everything is there now I believe. I have the backend installed (gutenprint53+usb) and have fixed the generation of PPD's (-x). Here is the link to download the latest I have built.
Gutenprint - Top Quality Printer Drivers Brought to you by: easysw,
|
|
| |
Gutenprint - Top Quality Printer Drivers ...
Your download will start shortly...
|
|
|
Steve Letter You're never to old to learn something stupid. -- unknown
On Monday, July 22, 2019, 1:52:13 PM EDT, Matthew Broughton <mab...@fa...> wrote:
On Jul 15, 2019, at 9:05 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
All, I still don't have 100% confidence, I know I still have parts of the build to look at. (libgutenprint.9.dylib for example) However, I was able to print with the build I put up here:
gutenprint-5.3.2-pre1.dmg
|
|
| |
Gutenprint - Top Quality Printer Drivers ...
Your download will start shortly... |
|
|
My printer is technically not a supported printer so I need more folks to test that it is operating properly. In tech terms, my build is still a bit wonky.
Steve Letter
I will confirm that I, too, was able to print with the gutenprint-5.3.2-pre1.dmg. I still want to look at a CUPS error log to see if there is any that stands out there.
I did find a fault with the installer. I will not update existing PPDs. The installer log says:
Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Updating Gutenprint printer queues...Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x!Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Did not update any PPD filesJul 22 10:54:51 Borodin installd[1116]: PackageKit: Writing receipt for org.gutenprint.printer-driver to /
*****************I added a new printer using Printers & Scanners. The driver for Gutenprint was very strange:
"5.3.2-pre1-2019-06-16T01-00-e55733ff"
After I added the new printer, I ran the cups-genppdupdate manually using `sudo`. It was able to update the new printer but still could not handle the old 5.2.14.x PPD
matt$ sudo /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/cups-genppdupdate Password:Updated /private/etc/cups/ppd/WF1100_53_1.ppd using gutenprint.5.3://escp2-wf1100/expertSkipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x!Updated 1 PPD file, 11 skipped. Restart cupsd for the changes to take effect.
I have never encountered `-x!`
Matt
|
|
From: Robert K. <rl...@al...> - 2019-07-22 17:54:48
|
On Mon, 22 Jul 2019 12:52:09 -0500, Matthew Broughton wrote: >> On Jul 15, 2019, at 9:05 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >> >> All, I still don't have 100% confidence, I know I still have parts of the build to look at. (libgutenprint.9.dylib for example) However, I was able to print with the build I put up here: >> >> gutenprint-5.3.2-pre1.dmg <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download> >> >> Gutenprint - Top Quality Printer Drivers ... >> Your download will start shortly... >> <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download> >> >> My printer is technically not a supported printer so I need more folks to test that it is operating properly. In tech terms, my build is still a bit wonky. >> >> Steve Letter > > I will confirm that I, too, was able to print with the gutenprint-5.3.2-pre1.dmg. I still want to look at a CUPS error log to see if there is any that stands out there. > > I did find a fault with the installer. I will not update existing PPDs. The installer log says: > > Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Updating Gutenprint printer queues... > Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x! > Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Did not update any PPD files > Jul 22 10:54:51 Borodin installd[1116]: PackageKit: Writing receipt for org.gutenprint.printer-driver to / > > > ***************** > I added a new printer using Printers & Scanners. The driver for Gutenprint was very strange: > > "5.3.2-pre1-2019-06-16T01-00-e55733ff" > > After I added the new printer, I ran the cups-genppdupdate manually using `sudo`. It was able to update the new printer but still could not handle the old 5.2.14.x PPD > > matt$ sudo /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/cups-genppdupdate > Password: > Updated /private/etc/cups/ppd/WF1100_53_1.ppd using gutenprint.5.3://escp2-wf1100/expert > Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x! > Updated 1 PPD file, 11 skipped. Restart cupsd for the changes to take effect. > > I have never encountered `-x!` This was discussed a while back. This is to allow people to continue to run 5.3 alongside 5.2. It doesn't matter for the Mac, so you should always use -x. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Matthew B. <mab...@fa...> - 2019-07-22 18:06:08
|
> On Jul 22, 2019, at 12:54 PM, Robert Krawitz <rl...@al...> wrote: > > On Mon, 22 Jul 2019 12:52:09 -0500, Matthew Broughton wrote: >>> On Jul 15, 2019, at 9:05 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>> >>> All, I still don't have 100% confidence, I know I still have parts of the build to look at. (libgutenprint.9.dylib for example) However, I was able to print with the build I put up here: >>> >>> gutenprint-5.3.2-pre1.dmg <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download> >>> >>> Gutenprint - Top Quality Printer Drivers ... >>> Your download will start shortly... >>> <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download> >>> >>> My printer is technically not a supported printer so I need more folks to test that it is operating properly. In tech terms, my build is still a bit wonky. >>> >>> Steve Letter >> >> I will confirm that I, too, was able to print with the gutenprint-5.3.2-pre1.dmg. I still want to look at a CUPS error log to see if there is any that stands out there. >> >> I did find a fault with the installer. I will not update existing PPDs. The installer log says: >> >> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Updating Gutenprint printer queues... >> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x! >> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Did not update any PPD files >> Jul 22 10:54:51 Borodin installd[1116]: PackageKit: Writing receipt for org.gutenprint.printer-driver to / >> >> >> ***************** >> I added a new printer using Printers & Scanners. The driver for Gutenprint was very strange: >> >> "5.3.2-pre1-2019-06-16T01-00-e55733ff" >> >> After I added the new printer, I ran the cups-genppdupdate manually using `sudo`. It was able to update the new printer but still could not handle the old 5.2.14.x PPD >> >> matt$ sudo /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/cups-genppdupdate >> Password: >> Updated /private/etc/cups/ppd/WF1100_53_1.ppd using gutenprint.5.3://escp2-wf1100/expert >> Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x! >> Updated 1 PPD file, 11 skipped. Restart cupsd for the changes to take effect. >> >> I have never encountered `-x!` > > This was discussed a while back. This is to allow people to continue > to run 5.3 alongside 5.2. It doesn't matter for the Mac, so you > should always use -x. > -- > Robert Krawitz <rl...@al...> I do remember part of that discussion. I just used `cups-genppdupdate -x` manually and everything is fine. It would seem that this would be a simple fix for the Mac installer. Just use `cups-genppdupdate -x` in the post install script. I will leave the implementation to you and Steve. Matt |
|
From: Matt B. <wal...@ma...> - 2019-07-22 19:05:53
|
<html><head></head><body dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 22, 2019, at 1:05 PM, Matthew Broughton <<a href="mailto:mab...@fa..." class="">mab...@fa...</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">On Jul 22, 2019, at 12:54 PM, Robert Krawitz <<a href="mailto:rl...@al..." class="">rl...@al...</a>> wrote:<br class=""><br class="">On Mon, 22 Jul 2019 12:52:09 -0500, Matthew Broughton wrote:<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">On Jul 15, 2019, at 9:05 PM, Steve Letter via Gimp-print-devel <<a href="mailto:gim...@li..." class="">gim...@li...</a>> wrote:<br class=""><br class="">All, I still don't have 100% confidence, I know I still have parts of the build to look at. (libgutenprint.9.dylib for example) However, I was able to print with the build I put up here:<br class=""><br class=""> gutenprint-5.3.2-pre1.dmg <<a href="https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download" class="">https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download</a>><br class=""><br class="">Gutenprint - Top Quality Printer Drivers ...<br class="">Your download will start shortly...<br class=""><<a href="https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download" class="">https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download</a>><br class=""><br class="">My printer is technically not a supported printer so I need more folks to test that it is operating properly. In tech terms, my build is still a bit wonky.<br class=""><br class="">Steve Letter<span class="Apple-converted-space"> </span><br class=""></blockquote><br class="">I will confirm that I, too, was able to print with the gutenprint-5.3.2-pre1.dmg. I still want to look at a CUPS error log to see if there is any that stands out there.<br class=""><br class="">I did find a fault with the installer. I will not update existing PPDs. The installer log says:<br class=""><br class="">Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Updating Gutenprint printer queues...<br class="">Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x!<br class="">Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Did not update any PPD files<br class="">Jul 22 10:54:51 Borodin installd[1116]: PackageKit: Writing receipt for org.gutenprint.printer-driver to /<br class=""><br class=""><br class="">*****************<br class="">I added a new printer using Printers & Scanners. The driver for Gutenprint was very strange:<br class=""><br class="">"5.3.2-pre1-2019-06-16T01-00-e55733ff"<br class=""><br class="">After I added the new printer, I ran the cups-genppdupdate manually using `sudo`. It was able to update the new printer but still could not handle the old 5.2.14.x PPD<br class=""><br class="">matt$ sudo /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/cups-genppdupdate<span class="Apple-converted-space"> </span><br class="">Password:<br class="">Updated /private/etc/cups/ppd/WF1100_53_1.ppd using <a href="gutenprint.5.3://escp2-wf1100/expert" class="">gutenprint.5.3://escp2-wf1100/expert</a><br class="">Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x!<br class="">Updated 1 PPD file, 11 skipped. Restart cupsd for the changes to take effect.<br class=""><br class="">I have never encountered `-x!`<br class=""></blockquote><br class="">This was discussed a while back. This is to allow people to continue<br class="">to run 5.3 alongside 5.2. It doesn't matter for the Mac, so you<br class="">should always use -x.<br class="">--<span class="Apple-converted-space"> </span><br class="">Robert Krawitz <<a href="mailto:rl...@al..." class="">rl...@al...</a>><br class=""></blockquote><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">I do remember part of that discussion. I just used `cups-genppdupdate -x` manually and everything is fine. It would seem that this would be a simple fix for the Mac installer. Just use `cups-genppdupdate -x` in the post install script. I will leave the implementation to you and Steve.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Matt</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""></div></blockquote><br class=""></div><div>That still leaves the problem (?) of the PPD File version "5.3.2-pre1-2019-06-16T01-00-e55733ff"</div><div><br class=""></div><div><br class=""></div><div class=""><br class="Apple-interchange-newline"> </div> <br class=""></div></body></html> |
|
From: Matt B. <wal...@ma...> - 2019-07-22 21:54:02
|
> On Jul 22, 2019, at 1:21 PM, Matt Broughton <wal...@ma...> wrote: > > > >> On Jul 22, 2019, at 1:05 PM, Matthew Broughton <mab...@fa... <mailto:mab...@fa...>> wrote: >> >> >> >>> On Jul 22, 2019, at 12:54 PM, Robert Krawitz <rl...@al... <mailto:rl...@al...>> wrote: >>> >>> On Mon, 22 Jul 2019 12:52:09 -0500, Matthew Broughton wrote: >>>>> On Jul 15, 2019, at 9:05 PM, Steve Letter via Gimp-print-devel <gim...@li... <mailto:gim...@li...>> wrote: >>>>> >>>>> All, I still don't have 100% confidence, I know I still have parts of the build to look at. (libgutenprint.9.dylib for example) However, I was able to print with the build I put up here: >>>>> >>>>> gutenprint-5.3.2-pre1.dmg <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download>> >>>>> >>>>> Gutenprint - Top Quality Printer Drivers ... >>>>> Your download will start shortly... >>>>> <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download>> >>>>> >>>>> My printer is technically not a supported printer so I need more folks to test that it is operating properly. In tech terms, my build is still a bit wonky. >>>>> >>>>> Steve Letter >>>> >>>> I will confirm that I, too, was able to print with the gutenprint-5.3.2-pre1.dmg. I still want to look at a CUPS error log to see if there is any that stands out there. >>>> >>>> I did find a fault with the installer. I will not update existing PPDs. The installer log says: >>>> >>>> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Updating Gutenprint printer queues... >>>> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x! >>>> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Did not update any PPD files >>>> Jul 22 10:54:51 Borodin installd[1116]: PackageKit: Writing receipt for org.gutenprint.printer-driver to / >>>> >>>> >>>> ***************** >>>> I added a new printer using Printers & Scanners. The driver for Gutenprint was very strange: >>>> >>>> "5.3.2-pre1-2019-06-16T01-00-e55733ff" >>>> >>>> After I added the new printer, I ran the cups-genppdupdate manually using `sudo`. It was able to update the new printer but still could not handle the old 5.2.14.x PPD >>>> >>>> matt$ sudo /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/cups-genppdupdate >>>> Password: >>>> Updated /private/etc/cups/ppd/WF1100_53_1.ppd using gutenprint.5.3://escp2-wf1100/expert <gutenprint.5.3://escp2-wf1100/expert> >>>> Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x! >>>> Updated 1 PPD file, 11 skipped. Restart cupsd for the changes to take effect. >>>> >>>> I have never encountered `-x!` >>> >>> This was discussed a while back. This is to allow people to continue >>> to run 5.3 alongside 5.2. It doesn't matter for the Mac, so you >>> should always use -x. >>> -- >>> Robert Krawitz <rl...@al... <mailto:rl...@al...>> >> >> I do remember part of that discussion. I just used `cups-genppdupdate -x` manually and everything is fine. It would seem that this would be a simple fix for the Mac installer. Just use `cups-genppdupdate -x` in the post install script. I will leave the implementation to you and Steve. >> >> Matt >> > > That still leaves the problem (?) of the PPD File version "5.3.2-pre1-2019-06-16T01-00-e55733ff" Oops. I forgot to check the backend. The gutenprint53+usb backend is not there. That's a killer for this package. Matt |
|
From: Steve L. <sle...@ya...> - 2019-07-25 00:56:41
|
Fixed. Looking at the other issues. Will post a build soon I think. Steve Letter > On Jul 22, 2019, at 5:53 PM, Matt Broughton <wal...@ma...> wrote: > > > >>> On Jul 22, 2019, at 1:21 PM, Matt Broughton <wal...@ma...> wrote: >>> >>> >>> >>>> On Jul 22, 2019, at 1:05 PM, Matthew Broughton <mab...@fa...> wrote: >>>> >>>> >>>> >>>> On Jul 22, 2019, at 12:54 PM, Robert Krawitz <rl...@al...> wrote: >>>> >>>> On Mon, 22 Jul 2019 12:52:09 -0500, Matthew Broughton wrote: >>>>>> On Jul 15, 2019, at 9:05 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>>>>> >>>>>> All, I still don't have 100% confidence, I know I still have parts of the build to look at. (libgutenprint.9.dylib for example) However, I was able to print with the build I put up here: >>>>>> >>>>>> gutenprint-5.3.2-pre1.dmg <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download> >>>>>> >>>>>> Gutenprint - Top Quality Printer Drivers ... >>>>>> Your download will start shortly... >>>>>> <https://sourceforge.net/projects/gimp-print/files/snapshots/gutenprint-5.3.2-pre1.dmg/download> >>>>>> >>>>>> My printer is technically not a supported printer so I need more folks to test that it is operating properly. In tech terms, my build is still a bit wonky. >>>>>> >>>>>> Steve Letter >>>>> >>>>> I will confirm that I, too, was able to print with the gutenprint-5.3.2-pre1.dmg. I still want to look at a CUPS error log to see if there is any that stands out there. >>>>> >>>>> I did find a fault with the installer. I will not update existing PPDs. The installer log says: >>>>> >>>>> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Updating Gutenprint printer queues... >>>>> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x! >>>>> Jul 22 10:54:51 Borodin installd[1116]: ./postinstall: Did not update any PPD files >>>>> Jul 22 10:54:51 Borodin installd[1116]: PackageKit: Writing receipt for org.gutenprint.printer-driver to / >>>>> >>>>> >>>>> ***************** >>>>> I added a new printer using Printers & Scanners. The driver for Gutenprint was very strange: >>>>> >>>>> "5.3.2-pre1-2019-06-16T01-00-e55733ff" >>>>> >>>>> After I added the new printer, I ran the cups-genppdupdate manually using `sudo`. It was able to update the new printer but still could not handle the old 5.2.14.x PPD >>>>> >>>>> matt$ sudo /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/cups-genppdupdate >>>>> Password: >>>>> Updated /private/etc/cups/ppd/WF1100_53_1.ppd using gutenprint.5.3://escp2-wf1100/expert >>>>> Skipping /private/etc/cups/ppd/WorkForce_1100_GP.ppd: mismatched file versions (old 5.2, new 5.3); will not update without -x! >>>>> Updated 1 PPD file, 11 skipped. Restart cupsd for the changes to take effect. >>>>> >>>>> I have never encountered `-x!` >>>> >>>> This was discussed a while back. This is to allow people to continue >>>> to run 5.3 alongside 5.2. It doesn't matter for the Mac, so you >>>> should always use -x. >>>> -- >>>> Robert Krawitz <rl...@al...> >>> >>> I do remember part of that discussion. I just used `cups-genppdupdate -x` manually and everything is fine. It would seem that this would be a simple fix for the Mac installer. Just use `cups-genppdupdate -x` in the post install script. I will leave the implementation to you and Steve. >>> >>> Matt >>> >> >> That still leaves the problem (?) of the PPD File version "5.3.2-pre1-2019-06-16T01-00-e55733ff" > > Oops. I forgot to check the backend. The gutenprint53+usb backend is not there. That's a killer for this package. > > Matt > > > > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
|
From: Robert K. <rl...@al...> - 2019-07-25 01:47:23
|
On Thu, 25 Jul 2019 01:41:03 +0000 (UTC), Steve Letter wrote: > I have replaced the file with a new build. The long name you > mention is because it is embedded in the configure script. I could > hand edit it. Everything is there now I believe. I have the > backend installed (gutenprint53+usb) and have fixed the generation > of PPD's (-x). Here is the link to download the latest I have built. You're referring to "5.3.2-pre1-2019-06-16T01-00-e55733ff"? That would be a snapshot build; the standard builds should not have all that extra. If it does, then I did something wrong. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Matthew B. <mab...@fa...> - 2019-07-27 02:20:59
|
> On Jul 24, 2019, at 8:47 PM, Robert Krawitz <rl...@al...> wrote: > > On Thu, 25 Jul 2019 01:41:03 +0000 (UTC), Steve Letter wrote: >> I have replaced the file with a new build. The long name you >> mention is because it is embedded in the configure script. I could >> hand edit it. Everything is there now I believe. I have the >> backend installed (gutenprint53+usb) and have fixed the generation >> of PPD's (-x). Here is the link to download the latest I have built. > > You're referring to "5.3.2-pre1-2019-06-16T01-00-e55733ff"? That > would be a snapshot build; the standard builds should not have all > that extra. If it does, then I did something wrong. I will have to be more circumspect in the future and just say I noticed this and ask if this is this correct. The current iteration as of July 26th seems to test out fine. The back end is in the package. I think the preinstall script may need to be changed a bit. It looks like there are some tidbits -- probably only symlinks -- not being removed. I also found that the Uninstaller needs updating to work with 5.3.x My guess at this point is that the preinstall script has some similar problems. This shouldn't effect the functioning of the package, but the issues should be cleaned up before a full 5.3.x release. Matt |
|
From: Solomon P. <pi...@sh...> - 2019-07-27 12:02:44
Attachments:
signature.asc
|
On Fri, Jul 26, 2019 at 09:20:49PM -0500, Matthew Broughton wrote: > I will have to be more circumspect in the future and just say I > noticed this and ask if this is this correct. Probably wise. > The current iteration as of July 26th seems to test out fine. The > back end is in the package. Yesterday I got a report of a successful printing with a Sony UP-CR10L using the /snapshots/gutenprint-5.3.2-pre1.dmg image. In other news -- one of my clients wants me to do some OSX airprint-related debug and is sending me an older Mac Mini. So I should soon be able to test, and eventually build, Gutenprint OSX's packages. - Solomon -- Solomon Peachy pizza at shaftnet dot org High Springs, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum videtur. |
|
From: Steve L. <sle...@ya...> - 2019-07-27 20:59:16
|
Great! If I can help let me know. Steve Letter > On Jul 27, 2019, at 8:02 AM, Solomon Peachy <pi...@sh...> wrote: > >> On Fri, Jul 26, 2019 at 09:20:49PM -0500, Matthew Broughton wrote: >> I will have to be more circumspect in the future and just say I >> noticed this and ask if this is this correct. > > Probably wise. > >> The current iteration as of July 26th seems to test out fine. The >> back end is in the package. > > Yesterday I got a report of a successful printing with a Sony > UP-CR10L using the /snapshots/gutenprint-5.3.2-pre1.dmg image. > > In other news -- one of my clients wants me to do some OSX > airprint-related debug and is sending me an older Mac Mini. So I should > soon be able to test, and eventually build, Gutenprint OSX's packages. > > - Solomon > -- > Solomon Peachy pizza at shaftnet dot org > High Springs, FL ^^ (email/xmpp) ^^ > Quidquid latine dictum sit, altum videtur. > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
|
From: Robert K. <rl...@al...> - 2019-07-27 15:04:53
|
On Fri, 26 Jul 2019 21:20:49 -0500, Matthew Broughton wrote: > > >> On Jul 24, 2019, at 8:47 PM, Robert Krawitz <rl...@al...> wrote: >> >> On Thu, 25 Jul 2019 01:41:03 +0000 (UTC), Steve Letter wrote: >>> I have replaced the file with a new build. The long name you >>> mention is because it is embedded in the configure script. I could >>> hand edit it. Everything is there now I believe. I have the >>> backend installed (gutenprint53+usb) and have fixed the generation >>> of PPD's (-x). Here is the link to download the latest I have built. >> >> You're referring to "5.3.2-pre1-2019-06-16T01-00-e55733ff"? That >> would be a snapshot build; the standard builds should not have all >> that extra. If it does, then I did something wrong. > > I will have to be more circumspect in the future and just say I > noticed this and ask if this is this correct. No problem, it was definitely worth bringing it up. > The current iteration as of July 26th seems to test out fine. The > back end is in the package. I think the preinstall script may need > to be changed a bit. It looks like there are some tidbits -- > probably only symlinks -- not being removed. I also found that the > Uninstaller needs updating to work with 5.3.x My guess at this point > is that the preinstall script has some similar problems. This > shouldn't effect the functioning of the package, but the issues > should be cleaned up before a full 5.3.x release. Sounds like excellent progress, thanks Steve and Matt! Once we have all of that squared away, I'll plan on releasing a 5.3.3. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Steve L. <sle...@ya...> - 2019-07-27 21:03:35
|
I’d like to build something current first. Give me a few more days and let me see what I can do. Matt, did you want me to update your uninstall or would you rather do it? Steve Letter > On Jul 27, 2019, at 11:04 AM, Robert Krawitz <rl...@al...> wrote: > >> On Fri, 26 Jul 2019 21:20:49 -0500, Matthew Broughton wrote: >> >> >>> On Jul 24, 2019, at 8:47 PM, Robert Krawitz <rl...@al...> wrote: >>> >>> On Thu, 25 Jul 2019 01:41:03 +0000 (UTC), Steve Letter wrote: >>>> I have replaced the file with a new build. The long name you >>>> mention is because it is embedded in the configure script. I could >>>> hand edit it. Everything is there now I believe. I have the >>>> backend installed (gutenprint53+usb) and have fixed the generation >>>> of PPD's (-x). Here is the link to download the latest I have built. >>> >>> You're referring to "5.3.2-pre1-2019-06-16T01-00-e55733ff"? That >>> would be a snapshot build; the standard builds should not have all >>> that extra. If it does, then I did something wrong. >> >> I will have to be more circumspect in the future and just say I >> noticed this and ask if this is this correct. > > No problem, it was definitely worth bringing it up. > >> The current iteration as of July 26th seems to test out fine. The >> back end is in the package. I think the preinstall script may need >> to be changed a bit. It looks like there are some tidbits -- >> probably only symlinks -- not being removed. I also found that the >> Uninstaller needs updating to work with 5.3.x My guess at this point >> is that the preinstall script has some similar problems. This >> shouldn't effect the functioning of the package, but the issues >> should be cleaned up before a full 5.3.x release. > > Sounds like excellent progress, thanks Steve and Matt! Once we have > all of that squared away, I'll plan on releasing a 5.3.3. > -- > Robert Krawitz <rl...@al...> > > *** MIT Engineers A Proud Tradition http://mitathletics.com *** > Member of the League for Programming Freedom -- http://ProgFree.org > Project lead for Gutenprint -- http://gimp-print.sourceforge.net > > "Linux doesn't dictate how I work, I dictate how Linux works." > --Eric Crampton |
|
From: Robert K. <rl...@al...> - 2019-07-27 22:22:13
|
On Sat, 27 Jul 2019 17:03:20 -0400, Steve Letter wrote: > I'd like to build something current first. Give me a few more days > and let me see what I can do. Of course. > Matt, did you want me to update your uninstall or would you rather do it? -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Matthew B. <mab...@fa...> - 2019-07-28 00:41:29
|
> On Jul 27, 2019, at 4:03 PM, Steve Letter <sle...@ya...> wrote: > > I’d like to build something current first. Give me a few more days and let me see what I can do. > > Matt, did you want me to update your uninstall or would you rather do it? > > Steve Letter I've made the necessary changes to the uninstaller and tested it. I'll send it to you after I check the preinstall script. There was a lot in there that was the same as the uninstaller. Matt |
|
From: Matthew B. <mab...@fa...> - 2019-07-28 00:49:33
|
> On Jul 27, 2019, at 7:41 PM, Matthew Broughton <mab...@fa...> wrote: > > > >> On Jul 27, 2019, at 4:03 PM, Steve Letter <sle...@ya... <mailto:sle...@ya...>> wrote: >> >> I’d like to build something current first. Give me a few more days and let me see what I can do. >> >> Matt, did you want me to update your uninstall or would you rather do it? >> >> Steve Letter > > I've made the necessary changes to the uninstaller and tested it. I'll send it to you after I check the preinstall script. There was a lot in there that was the same as the uninstaller. > > Matt The preinstall script is fine. It uses `grep` rather than having specific file names when removing symlinks. I'll send the updated uninstaller to you as a compressed file. Let me know if you have any problems getting it through your mail server or if you prefer another way of getting it to you. Matt |
|
From: Robert K. <rl...@al...> - 2019-07-28 02:25:42
Attachments:
uninstall.shellcheck.out
utility.shellcheck.out
|
BTW, I ran shellcheck on the escputil wrapper and the uninstaller; there are quite a few messages (and the escputil wrapper doesn't completely parse). Got quite a few messages; they should be checked out. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Matt B. <wal...@ma...> - 2019-08-01 01:27:04
|
> On Jul 27, 2019, at 9:25 PM, Robert Krawitz <rl...@al...> wrote: > > BTW, I ran shellcheck on the escputil wrapper and the uninstaller; > there are quite a few messages (and the escputil wrapper doesn't > completely parse). Got quite a few messages; they should be checked > out. > > -- > Robert Krawitz <rl...@al...> More than a bit embarrassing. I remember having some problems making sure all the `if...fi` sections were matched up. Either I missed it or the final version didn't have the last fi removed. At least for the escputil wrapper, many of the comments had to do with not being POSIX compliant. I am self taught on shell scripting by following the scripts of developers that were doing wrapper scripts or scripts to automate a post install process. I was also using the man pages in macos. The web is also full of wonderful help turns out to be non POSIX compliant. Hmmm. I am sending Robert a revised wrapper for the escputil script that should parse better. Matt -- Matt |
|
From: Robert K. <rl...@al...> - 2019-08-16 16:14:40
|
On Fri, 16 Aug 2019 11:41:49 -0400, Steve Letter via Gimp-print-devel wrote: > Sorry. If you want to build I am good. I still need to “pretty” up > my build script and do some documentation but nothing that should > stop us from producing a build. Is your script in the repo? >> On Aug 16, 2019, at 8:31 AM, Robert Krawitz <rl...@al...> wrote: >> >> On Sat, 27 Jul 2019 19:49:21 -0500, Matthew Broughton wrote: >>>> On Jul 27, 2019, at 7:41 PM, Matthew Broughton <mab...@fa...> wrote: >>>> >>>>> On Jul 27, 2019, at 4:03 PM, Steve Letter <sle...@ya... <mailto:sle...@ya...>> wrote: >>>>> >>>>> I'd like to build something current first. Give me a few more days and let me see what I can do. >>>>> >>>>> Matt, did you want me to update your uninstall or would you rather do it? >>>>> >>>>> Steve Letter >>>> >>>> I've made the necessary changes to the uninstaller and tested it. I'll send it to you after I check the preinstall script. There was a lot in there that was the same as the uninstaller. >>>> >>>> Matt >>> >>> The preinstall script is fine. It uses `grep` rather than having specific file names when removing symlinks. I'll send the updated uninstaller to you as a compressed file. Let me know if you have any problems getting it through your mail server or if you prefer another way of getting it to you. >> >> How are things progressing? -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X