REVU-Tools

Differences between revisions 1 and 4 (spanning 3 versions)
⇤ ← Revision 1 as of 2006-02-04 12:52:48 →
Size: 1035
Editor: bur91-2-82-231-159-240
Comment:
← Revision 4 as of 2006-02-06 21:32:01 → ⇥
Size: 2486
Editor: bur91-2-82-231-159-240
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
If you are a review admin, wanting to review a package $package updated on date $date, and $url is the url of the $upstream tarball, run If you are a review admin, wanting to review a $package updated on $date, and $url is the url of the $upstream tarball, run
Line 17: Line 17:
revu-report $package_blahblah.dsc $upstream revu-report
Line 21: Line 21:
This will generate report files in the current directory. This will generate report files in the current directory, that will appear on the REVU interface.
Line 23: Line 23:
The file to look at is REVU_report, that gathers most of the useful informations gotten from the scripts :
 * Whether the package FTBFS
 * Whether the upstream tarball has been changed
 * Whether `debuild && debuild -S -sa` generates files in diff.gz outside of debian/
 * Whether lintian and linda are happy about the package		 Note: revu-report detects the dsc, the orig and the upstream tarball automagically. If there are several dsc files in the directory and/or several files that could be upstream tarballs, you'll have to run:

{{{
cd /var/revu/revu1-incoming/$package-$date
wget $url
revu-report $tarball $dscfile
}}}


Tip: Since version 0.3, revu-orig uses uscan to take advantage of debian/watch files in the package and get the upstream tarball automagically. Therefore, it is not necessary to download the upstream tarball anymore in many cases, just run :

{{{
cd /var/revu/revu1-incoming/$package-$date
revu-report
}}}

If files are missing to generate the report and there is no debian/watch, then it will be said so in the report, and you can get the upstream tarball manually and run the command again.


The main file to look at is REVU_report, that gathers most of the useful informations gotten from the scripts :
 * Whether there is a usable debian/watch file in the package ;
 * Whether the is a new upstream tarball available ;
 * Whether the package is a Debian-native (no orig.tar.gz + diff.gz) ;
 * Whether the package FTBFS ;
 * Whether the upstream tarball has been changed or repacked ;
 * Whether `debuild && debuild -S -sa` generates files in diff.gz outside of debian/ ;
 * Whether lintian and linda are happy about the package.


Since version 0.3.1, REVU-tools have been made into a REVU-independant deb package, available on http://revu.tauware.de/~raphink/debs/ . This package is made to work on any system, but might require to adjust some settings in the scripts.
In particular, you might want to change PBUILDERNAME in /usr/bin/revu-build (on my machine, I use "sudo pbuilder", on REVU it's "pbuilder-dapper") to have it fit with your settings.

What is REVU-Tools

REVU-Tools is a set of scripts used on [:REVU] to automatize the reviewing process.

It is included in the REVU svn, and distributed on http://revu.tauware.de/~raphink .

How to use it

On [:REVU], only REVU admins can run these tools. If you are not a REVU admin, ask one to run it on the package you want to review.

If you are a review admin, wanting to review a $package updated on $date, and $url is the url of the $upstream tarball, run 

cd /var/revu/revu1-incoming/$package-$date
wget $url
revu-report

This will generate report files in the current directory, that will appear on the REVU interface.

Note: revu-report detects the dsc, the orig and the upstream tarball automagically. If there are several dsc files in the directory and/or several files that could be upstream tarballs, you'll have to run: 

cd /var/revu/revu1-incoming/$package-$date
wget $url
revu-report $tarball $dscfile

Tip: Since version 0.3, revu-orig uses uscan to take advantage of debian/watch files in the package and get the upstream tarball automagically. Therefore, it is not necessary to download the upstream tarball anymore in many cases, just run : 

cd /var/revu/revu1-incoming/$package-$date
revu-report

If files are missing to generate the report and there is no debian/watch, then it will be said so in the report, and you can get the upstream tarball manually and run the command again.

The main file to look at is REVU_report, that gathers most of the useful informations gotten from the scripts :

  • Whether there is a usable debian/watch file in the package ;
  • Whether the is a new upstream tarball available ;
  • Whether the package is a Debian-native (no orig.tar.gz + diff.gz) ;
  • Whether the package FTBFS ;
  • Whether the upstream tarball has been changed or repacked ;

  • Whether debuild && debuild -S -sa generates files in diff.gz outside of debian/ ;

  • Whether lintian and linda are happy about the package.

Since version 0.3.1, REVU-tools have been made into a REVU-independant deb package, available on http://revu.tauware.de/~raphink/debs/ . This package is made to work on any system, but might require to adjust some settings in the scripts. In particular, you might want to change PBUILDERNAME in /usr/bin/revu-build (on my machine, I use "sudo pbuilder", on REVU it's "pbuilder-dapper") to have it fit with your settings.

[:CategoryMOTU]

MOTU/Packages/REVU/REVU-Tools (last edited 2009-05-10 20:16:29 by 213-148-201-39)