REVU Tools

Raphaël Pinson raphink at
Mon Feb 6 01:53:52 GMT 2006

Hello fellow MOTUs,

Just felt like writing a bit of bash tonight after dinner... and
worked on REVU-tools again.
I think I'll upload it to the REVU svn tomorrow, but if any of you
feel like giving some feedback, the tarball can be found at .

Changelog :

 - pbuilder-hooks/B01debuildtest :
        * Added directory name detection in
pbuilder-hooks/B01debuildtest to avoid a dirty cd /tmp/buildd/* ;

 - revu-build :
        * Cleaning files from previous runs in revu-build, revu-orig
and revu-report ;
        * Adding PBUILDERHOOKS variable to set the script cleanly ;

 - revu-orig :
        * revu-orig now takes two optional arguments (tarball and dsc)
and can auto-detect them if not given explicitely ;
        * Detecting orig.tar.gz automagically in revu-orig. Using it
as a variable now and detecting Debian-native packages ;
        * Adjusted tarball type detection in revu-orig to untar
upstream tarball ;

 - revu-report :
        * Inverted the tarball and dsc arguments in revu-report (since
tarball is harder to detect)  and made optional arguments ;
        * Automagically decting dsc and tarball in local folder ;
        * Adding report entries for Debian-native packages ;
        * Adapting md5 report entries depending on whether the
upstream tarball is tar.gz or other.



On 2/4/06, Raphaël Pinson <raphink at> wrote:
> Hello fellow MOTUs,
> Since I have based most of my work on reviewing packages so far, I
> have been interested in improving the tools on REVU, so that it would
> be possible to review a package entirely without having to use the
> console more than once.
> I have noticed that the main reasons to use the console to review
> packages were the following:
> 1) pbuilding the package
> 2) running a `debuild && debuild -S -sa` test for diff
> 3) comparing the md5 sums of the orig and upstream tarballs
> 4) checking the diff -ru of the untared orig and upstream tarballs if
> the md5 sums are different
> 1) is already achieved by revu-build on tiber. All other ones were
> lacking and had me get the files and my console on my machine.
> So I got to work to try and automatize all this.
> The result is a set of script, that I have added to the REVU svn
> (revu1 so far) and are waiting to be added to REVU. These scripts can
> be found at .
> When well set (sorry, haven't made a doc yet ...), running revu-report
> with two arguments (the dsc and the upstream tarball) will generated a
> few files and a full report.
> As examples, this is the report that it created with a dirty package :
> ;
> and this is what was created with a rather clean one :
> .
> I'm sure the reviewers of you see the use of such a tool : almost all
> the reviewing that is left can be checked by browsing the source
> packages on REVU.
> Note: there is still a need for a tool to check for the pre-existence
> of identical/similar packages in other sources (Debian,,
> etc.), and for a tool to automatically get the upstream tarball if
> that is ever possible to develop.
> I'm looking forward to comments and suggestions on it :)
> Cheers,
> Raphaël
> <raphink at>
> --
>   ----------------------------------------------------------------------------------------
> Raphaël Pinson - raphink at
> Ichthux - - Christian Linux Distribution

Raphaël Pinson - raphink at
Ichthux - - Christian Linux Distribution

More information about the Ubuntu-motu mailing list