tags 480545 + patch
thanks

Adding adduser (since postinst uses addgroup) to dependencies, as Ben
Hutchings suggested, seems to make vlock pass piuparts test.

Fixed incorrect debian/NEWS syntax while at it.

Suggested NMU diff attached, will upload soon unless there are any
objections.

HTH, HAND.

-- 
Regards,
Andreas Henriksson
diff -u vlock-2.1/debian/changelog vlock-2.1/debian/changelog
--- vlock-2.1/debian/changelog
+++ vlock-2.1/debian/changelog
@@ -1,3 +1,11 @@
+vlock (2.1-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add dependency on adduser since postinst uses addgroup (Closes: #480545)
+  * Fix indentation of debian/NEWS.
+
+ -- Andreas Henriksson <[EMAIL PROTECTED]>  Tue, 20 May 2008 23:28:03 +0200
+
 vlock (2.1-2) unstable; urgency=low
 
   * Fix copyright file 
diff -u vlock-2.1/debian/control vlock-2.1/debian/control
--- vlock-2.1/debian/control
+++ vlock-2.1/debian/control
@@ -8,7 +8,7 @@
 
 Package: vlock
 Architecture: any
-Depends: ${shlibs:Depends}, libpam-modules
+Depends: ${shlibs:Depends}, libpam-modules, adduser
 Conflicts: suidmanager (<< 0.50)
 Description: Virtual Console locking program
  vlock either locks the current terminal (which may be any kind of
diff -u vlock-2.1/debian/NEWS vlock-2.1/debian/NEWS
--- vlock-2.1/debian/NEWS
+++ vlock-2.1/debian/NEWS
@@ -1,11 +1,11 @@
 vlock (2.0-1) unstable; urgency=low
 
- vlock 2.0 expands the user's ability to lock a machine in two ways.  First is
- the ability to lock the entire console display without access to a virtual
- console, i.e. from an X11 or even an SSH session.  Secondly, SysRQ keys may be
- disabled while the entire console display is locked.  These two operations are
- priviledged and should be restricted.  Therefore, to be allowed to do either
- of these a user must be added to the group 'vlock'.  See
- /usr/share/doc/vlock/SECURITY for more information.
+  vlock 2.0 expands the user's ability to lock a machine in two ways. First is
+  the ability to lock the entire console display without access to a virtual
+  console, i.e. from an X11 or even an SSH session. Secondly, SysRQ keys may be
+  disabled while the entire console display is locked. These two operations are
+  priviledged and should be restricted. Therefore, to be allowed to do either
+  of these a user must be added to the group 'vlock'. See
+  /usr/share/doc/vlock/SECURITY for more information.
  
  -- Alexander Wirt <[EMAIL PROTECTED]>  Mon, 13 Aug 2007 19:39:12 +0200

Reply via email to