| 1 |
On Wed, 16 Dec 2015 14:38:03 +0100 |
| 2 |
Alexander Berntsen <bernalex@g.o> wrote: |
| 3 |
|
| 4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 5 |
> Hash: SHA512 |
| 6 |
> |
| 7 |
> On 16/12/15 06:33, Zac Medico wrote: |
| 8 |
> > Disable Manifest "stable mtime" behavior by default, and add a |
| 9 |
> > corresponding egencache option. |
| 10 |
> This message tells me nothing about why we need to do this. |
| 11 |
|
| 12 |
We need do this because we changed the behavior and the new behavior is |
| 13 |
counter-intuitive. We already had a number of bugs caused by it, |
| 14 |
and while it's used by Infra, it's at least unexpected when someone |
| 15 |
manually runs 'repoman manifest'. |
| 16 |
|
| 17 |
I mean, before this all started 'repoman manifest' just updated |
| 18 |
the Manifest which meant it's mtime changed. Nowadays, it also sets |
| 19 |
mtime to some value in the past, which means running 'repoman manifest' |
| 20 |
may result in updated Manifest having mtime older than the old |
| 21 |
Manifest. As a result, people using rsync are in trouble. And this has |
| 22 |
been reported too by overlay owners. |
| 23 |
|
| 24 |
-- |
| 25 |
Best regards, |
| 26 |
Michał Górny |
| 27 |
<http://dev.gentoo.org/~mgorny/> |
Archives