Re: [Gimp-print-devel] 5.3.3 Installation Failure on 10.6.8

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

> On Nov 27, 2019, at 12:12 PM, Matt Broughton <wal...@ma...> wrote:
> 
> 
> 
>> On Nov 27, 2019, at 12:02 PM, Matt Broughton <wal...@ma...> wrote:
>> 
>> 
>> 
>>> On Nov 26, 2019, at 7:28 PM, Matt Broughton <wal...@ma...> wrote:
>>> 
>>> 
>>> 
>>>> On Nov 26, 2019, at 4:35 PM, Robert Krawitz <rl...@al...> wrote:
>>>> 
>>>> I guess I should bump the minimum requirement to 10.7 now?
>>>> 
>>>> -- 
>>>> Robert Krawitz                                     <rl...@al...>
>>>> 
>>> 
>>> Unfortunately yes. I’m a bit apprehensive as to what will break when we start getting things notarized for Catalina. Hopefully we can find more testers. All I have now is Mac OS X 10.6.8 and lower. I also have macOS 10.14.x Mojave. I don’t know when I will be able to upgrade to Catalina. I will need several hundred dollars of software upgrades. I’ll look into installing a bare bones version of Catalina on another disk.
>>> Matt
>> 
>> I did more than a bit on this.  I ran the installer and looked at the error log.  It didn't get very far and quit with the following two errors:
>> 
>> Failed to verify data against certificate.
>> Invalid Distribution File/Package
>> 
>> We should be able to resolve this continue supporting 10.6.x pending what happens with notarization.I am trying to find a tool for Mac OS X 10.6.x to take a look at the the certificate and why it would fail.  The signature is reported as fine in macos 10.14.x Mojave.    I also discovered what appears to be an error in the build script where it is testing for minimum version.  It is something in the preinstall script that is possibly ignored.  That is a separate issue for another thread.
>> 
>> Matt
> 
> I forgot to mention, there was one other difference between the the 5.2.15 and 5.3.3 installers.
> file gutenprint-5.2.15.dmg
> VAX COFF executable not stripped - version 2358
> 
> file gutenprint-5.3.3.dmg VAX COFF executable
> 
> I have no clue as ro what this means or whether it pertains to the signing of the packages.
> 
> Matt

Continuing my monologue --  I found something very interesting even though I can't explain it.  I used an application called Pacifist to look at what was in the v5.25 and the v5.3.3 installers on Mac OS X 10.6.8.  The _CodeSignature files were definitely missing for v5.3.3.

In macos 10.4.6, the Terminal check for signatures shows that they are valid for both v5.2.5 and 5.3.3.  Pacifist does not find the _CodeSignature files for v5.3.3 under macos 10.14.6.

I'm not sure what is going on here.  Perhaps the build environment and tools used for v5.3.3 handle the signature files differently and macos 10.6 can't deal with the change.  Hopefully the attachments will all pass to the list.

Matt