GNOME Bugzilla – Bug 789483
Broken archive on FTP
Last modified: 2017-10-26 18:16:53 UTC
In http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.12/ the obviously wrongly-generated glibmm-2.12.5.tar.bz2 is an empty file glibmm-2.12.5.md5sum is also an empty file. This causes the lgo.py script to fail midway: I:[20171025 17:25:44] extracting module glibmm (from 2.16.3 moduleset) D:[20171025 17:25:44] looking for doc modules in /home/hadess/.cache/lgo/downloads/ftp.gnome.org/pub/GNOME/sources/glibmm/2.12/glibmm-2.12.5.tar.bz2 Traceback (most recent call last):
+ Trace 238106
app.run()
self.process_releases()
doc_modules.extend(self.get_doc_modules(moduleset, r))
doc_modules.extend(self.extract_modules(filename))
tar = tarfile.open(filename, 'r')
return func(name, "r", fileobj, **kwargs)
fileobj.read(_LZMAProxy.blocksize)
Those files were removed, next mirror sync is also required.
Ha! Seeing as the lgo.py script doesn't fail on the production machine, it's probably because it has that file in its cache! Would it be possible to add the file back in the same place as the 0-length one, and regenerate a corrected checksums file? That might be the easiest way to repair that problem.
Bastien, got the tarball from [1], placed it on download.g.o and generated md5sums again. Please confirm and close the bug accordingly if it looks good.
And [1]. [1] http://pkgs.fedoraproject.org/repo/pkgs/glibmm24/glibmm-2.12.5.tar.bz2/309fab274ada3d62aa4506fb6f5685e2/
The modules list [1] released by the release-team mentions: <tarball id="glibmm" version="2.12.5"> <source href="http://download.gnome.org/sources/glibmm/2.12/glibmm-2.12.5.tar.bz2" md5sum="309fab274ada3d62aa4506fb6f5685e2" size="2343299"/> The new md5sum files says: 309fab274ada3d62aa4506fb6f5685e2 glibmm-2.12.5.tar.bz2 glibmm-2.12.5.tar.bz2 which matches the md5sum of the downloaded file. The size also matches the downloaded file. Looks good! [1]: https://download.gnome.org/teams/releng/2.16.3/gnome-2.16.3.modules