Re: pkgin repositories

[Jonathan Perkin <jperkin%joyent.com@localhost>]

* On 2018-11-01 at 22:32 GMT, Jason Bacon wrote:

> My current etc/pkgin/repositories.conf is as follows:
> 
> https://mirror1.hpc.uwm.edu/pkgsrc/packages/usr/pkg/RHEL7/All
> https://mirror2.hpc.uwm.edu/pkgsrc/packages/usr/pkg/RHEL7/All
> 
> I've noticed a few times that if either server is down, pkgin operations
> like update or install will fail.
> 
> I would have thought that if one server is down, it would fail over to the
> next one, but it appears
> they all have to be available.
> 
> Is this by design, and if so, for what reason?

Yes, this is the current design.  This is the first I've heard of
someone trying to use it for round-robin or failover type access.  It
was introduced in order to support additional repositories that
contain extra packages (usually locally-built) not available from the
primary.

The multiple repository code already has some rough edges with unclear
semantics on exactly how packages are chosen when available from
multiple repositories, and I wouldn't want to commit even further to
trying to support that.

-- 
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com