On 3/8/18 11:17 am, Kurt Jaeger wrote:
Hi!
I've asked for this but the answer is
"no we don't do that.. and have no plans to".
What is the rationale?
I don't know, but as the setup of your own package builder box
is simple enough -- wouldn't that be an alternative for you ?
If the answer is
On 4/8/18 7:44 am, Yuet-nan Wong via freebsd-ports wrote:
Are FreeBSD ports supposed to change version numbers when a change is made?
Issue is reproducibility is void when packages have changed like suricata or
the many changes to binutils. Some removing package content but version not
On Fri, Jul 20, 2018 at 05:52:51AM -0700, David Wolfskill wrote:
>
> A symptom is that an attempt to send a signed, unencrypted message
> yields a failure, with the messages:
>
> | gpg: skipped "0x6757003D": Unusable secret key
> | gpg: signing failed: Unusable secret key
>
I found a
Are FreeBSD ports supposed to change version numbers when a change is made?
Issue is reproducibility is void when packages have changed like suricata or
the many changes to binutils. Some removing package content but version not
changed. Need to diff Makefile is inefficient.
> And many 10s of GB which we would be forcing all the mirrors to carry
> (and remember, *N archs *n OSVERSIONS).
> This has been cited as a stopper in the past.
There's enough slack to pull down at least one
new quarter, how deep that slack goes hasn't
been chimed in on but this was copied out
Van: grarpamp
Datum: donderdag, 2 augustus 2018 22:21
Aan: freebsd-ports@freebsd.org
CC: freebsd-...@freebsd.org
Onderwerp: Re: Archives of last quarterly package builds?
> I've asked for this but the answer is
> "no we don't do that.. and have no plans to".
What is the rationale? Or is
On Thu, Aug 2, 2018 at 11:17 PM, Kurt Jaeger wrote:
> as the setup of your own package builder box
> is simple enough -- wouldn't that be an alternative for you ?
Simple and even done. Yet being local, that wouldn't cover others out
there who might have found or thought of similar or additional
