[Piuparts-commits] rev 371 - trunk

[Holger Levsen]

Author: holger
Date: 2009-04-21 21:45:28 +0000 (Tue, 21 Apr 2009)
New Revision: 371

Modified:
   trunk/TODO
   trunk/piuparts.1.txt
Log:
improve layout

Modified: trunk/TODO
===================================================================
--- trunk/TODO	2009-04-21 08:51:14 UTC (rev 370)
+++ trunk/TODO	2009-04-21 21:45:28 UTC (rev 371)
@@ -3,14 +3,15 @@
 
 for 0.36:
 
-- report:
- - refactor code, sources.txt should not be calculated where it currently is
- - get rid of old log pages and put stats in the index page
+- broken packages should be moved to untestable, and untestable log files
+  should be deleted automatically after a week
 - then R
-- probably include patch for #519192 - not sure if i like that aproach
 - take care of old conf files on upgrades
 - take care of old pyc files from python-central
 - test pipuparts with piuparts before uploading
+- report:
+ - refactor code, sources.txt should not be calculated where it currently is
+ - get rid of old log pages and put stats in the index page
 - provides are not handled correctly: ie libapt-pkg-perl has a dependency on 
   libapt-pkg-libc6.7-6-4.6 which piuparts believes is an unknown-package while 
   in reality its provided by apt
@@ -32,6 +33,7 @@
 for 0.37:
 
 - probably include patch for #523950
+- probably include patch for #519192 - not sure if i like that aproach
 
 - report: 
  - write stats about the reasons for failures:

Modified: trunk/piuparts.1.txt
===================================================================
--- trunk/piuparts.1.txt	2009-04-21 08:51:14 UTC (rev 370)
+++ trunk/piuparts.1.txt	2009-04-21 21:45:28 UTC (rev 371)
@@ -128,23 +128,31 @@
 --------
 Assume that you have just built a new version of your Debian package, to be uploaded to Debian unstable. It is in _../foo_1.0-2_i386.deb_ and you would like to know whether it installs and uninstalls properly. Here's what you would do:
 
+----
 piuparts ../foo_1.0-2_i386.deb
+----
 
 If the package exists in the Debian archive already, the above command also tests that it upgrades properly.
 
 To do the same test, but using a particular mirror, and only the main component, you would do this:
 
+----
 piuparts -m 'http://gytha/debian main' ../foo_1.0-2_i386.deb
+----
 
 If you want to do the same as above but for your changes files, pass in your changes files when running piuparts, and piuparts will process each package in the changes files as though you had passed all those packages on the command line to piuparts yourself. For example:
 
+----
 piuparts ../foo_1.0-2_i386.changes
 
 piuparts -m 'http://gytha/debian main' ../foo_1.0-2_i386.changes
+----
 
 If you want to test that a package installs properly in the stable (etch) Debian release, then can be upgraded to the testing (lenny) and unstable (sid) versions, and then uninstalled without problems, you would give the following command:
 
+----
 piuparts -a -d etch -d lenny -d sid foo
+----
 
 ENVIRONMENT
 -----------