On Mon, 05 Aug 2019 at 11:25:53 +0100, Simon McVittie wrote:
> On Mon, 05 Aug 2019 at 10:09:09 +0200, David Kalnischkies wrote:
> > The other thing is repositories without a Release file, which seems to
> > be something used (legally) by the same class of repositories only, too.
>
> [in OBS] anything short-term or
> purely automatic (like personal branches used to test a batch
> of changes) uses flat repositories, typically something like
> "deb
> https://build.example.com/home:/smcv:/branches:/mydistro:/1.x:/main:/my-topic-branch
> ./".
> I'll check whether OBS generates an unsigned Release file for those,
> or no Release at all.
It generates an unsigned Release file, so requiring Release files (but
allowing them to be unsigned if [trusted=yes]) would not break this
mechanism.
smcv
