Re: debian-volatile mirrors
On Tue, Oct 23, 2007 at 12:32:07PM -0200, Felipe Augusto van de Wiel (faw) wrote:
> >> Sorry for the late reply, I was unsure about how to
> >> reply to the subject. I've been wondering how we could merge
> >> the Volatile Mirrors with the Debian Mirrors, and I would to
> >> volunteer to the team if you are needing manpower.
> > Yes, we would always welcome more people at firstname.lastname@example.org :)
> I would be happy to help. :)
I'm filing an RT ticket to assimil... er... add you :)
> > Right now the Mirrors-from field isn't really used, it's just there for our
> > own accounting purposes - it's good for analysis when its state differs from
> > the one discovered by the mirror checker. It would be fairly easy (and
> > probably desirable) to convert it to fields like Archive-upstream,
> > Volatile-upstream, ...
> I don't really know how they work, as already explained by
> zobel the Mirrors-from where used by the push infrastructure, the
> other fields were unknown to me, what I was doing is just trying
> to keep Volatile Mirrors.masterlist using "good practices" IMHO
> considering the existing and presented file format. :-)
(In the meantime I actually went ahead and implemented that change above.)
In the private discussion in the meantime I realized that you actually kept
private data in those fields, and that they went in the other direction -
they documented from where the push comes and where it goes, whereas our
existing field documented from where the downstream mirror actually rsyncs.
The private data should stay private, and the other data can be generated
from the DMC results which should be available soonish (I was still tying up
some loose ends and this morning's run failed, the next one should succeed).
> >> We have a push-mirror infrastructure and I added a
> >> patch to use a different SSH port to prod servers, not sure
> >> if Debian mirrors carry this patch or support this, I will
> >> be happy to provide it again.
> > You mean, patch to the documentation or?
> I mean that some of the clients of the push network use
> non standard SSH ports to get pushed, I added support for that
> in our script, but AIUI, volatile.d.o will push the changes from
> verdi.d.o which will be maintained by Volatile Team, so it is
> still a different script. :-)
> I had the impression that we are going to merge the
> push infrastructure, then I realized that the Volatile archive
> is on a different machine, with a different another dak instance.
Yes. But we can still have the same people look at and maybe edit both,
because it's essentially the same matter.