On Sun, 2023-06-11 at 15:53 -0500, Jeremiah Benham wrote: > Richard, > I can't seem to find any problem.
The good news is that the problem has gone away this morning: I've downloaded unzipped and tested denemo.zip and it is running fine. > My only guess is that maybe they > were downloading when I retarted apache or something. These were downloads on different days, I guess it will remain a mystery. > I had to restart > a few times last week to install an ssl certificate for denemo.org. > This allows us to now use https. I am waiting on an issue to be > resolved and then I will enable mod rewrite which allows us to use > https instead of http by default. This way if a user types in > denemo.org it directs to https://www.denemo.org and not > http://www.denemo.org. This adds legitimacy to our site. That's great - it's working now. > > I did notice while downloading for windows through the website that > the website links to 3 seperate versions of denemo for windows. The > first one is for a windows installer for denemo 2.4.4. Firefox gives > me a warning say that it has a virus. I ignored it and denemo > installed and ran fine. It was just the older 2.4.4. The were to > other > zip files linked on the site for windows. One of them was a binary in > my home folder that autogenerates every night. I forced a rebuild on > that and downloaded and tested it with wine. I had no issues. > Denemo.bat was not empty. I checked the one that was linked to your > directory and it also ran fine with no issues. Denemo.bat was not > empty here either. Do you think we should have these scripts generate > a md5sum when these zip files are created? This way users can tell if > their zip file got corrupted when they downloaded it. The checksum thing is of most use to build systems - individual users would just download a second time if they smelt a rat as they would find it quicker than sorting out how to run the checksum program... > > I have been looking at the build system that the lilypond uses and > trying to see what I need to do to have it build denemo. I have made > some progress but am having issue with the pango cairo thing. It > creates a circular dependency. cairo needs pango to build but we need > pango to compile with cairo support. So I need to figure out how to > rebuild pango in that with that build system. I think in gub they > created a new package and called it pangocairo or something. This is > all a dependency of GTK3. This is very good news, because we are heading for a tricky situation with LilyPond. The latest 2.24 release no longer creates the lilypond- windows.exe executable, only the lilypond.exe one. This means a console is thrown up every time that LilyPond is run, which besides disconcerting the user makes continuous typesetting unusable, and affects the Multi-line Text dialog and the graphical interface for setting transposition. If you can get control of the generation of LilyPond for Denemo then you can add the -mconsole flag back into LilyPond build which is the thing that controls whether a console is started up. Best wishes Richard > > Best, > Jeremiah > > On Sun, Jun 11, 2023 at 2:25 PM Jeremiah Benham > <jeremiahben...@gmail.com> wrote: > > > > Richard, > > Thanks for letting me know. I am going to look into what is going > > there tonight. > > > > Best, > > Jeremiah > > > > On Fri, Jun 9, 2023 at 9:31 AM Richard Shann < > > rich...@rshann.plus.com> wrote: > > > > > > Jermiah - > > > > > > I'm getting reports that the Windows build overnight is > > > generating a > > > corrupt file/installation. > > > I have downloaded last night's denemo.zip. > > > I couldn't get the zip file to uncompressat all by the usual > > > means > > > until I tried the unzip program which then generated Denemo.bat > > > with 0 > > > bytes and a bin/regfont.exe file which is not a valid Windows > > > executble. > > > The bin/denemo.exe did run but with very weird effects - no > > > window > > > title bar fonts etc - and, worse still, older versions of denemo > > > on > > > that machine would not run correctly until I rebooted. > > > > > > Unfortunately I haven't been able to build for Windows since, I > > > think, > > > my last Debian upgrade so I have nothing to debug, but I can only > > > guess > > > that the build machine has some file corruption... > > > > > > Richard > > > > > >
