Control: severity 795226 normal
Control: tags 795226 + moreinfo unreproducible

Hi Dave--

this sounds frustrating!  I'm closing this bug because i don't think
it's about xdotool at all.  but feel free to reopen it if you think it
really is xdotool that's breaking things.

Rather than being xdotool that's causing the problem, it might be:

 * a problem with the mirror you've reached or

 * a problem with your local proxy modifying traffic or

 * a problem with your ISP modifying traffic

in particular:

On Tue 2015-08-11 18:51:44 -0400, Dave Rutherford wrote:
> $ sudo apt-get install xdotool
 [...]
> Get:1 http://http.us.debian.org/debian/ wheezy/main libxdo2 amd64 
> 1:2.20100701.2961-3+deb7u3 [28.5 kB]
> Get:2 http://http.us.debian.org/debian/ wheezy/main xdotool amd64 
> 1:2.20100701.2961-3+deb7u3 [37.8 kB]
> Fetched 69.3 kB in 0s (0 B/s)
> Failed to fetch 
> http://http.us.debian.org/debian/pool/main/x/xdotool/libxdo2_2.20100701.2961-3+deb7u3_amd64.deb
>   Size mismatch
> Failed to fetch 
> http://http.us.debian.org/debian/pool/main/x/xdotool/xdotool_2.20100701.2961-3+deb7u3_amd64.deb
>   Size mismatch
> E: Unable to fetch some archives, maybe run apt-get update or try with 
> --fix-missing?

This is an indication that the files in question are *not* the files
From the debian archive.  something is amiss!

I did the same wget fetch that you did and i found:

> $ ls -l *.deb
> - -rw-r--r-- 1 dave dave 29800 Mar 27  2013 
> libxdo2_2.20100701.2961-3+deb7u3_amd64.deb
> - -rw-r--r-- 1 dave dave 39520 Mar 27  2013 
> xdotool_2.20100701.2961-3+deb7u3_amd64.deb
>
> $ file *.deb
> libxdo2_2.20100701.2961-3+deb7u3_amd64.deb: Debian binary package (format 2.0)
> xdotool_2.20100701.2961-3+deb7u3_amd64.deb: Debian binary package (format 2.0)
>
> $ md5sum *.deb
> f671f0dade7438722b3d80850a881892  libxdo2_2.20100701.2961-3+deb7u3_amd64.deb
> 0ea06f3c6f1d31767430885c5c595c8e  xdotool_2.20100701.2961-3+deb7u3_amd64.deb


0 $ ls -l
-rw-r--r--  1 dkg  dkg  28510 Mar 27  2013 
libxdo2_2.20100701.2961-3+deb7u3_amd64.deb
-rw-r--r--  1 dkg  dkg  37808 Mar 27  2013 
xdotool_2.20100701.2961-3+deb7u3_amd64.deb
0 $ file *
libxdo2_2.20100701.2961-3+deb7u3_amd64.deb: Debian binary package (format 2.0)
xdotool_2.20100701.2961-3+deb7u3_amd64.deb: Debian binary package (format 2.0)
0 $ md5sum *.deb
35d5e06c35973d952552e058606eb6a3  libxdo2_2.20100701.2961-3+deb7u3_amd64.deb
def2c3eec508c921bbd298c8c7947055  xdotool_2.20100701.2961-3+deb7u3_amd64.deb
0 $ 


could you also try bypassing your local proxy to see if the update works
properly?  if it still fails, then that would rule out your proxy as the
cause of the problem.  That would also let you know which IP addresses
you're pulling the bad files from.  if you let me know the IP addresses
i can verify those files from my view on the network as well.

Out of curiosity, what happens if you do:

head -c 28510 < libxdo2*.deb | md5sum -
head -c 37808 < xdotool*.deb | md5sum -

if those checksums match the ones i've got above, then you'll know that
something is just appending chunks of data to your HTTP transfers
(weird!)


> $ sudo dpkg -i *.deb
> tar: This does not look like a tar archive
> tar: Skipping to next header
> tar: Exiting with failure status due to previous errors
> dpkg-deb: error: subprocess tar returned error exit status 2
> dpkg: error processing libxdo2_2.20100701.2961-3+deb7u3_amd64.deb (--install):
>  subprocess dpkg-deb --control returned error exit status 2
> tar: This does not look like a tar archive
> tar: Skipping to next header
> tar: Exiting with failure status due to previous errors
> dpkg-deb: error: subprocess tar returned error exit status 2
> dpkg: error processing xdotool_2.20100701.2961-3+deb7u3_amd64.deb (--install):
>  subprocess dpkg-deb --control returned error exit status 2
> Errors were encountered while processing:
>  libxdo2_2.20100701.2961-3+deb7u3_amd64.deb
>  xdotool_2.20100701.2961-3+deb7u3_amd64.deb

trying to install a .deb that apt has refused to install could
potentially put your system at risk -- i hope this was just an
experiment within a throwaway machine to see what would happen.

Sorry this is happening!  let me know if you've got more information we
can use to reproduce it.

    --dkg

Attachment: signature.asc
Description: PGP signature

Reply via email to