Re: [PATCH v3 3/3] dak.conf: add packages that trigger byhand-code-sign
- To: Ben Hutchings <ben@decadent.org.uk>
- Cc: Helen Koike <helen.koike@collabora.co.uk>, Helen Koike <helen.koike@collabora.com>, Julien Cristau <jcristau@debian.org>, Jakub Wilk <jwilk@debian.org>, 821051@bugs.debian.org, debian-admin@lists.debian.org, Steve McIntyre <steve@einval.com>, debian-dak@lists.debian.org
- Subject: Re: [PATCH v3 3/3] dak.conf: add packages that trigger byhand-code-sign
- From: Joerg Jaspert <joerg@debian.org>
- Date: Mon, 12 Dec 2016 23:35:33 +0100
- Message-id: <[🔎] 87vauowzbe.fsf@delenn.ganneff.de>
- Mail-followup-to: Ben Hutchings <ben@decadent.org.uk>, Helen Koike <helen.koike@collabora.co.uk>, Helen Koike <helen.koike@collabora.com>, Julien Cristau <jcristau@debian.org>, Jakub Wilk <jwilk@debian.org>, 821051@bugs.debian.org, debian-admin@lists.debian.org, Steve McIntyre <steve@einval.com>, debian-dak@lists.debian.org
- In-reply-to: <[🔎] 1481580327.2742.34.camel@decadent.org.uk> (Ben Hutchings's message of "Mon, 12 Dec 2016 22:05:27 +0000")
- References: <1475789253-4597-1-git-send-email-helen.koike@collabora.com> <cover.1479261618.git.helen.koike@collabora.com> <c351cba2a6b2712b05fb5eecc32d44858b72e635.1479261618.git.helen.koike@collabora.com> <1479641248.16599.34.camel@decadent.org.uk> <2929db43-e876-55a1-21bb-4a9c53ce1535@collabora.co.uk> <1480437307.16599.65.camel@decadent.org.uk> <[🔎] 87a8c1yp8y.fsf@delenn.ganneff.de> <[🔎] 1481577100.2742.30.camel@decadent.org.uk> <[🔎] 87bmwgyh62.fsf@delenn.ganneff.de> <[🔎] 1481580327.2742.34.camel@decadent.org.uk>
On 14519 March 1977, Ben Hutchings wrote:
>> We offer the archives, including security, by rsync too.
>> And that should stay. Mirrors of security do exist, for good
>> reasons.[1]
>> Why does it need to be in the archive?
> [...]
> I don't know of any other way of getting files back out of dak.
So my first thought it will be. Some random structure on some random
place. Possibly an apache run by DSA or so, but nothing relying on our
mirrors.
As "getting files back out of dak" is simple. dak writes files where we
tell it to, see for example our changelog/metadata exports, buildd
queues, etc which don't live on the usual mirror network.
--
bye, Joerg
Reply to: