On Sat, 2009-01-31 at 20:10 +0200, Axel Thimm wrote:
a current rsync shows that thousands of files have been changed in the last week. This is not expected as /releases/ is considered to only change for the release day and then never again.
The files have a date of Jan 23rd. Although I don't have a copy to compare with looking at the internal date it looks like the files have just been `touch'ed (but I only checked a coupl of the 2000+ changed ones). Could someone bring back the old dates to make it consistent again? Thanks!
Hrm, there was no action on my part to touch everything, so I'll have to do some investigation into what's going on.
Looking on the server, all the files in releases/10/Everything/i386/os/Packages/ have varying timestamps, but I do indeed see some things with a stamp as new as Jan 22. Its certainly not every file, but I'm still not quite finding any commonality in my brief looking. More investigation to follow.
On Sat, 2009-01-31 at 12:14 -0800, Jesse Keating wrote:
Hrm, there was no action on my part to touch everything, so I'll have to do some investigation into what's going on.
Looking on the server, all the files in releases/10/Everything/i386/os/Packages/ have varying timestamps, but I do indeed see some things with a stamp as new as Jan 22. Its certainly not every file, but I'm still not quite finding any commonality in my brief looking. More investigation to follow.
I take that back. This happened when I was trying to pre-stage some 11-Alpha content. I misread/misunderstood what --size-only option would do, in relation to --link-dest. I was trying to link 11-Alpha packages to the same ones found in /pub/fedora/linux/releases/development/. However these that were touched were packages that were in development/ that hadn't changed since the F10 release. --size-only seems to have updated the timestamps on these files to match something that was going on with my compose output I was trying to sync in.
This was certainly unexpected, and repairing this is going to be... interesting.
I need to investigate why my compose hosts are creating a timestamp on these files when they shouldn't be.
Sorry for the churn!
On Sat, 2009-01-31 at 12:21 -0800, Jesse Keating wrote:
I misread/misunderstood what --size-only option would do, in relation to --link-dest
Actually it may have nothing to do with --size-only, that may have just been my clue that something was wrong.
On Sat, 2009-01-31 at 12:21 -0800, Jesse Keating wrote:
This was certainly unexpected, and repairing this is going to be... interesting.
Through some fun work with /sbin/hardlink I got a lot of the packages fixed up. There are some more that aren't quite right, due to the development tree having moved on, so I'll have to fix this individually.
On Sat, Jan 31, 2009 at 01:58:28PM -0800, Jesse Keating wrote:
On Sat, 2009-01-31 at 12:21 -0800, Jesse Keating wrote:
This was certainly unexpected, and repairing this is going to be... interesting.
Through some fun work with /sbin/hardlink I got a lot of the packages fixed up. There are some more that aren't quite right, due to the development tree having moved on, so I'll have to fix this individually.
Isn't there a backup of /releases/ to pull back the original files?
On Sun, 2009-02-01 at 10:16 +0100, Axel Thimm wrote:
Isn't there a backup of /releases/ to pull back the original files?
I do believe there is, but it would involve tape and a long wait, for something as easy to fix as timestamps. I have most of them fixed, there are only a tiny few that are not, something that I'm almost willing to live with.
infrastructure@lists.fedoraproject.org
-
Axel Thimm -
Jesse Keating