The problem seems to be the UIMA DOAP; it has the following tag: <asfext:pmc rdf:about="UIMA">
Normal DOAPs have tags of the form: <asfext:pmc rdf:resource="http://vcl.apache.org" /> The template utils.xsl tries to extract the PMC name (in <xsl:template match="asfext:pmc") and fails. It's easy enough to do more checks on the asfext:pmc attributes, and I can add a message to display an error if the format is unexpected, but I'm having problems including suitable context in the output. On 27 April 2015 at 23:35, David Crossley <cross...@apache.org> wrote: > On Mon, Apr 27, 2015 at 07:52:37AM -0400, Shane Curcuru wrote: >> Just a quick note: I'm pretty confident the medium term plan is to >> replace the entire projects.a.o build system (rather complicated, >> involving multiple steps in Perl and XSLT) with the software behind the >> projects-new.apache.org site. Thus, I highly recommend looking at the >> below work instead of doing anything with the old Perl! > > Yes, but as i tried to explain, the old projects.a.o build has the DOAP > files. They are imported by an irregular manually-started build > process to feed the projects-new.a.o site. > > The old site was working fine until recently (see below). > It is now broken. Therefore i presume that the new site cannot > be updated. > > Over and out. > > -David > >> Discussion on making changes to the code: >> https://mail-archives.apache.org/mod_mbox/community-dev/201503.mbox/%3C1935041.Ku0l4cXdRX%40herve-desktop%3E >> >> Vote thread to start the process: >> https://mail-archives.apache.org/mod_mbox/community-dev/201503.mbox/%3C54F9DB53.1030005%40redhat.com%3E >> >> Sources and docs for projects-new: >> https://projects-new.apache.org/about.html >> >> - Shane >> >> On 4/27/15 4:51 AM, Sergio Fernández wrote: >> > Hi David, >> > >> > I could help on the doap part, but I see that part of the site is built >> > using Perl, so I have an issue with that: on the one hand it's language I >> > never felt comfortable with, on the other the RDF support is very limited. >> > >> > Therefore, before jumping to the see, I'd like to ask you guys a couple of >> > details: how much that part of the site is build on doap? and how actively >> > maintained is it? Before I could commit some time to branch it and refactor >> > it to Python for instance, where I'm more skilled and I can warranty better >> > RDF pipeline. >> > >> > So comments from you are welcomed. >> > >> > Cheers, >> > >> > >> > >> > >> > >> > On Sat, Apr 25, 2015 at 3:20 AM, David Crossley <cross...@apache.org> >> > wrote: >> > >> >> The 3-hourly processing of the list of DOAP files for people.apache.org >> >> site >> >> has been spewing errors for many days. >> >> >> >> I do not know enough about how the site build works >> >> (see >> >> https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects) >> >> and i do not have it installed locally. >> >> >> >> I have done some investigation. >> >> This error message on 2015-04-17 at 15:30 was the first: >> >> >> >> http://mail-archives.apache.org/mod_mbox/www-site-dev/201504.mbox/%3c20150417153422.0b7c817...@minotaur.apache.org%3e >> >> >> >> These are the only likely changes that i can find >> >> leading up to the error: >> >> >> >> Author: hboutemy >> >> Date: Tue Apr 14 00:31:26 2015 >> >> URL: http://svn.apache.org/r1673325 >> >> Log: s/asfext:PMC/asfext:pmc/ to match the extension >> >> >> >> Author: gmcdonald >> >> Date: Tue Apr 14 10:28:09 2015 >> >> URL: http://svn.apache.org/r1673402 >> >> Log: remove zookeeper entry for now >> >> Modified: infrastructure/site-tools/trunk/projects/pmc_list.xml >> >> (Note that there is still a zookeeper entry in >> >> site-tools/trunk/projects/files.xml if that matters. >> >> The commit comment is not useful.) >> >> >> >> However those were a few days before this error started, so they >> >> do not seem likely. >> >> >> >> Perhaps it is coming from a remote project DOAP file, >> >> but the build system does not report which file it is having >> >> trouble with. >> >> >> >> These files also are utilised for people-new.apache.org with a manual >> >> import at present. >> >> >> >> That is all that i have time to do, so hopefully this helps >> >> someone else to go further. >> >> >> >> -David