Re: [GUB] error while trying to make a darwin cross-compiler
>> Then some downloads and later it came to this error saying make is too old: >> >> Tail of target/linux-x86/log/glibc-core.log >> checking for gnumsgfmt... no >> checking for gmsgfmt... no >> checking for msgfmt... msgfmt >> checking version of msgfmt... 0.19.2, ok >> checking for makeinfo... makeinfo >> checking version of makeinfo... 6.1, bad >> checking for sed... sed >> checking version of sed... v. ?.??, bad >> checking for autoconf... autoconf >> checking whether autoconf works... yes >> configure: error: >> *** These critical programs are missing or too old: make >> *** Check the INSTALL file for required versions. >> Command barfed: cd > > Have a look at the specific config.log I think I found the problem: while running configure in glibc, configure finds make 4.0 but checks for 3.79* or 3.8* or 3.9*. Here is what's about make in Makefile.in: AC_CHECK_PROG_VER(MAKE, gnumake gmake make, --version, [GNU Make[^0-9]*\([0-9][0-9.]*\)], [3.79* | 3.[89]*], critic_missing="$critic_missing make") probably an old glibc compared to my make. Anything I can do to either download a newer glibc or change autmatically Makefile.in from glibc? Thanks, Frédéric ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [GUB] error while trying to make a darwin cross-compiler
Meanwhile, I have compiled make 3.82 and made it available before make
4.0 in the PATH. Then the process goes further up to this point:
$ bin/gub --verbose darwin-x86::cross/gcc
...
building package: linux-x86::cross/gcc
*** Stage: download (cross/gcc, linux-x86)
*** Stage: untar (cross/gcc, linux-x86)
*** Stage: patch (cross/gcc, linux-x86)
*** Stage: autoupdate (cross/gcc, linux-x86)
*** Stage: configure (cross/gcc, linux-x86)
*** Stage: compile (cross/gcc, linux-x86)
*** Stage: install (cross/gcc, linux-x86)
*** Stage: package (cross/gcc, linux-x86)
*** Stage: clean (cross/gcc, linux-x86)
*** Stage: pkg_install (cross/gcc, linux-x86)
cross/gcc-core conflicts with cross/gcc-doc
removing cross/gcc-core
db delete failing for ./usr/cross/bin/i686-linux-gcc-ranlib
db delete failing for ./usr/cross/bin/i686-linux-cpp
db delete failing for ./usr/cross/bin/i686-linux-gcc-4.9.2
db delete failing for ./usr/cross/bin/i686-linux-gcc
db delete failing for ./usr/cross/bin/i686-linux-gcc-ar
db delete failing for ./usr/cross/bin/i686-linux-gcov
db delete failing for ./usr/cross/bin/i686-linux-gcc-nm
db delete failing for
./usr/cross/lib/gcc/i686-linux/4.9.2/plugin/include/ipa-ref.h
db delete failing for
./usr/cross/lib/gcc/i686-linux/4.9.2/plugin/include/tm_p.h
...
already have file ./usr/cross/bin/i686-linux-gcc-ranlib: cross/gcc-core
already have file ./usr/cross/bin/i686-linux-cpp: cross/gcc-core
already have file ./usr/cross/bin/i686-linux-gcc-4.9.2: cross/gcc-core
already have file ./usr/cross/bin/i686-linux-gcc: cross/gcc-core
already have file ./usr/cross/bin/i686-linux-gcc-ar: cross/gcc-core
already have file ./usr/cross/bin/i686-linux-gcov: cross/gcc-core
already have file ./usr/cross/bin/i686-linux-gcc-nm: cross/gcc-core
already have file
./usr/cross/lib/gcc/i686-linux/4.9.2/plugin/include/ipa-ref.h:
cross/gcc-core
already have file
./usr/cross/lib/gcc/i686-linux/4.9.2/plugin/include/tm_p.h:
cross/gcc-core
...
The end of target/linux-x86/log/cross/gcc.log is:
invoking rm -rf /home/fred/gub/target/linux-x86/install/cross/gcc-4.9.2-root/lib
invoking rm -rf
/home/fred/gub/target/linux-x86/install/cross/gcc-4.9.2-root/usr/lib
invoking rm -rf
/home/fred/gub/target/linux-x86/install/cross/gcc-4.9.2-root/usr/share
invoking tar -C
/home/fred/gub/target/linux-x86/install/cross/gcc-4.9.2-root/
--ignore-failed --exclude="*~" -zcf
/home/fred/gub/target/linux-x86/packages/cross/gcc-4.9.2.linux-x86.gup
./
Running dump_file
('\x80\x02]q\x00(U\x05CPATHq\x01U\x00q\x02\x86q\x03U\x12CPLUS_INCLUDE_PATHq\x04U,/home/fred/gub/target/tools/root/usr/includeq\x05\x86q\x06U\x0eC_INCLUDE_PATHq\x07U,/home/fred/gub/target/tools/root/usr/includeq\x08\x86q\tU\x0fLD_LIBRARY_PATHq\nU$/home/fred/gub/target/linux-x86/rootq\x0b\x86q\x0cU\nLD_PRELOADq\rU\x00q\x0e\x86q\x0fU\x0cLIBRARY_PATHq\x10U(/ho
...
\x01\x00\x00U\tvc_branchrY\x01\x00\x00h\x0e\x86rZ\x01\x00\x00U\x10vc_branch_suffixr[\x01\x00\x00h\x0e\x86r\\\x01\x00\x00U\x07versionr]\x01\x00\x00h\xaa\x86r^\x01\x00\x00U\x07workdirr_\x01\x00\x00U\x0e/home/fred/gubr`\x01\x00\x00\x86ra\x01\x00\x00U\x0eworkdir_prefixrb\x01\x00\x00j`\x01\x00\x00\x86rc\x01\x00\x00e.',
'/home/fred/gub/target/linux-x86/packages/cross/gcc.linux-x86.hdr',
'w')
{}
invoking rm -rf /home/fred/gub/target/linux-x86/install/cross/gcc-4.9.2-root
Running dump_file
('package',
'/home/fred/gub/target/linux-x86/status/cross/gcc-4.9.2-gcc-4.9.2',
'w')
{'permissions': 420}
*** Stage: clean (cross/gcc, linux-x86)
invoking rm -rf
/home/fred/gub/target/linux-x86/status/cross/gcc-4.9.2-gcc-4.9.2
/home/fred/gub/target/linux-x86/install/cross/gcc-4.9.2-root
invoking rm -rf /home/fred/gub/target/linux-x86/src/cross/gcc-4.9.2
/home/fred/gub/target/linux-x86/build/cross/gcc-4.9.2
*** Stage: pkg_install (cross/gcc, linux-x86)
Traceback (most recent call last):
File "bin/gub", line 233, in exceptional_build
build (settings, options, files)
File "bin/gub", line 229, in build
b.build_source_packages (names)
File "bin/../gub/buildrunner.py", line 334, in build_source_packages
self.spec_build (spec_name)
File "bin/../gub/buildrunner.py", line 276, in spec_build
self.spec_install (spec)
File "bin/../gub/buildrunner.py", line 192, in spec_install
self.pkg_install (spec, pkg)
File "bin/../gub/buildrunner.py", line 188, in pkg_install
manager.install_package (install_candidate.name ())
File "bin/../gub/gup.py", line 336, in install_package
self.install_tarball (ball, name, d['prefix_dir'])
File "bin/../gub/gup.py", line 119, in install_tarball
raise Exception ('Duplicate files found.')
Exception: Duplicate files found.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Staging not merging with master - make website fails
Hello, commit29941d96aa9942cfe914440b90b49ff7e015742e >From Paul is missing its image files - they have been uploaded into LilyPond Extra but need to be included in this commit in staging. Regards -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic)
Looked a bit furher into this, and seems to be an issue of the fontconfig
library. Was that upgraded between the binaries of 2.19.46 and 2.19.47?
Seems that in Lilypond 2.19.47 fontconfig is no longer having a cache/dir
checksum match for the system font library and thus rescans it on each run to
build the cache. On 2.19.46 it still shows a match.
Lilypond 2.19.46:
GNU LilyPond 2.19.46
FC_DEBUG=16
FcCacheTimeValid dir
"/Users/aikebah/Downloads/LilyPond2.19.46.app/Contents/Resources/share/lilypond/current/fonts/otf"
cache checksum 1469570231 dir checksum 1469570231
FcCacheTimeValid dir "/Library/Fonts" cache checksum 1458750870 dir checksum
1458750870
FcCacheTimeValid dir "/System/Library/Fonts" cache checksum 1458750878 dir
checksum 1458750878
Verwerken van 'test.ly'
Ontleden...
Vertolken van muziek...
Voorbewerken van grafische objecten...
Zoeken naar het ideale aantal pagina's...Fontconfig warning: ignoring UTF-8:
not a valid region tag
Muziek passend maken voor 1 pagina...
Tekenen van systemen...
Opmaakuitvoer naar
'/var/folders/w1/2ppjzq0j4cj2wv3f06_rd6twgn/T//lilypond-GNcNkQ'...
Converteren naar 'test.pdf'...
Verwijderen van
'/var/folders/w1/2ppjzq0j4cj2wv3f06_rd6twgn/T//lilypond-GNcNkQ'...
Gelukt: compilatie is met succes voltooid
Lilypond 2.19.47:
GNU LilyPond 2.19.47
FC_DEBUG=16
FcCacheTimeValid dir
"/Users/aikebah/Downloads/LilyPond2.19.47.app/Contents/Resources/share/lilypond/current/fonts/otf"
cache checksum 1472556057 dir checksum 1472556057
FcCacheTimeValid dir "/Library/Fonts" cache checksum 1458750870 dir checksum
1458750870
charsets 281 -> 80 leaves 30419 -> 1687
FcDirCacheWriteDir dir "/System/Library/Fonts" file
"/Users/aikebah/.lilypond-fonts.cache-2//b0a71e6bf6a8a1a908413a823d76e21f-i686-apple-darwin8.cache-7"
Verwerken van 'test.ly'
Ontleden...
Vertolken van muziek...
Voorbewerken van grafische objecten...
Zoeken naar het ideale aantal pagina's...Fontconfig warning: ignoring UTF-8:
not a valid region tag
Muziek passend maken voor 1 pagina...
Tekenen van systemen...
Opmaakuitvoer naar
'/var/folders/w1/2ppjzq0j4cj2wv3f06_rd6twgn/T//lilypond-JVrgSZ'...
Converteren naar 'test.pdf'...
Verwijderen van
'/var/folders/w1/2ppjzq0j4cj2wv3f06_rd6twgn/T//lilypond-JVrgSZ'...
Gelukt: compilatie is met succes voltooid
> On 05 Sep 2016, at 00:20, Hans Aikema wrote:
>
> On 04 Sep 2016, at 19:42, Cynthia Karl wrote:
>>
>>
>>> Message: 5
>>> Date: Sun, 4 Sep 2016 17:41:42 +0200
>>> From: Jacques Menu Muzhic
>>> To: Andrew Bernard
>>> Cc: Jacques Menu Muzhic ,lilypond-user
>>>
>>> Subject: Re: v2.19.47 on Mac x86
>>> I run El Capitan 10.11.6:
>>>
>>> menu@macbookprojm:~/Documents/LaTeX/PartitionsLilypond > uname -a
>>> Darwin macbookprojm 15.6.0 Darwin Kernel Version 15.6.0: Mon Aug 29
>>> 20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64 x86_64
>>>
>>> and I get:
>>>
>>> menu@macbookprojm:~ > sudo dtruss lilypond --version
>>
>>
>> I run El Capitan 10.11.6 and get the exact same output for “uname -a”.
>>
>> I wanted to see what the difference was between v2.19.46 and v2.19.47, so I
>> ran them both on the following file:
>>
>> bash-3.2$ cat 1note.ly
>> \version "2.19.46"
>> { c4 }
>>
>> <….>
>
>> I then ran dtruss -c on both versions to see what the difference in system
>> calls was.
>>
>> The following table shows the number of system calls which have a Count >
>> 100 for the v2.19.47 version and the corresponding count for the v2.19.46
>> version:
>>
>> CALL COUNT LP46 COUNT LP47
>> …… …
>> getattrlist 112 128
>> stat 178 171
>> stat64 207 207
>> sigaltstack 222 228
>> sigprocmask 263 269
>> select_nocancel 320 323
>> lseek 57 123013
>> read_nocancel341 125474
>>
>> I then did a count of the number of lseeks on file descriptors <= 13 (at
>> first glance there are no file descriptors greater than 12:
>>
>> lseek(0xfiledes v46 v47
>>
>> lseek(0x0 1 23
>> lseek(0x1 1 1
>> lseek(0x2 1 1
>> lseek(0x3 2 2
>> lseek(0x4 0 0
>> lseek(0x5 0 0
>> lseek(0x6 2 2
>> lseek(0x735 35
>> lseek(0x8 8 122969
>> lseek(0x9 3 3
>> lseek(0xA 11
>> lseek(0xB 33
>> lseek(0xC 00
Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic)
Discovered already that indeed a newer version of font-config is packaged with
2.19.47 (2.12.1 versus 2.11.95).
Most likely cause of the issue will be the 2.12.1 change that improved cache
validation logic (and for yet unknown reasons always invalidates the cache of
the Mac OS System fonts)
https://www.freedesktop.org/software/fontconfig/release/ChangeLog-2.12.1
> On 24 Sep 2016, at 12:55, Hans Aikema wrote:
>
> Looked a bit furher into this, and seems to be an issue of the fontconfig
> library. Was that upgraded between the binaries of 2.19.46 and 2.19.47?
>
> Seems that in Lilypond 2.19.47 fontconfig is no longer having a cache/dir
> checksum match for the system font library and thus rescans it on each run to
> build the cache. On 2.19.46 it still shows a match.
>
> Lilypond 2.19.46:
>
> GNU LilyPond 2.19.46
> FC_DEBUG=16
> FcCacheTimeValid dir
> "/Users/aikebah/Downloads/LilyPond2.19.46.app/Contents/Resources/share/lilypond/current/fonts/otf"
> cache checksum 1469570231 dir checksum 1469570231
> FcCacheTimeValid dir "/Library/Fonts" cache checksum 1458750870 dir checksum
> 1458750870
> FcCacheTimeValid dir "/System/Library/Fonts" cache checksum 1458750878 dir
> checksum 1458750878
> Verwerken van 'test.ly'
> Ontleden...
> Vertolken van muziek...
> Voorbewerken van grafische objecten...
> Zoeken naar het ideale aantal pagina's...Fontconfig warning: ignoring UTF-8:
> not a valid region tag
>
> Muziek passend maken voor 1 pagina...
> Tekenen van systemen...
> Opmaakuitvoer naar
> '/var/folders/w1/2ppjzq0j4cj2wv3f06_rd6twgn/T//lilypond-GNcNkQ'...
> Converteren naar 'test.pdf'...
> Verwijderen van
> '/var/folders/w1/2ppjzq0j4cj2wv3f06_rd6twgn/T//lilypond-GNcNkQ'...
> Gelukt: compilatie is met succes voltooid
>
>
>
>
> Lilypond 2.19.47:
>
> GNU LilyPond 2.19.47
> FC_DEBUG=16
> FcCacheTimeValid dir
> "/Users/aikebah/Downloads/LilyPond2.19.47.app/Contents/Resources/share/lilypond/current/fonts/otf"
> cache checksum 1472556057 dir checksum 1472556057
> FcCacheTimeValid dir "/Library/Fonts" cache checksum 1458750870 dir checksum
> 1458750870
>
> charsets 281 -> 80 leaves 30419 -> 1687
> FcDirCacheWriteDir dir "/System/Library/Fonts" file
> "/Users/aikebah/.lilypond-fonts.cache-2//b0a71e6bf6a8a1a908413a823d76e21f-i686-apple-darwin8.cache-7"
> Verwerken van 'test.ly'
> Ontleden...
> Vertolken van muziek...
> Voorbewerken van grafische objecten...
> Zoeken naar het ideale aantal pagina's...Fontconfig warning: ignoring UTF-8:
> not a valid region tag
>
> Muziek passend maken voor 1 pagina...
> Tekenen van systemen...
> Opmaakuitvoer naar
> '/var/folders/w1/2ppjzq0j4cj2wv3f06_rd6twgn/T//lilypond-JVrgSZ'...
> Converteren naar 'test.pdf'...
> Verwijderen van
> '/var/folders/w1/2ppjzq0j4cj2wv3f06_rd6twgn/T//lilypond-JVrgSZ'...
> Gelukt: compilatie is met succes voltooid
>
>
>
>> On 05 Sep 2016, at 00:20, Hans Aikema wrote:
>>
>> On 04 Sep 2016, at 19:42, Cynthia Karl wrote:
>>>
>>>
Message: 5
Date: Sun, 4 Sep 2016 17:41:42 +0200
From: Jacques Menu Muzhic
To: Andrew Bernard
Cc: Jacques Menu Muzhic , lilypond-user
Subject: Re: v2.19.47 on Mac x86
I run El Capitan 10.11.6:
menu@macbookprojm:~/Documents/LaTeX/PartitionsLilypond > uname -a
Darwin macbookprojm 15.6.0 Darwin Kernel Version 15.6.0: Mon Aug 29
20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64 x86_64
and I get:
menu@macbookprojm:~ > sudo dtruss lilypond --version
>>>
>>>
>>> I run El Capitan 10.11.6 and get the exact same output for “uname -a”.
>>>
>>> I wanted to see what the difference was between v2.19.46 and v2.19.47, so I
>>> ran them both on the following file:
>>>
>>> bash-3.2$ cat 1note.ly
>>> \version "2.19.46"
>>> { c4 }
>>>
>>> <….>
>>
>>> I then ran dtruss -c on both versions to see what the difference in system
>>> calls was.
>>>
>>> The following table shows the number of system calls which have a Count >
>>> 100 for the v2.19.47 version and the corresponding count for the v2.19.46
>>> version:
>>>
>>> CALLCOUNT LP46 COUNT LP47
>>> … … …
>>> getattrlist 112 128
>>> stat178
>>> 171
>>> stat64 207 207
>>> sigaltstack 222 228
>>> sigprocmask 263 269
>>> select_nocancel 320 323
>>> lseek 57 123013
>>> read_nocancel 341 125474
>>>
>>> I then did a count of the number of lseeks on file descriptors <= 13 (at
>>> first glance there are no file descriptors greater than 12:
>>>
>>> lseek(0xfile
Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic)
> Most likely cause of the issue will be the 2.12.1 change that > improved cache validation logic (and for yet unknown reasons always > invalidates the cache of the Mac OS System fonts) > > https://www.freedesktop.org/software/fontconfig/release/ChangeLog-2.12.1 Aah, this rings a bell. https://bugs.freedesktop.org/show_bug.cgi?id=97546 The proposed fix hasn't been applied yet to the fontconfig git repository – maybe we should downgrade GUB's fontconfig version to 2.12.0 until this is fixed. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Staging not merging with master - make website fails
Hello James, Thanks for your message. I was wondering what had gone wrong... What's the best way to fix things from here? Should I back out my commit on staging and redo the push with a new patch with images included? I'm not sure how to back out a commit on a remote branch... Locally I would just do: git checkout staging git reset --hard HEAD~ Would it work to just do: git checkout origin/staging git reset --hard HEAD~ I'll wait until I hear back before doing anything. Thanks again, -Paul On 09/24/2016 06:48 AM, James Lowe wrote: Hello, commit29941d96aa9942cfe914440b90b49ff7e015742e From Paul is missing its image files - they have been uploaded into LilyPond Extra but need to be included in this commit in staging. Regards ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Staging not merging with master - make website fails
I think you will definitely have to back out the current commit, add the images and repush to staging. My notes on how to do this: Removing and recreating staging --- First do something like git fetch git log -3 origin/staging to be really, really sure what commit you want to have in staging rather than the one that currently is there, and that you are sure that you will only lose your own commit and nothing else. Then do git push origin :staging git push origin commit-id-that-you-actually-wanted:refs/heads/staging The first line deletes the staging branch, the second reestablishes it. Then push your new patch. -- Phil Holmes - Original Message - From: "Paul" To: Sent: Saturday, September 24, 2016 2:02 PM Subject: Re: Staging not merging with master - make website fails Hello James, Thanks for your message. I was wondering what had gone wrong... What's the best way to fix things from here? Should I back out my commit on staging and redo the push with a new patch with images included? I'm not sure how to back out a commit on a remote branch... Locally I would just do: git checkout staging git reset --hard HEAD~ Would it work to just do: git checkout origin/staging git reset --hard HEAD~ I'll wait until I hear back before doing anything. Thanks again, -Paul On 09/24/2016 06:48 AM, James Lowe wrote: Hello, commit29941d96aa9942cfe914440b90b49ff7e015742e From Paul is missing its image files - they have been uploaded into LilyPond Extra but need to be included in this commit in staging. Regards ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Staging not merging with master - make website fails
On 09/24/2016 09:56 AM, Phil Holmes wrote: I think you will definitely have to back out the current commit, add the images and repush to staging. My notes on how to do this: Thanks Phil! That worked. My new patch is now pushed to staging with the images added (commit message is the same as before). -Paul ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic)
>> Most likely cause of the issue will be the 2.12.1 change that >> improved cache validation logic (and for yet unknown reasons always >> invalidates the cache of the Mac OS System fonts) >> >> https://www.freedesktop.org/software/fontconfig/release/ChangeLog-2.12.1 > > Aah, this rings a bell. > > https://bugs.freedesktop.org/show_bug.cgi?id=97546 > > The proposed fix hasn't been applied yet to the fontconfig git > repository – maybe we should downgrade GUB's fontconfig version to > 2.12.0 until this is fixed. I think that there is another possible solution. To use the proposed patch in GUB. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: v2.19.47 on Mac x86 (Jacques Menu Muzhic)
>> https://bugs.freedesktop.org/show_bug.cgi?id=97546 >> >> The proposed fix hasn't been applied yet to the fontconfig git >> repository – maybe we should downgrade GUB's fontconfig version to >> 2.12.0 until this is fixed. > > I think that there is another possible solution. To use the > proposed patch in GUB. Certainly. However, I can't estimate whether there aren't side effects... On the other hand, given that the patch is from the fontconfig maintainer, there are high chances that it is the right one :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Staging not merging with master - make website fails
- Original Message - From: "Paul" To: "Phil Holmes" ; Sent: Saturday, September 24, 2016 3:23 PM Subject: Re: Staging not merging with master - make website fails On 09/24/2016 09:56 AM, Phil Holmes wrote: I think you will definitely have to back out the current commit, add the images and repush to staging. My notes on how to do this: Thanks Phil! That worked. My new patch is now pushed to staging with the images added (commit message is the same as before). -Paul And by the wonder that is the website build, you'll see that lilypond.org is already showing the new front page. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Staging not merging with master - make website fails
On 09/24/2016 12:55 PM, Phil Holmes wrote: And by the wonder that is the website build, you'll see that lilypond.org is already showing the new front page. Indeed! Very nice. One problem... the news page is redirecting to the home page because the htaccess file here: Documentation/web/server/lilypond.org.htaccess has these lines (46-47): # the new website has news on the main page RedirectMatch ^/news/ (Of course this didn't show up in local testing, and I didn't think to check the htaccess rewrite rules. Sorry about that.) So we should remove those lines to fix it. How to proceed? Let me know what I can do. I'm can prepare a separate commit to remove those lines, or we can back out the current commit and I can make a new commit that has the htaccess changes. -Paul ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
