Your message dated Fri, 2 Nov 2007 10:27:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line mirrors: ftp.tu-chemnitz.de serves corrupted packages
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: mirrors
Severity: normal
Hi,
this seems specific to ftp.tu-chemnitz.de, e.g. no problem with
ftp.de.debian.org.
Transcript:
penelope[tu-chemnitz.de]$ ncftp ftp.tu-chemnitz.de
NcFTP 3.1.8 (Jul 27, 2004) by Mike Gleason (http://www.NcFTP.com/contact/).
Connecting to 134.109.140.122...
Welcome to TU Chemnitz FTP service (postel).
Logging in...
Login successful.
Logged in to ftp.tu-chemnitz.de.
ncftp /> cd pub/linux/debian/debian/main/x/xprint
Directory successfully changed.
ncftp ...ian/pool/main/x/xprint > mget *.deb
[...]
ncftp ...ian/pool/main/x/xprint > quit
penelope[tu-chemnitz.de]$ file *
xprint_0.1.0.alpha1-10_alpha.deb: data
xprint_0.1.0.alpha1-10_arm.deb: data
xprint_0.1.0.alpha1-10_hppa.deb: data
xprint_0.1.0.alpha1-10_i386.deb: data
xprint_0.1.0.alpha1-10_ia64.deb: data
xprint_0.1.0.alpha1-10_m68k.deb: data
xprint_0.1.0.alpha1-10_mips.deb: data
xprint_0.1.0.alpha1-10_mipsel.deb: data
xprint_0.1.0.alpha1-10_powerpc.deb: data
xprint_0.1.0.alpha1-10_s390.deb: data
xprint_0.1.0.alpha1-10_sparc.deb: data
xprint_1.0.2-1_alpha.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_amd64.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_arm.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_hppa.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_i386.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_ia64.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_m68k.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_mips.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_mipsel.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_powerpc.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_s390.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.0.2-1_sparc.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.1.99.3+git20060910-1_amd64.deb: Debian binary package (format
2.0), uses gzip compression
xprint_1.1.99.3+git20060910-1_i386.deb: Debian binary package (format
2.0), uses gzip compression
xprint-common_0.1.0.alpha1-10_all.deb: data
xprint-common_1.0.2-1_all.deb: Debian binary package (format
2.0), uses gzip compression
xprint-common_1.1.99.3+git20060910-1_all.deb: Debian binary package (format
2.0), uses gzip compression
xprt_0.1.0.alpha1-10_all.deb: Debian binary package (format
2.0), uses gzip compression
xprt-xprintorg_0.1.0.alpha1-10_all.deb: Debian binary package (format
2.0), uses gzip compression
penelope[tu-chemnitz.de]$ hexdump -C xprint_0.1.0.alpha1-10_alpha.deb #
arbitrary example
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00253b40 00 00 |..|
00253b42
penelope[tu-chemnitz.de]$
The xprint 0.1.0 packages contain only zeroes! The files seem to have the
correct size, however. I haven't found any other packages to be affected, but
who knows.
Nikolaus
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-deb.150606
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
--- End Message ---
--- Begin Message ---
Dear Guenther,
On Tue, Oct 24, 2006 at 08:52:43PM +0200, Simon Paillard wrote:
> Many other packages might be corrupted.
>
> As the user suggested in the bug report, you may test all the files of
> the mirror using 'file', since corrupted packages are not detected as a
> "Debian binary package" :
>
> find . -name *deb -exec file {} \; | grep -v "Debian binary package"
Assuming that you've checked your mirror, and since there have been no
user reporting corrupted package on your mirror, the bug is closed.
--
Simon Paillard
--- End Message ---
