Hi all, Sorry for being out of touch - other obligations caught up with me.
I'm not sure how to proceed on the bugs.lilypond.org side. The Allura server there is operational (visit the site to see), but - as Federico points out - we don't have working HTTPS connections. It looks like the GNU certificate only covers *.gnu.org domains, which bugs.lilypond.org isn't. I believe someone suggested renaming the site something like "bugs-lilypond.gnu.org" or "lilypond-bugs.gnu.org", which would allow wildcard coverage from the certificate. I don't believe the change can be made on our end (but I couldn't say for sure). More advanced Apache-wrangling than what I've managed to get the Allura application online is outside my knowledge. Best On Tue, Sep 1, 2015 at 8:31 PM Federico Bruni <f...@inventati.org> wrote: > Il giorno dom 30 ago 2015 alle 17:57, Trevor Daniels > <t.dani...@treda.co.uk> ha scritto: > > I've not heard anything from Federico or Josiah for over a week, so > > I've no idea what state Allura at Savannah is in. I suggest we wait > > a few days for news before inviting devs to join at SF, in case the > > Savannah system comes on line soon. > > I gave up with Allura. I started working on it just "by accident". > Josiah has the skills to work on it, while I don't. > > There's no https connection at the moment but I _think_ that nobody is > working on a solution: > http://bugs.lilypond.org/ > > > > > _______________________________________________ > 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
