lintian: r13 - in trunk: debian private
Author: jeroen
Date: 2004-02-08 21:56:42 +0100 (Sun, 08 Feb 2004)
New Revision: 13
Modified:
trunk/debian/control
trunk/debian/prerm
trunk/private/TODO
Log:
- Make lintian itself policy 3.6.1 compliant (by not prompting at all in
prerm, purging is intentionally removing everything lintian-related)
- Update description to say lintian is ready for 3.6.1
- Remove obsolete TODO entry
Modified: trunk/debian/control
===================================================================
--- trunk/debian/control 2004-02-08 20:27:22 UTC (rev 12)
+++ trunk/debian/control 2004-02-08 20:56:42 UTC (rev 13)
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Josip Rodin <joy-packages@debian.org>
Build-Depends-Indep: debiandoc-sgml
-Standards-Version: 3.5.10
+Standards-Version: 3.6.1
Package: lintian
Architecture: all
@@ -25,4 +25,4 @@
should check packages with this tool before uploading them to the
archive.
.
- This version of Lintian is calibrated for policy version 3.5.10.
+ This version of Lintian is calibrated for policy version 3.6.1.
Modified: trunk/debian/prerm
===================================================================
--- trunk/debian/prerm 2004-02-08 20:27:22 UTC (rev 12)
+++ trunk/debian/prerm 2004-02-08 20:56:42 UTC (rev 13)
@@ -5,7 +5,5 @@
fi
if [ "$1" = "purge" ]; then
-# to-do: check for the existance of useful files in the lab
- echo -n " Shall I also remove the whole lintian tree (no/yes)? "; read ans
- case $ans in [yY]*) lintian --remove-lab;; esac
+ lintian --remove-lab
fi
Modified: trunk/private/TODO
===================================================================
--- trunk/private/TODO 2004-02-08 20:27:22 UTC (rev 12)
+++ trunk/private/TODO 2004-02-08 20:56:42 UTC (rev 13)
@@ -9,9 +9,6 @@
that the controller script can open and use. Probably some OO design.
I am leaning towards python, but will give OO perl a look first.
-policy 3.5 updates, which means reading policy and ensuring lintian follows it
-then I need to updater lintian to know about 3.5.
-
various items require the policy team to make a new policy or update existing
need to keep on them about this
* libs v. plugins
Reply to: