Re: GIT for pdiff generation

2011-03-28 Thread Joerg Jaspert
Right now the source contents of unstable has, unpacked, 220MB. (Packed gzip its 28MB, while the binary contents per have each have 18MB packed). That should not be a problem in any non-joke box. Unless you'll run it in a memory-constrained vm or something. Well. For our archives it is

GIT for pdiff generation (was: Meeting Minutes, FTPMaster meeting March 2011)

2011-03-27 Thread Henrique de Moraes Holschuh
On Sun, 27 Mar 2011, Joerg Jaspert wrote: - As there have been intermittent problems with the current tool which generates the pdiff files (on occasion causing us to have to restart the whole diff series), we looked into improving the situation. We finally came up with the idea to store

Re: GIT for pdiff generation

2011-03-27 Thread Joerg Jaspert
As we are no git gurus ourself: Does anyone out there see any trouble doing it this way? It means storing something around 7GB of uncompressed text files in git, plus the daily changes happening to them, then diffing them in the way described above, however the archive will only

Re: GIT for pdiff generation

2011-03-27 Thread Henrique de Moraes Holschuh
On Sun, 27 Mar 2011, Joerg Jaspert wrote: Right now the source contents of unstable has, unpacked, 220MB. (Packed gzip its 28MB, while the binary contents per have each have 18MB packed). That should not be a problem in any non-joke box. Unless you'll run it in a memory-constrained vm or