Re: Switch of GNOME tarball compression format: tar.xz only
On Mon, Sep 12, 2011 at 02:03:23PM +, Gregory Leblanc wrote: For maintainers: - ftpadmin script will automatically handle conversion of compression formats Will this cause excessive load on the server, if everyone is uploading .tar.bz2 or .tar.gz, and then we have to convert to .xz? I haven't run any real benchmarks, but the literature I can find shows that creating the .xz files uses gobs of memory, and takes quite a bit longer than either .gz or .bz2 files. It is not ideal, but hope that the maintainer will notice and convert. But does not matter too much. We use the standard xz compression method; uses about 100MB of memory and should take less than a minute to compress. It is a pretty good tradeoff between saved space and time+memory it takes to compress. - it would still be nice if 'make dist' was changed to create a .tar.xz file, using: AM_INIT_AUTOMAKE([1.11 no-dist-gzip dist-xz]) I suppose this pushes it off on maintainers, eliminating the problems on the server. I'm not sure if the time involved is still an issue once this work is distributed, though. Knowing you, Olav, you've already thought of this and it's not a problem, but I figured I should throw it out there anyway. Thanks, The standard xz compression option is not too bad. And it saves a bit of space, so time spent on compressing can be saved on the upload. All depends on your CPU, upload bandwidth and if the maintainer cares. Also, 'make dist' usually takes quite a bit of time anyway. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switch of GNOME tarball compression format: tar.xz only
On Sun, Sep 11, 2011 at 03:47:33PM +0200, Vincent Untz wrote: Le dimanche 11 septembre 2011, à 13:41 +0200, Olav Vitters a écrit : If you have concerns, I'd like to hear about it. I've set the reply-to to desktop-devel-list and distributor-list. With a few other (non-gnome) tarballs switching to xz-only, one thing I realized is that python doesn't support that yet: http://bugs.python.org/issue6715 It means that, for my downstream activities, I'll have to update some scripts to work around this missing feature in python. Right, I have code to handle that in the ftpadmin script in the sysadmin-bin module. It makes xz handling pretty much transparent. Still looking for a stronger No!!! though as I was already aware of this, but don't consider it a blocker. -- Regards, Olav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switch of GNOME tarball compression format: tar.xz only
On Sun, Sep 11, 2011 at 11:41 AM, Olav Vitters o...@vitters.nl wrote: In a few months, newly uploaded tarballs on ftp.gnome.org will only be available as tar.xz. Change occurs after the last stable release of GNOME 3.2, approximately on Nov 16 2011. This only for *new* tarballs. All existing tarballs on ftp.gnome.org will NOT be affected nor removed. Currently tarballs are released using the formats: - tar.xz - tar.bz2 (until 2011-11-15) == After Nov 16 2011 (approx.) tarballs will only use tar.xz == For packagers: - please package GNOME 3.2 using tar.xz - default options are used for xz compression; requires about 9 MiB of memory to decompress (bz2 uses 3700KB) For maintainers: - for your information only; you do not need to do anything - ftpadmin script will automatically handle conversion of compression formats Will this cause excessive load on the server, if everyone is uploading .tar.bz2 or .tar.gz, and then we have to convert to .xz? I haven't run any real benchmarks, but the literature I can find shows that creating the .xz files uses gobs of memory, and takes quite a bit longer than either .gz or .bz2 files. - it would still be nice if 'make dist' was changed to create a .tar.xz file, using: AM_INIT_AUTOMAKE([1.11 no-dist-gzip dist-xz]) I suppose this pushes it off on maintainers, eliminating the problems on the server. I'm not sure if the time involved is still an issue once this work is distributed, though. Knowing you, Olav, you've already thought of this and it's not a problem, but I figured I should throw it out there anyway. Thanks, Greg P.S. Please CC me on replies if you want my input, as I only monitor the -announce lists closely. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switch of GNOME tarball compression format: tar.xz only
Le dimanche 11 septembre 2011, à 13:41 +0200, Olav Vitters a écrit : If you have concerns, I'd like to hear about it. I've set the reply-to to desktop-devel-list and distributor-list. With a few other (non-gnome) tarballs switching to xz-only, one thing I realized is that python doesn't support that yet: http://bugs.python.org/issue6715 It means that, for my downstream activities, I'll have to update some scripts to work around this missing feature in python. It's not a blocker for the switch (at least for me), but that might be something others need to consider. Note that there's been some recent activity in the python bug, so maybe that won't be an issue at all. Cheers, Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Switch of GNOME tarball compression format: tar.xz only
Vincent Untz wrote: Le dimanche 11 septembre 2011, à 13:41 +0200, Olav Vitters a écrit : If you have concerns, I'd like to hear about it. I've set the reply-to to desktop-devel-list and distributor-list. With a few other (non-gnome) tarballs switching to xz-only, one thing I realized is that python doesn't support that yet: http://bugs.python.org/issue6715 It means that, for my downstream activities, I'll have to update some scripts to work around this missing feature in python. This is also a problem for library-web (library.gnome.org developer. gnome.org). Fred ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
