| 2020-08-17 08:28:24 |
Iain Lane |
description |
Once the archive moves on, it is practically impossible to reconstruct its state, if you would like to examine the way that proposed-migration operated - for example to reproduce a bug or just to make a behaviour change.
b1 currently archives update_excuses and update_output in e.g. https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses/
The idea is to similarly archive the contents of the state/ directory, namely series{,-proposed}. Done naively this will be quite huge:
$ du -hs groovy groovy-proposed/
484M groovy
24MI groovy-proposed/
but after some chatting on #ubuntu-release we came up with the idea of committing the files to git instead which should be much more space efficient. |
Once the archive moves on, it is practically impossible to reconstruct its state, if you would like to examine the way that proposed-migration operated - for example to reproduce a bug or just to make a behaviour change.
b1 currently archives update_excuses and update_output in e.g. https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses/
The idea is to similarly archive the contents of the state/ directory, namely series{,-proposed}. Done naively this will be quite huge:
$ du -hs groovy groovy-proposed/
484M groovy
24M groovy-proposed/
but after some chatting on #ubuntu-release we came up with the idea of committing the files to git instead which should be much more space efficient. |
|
