Hi Stefan,
Quoting Stefan Müller-Klieser (2018-01-22 14:28:48)
> I could not find a responsible mailinglist in the docs. Sorry if you are the
> wrong persons to address the patch to. It would be nice to have kind like
> this dev option for multistrap. Is this acceptable? Should this be done in a
Hi,
I could not find a responsible mailinglist in the docs. Sorry if you
are the wrong persons to address the patch to. It would be nice to have
kind like this dev option for multistrap. Is this acceptable? Should
this be done in a different way? Some fine tuning?
Thanks for your time!
Stefan
Since apt 1.5 it is not enough to have the noauth option for dev
repositories. The content of the release file will also be checked
before apt starts it work. To be able to use a repo without signing
infrastructure for development we need an additional option
allow-insecure=yes which can be set
I am also affected by this bug.
Since multistrap can only use keys it downloads from the host system's
repositories this effectively makes it impossible to use with anything
other than official Debian or Ubuntu repositories.
--
Alistair Buxton
a.j.bux...@gmail.com
Package: multistrap
Version: 2.2.9
Severity: important
--- Please enter the report below this line. ---
Hi.
Since (I assume) apt 1.5~alpha1 the following change is in apt (from
apts changelog):
* fail instead of warn on insecure repositories in apt-get
This makes multistraps initial package
5 matches
Mail list logo
