Re: [Debian-ports-devel] Using incoming.debian.org on buildds
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 08/31/2015 03:16 PM, Aurelien Jarno wrote:
>> You can change the configuration for them as well already. I will
>> add the source repository entry as soon as they are back online.
>
> The configuration is not per buildd, but rather per architecture.
> Could you please make sure that for a given architecture, all of
> the buildds are using the incoming entry? If not wanna-buildd will
> offer the buildds without the incoming entry packages they can't
> build.
Ah, I didn't know.
Ok, I talked to Nobuhiro already and he will take care of the two
remaining buildds which are currently down. You can therefore change
the settings for sh4 completely now!
As for m68k, all my buildds have been updated and I think Torsten
Glaser updated ara5 as well. I just don't know about Christian's
buildd, garkin, but I'm sure he will quickly follow up on this
discussion :).
As for sparc64, I will get back to you regarding this. What about
sompek and sompek2? Have they been updated yet?
As for x32, there is only vs76 and frobozz and since vs76 has already
been switched over, it's just up to Daniel to change frobozz
as well.
> Yes, the incoming.debian-ports.org entry basically stopped being
> useful a few years ago when the .changes files have been removede
> from incoming.debian.org.
Ok, good to know!
Adrian
- --
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJV5FVBAAoJEHQmOzf1tfkTD8MP/3FI85WvKVM1hWODzy/gl+26
YiF9WFx0CRqzghYJbaOm1z69abH1f2lFQ7jRS68MSQnXV24/3YrIy60ALWVoJFBV
fRtx2K0abXEv0a46fKTBn73YdjOTcE03VDFTJc5cjZqxzQtNLcrSpJYxztlvcBrX
yGa4jvQSD/Qy43dNrk2BCXLoZ5m8C3GVFxoAv9+YyRMofblFuEH00B1Vvr9hcLxH
/vh8R/WZSgj5Fw8kkwzZX5MRBXUis/0mRQ4KKbPz2+uaTjCdBrVTAtzfPMh9CFgm
nA1qLvNqWScq1s7454BF+Enqn7tQibVLlVjQc3Qi31Aal13zhpJbkNiJK+0ioEPB
Us6IUqzwrU2s59ztqykcnFN6YpY+IB6feg/ouASj7dYYEj8td8k16q0dp7yvzuA2
fp5HeirQ5fj97KEkVH7YCelkDxVdT/pzcH5fQebkGR2QJV+6v7rwnzv4kgcQ9OyY
ayLnFqgo0kJvkWjSiaZxO1Nqof3SXnrtThZ8dyPGOITUPPUvR1Tks16zr1MmvsMX
r8Dv4vpACUEgeA5V7TSbM3cPIIFDDN1XPlYlSY4DT+BP62b4jkxYa6YGcaeW6TGT
41rlKi1ecEjhQx7oOvgyv0Bpq53z9UBGX8mw5VwfqeCTzOoQpnQgCRECCzPVohCy
35QzrCmay/dhEFoaWFqH
=2Qvt
-----END PGP SIGNATURE-----
Reply to: