Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-27 Thread Dan Langille
On Wed, Nov 27, 2019, at 12:26 PM, Dan Langille wrote: > On Wed, Nov 27, 2019, at 8:36 AM, Dan Langille wrote: > > This appears to be a DNS issue. > > > > [dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ > > sudo make makesum > > ===> License BSD2CLAUSE accepted by the user >

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-27 Thread Dan Langille
On Wed, Nov 27, 2019, at 8:36 AM, Dan Langille wrote: > On Fri, Nov 15, 2019, at 10:44 AM, Matthew Seaman wrote: > > On 15/11/2019 15:25, Nick Rogers wrote: > > > For me the affected ports were sysutils/pftop, sysutils/zfs-stats, and > > > sysutils/stress, which worked just fine before this commit.

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-27 Thread Dan Langille
On Fri, Nov 15, 2019, at 10:44 AM, Matthew Seaman wrote: > On 15/11/2019 15:25, Nick Rogers wrote: > > For me the affected ports were sysutils/pftop, sysutils/zfs-stats, and > > sysutils/stress, which worked just fine before this commit. Apologies if I > > am missing something, but it seems like th

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-15 Thread w.schwarzenfeld
A PR for zfs-stats already exists: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241963 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-15 Thread Tatsuki Makino
Hello. Could you include this as well? pkg delete -f ca_root_nss Do some rely on MASTER_SITE_BACKUP? Regards. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebs

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-15 Thread w.schwarzenfeld
Sorry, was too fast. pftop is wrong. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-15 Thread Jan Beich
Matthew Seaman writes: > On 15/11/2019 15:25, Nick Rogers wrote: > >> For me the affected ports were sysutils/pftop, sysutils/zfs-stats, and >> sysutils/stress, which worked just fine before this commit. Apologies if I >> am missing something, but it seems like they are not actually broken? > > I

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-15 Thread w.schwarzenfeld
For pftop https://github.com/freebsd/freebsd-ports/tree/master/sysutils/pftop and zfs-stats https://github.com/mmatuska/zfs-stats ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, s

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-15 Thread w.schwarzenfeld
For stress https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241986 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-15 Thread Matthew Seaman
On 15/11/2019 15:25, Nick Rogers wrote: For me the affected ports were sysutils/pftop, sysutils/zfs-stats, and sysutils/stress, which worked just fine before this commit. Apologies if I am missing something, but it seems like they are not actually broken? If you were building these ports previo

Many ports recently marked BROKEN/unfetchable that aren't broken?

2019-11-15 Thread Nick Rogers
Hello, I'm not sure if this belongs in a bug report or not, but it seems that a recent commit marked many ports BROKEN with reason "unfetchable". However, I don't seem to have a problem fetching and building them if I remove the BROKEN declaration. The commit was: