Re: incoming.d.o/debian-buildd, usage polivy/advice
On 17731 March 1977, Ian Jackson wrote:
Who is supposed/allowed to use
https://incoming.debian.org/debian-buildd
and when? In particular, is it OK for Debian downstreams to access
it to obtain source files that the archive has accepted but which
aren't yet availabe on mirrors?
Buildds for building stuff.
We have a question about when it is appropriate or not to use
https://incoming.debian.org/debian-buildd. I'm not sure I'm asking in
the right place. Please feel free to redirect me.
incoming.debian.org has the following header:
--8<---------------cut here---------------start------------->8---
incoming.debian.org
This is incoming.debian.org, a service which provides access to uploads
immediately after they are accepted into the archive. It is primarily
for the use of the Debian buildd-network but is publically available.
Most Debian suites have an equivalent buildd-SUITE available under the
debian-buildd directory. These can be used in the normal way via apt's
sources.list. For example:
deb https://incoming.debian.org/debian-buildd buildd-unstable main
contrib non-free
--8<---------------cut here---------------end--------------->8---
So it *can* be used, but we make no guarantee that it stays the way it
is now. If it ever turns out something else is better for the buildds,
it will change.
Also, the buildd queues do NOT keep the files around for long. While the
normal archive keeps files for 36hours after they are no longer needed,
that is only 10 minutes for the buildd queues. So do not expect things
to be there for long, it's really only from ACCEPT to dinstall.
incoming is pushed to the static mirrors and served from there - i leave
it to DSA to say something about the extra traffic and if thats
noticable.
--
bye, Joerg
Reply to: