gimp-print-devel

[Gimp-print-devel] Revised Mac Installer Gutenprint v5.3.3

[Matt <wal...@ma...>]

Gutenprint is pleased to announce that a revised macos installer for v5.3.3 has been released.   This installer will now work with Catalina (macos 10.15) and BigSur (macos 11).  Beginning with macos 10.15, Apple added a new level of security that has now been met.

Everything else is the same. The code is the same and the supported printers are the same.  This means that if you already have Gutenprint v5.3.3 installed, there is no need to install it again.

The revised installer can be downloaded using the following link.
https://sourceforge.net/projects/gimp-print/files/gutenprint-5.3/5.3.3/gutenprint-5.3.3_rev.dmg/download

[Gimp-print-devel] Epson WorkForce WF-2630 printer

[<vi...@or...>]

Hello,

I use a Mac Mini M1 with macOS Big Sur and my Epson WorkForce WF-2630 printer no longer works in USB mode.

I don’t speak English very well, but I think I read in the “News” file that I downloaded with Gutenprint 5.3.3 that you might have a solution for me to run this printer.

Thank you very much for what you do to help printer users. You do a great job.

Sincerely,

Thierry Vinot
vin...@or...



Bonjour,

J’utilise un Mac Mini M1 avec macOS Big Sur et mon imprimante Epson WorkForce WF-2630 ne fonctionne plus en mode USB. 

Je ne parle pas très bien l’Anglais, mais je crois avoir lu dans le fichier « News » que j’ai téléchargé avec Gutenprint 5.3.3 que vous auriez peut-être une solution à me proposer pour faire fonctionner cette imprimante.

Je vous remercie énormément de ce que vous faites pour aider les utilisateurs d’imprimante. Vous faites un grand et beau travail.

Cordialement,

Thierry Vinot
vin...@or...

Re: [Gimp-print-devel] Driver for printer

[Protea W. J. <aik...@gm...>]

On Thu, Dec 3, 2020 at 11:31 PM Ibrahim Sabit, MD via Gimp-print-devel <
gim...@li...> wrote:

> I’m OS is Mac High Sierra. I purchased a Canon Ink Tank G2411 and it not
> compatible. Can you recommend a patch that fixes this? Thanks
>

Hello Ibrahim,
Are you reporting a bug? What is not working in the gutenprint driver for
the G2400 series?
Best regards,
Gernot Hassenpflug

Re: [Gimp-print-devel] macOS big sur and hp phontsmart b209a

[Protea W. J. <aik...@gm...>]

On Thu, Dec 3, 2020 at 11:31 PM Richard Frederick <rfr...@ri...>
wrote:

> is there a print driver that will support the interface between my MacBook
> air with MACOS Big Sur and my HP photo smart plus b209a?
>

Hello Richard,
I presume you mean the HP Photosmart Plus B209a: this printer supports PCL3
so it should work with generic PCL3 drivers and perhaps one of the
gutenprint PCL3 drivers---there is no specific entry for this model as far
as I could tell, so it would be a case of experimenting.

Big Sur is a problem though, we do not have a working gutenprint package
yet, still ironing out some issues.

Best regards,
Gernot Hassenpflug

[Gimp-print-devel] Driver for printer

[Ibrahim S. M. <drs...@ic...>]

I’m OS is Mac High Sierra. I purchased a Canon Ink Tank G2411 and it not compatible. Can you recommend a patch that fixes this? Thanks 

Regards,

Ibrahim Sabit, MD

Sent from my iPhone

[Gimp-print-devel] drivers HP on Big Sur

[<iic...@ya...>]

<div><div>Hello.</div><div>My operating system is Big Sur. I installed your build 5.3.3.</div><div>But my HP Laser JET 1018 printer did not work.</div><div><div>Can you please tell me what solutions are there?</div></div></div>

[Gimp-print-devel] macOS big sur and hp phontsmart b209a

[Richard F. <rfr...@ri...>]

is there a print driver that will support the interface between my MacBook air with MACOS Big Sur and my HP photo smart plus b209a?

Re: [Gimp-print-devel] 64 bit drivers for Canon ip90

[Matt B. <wal...@ma...>]

> On Nov 30, 2020, at 4:23 PM, Alan Becker <a.b...@in...> wrote:
> 
> Hi, I wonder if you guys have plans to update your drivers for 64 bit?
> My favorite printer won’t work (yet) on Mac Catalina 10.15 because they have gone totally 64 bit and stopped supporting any 32 bit drivers.  I sure would hate to lose my wonderful ip90 printer.
> How difficult is it to update the driver?
> Thanks for any help or advice.
> Kind regards
> Alan

Thank you for contacting the Gutenprint team.  The Mac printer drivers are 64 bit drivers.  Your printer model is supported by the Gutenprint drivers.

Unfortunately, we don't have an installer that works properly under macos 10.15.  It appears that the current installer being tested will work with macos 15. I hope it will be available for download very soon.  Possibly even this week.

Matt

Re: [Gimp-print-devel] While we're on the subject of MacOS builds..

[Matt B. <wal...@ma...>]

> On Nov 30, 2020, at 11:16 AM, Matt Broughton <wal...@ma...> wrote:
> 
> 
> 
>> On Nov 30, 2020, at 10:45 AM, Solomon Peachy <pi...@sh... <mailto:pi...@sh...>> wrote:
>> 
>> On Mon, Nov 30, 2020 at 10:24:50AM -0600, Matt Broughton wrote:
>>> What does the user have to do to get the correct backend associated 
>>> with the printer?
>> 
>> When using the CUPS UI, it's straightforward once they know what to look 
>> for; they can visually confirm which backend is being used from the 
>> connection URI.  Naturally, the CUPS UI is not enabled by default.
>> 
>> So I don't know if there is any way to make this determination from 
>> within the native MacOS printer setup dialogs; from what I infer from 
>> the support requests that come in, if both backends claim to support the 
>> printer, MacOS just picks [the wrong] one for the user and carries on.
>> 
>> - Solomon
> 
> Solomon,
> Let's try this.  Use the native macos printer set up dialog in System Preferences.  When they add the printer, they should see the printer in the sheet "Add" as it is detected by the system.  Hopefully there will be the gutenprint53+usb in addition to the USB.  Just choose the one that shows the backend you want and you are good to go.  I am attaching a screen shot if the mailing list allows.  Else I can send it off list.  Get someone on the Mac platform to take a look.
> 
> A long time ago, we had a  third party backend 'usbtb' that dealt better with the parallel to USB converters.  Both USB and USBTB showed up.  All we had to do is to select the backend we wanted.
> Matt
> 
> <add_Canon_printer.jpeg>

After some further thought, that won't work.  The gutenprint53+usb would hve to show as a backend for everyone.  I don't think that the printer is going to advertise itself as looking for the gutenprint53+usb backend.
Matt

[Gimp-print-devel] 64 bit drivers for Canon ip90

[Alan B. <a.b...@in...>]

Hi, I wonder if you guys have plans to update your drivers for 64 bit?
My favorite printer won’t work (yet) on Mac Catalina 10.15 because they have gone totally 64 bit and stopped supporting any 32 bit drivers.  I sure would hate to lose my wonderful ip90 printer.
How difficult is it to update the driver?
Thanks for any help or advice.
Kind regards
Alan

Re: [Gimp-print-devel] While we're on the subject of MacOS builds..

[Matt B. <wal...@ma...>]

> On Nov 30, 2020, at 10:45 AM, Solomon Peachy <pi...@sh...> wrote:
> 
> On Mon, Nov 30, 2020 at 10:24:50AM -0600, Matt Broughton wrote:
>> What does the user have to do to get the correct backend associated 
>> with the printer?
> 
> When using the CUPS UI, it's straightforward once they know what to look 
> for; they can visually confirm which backend is being used from the 
> connection URI.  Naturally, the CUPS UI is not enabled by default.
> 
> So I don't know if there is any way to make this determination from 
> within the native MacOS printer setup dialogs; from what I infer from 
> the support requests that come in, if both backends claim to support the 
> printer, MacOS just picks [the wrong] one for the user and carries on.
> 
> - Solomon

Solomon,
Let's try this.  Use the native macos printer set up dialog in System Preferences.  When they add the printer, they should see the printer in the sheet "Add" as it is detected by the system.  Hopefully there will be the gutenprint53+usb in addition to the USB.  Just choose the one that shows the backend you want and you are good to go.  I am attaching a screen shot if the mailing list allows.  Else I can send it off list.  Get someone on the Mac platform to take a look.

A long time ago, we had a  third party backend 'usbtb' that dealt better with the parallel to USB converters.  Both USB and USBTB showed up.  All we had to do is to select the backend we wanted.
Matt

Re: [Gimp-print-devel] While we're on the subject of MacOS builds..

[Solomon P. <pi...@sh...>]

On Mon, Nov 30, 2020 at 10:24:50AM -0600, Matt Broughton wrote:
> What does the user have to do to get the correct backend associated 
> with the printer?

When using the CUPS UI, it's straightforward once they know what to look 
for; they can visually confirm which backend is being used from the 
connection URI.  Naturally, the CUPS UI is not enabled by default.

So I don't know if there is any way to make this determination from 
within the native MacOS printer setup dialogs; from what I infer from 
the support requests that come in, if both backends claim to support the 
printer, MacOS just picks [the wrong] one for the user and carries on.

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
High Springs, FL                      speachy (freenode)

Re: [Gimp-print-devel] While we're on the subject of MacOS builds..

[Matt B. <wal...@ma...>]

> On Nov 30, 2020, at 10:19 AM, Matt Broughton <wal...@ma...> wrote:
> 
> Michael,
>> On Nov 30, 2020, at 7:25 AM, Michael Sweet <ms...@ms...> wrote:
>> 
>> Solomon,
>> 
>>> On Nov 30, 2020, at 6:59 AM, Solomon Peachy <pi...@sh...> wrote:
>>> 
>>> Signed PGP part
>>> We're still having problems where the 'usb' backend is being chosen
>>> instead of the gutenprint backend, and it's not obvious how (if at all)
>>> the user is supposed to figure this out.
>>> 
>>> Ireally we'd use the USB backend's blacklist mechanism but clearly that
>>> is configured differently on MacOS.
>> 
>> I don't believe that the macOS USB backend supports the notion of blacklisting, just redirecting which class driver gets used for IO.  So for macOS we'd need to provide an equivalent version of the gutenprint backend, along with codeless kexts, to handle those printers' IO needs.
>> 
>> (and yes it would really be super-helpful if printer vendors stopped making non-standard aka broken USB printer implementations...)
> 
>> 
>> ________________________
>> Michael Sweet
>> 
>> 
> 
> Didn't we try that a while ago and we couldn't get it to work?
> 
> 
> Matt
> 

Solomon,
What does the user have to do to get the correct backend associated with the printer?
Matt

Re: [Gimp-print-devel] While we're on the subject of MacOS builds..

[Michael S. <ms...@ms...>]

Matt,

> On Nov 30, 2020, at 11:19 AM, Matt Broughton <wal...@ma...> wrote:
> ...
> Didn't we try that a while ago and we couldn't get it to work?

IIRC the issue was getting a kernel code signing certificate from Apple.  The normal developer ID certs weren't enough to bypass the security warning, although maybe the new notarization stuff replaced the special certs?  I'll see if I can install one on my system using my Developer ID Application certificate with or without notarization...

________________________
Michael Sweet

Re: [Gimp-print-devel] While we're on the subject of MacOS builds..

[Matt B. <wal...@ma...>]

Michael,
> On Nov 30, 2020, at 7:25 AM, Michael Sweet <ms...@ms...> wrote:
> 
> Solomon,
> 
>> On Nov 30, 2020, at 6:59 AM, Solomon Peachy <pi...@sh...> wrote:
>> 
>> Signed PGP part
>> We're still having problems where the 'usb' backend is being chosen
>> instead of the gutenprint backend, and it's not obvious how (if at all)
>> the user is supposed to figure this out.
>> 
>> Ireally we'd use the USB backend's blacklist mechanism but clearly that
>> is configured differently on MacOS.
> 
> I don't believe that the macOS USB backend supports the notion of blacklisting, just redirecting which class driver gets used for IO.  So for macOS we'd need to provide an equivalent version of the gutenprint backend, along with codeless kexts, to handle those printers' IO needs.
> 
> (and yes it would really be super-helpful if printer vendors stopped making non-standard aka broken USB printer implementations...)

> 
> ________________________
> Michael Sweet
> 
> 

Didn't we try that a while ago and we couldn't get it to work?


Matt

Re: [Gimp-print-devel] While we're on the subject of MacOS builds..

[Michael S. <ms...@ms...>]

Solomon,

> On Nov 30, 2020, at 6:59 AM, Solomon Peachy <pi...@sh...> wrote:
> 
> Signed PGP part
> We're still having problems where the 'usb' backend is being chosen
> instead of the gutenprint backend, and it's not obvious how (if at all)
> the user is supposed to figure this out.
> 
> Ireally we'd use the USB backend's blacklist mechanism but clearly that
> is configured differently on MacOS.

I don't believe that the macOS USB backend supports the notion of blacklisting, just redirecting which class driver gets used for IO.  So for macOS we'd need to provide an equivalent version of the gutenprint backend, along with codeless kexts, to handle those printers' IO needs.

(and yes it would really be super-helpful if printer vendors stopped making non-standard aka broken USB printer implementations...)

________________________
Michael Sweet

[Gimp-print-devel] While we're on the subject of MacOS builds..

[Solomon P. <pi...@sh...>]

We're still having problems where the 'usb' backend is being chosen 
instead of the gutenprint backend, and it's not obvious how (if at all) 
the user is supposed to figure this out.

Ireally we'd use the USB backend's blacklist mechanism but clearly that 
is configured differently on MacOS.

Any suggestions?

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
High Springs, FL                      speachy (freenode)

Re: [Gimp-print-devel] A question

[Matt B. <wal...@ma...>]

> On Nov 29, 2020, at 9:41 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
> 
> If I wanted an M1 now I would have had to travel 3 or 4 hours so I opted to have it delivered. I saw 16” wasn’t available so I opted for another 13”. 16” is too big for flying IMO anyway. 
> 
> Steve Letter
> Sent from my Commodore PET

I'm going to wait on getting an M1 until my local independent Apple retailer (Premiere Partner status) is offering product again.  They are one of the smallish retailers that must be taking a beating with Covid-19.  I started dealing with them when I bought my Blue and White (generation 1).
Matt

Re: [Gimp-print-devel] HP Deskjet 3940 with Big Sur

[Matt B. <wal...@ma...>]

> On Nov 29, 2020, at 3:44 PM, Bruce Krueger <bru...@gm...> wrote:
> 
> Do you have a driver to allow my HP Deskjet 3940 to print using Mac OS 11.0.1 Big Sur? Apparently HP does not.

We are still in the testing phase for supporting Big Sur.  As to your printer, Gutenprint does not specifically support that model.  The OpenPrinting site does indicate that using the Gutenprint pcl-900 driver should give you most of the functionality you had before.
https://openprinting.org/printer/HP/HP-DeskJet_3940
Matt

Re: [Gimp-print-devel] A question

[Steve L. <sle...@ya...>]

Yay, another fat binary. 

Steve Letter
Sent from my Commodore PET

> On Nov 29, 2020, at 10:20 PM, Matt Broughton <wal...@ma...> wrote:
> 
> 
> 
>> On Nov 29, 2020, at 9:05 PM, Robert Krawitz <rl...@al...> wrote:
>> 
>>> On 11/29/20 9:50 PM, Steve Letter via Gimp-print-devel wrote:
>>> I ordered a new M1 system, it won’t be delivered until Christmas week. I prefer to wait to attempt a new build until after I receive it. Any objections?  Michael, will you be available to notarize if I don’t get that figured out?
>> 
>> Will that be able to build and test x86 bits?
> 
> From Apple's Developer's site:
>> "To build a universal binary, you need Xcode 12 or a later version, which adds arm64 to the standard list of build architectures for macOS binaries."
> 
> That indicates to me that any Mac that can run Xcode 12 could build a Universal Binary.  You need macos 15.x for Xcode 12.  This is how they handled the switch from PPC to i386.  I was able to build PPC and i386 on macosx 10.4.x.
> Matt
> 
> 
> 
> _______________________________________________
> Gimp-print-devel mailing list
> Gim...@li...
> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: [Gimp-print-devel] A question

[Steve L. <sle...@ya...>]

If I wanted an M1 now I would have had to travel 3 or 4 hours so I opted to have it delivered. I saw 16” wasn’t available so I opted for another 13”. 16” is too big for flying IMO anyway. 

Steve Letter
Sent from my Commodore PET

> On Nov 29, 2020, at 10:18 PM, Michael Sweet <ms...@ms...> wrote:
> 
> Steve,
> 
>> On Nov 29, 2020, at 9:50 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
>> 
>> I ordered a new M1 system, it won’t be delivered until Christmas week. I prefer to wait to attempt a new build until after I receive it. Any objections?  Michael, will you be available to notarize if I don’t get that figured out?
> 
> Sure.
> 
> In the meantime, I got a possible solution for the Rosetta issue - apparently it isn't installed by default, so running the following command may allow the Intel build to work on the M1 systems:
> 
>    softwareupdate --install-rosetta
> 
> I won't have access to my M1 system again until next weekend so I can't try it myself... :/
> 
>> 
>> Steve Letter
>> Sent from my Commodore PET
>> 
>>>> On Nov 28, 2020, at 10:47 PM, Robert Krawitz <rl...@al...> wrote:
>>> 
>>> On 11/27/20 5:06 PM, Steve Letter via Gimp-print-devel wrote:
>>>> Sorry, I meant notarize, I can still sign (and when I meet the requirements, notarize).
>>>> 
>>>> Steve Letter
>>>> Sent from my Commodore PET
>>>> 
>>>>>> On Nov 27, 2020, at 4:03 PM, Matt <wal...@ma...> wrote:
>>>>> 
>>>>> 
>>>>>> On Nov 27, 2020, at 12:40 PM, Steve Letter via Gimp-print-devel
>>>>>> <gim...@li...> wrote:
>>>>>> 
>>>>>> I can certainly do the builds and ask Michael to sign until I can get that straight.
>>> I don't really understand the Mac environment.  Could you, Matt, and Mike work out how to handle
>>> this?  Thanks!
>>> 
>>> I'd like to be able to support as far back as possible, preferably to 10.6 if feasible.  If that's
>>> going to prove to be too much work, we'll figure out where to go from there, but I'd like to
>>> maintain compatibility as far as we can.
>>> 
>>> 
>>> _______________________________________________
>>> Gimp-print-devel mailing list
>>> Gim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
>> 
>> 
>> 
>> _______________________________________________
>> Gimp-print-devel mailing list
>> Gim...@li...
>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
> 
> ________________________
> Michael Sweet
> 
> 
> 

Re: [Gimp-print-devel] A question

[Matt B. <wal...@ma...>]

> On Nov 29, 2020, at 9:35 PM, Steve Letter <sle...@ya...> wrote:
> 
> I will build the disk image tomorrow. I would have sooner had I known. 
> 
> I’ve always had problems getting email from the list, I’m going to start monitoring the list directly. 
> 
> Steve Letter
> Sent from my Commodore PET

Michael just made it available to us November 25th -- last Wednesday
Matt


> 
>> On Nov 29, 2020, at 10:11 PM, Matt Broughton <wal...@ma...> wrote:
>> 
>> 
>> 
>>> On Nov 29, 2020, at 7:50 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
>>> 
>>> I’m going to get a new Mac, that should help me get up to date hardware wise. 
>>> 
>>> Steve Letter
>>> Sent from my Commodore PET
>> 
>> Steve,
>> Michael did notarize and post your last package of 5.3.3.  It is at
>> https://www.dropbox.com/s/3223e9y5v9zcc0z/gutenprint-5.3.3-msweet.zip?dl=0
>> 
>> Maybe you could grab that and make a .dmg of it.  My guess is that Robert would upload that which will take care of a *lot* of problems.  It would probably be best to rename things so everyone will know which package is which. That should work on macos 10.7 through macos 15.x and presumably/hopefully Intel maos 11.  Michael did specifically say that it would not work on the new M1 Macs.  In any event, this would fill a *huge* gap.
>> 
>> In the next release, we can hopefully get the M1 Macs running and if possible fix an installer issue with osx 10.6.x.  At least they can run the earlier version.
>> 
>> Matt
>> 
>>> 
>>>>> On Nov 28, 2020, at 10:47 PM, Robert Krawitz <rl...@al...> wrote:
>>>> 
>>>> On 11/27/20 5:06 PM, Steve Letter via Gimp-print-devel wrote:
>>>>> Sorry, I meant notarize, I can still sign (and when I meet the requirements, notarize).
>>>>> 
>>>>> Steve Letter
>>>>> Sent from my Commodore PET
>>>>> 
>>>>>>> On Nov 27, 2020, at 4:03 PM, Matt <wal...@ma...> wrote:
>>>>>> 
>>>>>> 
>>>>>>> On Nov 27, 2020, at 12:40 PM, Steve Letter via Gimp-print-devel
>>>>>>> <gim...@li...> wrote:
>>>>>>> 
>>>>>>> I can certainly do the builds and ask Michael to sign until I can get that straight.
>>>> I don't really understand the Mac environment.  Could you, Matt, and Mike work out how to handle
>>>> this?  Thanks!
>>>> 
>>>> I'd like to be able to support as far back as possible, preferably to 10.6 if feasible.  If that's
>>>> going to prove to be too much work, we'll figure out where to go from there, but I'd like to
>>>> maintain compatibility as far as we can.
>>>> 
>> 
> 

Re: [Gimp-print-devel] A question

[Steve L. <sle...@ya...>]

I will build the disk image tomorrow. I would have sooner had I known. 

I’ve always had problems getting email from the list, I’m going to start monitoring the list directly. 

Steve Letter
Sent from my Commodore PET

> On Nov 29, 2020, at 10:11 PM, Matt Broughton <wal...@ma...> wrote:
> 
> 
> 
>> On Nov 29, 2020, at 7:50 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
>> 
>> I’m going to get a new Mac, that should help me get up to date hardware wise. 
>> 
>> Steve Letter
>> Sent from my Commodore PET
> 
> Steve,
> Michael did notarize and post your last package of 5.3.3.  It is at
> https://www.dropbox.com/s/3223e9y5v9zcc0z/gutenprint-5.3.3-msweet.zip?dl=0
> 
> Maybe you could grab that and make a .dmg of it.  My guess is that Robert would upload that which will take care of a *lot* of problems.  It would probably be best to rename things so everyone will know which package is which. That should work on macos 10.7 through macos 15.x and presumably/hopefully Intel maos 11.  Michael did specifically say that it would not work on the new M1 Macs.  In any event, this would fill a *huge* gap.
> 
> In the next release, we can hopefully get the M1 Macs running and if possible fix an installer issue with osx 10.6.x.  At least they can run the earlier version.
> 
> Matt
> 
>> 
>>>> On Nov 28, 2020, at 10:47 PM, Robert Krawitz <rl...@al...> wrote:
>>> 
>>> On 11/27/20 5:06 PM, Steve Letter via Gimp-print-devel wrote:
>>>> Sorry, I meant notarize, I can still sign (and when I meet the requirements, notarize).
>>>> 
>>>> Steve Letter
>>>> Sent from my Commodore PET
>>>> 
>>>>>> On Nov 27, 2020, at 4:03 PM, Matt <wal...@ma...> wrote:
>>>>> 
>>>>> 
>>>>>> On Nov 27, 2020, at 12:40 PM, Steve Letter via Gimp-print-devel
>>>>>> <gim...@li...> wrote:
>>>>>> 
>>>>>> I can certainly do the builds and ask Michael to sign until I can get that straight.
>>> I don't really understand the Mac environment.  Could you, Matt, and Mike work out how to handle
>>> this?  Thanks!
>>> 
>>> I'd like to be able to support as far back as possible, preferably to 10.6 if feasible.  If that's
>>> going to prove to be too much work, we'll figure out where to go from there, but I'd like to
>>> maintain compatibility as far as we can.
>>> 
> 

Re: [Gimp-print-devel] A question

[Matt B. <wal...@ma...>]

> On Nov 29, 2020, at 9:18 PM, Michael Sweet <ms...@ms...> wrote:
> 
> Steve,
> 
>> On Nov 29, 2020, at 9:50 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
>> 
>> I ordered a new M1 system, it won’t be delivered until Christmas week. I prefer to wait to attempt a new build until after I receive it. Any objections?  Michael, will you be available to notarize if I don’t get that figured out?
> 
> Sure.
> 
> In the meantime, I got a possible solution for the Rosetta issue - apparently it isn't installed by default, so running the following command may allow the Intel build to work on the M1 systems:
> 
>    softwareupdate --install-rosetta
> 
> I won't have access to my M1 system again until next weekend so I can't try it myself... :/

We can deal with that with the preinstall script in the next build if that solution works.  Before then, I think we can deal with it on list.  It's amazing what gets picked up off mailing lists and is distributed on other lists.  Also, I would think that most users of M1 systems will already have rosetta installed.  It always takes a while before apps catch up with a change like this. 
Matt


> 
>> 
>> Steve Letter
>> Sent from my Commodore PET
>> 
>>> On Nov 28, 2020, at 10:47 PM, Robert Krawitz <rl...@al...> wrote:
>>> 
>>> On 11/27/20 5:06 PM, Steve Letter via Gimp-print-devel wrote:
>>>> Sorry, I meant notarize, I can still sign (and when I meet the requirements, notarize).
>>>> 
>>>> Steve Letter
>>>> Sent from my Commodore PET
>>>> 
>>>>>> On Nov 27, 2020, at 4:03 PM, Matt <wal...@ma...> wrote:
>>>>> 
>>>>> 
>>>>>> On Nov 27, 2020, at 12:40 PM, Steve Letter via Gimp-print-devel
>>>>>> <gim...@li...> wrote:
>>>>>> 
>>>>>> I can certainly do the builds and ask Michael to sign until I can get that straight.
>>> I don't really understand the Mac environment.  Could you, Matt, and Mike work out how to handle
>>> this?  Thanks!
>>> 
>>> I'd like to be able to support as far back as possible, preferably to 10.6 if feasible.  If that's
>>> going to prove to be too much work, we'll figure out where to go from there, but I'd like to
>>> maintain compatibility as far as we can.
>>> 
>>> 
>>> _______________________________________________
>>> Gimp-print-devel mailing list
>>> Gim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
>> 
>> 
>> 
>> _______________________________________________
>> Gimp-print-devel mailing list
>> Gim...@li...
>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
> 
> ________________________
> Michael Sweet
> 
> 
> 
> _______________________________________________
> Gimp-print-devel mailing list
> Gim...@li...
> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: [Gimp-print-devel] A question

[Steve L. <sle...@ya...>]

I believe it will build. I have an x86 system to test with and build if the M1 won’t. 

Steve Letter
Sent from my Commodore PET

> On Nov 29, 2020, at 10:06 PM, Robert Krawitz <rl...@al...> wrote:
> 
> On 11/29/20 9:50 PM, Steve Letter via Gimp-print-devel wrote:
>> I ordered a new M1 system, it won’t be delivered until Christmas week. I prefer to wait to attempt a new build until after I receive it. Any objections?  Michael, will you be available to notarize if I don’t get that figured out?
> 
> Will that be able to build and test x86 bits?
> 
> 
> _______________________________________________
> Gimp-print-devel mailing list
> Gim...@li...
> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel