Zeitgeist Framework

raptor2 not supported

Bug #807076 reported by Siegfried Gevatter on 2011-07-07

328

This bug affects 129 people

	Status	Importance	Assigned to	Milestone
Redland librdf	Fix Released	Unknown	librdf-mantis #451
Zeitgeist Framework	Invalid	High	Unassigned	Zeitgeist Framework 0.8.2
raptor2 (Ubuntu)	Fix Released	High	Unassigned
Oneiric	Fix Released	High	Unassigned

Bug Description

Ubuntu seems to have switched to some new Raptor which seems to fail really badly:

make[3]: Entering directory `/tmp/buildd/zeitgeist-0.8.1/extra/ontology'
echo -e "#\n# Auto-generated from zg.trig. Do not edit\n#" > zg.py
rapper -i trig -o rdfxml zg.trig | ../../extra/rdfxml2py >> zg.py
rapper: Parsing URI file:///tmp/buildd/zeitgeist-0.8.1/extra/ontology/zg.trig with parser trig
rapper: Serializing with serializer rdfxml
rapper: Error - - The namespace prefix in "zg" was not declared.
rapper: Error - URI file:///tmp/buildd/zeitgeist-0.8.1/extra/ontology/zg.trig:17 - turtle_qname_to_uri failed
rapper: Parsing returned 0 triples
Parsing from stdin
echo -e "#\n# Auto-generated from nie.trig. Do not edit\n#" > nie.py
rapper -i trig -o rdfxml nie.trig | ../../extra/rdfxml2py >> nie.py
rapper: Parsing URI file:///tmp/buildd/zeitgeist-0.8.1/extra/ontology/nie.trig with parser trig
rapper: Serializing with serializer rdfxml
rapper: Error - - The namespace prefix in "nie" was not declared.
rapper: Error - URI file:///tmp/buildd/zeitgeist-0.8.1/extra/ontology/nie.trig:56 - turtle_qname_to_uri failed
rapper: Parsing returned 0 triples
Parsing from stdin

Siegfried Gevatter (rainct) on 2011-07-07

Changed in zeitgeist:
assignee:	nobody → Siegfried Gevatter (rainct)
importance:	Undecided → Low
milestone:	none → 0.8.2
status:	New → In Progress

Revision history for this message

3vi1 (launchpad-net-eternaldusk) wrote on 2011-07-08:

If this is the cause of bug 807203, it might be a bit higher priority than low... as it causes the affected systems to go to 100% CPU respawning the ubuntu-one syncdaemon.

Revision history for this message

Didier Roche-Tolomelli (didrocks) wrote on 2011-07-08:

the switch to raptor2 has been done in https://launchpad.net/ubuntu/+source/zeitgeist/0.8.0-1ubuntu1.
We didn't get any crash then, until the update to 0.8.1

Revision history for this message

Markus Korn (thekorn) wrote on 2011-07-11:

The problem is not in zeitgeist itself, but in the recent version of raptor2-utils in ubuntu oneiric.
See http://bugs.librdf.org/mantis/view.php?id=451 for the upstream bugreport.

Siegfried Gevatter (rainct) on 2011-07-11

Changed in zeitgeist:
assignee:	Siegfried Gevatter (rainct) → nobody
status:	In Progress → Triaged

Revision history for this message

Markus Korn (thekorn) wrote on 2011-07-11:

Affected version is raptor2-utils >= 2.0.2

Bug Watch Updater (bug-watch-updater) on 2011-07-14

Changed in librdf:
status:	Unknown → Fix Released

Seif Lotfy (seif) on 2011-07-14

Changed in zeitgeist:
status:	Triaged → In Progress

Revision history for this message

Brendan Donegan (brendan-donegan) wrote on 2011-07-15:

The fixing of this bug seems well under way - so should be Triaged. Also the duplicate was High (and should have been) so this should also be High (can't do anything about the Importance in the upstream project unfortunately)

Changed in zeitgeist (Ubuntu):
importance:	Undecided → High
status:	New → Triaged

Revision history for this message

Seif Lotfy (seif) wrote on 2011-07-18:

Did some patch and package python-rdflib with the fix or not?

Changed in zeitgeist:
importance:	Low → High

Revision history for this message

Mikkel Kamstrup Erlandsen (kamstrup) wrote on 2011-07-19:

Phew - after much fiddling about I got raptor build from a git checkout and indeed the 'rapper' build from raptor trunk fixes this as described in the upstream bug report.

Caveat distropatcheum: The upstream patch requires a re-autogen as it changes some of the flex source files that are used to generate some of the distributed source files. Unfortunately this re-autogen will fail since autogen.sh requires some files that are not shipped in the tarball. So; you must check out the 2.0.3 revision, apply the patch, and reroll the tarball or something...

Revision history for this message

Ted Gould (ted) wrote on 2011-07-19: Re: [Bug 807076] Re: raptor2 not supported

On Tue, 2011-07-19 at 11:30 +0000, Mikkel Kamstrup Erlandsen wrote:
> Caveat distropatcheum: The upstream patch requires a re-autogen as it
> changes some of the flex source files that are used to generate some of
> the distributed source files. Unfortunately this re-autogen will fail
> since autogen.sh requires some files that are not shipped in the
> tarball. So; you must check out the 2.0.3 revision, apply the patch, and
> reroll the tarball or something...

Yeah, generate the patch. Reroll tarball. Then make the diff from that
tarball to the previous one. That'll make the "final patch" include all
the Makefile and other build file changes as well. PITA, but works :-)

--Ted

Revision history for this message

Siegfried Gevatter (rainct) wrote on 2011-07-23:

(According to Travis Hansen 2.0.2 works fine and only 2.0.3 is affected.)

Revision history for this message

Michael Terry (mterry) wrote on 2011-08-26:

#10

raptor2 (2.0.4-1) unstable; urgency=low

  * New upstream release (Closes: #632836)
  * debian/libraptor2-0.shlibs: 2.0.4 (Closes: #635003)
  * debian/control: libraptor2-dev recommends raptor2-utils (Closes: #625910)
  * debian/rules: use make distclean to avoid destroying docs/html

-- Dave Beckett <email address hidden> Mon, 25 Jul 2011 23:36:14 -0700