[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

deb-check 0.1 uploaded to master.debian.org



hy.

i have rewritten my script to check debian packages in tcl and uploaded
it to master (deb-check_0.1_all.deb, will be placed into experimental).

- output goes to standart out, will be mailed to an email adress, or
  (untested) to the Maintainer
- will check either directories or .deb files

reports warnings:
- usr/doc/PACKAGE/changelog.Debian.gz	this file should exist
- usr/doc/PACKAGE/changelog.gz		this file should exist
- usr/doc files > 10k, not .gz	large files in usr/doc should be gzipped
- files/dirs not owned by root
- files/dirs not owned by group root
- dirs not mode 755
- files (non binaries, non shared lib) not mode 644 or 444
- files (binaries, shared lib) not mode 755
- non file/dir/symlinks	(take care what you're doing !)

reports bugs:
- usr/doc/copyright (new policy: /usr/doc/PACKAGE/copyright)
- usr/doc/exapmles  (new policy: /usr/doc/PACKAGE/exaples)
- usr/doc/PACKAGE		this directory must exist
- usr/doc/PACKAGE/copyright	this file must exist
- man pages, not .gz		man pages must be gzipped
- info files, not .gz		info files must be gzipped
- binary files w/out manpage	each file must have a manpage (or link
  					to undocumented)

what shall be done now ? i have a lot of bug reports, but most are yust old
standard (usr/doc/copyright|examples), uncompressed man pages and
binary without manpage. should i forward all bugs to submit@bugs ?
what about sending "info mails" to all developers ? what about new
packages / updates ? everyone can check his own package, but a little
daemon can also send info messages whenever new packages are uploaded...

regards andreas


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com


Reply to: