[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Future of kFreeBSD in Debian unstable

Wouter Verhelst writes:
> On Mon, Jan 15, 2018 at 01:32:08PM +0000, Steven Chamberlain wrote:
>> Hi Ansgar,
>> Ansgar Burchardt wrote:
>> > however with the kFreeBSD buildds gone, we would also need at least some
>> > people willing to maintain buildds (this is limited to Debian Developers
>> > as long as the port lives on ftp.debian.org).
>> Assuming I could find/maintain a couple of VMs to build kfreebsd sid,
>> how exactly could the .debs be uploaded to ftp.d.o?  Are they simply
>> uploaded with ftp/scp along with a .changes/.buildinfo, just like a
>> binNMU or source package upload?
> Yes.
>> Would the buildds need their own GPG keys, added into some keyring also?
> GPG keys for buildds are in a separate keyring, and they are required to
> be limited to one year (since they are passwordless)
>> That's possible even for non-DSA maintained buildds?
> Yes, all the buildds for the other non-release ports (e.g., PowerPC,
> m68k, ...) do that.

For ports.d.o maybe; for ftp-master.d.o not: only DSA-maintained buildds
get automatic signing.

For non-DSA maintained buildds (hurd only?) the maintainer gets to
review the .changes and sign them with his own key.

Though it might make sense to move kfreebsd-* to ports.d.o.  That was
planned to happen for hurd-i386 too.


Reply to: