Your message dated Sun, 11 May 2008 10:47:11 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: [Buildd-tools-devel] Bug#470440: Processed: Re: 
Bug#470440: python-django: FTBFS: MD5SUM mismatch for .diff.gz
has caused the Debian Bug report #470440,
regarding sbuild doesn't cope with Checksums-Sha1 and Checksums-Sha256 headers
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.)


-- 
470440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=470440
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: python-django
Version: 0.96.1-3
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080310 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in sid, your package failed to build on i386.

Relevant part:
> DC-Build-Header: python-django 0.96.1-3 / Tue Mar 11 05:06:57 +0100 2008
> Automatic build of python-django_0.96.1-3 on grelon-31.nancy.grid5000.fr by 
> sbuild/amd64 0.57.0
> Build started at 20080311-0506
> ******************************************************************************
> Failed to open ./python-django_0.96.1-3.dsc
> Checking available source versions...
> Fetching source files...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Need to get 1755kB of source archives.
> Get:1 http://idpot.grenoble.grid5000.fr sid/main python-django 0.96.1-3 (dsc) 
> [1457B]
> Get:2 http://idpot.grenoble.grid5000.fr sid/main python-django 0.96.1-3 (tar) 
> [1746kB]
> Get:3 http://idpot.grenoble.grid5000.fr sid/main python-django 0.96.1-3 
> (diff) [7234B]
> Fetched 1755kB in 0s (3623kB/s)
> Download complete and in download only mode
> /var/lib/schroot/mount/sid32-e0221d34-ac59-4eb7-8a9a-eed3dd9f18ef/build/user/python-django_0.96.1-3.diff.gz:
>  MD5SUM mismatch 
> (d2653ab52567436d0ee0d3c59410aa7e60b5fdf92ad05c6e1c58bc820e1bda31 cf 
> dbc74dd2bf7093031016b0f4e2dd7813
> FAILED [dsc verification]
> ******************************************************************************
> Finished at 20080311-0507
> Build needed 00:00:00, 0k disk space
> DC-Build-Status: Failed 13.619396s
> DC-Time-Estimation: 13.619396 versus expected 44 (r/m: 2.23068658845077 ; m: 
> 13.619396)

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/03/10

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Version: 0.57.2-1

Adeodato Simó <[EMAIL PROTECTED]> writes:

> * Roger Leigh [Fri, 28 Mar 2008 16:47:18 +0000]:
>
>> However, we also need to parse it to get the list of files to copy from
>> the chroot back to the host system.  Is there a tool available that can
>> do this automatically, or do I need to keep parsing the .dsc myself?  A
>> tool that can copy entire .dsc and .changes file sets would be equally
>> useful, because that's what we want to do.
>
> Try:
>
>   % /usr/bin/dcmd cp /path/to/foo.dsc /path/outside/the/chroot
>
> dcmd is the devscripts package (>= 2.10.20).

We now use dcmd to get the file list (but not yet for copying; that
will come later).


Thanks,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux             http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?       http://gutenprint.sourceforge.net/
   `-    GPG Public Key: 0x25BFB848   Please GPG sign your mail.

Attachment: pgpWOGqxmB2cL.pgp
Description: PGP signature


--- End Message ---

Reply via email to