Your message dated Sun, 4 Nov 2007 15:04:37 +1100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#439431: wajig: debian/rules should generate md5sums 
control file
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: wajig
Version: 2.0.37
Severity: normal
Tags: patch


Debian policy recommends that all binary packages contain an 'md5sums'
control file. The following command shows that a package built from
this source package does not contain this file.

    $ lintian --info --display-info --check-part md5sums ./wajig_2.0.37_all.deb
    [...]
    I: wajig: no-md5sums-control-file
    N:
    N:   This package does not contain an md5sums control file. This control
    N:   file listing the MD5 checksums of the contents of the package is not
    N:   required, but if present debsums can use it to verify that no files
    N:   shipped with your package have been modified. Providing it is
    N:   recommended.
    N:   
    N:   If you are using debhelper to create your package, just add a call to
    N:   dh_md5sums at the end of your binary-indep or binary-arch target,
    N:   right before dh_builddeb.
    N:

The attached patch changes the 'debian/rules' file to generate the
'md5sums' file for this package, and causes the above command to run
cleanly (with no output).

If there is a specific reason for avoiding the recommended 'md5sums'
file and not applying this patch or something similar, could you
please explain in this bug entry.

-- 
 \       "Everyone is entitled to their own opinions, but they are not |
  `\         entitled to their own facts."  -- US Senator Pat Moynihan |
_o__)                                                                  |
Ben Finney <[EMAIL PROTECTED]>
=== modified file 'debian/rules'
--- old/debian/rules    2007-07-01 08:22:07 +0000
+++ new/debian/rules    2007-08-25 02:36:44 +0000
@@ -89,7 +89,7 @@
 #      dh_perl
        dh_installdeb
        dh_gencontrol
-#      dh_md5sums
+       dh_md5sums
        dh_builddeb
 
 # Build architecture-dependent files here.

--- End Message ---
--- Begin Message ---
Received Sat 25 Aug 2007  6:29pm +1000 from Ben Finney:
> Package: wajig
> Version: 2.0.37
> Severity: normal
> Tags: patch
> 
> 
> Debian policy recommends that all binary packages contain an 'md5sums'
> control file. The following command shows that a package built from
> this source package does not contain this file.
> 
>     $ lintian --info --display-info --check-part md5sums 
> ./wajig_2.0.37_all.deb
>     [...]
>     I: wajig: no-md5sums-control-file
>     N:
>     N:   This package does not contain an md5sums control file. This control
>     N:   file listing the MD5 checksums of the contents of the package is not
>     N:   required, but if present debsums can use it to verify that no files
>     N:   shipped with your package have been modified. Providing it is
>     N:   recommended.
>     N:   
>     N:   If you are using debhelper to create your package, just add a call to
>     N:   dh_md5sums at the end of your binary-indep or binary-arch target,
>     N:   right before dh_builddeb.
>     N:

Fixed in 2.0.38. Thanks.

Regards,
Graham


--- End Message ---

Reply via email to