#4955: update releases/15 repomd.xml timestamps to be newer than published development/15 timestamps
by Fedora Release Engineering
#4955: update releases/15 repomd.xml timestamps to be newer than published
development/15 timestamps
---------------------+------------------------------------------------------
Reporter: mdomsch | Owner: rel-eng(a)lists.fedoraproject.org
Type: task | Status: new
Milestone: | Component: other
Keywords: |
---------------------+------------------------------------------------------
https://fedorahosted.org/mirrormanager/ticket/35
<mdomsch> dgilmore: development/15 got a newer tree (with newer repomd.xml
timestamps) after releases/15 was published
<dgilmore> mdomsch: yeah i didsabled branched a day late
<mdomsch> which is a problem for anyone who updated in that window
<dgilmore> disabled
<mdomsch> now yum sees the development/15 timestamp, and the "older"
releases/15 timestamp, and throws out the releases/15 repomd.xml, keeping
the now-incorrect one.
<mdomsch> yum clean is needed to fix it
<dgilmore> mdomsch: considering the development/15 was removed ages ago im
not sure anyone should still see that
<mdomsch> skvidal: unfortunately yes
<skvidal> mdomsch: yum clean expire-cache should d oit
<mdomsch> skvidal: yum clean --enablerepo=\* or somesuch to pick up
debuginfo repos too...
<mdomsch> dgilmore: it's not that they still see it, it's that they saw it
once, with a newer timestamp than what they see now
<mdomsch> so a manual expire-cache is needed
<mdomsch> so between skvidal and dgilmore, how can we avoid that for f16+
?
<skvidal> how much newer is the timestamp?
<dgilmore> mdomsch: we really cant,
<skvidal> can we just touch the file(s) and move along?
<mdomsch> skvidal: hours
<mdomsch> it's not the file system timestamp, it's the repomd.xml
timestamp
<skvidal> okay can we modify the file manually
<dgilmore> mdomsch: well when we say go, i need to make sure i disabled
the branched repo then rsync the contents into place i guess
<mdomsch> <revision>1305638986</revision>
<mdomsch> is correct
<skvidal> right - I'm saying
<mdomsch> <revision>1305725445</revision>
<skvidal> 1. touch the files for a future date
<skvidal> 2. modify the repomd.xml to reflect that molestation
<mdomsch> skvidal: I like it
<skvidal> the mirrors should pick up the change in the repomd.xml and
mirror it out
<skvidal> the contents are all the same in the repodata - it just LOOKS
newer
<skvidal> this is not something I'd recommend doing often
<skvidal> but as a one-time deal
<skvidal> it seems easy enough
<mdomsch> skvidal: I presume that's a rel-eng task, and I should assign
there?
<skvidal> mdomsch: I think so....
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/4955>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project