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

Re: ci.d.n direct access to experimental ?


On 29-06-18 16:49, Ian Jackson wrote:
> Ansgar Burchardt writes ("Re: ci.d.n direct access to experimental ?"):
>> On Fri, 2018-06-29 at 14:09 +0100, Ian Jackson wrote:
>>>  4. Wait ???? hours (2-8 hours?) for deb.debian.net to have the
>>>     updated package.
>> ci.d.n seems to use incoming.debian.org where packages are published
>> right after processing.  That's the earliest access we provide to
>> uploaded packages (and the one buildds also use)
>> Maybe the test runner needs to consider packages from the suite
>> "buildd-experimental" as well as just "experimental"?  They have
>> different names and the default pinning (to "1") might result in the
>> newer version in the buildd suite not to be considered by ci.d.n.
> I tried resubmitting my ci api request with a pin to
> `buildd-experimental' but ci.d.n's apt didn't know what to do with
> that:
>   Err:2 http://deb.debian.org/debian buildd-experimental Release
> Full log at
>   https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dgit/529850/log.gz
> Obviously either this is not the way to do it, or some more setup is
> needed at the server side.

As said on IRC, ci.d.n isn't configured yet to use incoming on top of
the regular archive from deb.debian.org for tests that involve pinning.
It's on my TODO list, albeit not very high. On top of that it is rather
complicated due to the different names.

Patches welcome, probably to both autopkgtest and ci.d.n.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: