Re: Hadoop-ecosystem ports
Here's the PR for Hadoop 3.1 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231048 Items on the TODO list are outlined in BZ. Thanks, -xmj On 07/12/2018 22:21, Kurt Jaeger wrote: > Hi! > >> I will be working on making Hadoop a first class citizen on FreeBSD. > > Thanks, that sounds helpful, as that is a large group of applications. > >> This will include bumping the existing ports for Hadoop, HBase, Oozie, >> Spark (probably some others as well), and creating ports for HUE, Sqoop, >> Zeppelin, Flume, Ambari and a variety of other projects maintained by >> the ASF. Think Hortonworks HDP/Cloudera CDH/MapR, just on FreeBSD. >> >> This can't be done on just one laptop and I'm looking for people >> interested in testing and reviewing them. > >> Preferably also someone with hardware to stand up a large enough cluster >> as reference architecture, to show that Hadoop on FreeBSD trumps Hadoop >> on Linux. > > I can provide a 32 GB / 4c+4t box as a testing environment, if it > helps. > >> What's a good mailing list to coordinate this effort on? Given that >> they're mostly Apache projects, would apache@ be a good fit? > > apache@ looks very limited to the webserver (if you review > the last few month of posts). > > For a start, use ports@. If ports@ gets too much hadoop-related > posts, you can always ask postmaster@ to add a list, like > freebsd-hadoop@ or something similar. > > https://wiki.freebsd.org/Teams/postmaster#How_to_create_a_new_list.3F > > says: > > What we need > > Terse (one-line) description of list. > More verbose description of list. > Any deviations from these defaults: > Max message body size: 200KB > Not moderated > Open (subscription not required for) posting > Public archives > "Official" name of list "foo" is "freebsd-foo" > List is a technical list (vs. freebsd-chat@) > List is for discussions (vs. freebsd-announce@) > No designated non-postmaster "moderator" or "list administrator" > signature.asc Description: OpenPGP digital signature
Re: Committer for java/jdk8-doc update
On 31 August 2018 at 08:26, Kurt Jaeger wrote: > Hi! > >> Anyone available to take: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230811 >> >> It's a simple update with just version and distinfo changes. > > Done. Thanks! -- Jonathan Chen ___ 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: Committer for java/jdk8-doc update
Hi! > Anyone available to take: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230811 > > It's a simple update with just version and distinfo changes. Done. -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ 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: Cannot specify ntpd binary in ports with ntpd startup file.
In message
, Adam Weinberger writes:
> On Tue, Aug 28, 2018 at 6:34 PM Dan Mahoney (Gushi) wrote
> :
> >
> > 1) Got the version wrong. I'm on 10.4.
> >
> > 2) Forgot a subject. Whoops.
> >
> > 3) Forgot to cc maintainer. Doh!
> >
> > -Dan
> >
> > On Tue, 28 Aug 2018, Dan Mahoney (Gushi) wrote:
> >
> > > Hey all,
> > >
> > > Funny question. I'm on FreeBSD 11.4, and would like to use the latest
> > > version of NTP, which is in pkg.
> > >
> > > The version in pkg doesn't have a startup script, which I'm not sure is
> > > supposed to be the case. I know for things like BIND (when it was both i
> n
> > > base and in ports) you could override the binary in /etc/rc.conf.
> > >
> > > However, the version of /etc/rc.d/ntpd in BASE doesn't seem to have the
> > > ability to override the binary in rc.conf:
> > >
> > > name="ntpd"
> > > rcvar="ntpd_enable"
> > > command="/usr/sbin/${name}"
> > > pidfile="/var/run/${name}.pid"
> > > extra_commands="fetch"
> > > fetch_cmd="ntpd_fetch_leapfile"
> > > start_precmd="ntpd_precmd"
> > >
> > > What's weirder, is even if I manually modify the /etc/rc.d/ntpd file to p
> oint
> > > at /usr/local/sbin (which I should never have to do), the version in
> > > /usr/sbin gets started.
> > >
> > > root@vortex2:/etc/rc.d # service ntpd start
> > > Starting ntpd.
> > > root@vortex2:/etc/rc.d # ps auxwww|grep ntpd
> > > root 36362 38.3 0.2 26192 18132 - Ss 12:17AM0:04.73
> > > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drif
> t
> > > root 36364 0.0 0.0 18844 2328 1 R+ 12:17AM0:00.00 grep nt
> pd
> > > root@vortex2:/etc/rc.d # grep command ntpd
> > > command="/usr/local/sbin/${name}"
> > > [...]
> > >
> > > So, asking as a port maintainer, a few questions:
> > >
> > > 0) Why the heck is it doing this even when I override the path?
> > >
> > > 1) How can we encourage base to allow override of command_name?
> > >
> > > 2) Is this a brokenness in the port that it doesn't ship with a startup f
> ile?
> > >
> > > 3) Not strictly related, but what's the proper case for pathing since thi
> ngs
> > > like "ntpq", the base path would naturally be found in any standard $PATH
> .
> > > Some ports used to have an overwrite_base option, but this also feels wro
> ng
> > > as it breaks freebsd-update in various ways. I.e. should the port print
> a
> > > message stating that you should chmod 000 the original binaries? Should
> the
> > > ports versions be named something different? Should the port just warn y
> ou
> > > that you need to call these things by absolute path, always?
> > >
> > > -Dan
>
> Ping: cy
>
> Why does net/ntp not include an rc(8) script or a pkg-message
> describing how to activate it? It would go a long way if you could add
> at least one of those things.
The former makes no sense but the latter could be done. I'll put it on
my todo list.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
___
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: Cannot specify ntpd binary in ports with ntpd startup file.
On Tue, Aug 28, 2018 at 6:34 PM Dan Mahoney (Gushi) wrote:
>
> 1) Got the version wrong. I'm on 10.4.
>
> 2) Forgot a subject. Whoops.
>
> 3) Forgot to cc maintainer. Doh!
>
> -Dan
>
> On Tue, 28 Aug 2018, Dan Mahoney (Gushi) wrote:
>
> > Hey all,
> >
> > Funny question. I'm on FreeBSD 11.4, and would like to use the latest
> > version of NTP, which is in pkg.
> >
> > The version in pkg doesn't have a startup script, which I'm not sure is
> > supposed to be the case. I know for things like BIND (when it was both in
> > base and in ports) you could override the binary in /etc/rc.conf.
> >
> > However, the version of /etc/rc.d/ntpd in BASE doesn't seem to have the
> > ability to override the binary in rc.conf:
> >
> > name="ntpd"
> > rcvar="ntpd_enable"
> > command="/usr/sbin/${name}"
> > pidfile="/var/run/${name}.pid"
> > extra_commands="fetch"
> > fetch_cmd="ntpd_fetch_leapfile"
> > start_precmd="ntpd_precmd"
> >
> > What's weirder, is even if I manually modify the /etc/rc.d/ntpd file to
> > point
> > at /usr/local/sbin (which I should never have to do), the version in
> > /usr/sbin gets started.
> >
> > root@vortex2:/etc/rc.d # service ntpd start
> > Starting ntpd.
> > root@vortex2:/etc/rc.d # ps auxwww|grep ntpd
> > root 36362 38.3 0.2 26192 18132 - Ss 12:17AM0:04.73
> > /usr/sbin/ntpd -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drift
> > root 36364 0.0 0.0 18844 2328 1 R+ 12:17AM0:00.00 grep ntpd
> > root@vortex2:/etc/rc.d # grep command ntpd
> > command="/usr/local/sbin/${name}"
> > [...]
> >
> > So, asking as a port maintainer, a few questions:
> >
> > 0) Why the heck is it doing this even when I override the path?
> >
> > 1) How can we encourage base to allow override of command_name?
> >
> > 2) Is this a brokenness in the port that it doesn't ship with a startup
> > file?
> >
> > 3) Not strictly related, but what's the proper case for pathing since things
> > like "ntpq", the base path would naturally be found in any standard $PATH.
> > Some ports used to have an overwrite_base option, but this also feels wrong
> > as it breaks freebsd-update in various ways. I.e. should the port print a
> > message stating that you should chmod 000 the original binaries? Should the
> > ports versions be named something different? Should the port just warn you
> > that you need to call these things by absolute path, always?
> >
> > -Dan
Ping: cy
Why does net/ntp not include an rc(8) script or a pkg-message
describing how to activate it? It would go a long way if you could add
at least one of those things.
# Adam
--
Adam Weinberger
ad...@adamw.org
https://www.adamw.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: Cannot specify ntpd binary in ports with ntpd startup file.
On Tue, 28 Aug 2018 17:34:08 -0700 (PDT) Dan Mahoney (Gushi) wrote: > 1) Got the version wrong. I'm on 10.4. > > 2) Forgot a subject. Whoops. > > 3) Forgot to cc maintainer. Doh! > > -Dan > > On Tue, 28 Aug 2018, Dan Mahoney (Gushi) wrote: > > > Hey all, > > > > Funny question. I'm on FreeBSD 11.4, and would like to use the > > latest version of NTP, which is in pkg. If you mean opennntp, that's not a later version, it's a different implementation. > > The version in pkg doesn't have a startup script, which I'm not > > sure is supposed to be the case. My ports tree is a bit out of date, but it does appear to have a startup script. Where you looking in /usr/local/etc/rc.d/? ___ 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"
FreeBSD ports you maintain which are out of date
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 +-+ devel/libparserutils| 0.2.3 | 0.2.4 +-+ devel/nsgenbind | 0.5 | 0.6 +-+ emulators/mame | 0.200 | mame0201 +-+ emulators/mess | 0.200 | mame0201 +-+ graphics/libnsgif | 0.2.0 | 0.2.1 +-+ textproc/libcss | 0.7.0 | 0.8.0 +-+ www/libdom | 0.3.2 | 0.3.3 +-+ 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 Thanks. ___ 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"
