FreeBSD ports you maintain which are out of date

2019-11-27 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
archivers/zopfli| 1.0.2   | zopfli-1.0.3
+-+
emulators/mame  | 0.209   | mame0216
+-+
emulators/mess  | 0.209   | mame0216
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Reported by:portscout!
___
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: Checking you the maintainer of a port?

2019-11-27 Thread Kevin Oberman
On Wed, Nov 27, 2019 at 1:08 PM Brooks Davis  wrote:

> On Wed, Nov 27, 2019 at 02:05:56PM -0700, Janky Jay, III wrote:
> > Hello,
> >
> > On 11/27/19 2:03 PM, @lbutlr wrote:
> > > I thought that the maintainer of a port was listed somewhere in the
> files at user/ports//portbase/ but evidently not. What is the
> easiest way to find out, sitting in console on a server without a GUI, to
> find out who the maintainer is? (On my desktop I can just google and launch
> a browser, but that is not possible on most of the servers which do not
> have web clients installed.
> > >
> > > (Right now I am looking for the maintainer of roundcube, but this is a
> general question.)
> > >
> >
> >   Please see the "MAINTAINER=" line in the port's "Makefile".
>
> A slightly more general answer is:
>
> cd /usr/ports//; make -V MAINTAINER
>
> -- Brooks
>

Or:
make -C /usr/ports// maintainer
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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: Checking you the maintainer of a port?

2019-11-27 Thread Tatsuki Makino
I ride too.

pkg query %m package-name

___
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: Checking you the maintainer of a port?

2019-11-27 Thread @lbutlr
On 27 Nov 2019, at 14:05, Janky Jay, III  wrote:
> Please see the "MAINTAINER=" line in the port's "Makefile”.

Aw hell, I should have gripped all the files. I was sure it would’t be in the 
make file!



-- 
"Are you pondering what I'm pondering?"
"I think so, but where is a fish?”

___
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: Checking you the maintainer of a port?

2019-11-27 Thread Lars Engels
On Wed, Nov 27, 2019 at 09:07:55PM +, Brooks Davis wrote:
> On Wed, Nov 27, 2019 at 02:05:56PM -0700, Janky Jay, III wrote:
> > Hello,
> > 
> > On 11/27/19 2:03 PM, @lbutlr wrote:
> > > I thought that the maintainer of a port was listed somewhere in the files 
> > > at user/ports//portbase/ but evidently not. What is the easiest 
> > > way to find out, sitting in console on a server without a GUI, to find 
> > > out who the maintainer is? (On my desktop I can just google and launch a 
> > > browser, but that is not possible on most of the servers which do not 
> > > have web clients installed.
> > > 
> > > (Right now I am looking for the maintainer of roundcube, but this is a 
> > > general question.)
> > > 
> > 
> > Please see the "MAINTAINER=" line in the port's "Makefile".
> 
> A slightly more general answer is:
> 
> cd /usr/ports//; make -V MAINTAINER

There's already a target for it:

  make maintainer

in a port's directory.
___
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: Checking you the maintainer of a port?

2019-11-27 Thread Steve Kargl
On Wed, Nov 27, 2019 at 02:03:33PM -0700, @lbutlr wrote:
> I thought that the maintainer of a port was listed somewhere in the files at 
> user/ports//portbase/ but evidently not. What is the easiest way to 
> find out, sitting in console on a server without a GUI, to find out who the 
> maintainer is? (On my desktop I can just google and launch a browser, but 
> that is not possible on most of the servers which do not have web clients 
> installed.
> 
> (Right now I am looking for the maintainer of roundcube, but this is a 
> general question.)
> 
> 

man pkg-info

or

grep -i maintainer /path/to/port/Makefile

-- 
Steve
___
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: Checking you the maintainer of a port?

2019-11-27 Thread Brooks Davis
On Wed, Nov 27, 2019 at 02:05:56PM -0700, Janky Jay, III wrote:
> Hello,
> 
> On 11/27/19 2:03 PM, @lbutlr wrote:
> > I thought that the maintainer of a port was listed somewhere in the files 
> > at user/ports//portbase/ but evidently not. What is the easiest way 
> > to find out, sitting in console on a server without a GUI, to find out who 
> > the maintainer is? (On my desktop I can just google and launch a browser, 
> > but that is not possible on most of the servers which do not have web 
> > clients installed.
> > 
> > (Right now I am looking for the maintainer of roundcube, but this is a 
> > general question.)
> > 
> 
>   Please see the "MAINTAINER=" line in the port's "Makefile".

A slightly more general answer is:

cd /usr/ports//; make -V MAINTAINER

-- Brooks


signature.asc
Description: PGP signature


Re: Checking you the maintainer of a port?

2019-11-27 Thread Janky Jay, III
Hello,

On 11/27/19 2:03 PM, @lbutlr wrote:
> I thought that the maintainer of a port was listed somewhere in the files at 
> user/ports//portbase/ but evidently not. What is the easiest way to 
> find out, sitting in console on a server without a GUI, to find out who the 
> maintainer is? (On my desktop I can just google and launch a browser, but 
> that is not possible on most of the servers which do not have web clients 
> installed.
> 
> (Right now I am looking for the maintainer of roundcube, but this is a 
> general question.)
> 

Please see the "MAINTAINER=" line in the port's "Makefile".

Regards,
Janky Jay, III

___
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"


Checking you the maintainer of a port?

2019-11-27 Thread @lbutlr
I thought that the maintainer of a port was listed somewhere in the files at 
user/ports//portbase/ but evidently not. What is the easiest way to find 
out, sitting in console on a server without a GUI, to find out who the 
maintainer is? (On my desktop I can just google and launch a browser, but that 
is not possible on most of the servers which do not have web clients installed.

(Right now I am looking for the maintainer of roundcube, but this is a general 
question.)


-- 
Yeah, and I never wanted to kick Albert Einstein in the nuts.

___
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"


what's happening to mysql56-server ?

2019-11-27 Thread tech-lists

Hi,

On the 11th I submitted a PR for mysql56-server
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241870
as mysql56-server has been marked as vulnerable. No meaningful 
update since. Is mysql56-server lapsed/EoL on FreeBSD? I'm sure 
mysql56-server must be common in a freebsd context, so it's odd that
it's taking so long to update. I note that mysql57-server for FreeBSD 
has been EoL'd according to Oracle (see

https://www.mysql.com/support/eol-notice.html ) but nothing mentioned for
mysql56-server. 


Can anyone explain what's happening/what plans are regarding this port?

thanks
--
J.


signature.asc
Description: PGP signature


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
> > ===>  License BSD2CLAUSE accepted by the user
> > ===>   zfs-stats-1.2.2_1 depends on file: /usr/local/sbin/pkg - found
> > => zfs-stats-1.2.2.tar.gz doesn't seem to exist in 
> > /usr/local/poudriere/ports/default/distfiles/.
> > => Attempting to fetch 
> > https://cloud.github.com/downloads/mmatuska/zfs-stats/zfs-stats-1.2.2.tar.gz
> > fetch: 
> > https://cloud.github.com/downloads/mmatuska/zfs-stats/zfs-stats-1.2.2.tar.gz:
> >  No address record
> > => Attempting to fetch 
> > http://distcache.FreeBSD.org/ports-distfiles/zfs-stats-1.2.2.tar.gz
> > zfs-stats-1.2.2.tar.gz   9 kB   36 MBps 
> >00s
> > ===> Fetching all distfiles required by zfs-stats-1.2.2_1 for building
> > 
> > 
> > [dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ 
> > host cloud.github.com
> > cloud.github.com is an alias for d24z2fz21y4fag.cloudfront.net.
> > 
> > [dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ 
> > host d24z2fz21y4fag.cloudfront.net
> > [dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ 
> 
> 
> Further discussions via IRC indicate that we should stop using GHC because
> GitHub isn't going to do anything about this issue.
> 
> cloud.github.com isn't 'public', it's backend.


I have opened this PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242268

-- 
  Dan Langille
  d...@langille.org
___
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-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. Apologies if I
> > > am missing something, but it seems like they are not actually broken?
> > 
> > If you were building these ports previously, then you probably have the 
> > distfiles in your local distfiles cache already.  That will give the 
> > impression that everything is fine if you just try and build the port. 
> > If you didn't have a cached copy of the distfiles, then you'ld probably 
> > have a rather different experience.
> > 
> > Although if you can show that the distfiles are now fetchable, eg. by:
> > 
> >  make distclean
> >  make fetch
> > 
> > then by all means please do report it.  A PR with patches is preferred, 
> > but any reasonable mechanism for bringing it to the attention of 
> > developers is acceptable.
> 
> 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
> ===>  License BSD2CLAUSE accepted by the user
> ===>   zfs-stats-1.2.2_1 depends on file: /usr/local/sbin/pkg - found
> => zfs-stats-1.2.2.tar.gz doesn't seem to exist in 
> /usr/local/poudriere/ports/default/distfiles/.
> => Attempting to fetch 
> https://cloud.github.com/downloads/mmatuska/zfs-stats/zfs-stats-1.2.2.tar.gz
> fetch: 
> https://cloud.github.com/downloads/mmatuska/zfs-stats/zfs-stats-1.2.2.tar.gz: 
> No address record
> => Attempting to fetch 
> http://distcache.FreeBSD.org/ports-distfiles/zfs-stats-1.2.2.tar.gz
> zfs-stats-1.2.2.tar.gz   9 kB   36 MBps 
>00s
> ===> Fetching all distfiles required by zfs-stats-1.2.2_1 for building
> 
> 
> [dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ 
> host cloud.github.com
> cloud.github.com is an alias for d24z2fz21y4fag.cloudfront.net.
> 
> [dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ 
> host d24z2fz21y4fag.cloudfront.net
> [dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ 


Further discussions via IRC indicate that we should stop using GHC because
GitHub isn't going to do anything about this issue.

cloud.github.com isn't 'public', it's backend.

-- 
  Dan Langille
  d...@langille.org

___
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-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 they are not actually broken?
> 
> If you were building these ports previously, then you probably have the 
> distfiles in your local distfiles cache already.  That will give the 
> impression that everything is fine if you just try and build the port. 
> If you didn't have a cached copy of the distfiles, then you'ld probably 
> have a rather different experience.
> 
> Although if you can show that the distfiles are now fetchable, eg. by:
> 
>  make distclean
>  make fetch
> 
> then by all means please do report it.  A PR with patches is preferred, 
> but any reasonable mechanism for bringing it to the attention of 
> developers is acceptable.

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
===>  License BSD2CLAUSE accepted by the user
===>   zfs-stats-1.2.2_1 depends on file: /usr/local/sbin/pkg - found
=> zfs-stats-1.2.2.tar.gz doesn't seem to exist in 
/usr/local/poudriere/ports/default/distfiles/.
=> Attempting to fetch 
https://cloud.github.com/downloads/mmatuska/zfs-stats/zfs-stats-1.2.2.tar.gz
fetch: 
https://cloud.github.com/downloads/mmatuska/zfs-stats/zfs-stats-1.2.2.tar.gz: 
No address record
=> Attempting to fetch 
http://distcache.FreeBSD.org/ports-distfiles/zfs-stats-1.2.2.tar.gz
zfs-stats-1.2.2.tar.gz   9 kB   36 MBps00s
===> Fetching all distfiles required by zfs-stats-1.2.2_1 for building


[dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ host 
cloud.github.com
cloud.github.com is an alias for d24z2fz21y4fag.cloudfront.net.

[dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ host 
d24z2fz21y4fag.cloudfront.net
[dan@pkg01:/usr/local/poudriere/ports/default/sysutils/zfs-stats] $ 

-- 
  Dan Langille
  d...@langille.org
___
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"