Package: dpkg-dev
Severity: normal

Ok, now that I actually checked the log files again, it turned out that I 
changed
the .orig.tar.gz after the first upload so the checksums didn't match. Copying
back the original .orig.tar.gz solved the problem.

Sorry for the fuss,

Adrian


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dpkg-dev depends on:
ii  base-files        5.6                    Debian base system miscellaneous f
ii  binutils          2.20.1-9               The GNU assembler, linker and bina
ii  bzip2             1.0.5-4                high-quality block-sorting file co
ii  libdpkg-perl      1.15.7.2               Dpkg perl modules
ii  make              3.81-8                 An utility for Directing compilati
ii  patch             2.6-2                  Apply a diff file to an original
ii  xz-utils          4.999.9beta+20100307-1 XZ-format compression utilities

Versions of packages dpkg-dev recommends:
ii  build-essential               11.5       Informational list of build-essent
ii  fakeroot                      1.14.4-1   Gives a fake root environment
ii  gcc [c-compiler]              4:4.4.3-1  The GNU C compiler
ii  gcc-4.3 [c-compiler]          4.3.5-1    The GNU C compiler
ii  gcc-4.4 [c-compiler]          4.4.4-1    The GNU C compiler
ii  gnupg                         1.4.10-4   GNU privacy guard - a free PGP rep
ii  gpgv                          1.4.10-4   GNU privacy guard - signature veri
pn  libalgorithm-merge-perl       <none>     (no description available)

Versions of packages dpkg-dev suggests:
ii  debian-keyring                2010.03.31 GnuPG (and obsolete PGP) keys of D

-- no debconf information




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to