08-16-2024, 09:58 AM | #1 |
Grand Sorcerer
Posts: 28,033
Karma: 199464182
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Sigil-2.3.0 Released
Sigil-2.3.0
Sigil version 2.3.0 represents a mix of bug fixes and new features. Sigil 2.3.0 also marks the first version to only support building with Qt6. New Features in this release
Bug Fixes
--------------------------------Notes ----------------------------------- The latest version of the Sigil User Guide can always be downloaded from the Sigil website, or from its own GitHub repository. Please check the Sigil website for important Sigil support links, additional resource downloads, and platform-specific trouble-shooting tips/requirements. The MacOS builds are signed AND notarized. PGP Fingerprint (for signed tags and source archives): Code:
B5A5 6206 AB0F BC1A 24EF AB8A A166 D29A 8FCD AC63 |
08-16-2024, 09:59 AM | #2 |
Grand Sorcerer
Posts: 28,033
Karma: 199464182
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Post reserved for future use.
|
Advert | |
|
08-16-2024, 10:28 AM | #3 |
Sigil Developer
Posts: 8,155
Karma: 5450818
Join Date: Nov 2009
Device: many
|
Mac OS users - especially people using the newest or Beta macOS versions, please try launching this version of Sigil and PageEdit with just a normal double-click instead of the "ctrl-click twice on open" approach that was needed before. Both Sigil and PageEdit should now launch with no warnings.
If not, please let me know. A screen capture of any warnings produced by macOS that you run into would help Last edited by KevinH; 08-16-2024 at 11:35 AM. |
08-16-2024, 04:00 PM | #4 |
just an egg
Posts: 1,685
Karma: 5513698
Join Date: Mar 2015
Device: Kindle, iOS
|
Hi Kevin — unfortunately I'm getting the same warning as previous releases.
I am on macOS Sonoma 14.6.1 installing Sigil.app-2.3.0-Mac-arm64.txz Screenshot: |
08-16-2024, 04:36 PM | #5 |
Sigil Developer
Posts: 8,155
Karma: 5450818
Join Date: Nov 2009
Device: many
|
Wow, that stinks. My signing tested out fine and my notarization reported back as accepted. I stapled it to the Sigil.app binary. Testing it on my own machine worked just fine.
So somehow making the tar.xz archive is messing things up. Sigil is huge. I can not distribute it on a dmg (even a compressed one). Not sure how to deal with that. Thanks for testing and reporting back. |
Advert | |
|
08-16-2024, 04:52 PM | #6 |
Sigil Developer
Posts: 8,155
Karma: 5450818
Join Date: Nov 2009
Device: many
|
@odamizu and any other macOS user:
Would you please try one thing for me? 1. Download a fresh copy of Sigil.app-2.3.0-Mac-arm64.txz from our github Releases page. 2. Move it from your Downloads to your Desktop 3. now run Terminal.app and enter the following commands: cd cd Desktop ls -a@l Sigil.app-2.3.0-Mac-arm64.txz xattr -d com.apple.quarantine Sigil.app-2.3.0-Mac-arm64.txz ls -a@l Sigil.app-2.3.0-Mac-arm64.txz And copy the output of Terminal.app and post it to this thread. 4. Then double click on Sigil.app-2.3.0-Mac-arm64.txz to unpack it 5. Double click on the resulting Sigil.app Did you still get that message? Last edited by KevinH; 08-16-2024 at 06:31 PM. |
08-16-2024, 05:00 PM | #7 |
Sigil Developer
Posts: 8,155
Karma: 5450818
Join Date: Nov 2009
Device: many
|
When I remove the com.apple.quarantine attribute from the Sigil.app*.txz before unpacking it. And double-click on the resulting Sigil.app, I get no warning anymore.
But that may be only on my machine I used to build it. I can not tell. |
08-16-2024, 05:07 PM | #8 |
Sigil Developer
Posts: 8,155
Karma: 5450818
Join Date: Nov 2009
Device: many
|
It is so upsetting that the act of downloading an archive from Github results in macOS treating it somehow differently than having the app, even though I signed and notarized it properly!
Are they trying to force us to use the Mac App store??? |
08-16-2024, 05:29 PM | #9 | |
Evangelist
Posts: 440
Karma: 77256
Join Date: Sep 2011
Device: none
|
Does this help? Seems you may be using it but not sure.
Quote:
|
|
08-16-2024, 05:38 PM | #10 |
Grand Sorcerer
Posts: 28,033
Karma: 199464182
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
There's no doubt in my mind that this is the case.
Out of curiosity: what size would a Sigil dmg be? Would it really be larger than Calibre's? It looks like the latest for it is a hair over 300Mb. That seems large to me (but I'm old) but users don't seem mind it. |
08-16-2024, 06:09 PM | #11 |
Grand Sorcerer
Posts: 28,033
Karma: 199464182
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Speaking of size... I'm going to drop the msvc2015+ redistributable (and the check to see if it is installed) from Sigil's Windows installer. Windows 10 ships with the msvc2015+ installer and our Sigil minimum is Windows 10 (1809). Not sure why I haven't chucked it sooner.
If this trend of Sigil's Windows Inno Setup installer triggering antivirus false positives continues, I may need to consider changing to a Wix-generated MSI installer on Windows. That would be a big learning curve and a considerable overhaul. Last edited by DiapDealer; 08-16-2024 at 06:12 PM. |
08-16-2024, 06:39 PM | #12 |
Sigil Developer
Posts: 8,155
Karma: 5450818
Join Date: Nov 2009
Device: many
|
I am using Apple's tar which handles extended attributes.
In all my testing if I use any Browser to download from github the "com.apple.quarantine" attribute is added to the what was downloaded. Unfortunately this attribute is then passed to the underlying Sigil.app when you unpack it. And then the damn notarization is totally ignored. So in order to prevent that noxious warning message, I need to do one of two things: A. download with any browser and then delete the resulting "com.apple.quarantine" attribute before unpacking it: xattr -d com.apple.quarantine Sigil.app-2.3.0-Mac-arm64.txz OR B. Use curl to do the download for me and allow github to do the needed relocations: curl -L -o Sigil.app.txz https://github.com/Sigil-Ebook/Sigil...-Mac-arm64.txz Using curl just moves the file from github to my machine and does not add any com.apple.quarantine extended attribute Then I can just double-click on Sigil.app.txz to unpack it and then launch the resulting Sigil.app with no warning then generated. --- So will some mac user please verify if one or both of these approaches work on their machine as I can not tell if they work only on the machine that built them or will work on any Mac. I am hoping for the latter case. Last edited by KevinH; 08-16-2024 at 06:42 PM. |
08-16-2024, 06:55 PM | #13 | |
Sigil Developer
Posts: 8,155
Karma: 5450818
Join Date: Nov 2009
Device: many
|
Quote:
If I try to create a level 9 compressed dmg with the following commands: hdiutil create ~/Desktop/test.dmg -ov -volname "Sigil" -fs HFS+ -srcfolder ~/Desktop/Sigil.app hdiutil convert ~/Desktop/test.dmg -format UDZO -imagekey zlib-level=9 -o Sigil.dmg The resulting Sigil.dmg is about 200meg (198180814). I have no idea if a dmg being unpacked will transfer any com.apple.quarantine attributes to the payload or not when mounted. |
|
08-16-2024, 06:59 PM | #14 |
Sigil Developer
Posts: 8,155
Karma: 5450818
Join Date: Nov 2009
Device: many
|
So using a highly compressed read only dmg increased the download size by about 80 meg. (120 vs 200).
So I will build and upload my compressed test dmg to my github repo and test if downloading it in that form will work. |
08-16-2024, 07:06 PM | #15 |
Evangelist
Posts: 420
Karma: 2737916
Join Date: May 2013
Location: Ontario, Canada
Device: Kindle KB, Oasis, Pop_Os!, Jutoh, Kobo Forma
|
Good News -- Linux
Just fyi, both Sigil and PageEdit 2.3.0 compiled with no issues on my Linux box, and work just fine!
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sigil-1.5.1 Released | DiapDealer | Sigil | 27 | 04-15-2021 10:27 AM |
Sigil-1.2.0 Released | DiapDealer | Sigil | 77 | 07-16-2020 12:55 PM |
Sigil-0.9.7 Released | DiapDealer | Sigil | 90 | 11-10-2016 01:30 PM |
Sigil-0.9.6 Released | DiapDealer | Sigil | 69 | 10-29-2016 10:35 AM |
Sigil-0.8.900 released for testing - Wait for Sigil-0.8.901 | KevinH | Sigil | 106 | 10-04-2015 10:41 AM |