Your message dated Tue, 17 Jun 2008 15:32:05 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#486665: fixed in vlock 2.2.2-3
has caused the Debian Bug report #486665,
regarding FTBFS: install: invalid group `vlock'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
486665: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486665
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: vlock
Version: 2.2.2-2
Severity: serious

Fails to build on all architectures. I believe you'll want to chmod
the user and group at postinst stage rather than when building the
package...

On Tue, Jun 17, 2008 at 12:31:23PM +0000, Debian/armel Build Daemon wrote:
> mkdir -p -m 755 /build/buildd/vlock-2.2.2/debian/vlock//usr/lib/vlock/modules
> install -m 0750 -o root -g vlock new.so 
> /build/buildd/vlock-2.2.2/debian/vlock//usr/lib/vlock/modules/new.so
> install: invalid group `vlock'
> make[2]: *** [install-new.so] Error 1
> make[2]: Leaving directory `/build/buildd/vlock-2.2.2/modules'
> make[1]: *** [install-modules] Error 2
> make[1]: Leaving directory `/build/buildd/vlock-2.2.2'
> make: *** [install] Error 2
> dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary-arch gave 
> error exit status 2



--- End Message ---
--- Begin Message ---
Source: vlock
Source-Version: 2.2.2-3

We believe that the bug you reported is fixed in the latest version of
vlock, which is due to be installed in the Debian FTP archive:

vlock_2.2.2-3.diff.gz
  to pool/main/v/vlock/vlock_2.2.2-3.diff.gz
vlock_2.2.2-3.dsc
  to pool/main/v/vlock/vlock_2.2.2-3.dsc
vlock_2.2.2-3_i386.deb
  to pool/main/v/vlock/vlock_2.2.2-3_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Wirt <[EMAIL PROTECTED]> (supplier of updated vlock package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Tue, 17 Jun 2008 17:13:25 +0200
Source: vlock
Binary: vlock
Architecture: source i386
Version: 2.2.2-3
Distribution: unstable
Urgency: low
Maintainer: Alexander Wirt <[EMAIL PROTECTED]>
Changed-By: Alexander Wirt <[EMAIL PROTECTED]>
Description: 
 vlock      - Virtual Console locking program
Closes: 486665
Changes: 
 vlock (2.2.2-3) unstable; urgency=low
 .
   * Don't try to chgrp to "vlock" during build time (Closes: #486665)
   * Bump standards version (No changes)
Checksums-Sha1: 
 6020e934a7be79a6a1c04f1ff8e9d16548b3e5e9 1020 vlock_2.2.2-3.dsc
 d346d0a650a4f3253d77549f87faf859ddb1f5e6 6778 vlock_2.2.2-3.diff.gz
 74088556ba91011eb1d6cce98ae9cb76fb16b68d 38054 vlock_2.2.2-3_i386.deb
Checksums-Sha256: 
 60b2b389baacf0b2060b4223b233be6d674858f26c3f347662eb319f5803a8d7 1020 
vlock_2.2.2-3.dsc
 c11be9603687fe16e36bd43d7e5d9262f7689381481e08b6a199a26973bc093c 6778 
vlock_2.2.2-3.diff.gz
 38d908cc3f4c3466785bde79fceb1331ee40447993beaff433aa9c3424550368 38054 
vlock_2.2.2-3_i386.deb
Files: 
 ff9d306c74d80fe40c83683329bfff31 1020 utils optional vlock_2.2.2-3.dsc
 cec5c8db6b24bb662ac02042a038634f 6778 utils optional vlock_2.2.2-3.diff.gz
 7ec11530bbf871a7f4976cba8ede7c39 38054 utils optional vlock_2.2.2-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkhX1QMACgkQ01u8mbx9AgorvgCfTDP0iLlYzOh/hm4piayYONhy
uUwAnR01iRAfvyE502qWUg77id8zHYvc
=jwhl
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to