This is really a bug in liborbit2, right? Same as: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266376