-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-01-02 at 01:35 -0300, Cristian Rodríguez wrote:
Carlos E. R. escribió:
Even so, a "dup" meant about 1 gigabyte. If, when the dup succeeded,
This is because of what Vicent told you, when a single vital component is rebuilt, everything dependent on it is as well, and that is expected and how it should work, however what is not really expected is the bandwidth waste that is produced when that rebuilds produce identical binaries with diffent rpm release numbers...
I know that, but knowing does not change the problem we on the receiving side have. There is nothing us, on this side, can do.
What I think is needed, is the repo not changing for a day or more. If you need to push changes, do so to another repo.
The process is already complex enough to add yet another step...
Then do something else. Do you want more testers or do you not? If you do, then help us. As it is now, sometimes it takes me weeks to update factory. Then, I start testing whatever I was going to test, I discover I have to install something else; but the repo has again changed, so I have to start again the process, and another week is lost. Instead of testing for bugs, I have to spend my also valuable time attempting to do dups. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAklesMMACgkQtTMYHG2NR9VQdQCeMXev7I2OT3GojEYr4zBEro9G bjAAn2fC2y+9P+f9b2FrZu2/WMGGZNaQ =l+4x -----END PGP SIGNATURE-----