Hi, On Wed, Apr 1, 2015 at 6:59 PM, Andreas Tille <[email protected]> wrote:
> On Wed, Apr 01, 2015 at 06:31:14PM +0530, Akshita Jha wrote: > > The above error is resoved, but now I get the following error: > > :-) > > > bzip2: Compressed file ends unexpectedly; > > perhaps it is corrupted? *Possible* reason follows. > > bzip2: Invalid argument > > Input file = (stdin), output file = (stdout) > > > > It is possible that the compressed file(s) have become corrupted. > > You can use the -tvv option to test integrity of such files. > > ... > > Hmmm, sounds strange. As you can obtain from the config file the > following script is executed: > > /srv/udd.debian.org/udd/scripts/fetch_machine-readable.sh > > This in turn calls > > wget -q > http://blends.alioth.debian.org/machine-readable/machine-readable.tar.bz2 > -O - | tar xj > > > There are no tracebacks to tell me what is causing the error. Can you > > please help me with this? > > If this kind of errors occure I'd suggest to add a 'set -x' into the > according shell script. I think you need to make sure that no crazy > proxy or whatever comes in your way. I have faced proxies that contain > a virus checker which delivered an *uncompressed* file named *.tar.gz. > I'd suggest to fetch > > wget > http://blends.alioth.debian.org/machine-readable/machine-readable.tar.bz2 > > and see what miht be wrong with this file. > > You were right. It was indeed a proxy problem. I fixed it and now have successfully executed $ ./update-and-run.sh blends-prospective. The metadata has been unpacked. Thanks alot :) -- Akshita Jha
