Re: WD Update delayed

perfect :D!
-------- Original message --------From: Gregg Kellogg <gregg@greggkellogg.net> Date: 5/10/19  06:59  (GMT+01:00) To: Simon Steyskal <simon.steyskal@wu.ac.at> Cc: W3C JSON-LD Working Group <public-json-ld-wg@w3.org> Subject: Re: WD Update delayed Actually, there was a build failure. I re-ran it and success! Thanks so much for your help. Gregg KelloggSent from my iPhone> On May 9, 2019, at 9:27 PM, Simon Steyskal <simon.steyskal@wu.ac.at> wrote:> > Hi!> >> Great suggestion, but it’s still failing. The fact that it things its>> using Specberus and not ReSpec is telling.> > I think Specberus is in general always running.. (see e.g., a successful WD publication of the Publishing WG [1])> > When comparing their status report [2] to ours [3] I noticed that in our latest failed attempt "thisVersion" still contains a ; instead of &.> > "thisVersion": "https://www.w3.org/TR/2019/WD;shortName=json-ld11-json-ld11-20190509/",> > so I checked https://w3c.github.io/json-ld-syntax/ECHIDNA and saw that it still contains a ; instead of & ...> > I think you've only pushed your changes to the publication branch, but not the main branch where Specberus seems to fetch the ECHIDNA file from..> > br simon> > > [1] https://lists.w3.org/Archives/Public/public-tr-notifications/2019Apr/0006.html> [2] https://labs.w3.org/echidna/api/status?id=fec173dd-c037-44ff-905d-b6d5d0d6b471> [3] https://labs.w3.org/echidna/api/status?id=1504c6f3-3516-4e4d-a832-5de8a5dfd1f2> ---> DDipl.-Ing. Simon Steyskal> Institute for Information Business, WU Vienna> > www: http://www.steyskal.info/  twitter: @simonsteys> > Am 2019-05-09 07:58, schrieb Gregg Kellogg:>> Great suggestion, but it’s still failing. The fact that it things its>> using Specberus and not ReSpec is telling.>> Gregg Kellogg>> gregg@greggkellogg.net>>> On May 8, 2019, at 10:49 PM, Simon Steyskal <simon.steyskal@wu.ac.at> wrote:>>> apparently yes.. they changed from ; to & on 5th of March (see https://github.com/w3c/echidna/wiki/How-to-use-Echidna-with-ReSpec-and-GitHub/_history)>>> br simon>>> --->>> DDipl.-Ing. Simon Steyskal>>> Institute for Information Business, WU Vienna>>> www: http://www.steyskal.info/  twitter: @simonsteys>>> Am 2019-05-09 07:47, schrieb Gregg Kellogg:>>>> Thanks for the suggestion, I’ll give it a shot. It worked on the last>>>> release, but that could have been luck.>>>> Gregg Kellogg>>>> Sent from my iPhone>>>>>> On May 8, 2019, at 10:44 PM, Simon Steyskal <simon.steyskal@wu.ac.at> wrote:>>>>>> Hi!>>>>>> # ECHIDNA configuration>>>>>> index.html?specStatus=WD;shortName=json-ld11 respec>>>>> idk if this changes anything but according to https://github.com/w3c/echidna/wiki/How-to-use-Echidna-with-ReSpec-and-GitHub#actually-publishing this should be>>>>> # ECHIDNA configuration>>>>> index.html?specStatus=WD&shortName=json-ld11 respec>>>>> i.e., s/;/&/>>>>> hth, simon>>>>> --->>>>> DDipl.-Ing. Simon Steyskal>>>>> Institute for Information Business, WU Vienna>>>>> www: http://www.steyskal.info/  twitter: @simonsteys>>>>> Am 2019-05-08 18:22, schrieb Gregg Kellogg:>>>>>> There’s an issue with Echidna which is delaying the update of the specs.>>>>>> The failure was noted on the mailing list [1], and I filed a bug>>>>>> report [2]. Unfortunately, no response as of yet.>>>>>> As you can see, it seems to think this isn’t a WD and is running>>>>>> Specberus rather than ReSpec; the ECHIDNA configuration is unchanged>>>>>> from the last publication.>>>>>> Once this is resolved, I’ll attempt to publish API and Framing specs too.>>>>>> Gregg Kellogg>>>>>> gregg@greggkellogg.net>>>>>> [1]>>>>>> https://lists.w3.org/Archives/Public/public-tr-notifications/2019May/0002.html>>>>>> [2] https://github.com/w3c/echidna/issues/669>>> <echidna.PNG>