Your message dated Fri, 28 Sep 2007 09:37:26 +0100 with message-id <20070928083726.GB5904@einval.com> and subject line Bug#444376: cdimage.debian.org: Debian 4.0r1 amd64 DVD image is broken- missmatch md5sum in Packages.gz 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 ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: cdimage.debian.org: Debian 4.0r1 amd64 DVD image is broken- missmatch md5sum in Packages.gz
- From: Alexander Sashnov <asashnov@swsoft.com>
- Date: Fri, 28 Sep 2007 12:48:44 +0700
- Message-id: <[🔎] 20070928054844.31284.36856.reportbug@www.burstnet.com>
Package: cdimage.debian.org Severity: normal http://cdimage.debian.org/debian-cd/4.0_r1/amd64/iso-dvd/ debian-40r1-amd64-DVD-1.iso 19-Aug-2007 with md5sum 2aed0338641a98ec534b31daece5c671 Installation from this image failed: debootstrap can't create base system. vim-common package MD5sum failed. I wrote tool for check md5sum files again md5sum from Packages.gz Around ~150 packages have missmatch md5sums. http://sashnov.fanstvo.com/apt_repository_check.py Usage: $ fuseiso -p debian-40r1-amd64-DVD-1.iso debdvd1_amd64 $ ./apt_repository_check.py -a binary-amd64 -d etch -s 'main,contrib' debdvd1_amd64 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-k7 (SMP w/1 CPU core) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
- To: Alexander Sashnov <asashnov@swsoft.com>, 444376-done@bugs.debian.org
- Subject: Re: Bug#444376: cdimage.debian.org: Debian 4.0r1 amd64 DVD image is broken- missmatch md5sum in Packages.gz
- From: Steve McIntyre <steve@einval.com>
- Date: Fri, 28 Sep 2007 09:37:26 +0100
- Message-id: <20070928083726.GB5904@einval.com>
- In-reply-to: <[🔎] 20070928054844.31284.36856.reportbug@www.burstnet.com>
- References: <[🔎] 20070928054844.31284.36856.reportbug@www.burstnet.com>
On Fri, Sep 28, 2007 at 12:48:44PM +0700, Alexander Sashnov wrote: >Package: cdimage.debian.org >Severity: normal > > >http://cdimage.debian.org/debian-cd/4.0_r1/amd64/iso-dvd/ > >debian-40r1-amd64-DVD-1.iso 19-Aug-2007 >with md5sum 2aed0338641a98ec534b31daece5c671 > >Installation from this image failed: > >debootstrap can't create base system. > >vim-common package MD5sum failed. > > >I wrote tool for check md5sum files again md5sum from Packages.gz >Around ~150 packages have missmatch md5sums. > >http://sashnov.fanstvo.com/apt_repository_check.py > >Usage: >$ fuseiso -p debian-40r1-amd64-DVD-1.iso debdvd1_amd64 >$ ./apt_repository_check.py -a binary-amd64 -d etch -s 'main,contrib' debdvd1_amd64 I've just done the following on my local mirror and found no errors: jack:/tmp# mount -o loop debian-40r1-amd64-DVD-1.iso /mnt1 jack:/tmp# cd /mnt1 jack:/mnt1# find . -name Packages | xargs cat | awk '/^Filename:/ {filename=$2}; /^MD5sum:/ {md5=$2; printf("%s %s\n", md5,filename)}' > /tmp/md5 jack:/mnt1# md5sum -c < /tmp/md5 jack:/mnt1# grep -v OK /tmp/md5-out The CD/DVD build system explicitly checks the md5sums of all packages that make it into the ISO images at build time, so it's nigh-on impossible for there to be a bug like you describe in an official release. In the case of vim-common: jack:/mnt1# grep vim-common /tmp/md5-out pool/main/v/vim/vim-common_7.0-122+1etch2_amd64.deb: OK I have the same md5sum for the image as a whole as you. There must be a bug somewhere at your end, I'm afraid. -- Steve McIntyre, Cambridge, UK. steve@einval.com Getting a SCSI chain working is perfectly simple if you remember that there must be exactly three terminations: one on one end of the cable, one on the far end, and the goat, terminated over the SCSI chain with a silver-handled knife whilst burning *black* candles. --- Anthony DeBoerAttachment: signature.asc
Description: Digital signature
--- End Message ---