From: Steve L. <sle...@ya...> - 2020-12-10 17:10:10
|
They are not the same. Under home is a release for Michael to notarize (was my intention). Steve Letter > On Dec 10, 2020, at 12:04 PM, Matt Broughton <wal...@ma...> wrote: > > > >> On Dec 9, 2020, at 9:57 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >> >> I uploaded gutenprint-5.3.4.dmg to snapshots. >> Steve Letter > > It is also showing as a new Mac release under Home / gutenprint-5.3 / 5.3.4. Was it your intention to make this an actual release? I don't think the installer is notarized. Compare the data shown below for the revised installer for v5.3.3 the installer for v5.3.4 > > > > ************************ > matt$ spctl -a -vvv -t install /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg > /Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg: accepted > source=Notarized Developer ID > origin=Developer ID Installer: Stephen Letter (63GMK36MRC) > > matt$ spctl -a -vvv -t install /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: accepted > source=Notarized Developer ID > > **v5.3.4 is not showing an 'origin=Developer ID ... NAME' I am not sure why both show as "accepted", but I think I read that you do need to have the 'origin=Developer ' with the name of the developer. > > ************************** > Compare codesign: > Borodin:~ matt$ codesign -dv /Volumes/gutenprint\ 5.3.3/gutenprint-5.3.3.pkg > Executable=/Volumes/gutenprint 5.3.3/gutenprint-5.3.3.pkg > Identifier=gutenprint-5 > Format=generic > CodeDirectory v=20200 size=172 flags=0x0(none) hashes=1+2 location=embedded > Signature size=9006 > Timestamp=Nov 25, 2020 at 8:09:29 AM > Info.plist=not bound > TeamIdentifier=RU58A2256H > Sealed Resources=none > Internal requirements count=1 size=172 > Borodin:~ matt$ > > Borodin:~ matt$ codesign -dv /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg > /Volumes/gutenprint-5.3.4/gutenprint-5.3.4.pkg: code object is not signed at all > > **v5.3.4 didn't return a lot of data that I think it should. > > I am speaking from real lack of knowledge here. I am only replying with I have read online as to how to verify that something is notarized plus what we see from the notarized package that Michael provided for v5.3.3 and what is shown for v5.3.4. > > Matt > > >> Sent from my Symbolics Lisp Machine using rmail. >> >>>> On Dec 9, 2020, at 10:50 PM, Steve Letter <sle...@ya...> wrote: >>> >>> >>> Nevermind, I'm an idiot. >>> >>> Steve Letter You're never to old to learn something stupid. -- unknown >>> >>> >>>> On Wednesday, December 9, 2020, 10:41:04 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote: >>> >>> >>> Forgive my ignorance but how do I get it there? I thought this might be an scp address but when I try I get: >>> scp: /home/frs/project/g/gi/gimp_print/snapshots/: No such file or directory >>> >>> >>> Steve Letter You're never to old to learn something stupid. -- unknown >>> >>> >>>> On Wednesday, December 9, 2020, 10:01:19 PM EST, Robert Krawitz <rl...@al...> wrote: >>> >>> >>>> On 12/9/20 2:48 PM, Steve Letter via Gimp-print-devel wrote: >>> >>>> I have available for testing an allegedly notarized disk image of gutenprint-5.3.4. Where should I upload it to? It is the same build (but different date / time) as the one I uploaded the other day. >>> >>> >>> snapshots would be ideal >>> (username,gim...@fr...:/home/frs/project/g/gi/gimp-print/snapshots/ for whatever >>> your Sourceforge username is). >>> >>> >>> _______________________________________________ >>> 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 >> _______________________________________________ >> Gimp-print-devel mailing list >> Gim...@li... >> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > |