Either of these should "just work" on any supported FreeBSD release
which would be 12.2 or 11.4 (13.0 will be out the door shortly).
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing
ing a parameter to tell the ports system to first
install dependencies via "bundler" then build the software using
"rake". Any insights or other ports I could look at would be really
appreciated!
Thanks,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
bsd.org/bugzilla/show_bug.cgi?id=245747
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
ess their is an
option missing in the default pkg I'd highly recommend going that route.
(look for all postgresql11 pkgs available)
$ pkg search postgresql11
(install psql server for example)
$ pkg install postgresql11-server
cheers,
On 5/26/20 5:24 PM, Jan Beich wrote:
Pete Wright writes:
hello - on current i found myself in a situation where python37 was
unable to import ssl:
$ python3.7
Python 3.7.7 (default, May 9 2020, 01:37:42)
[Clang 10.0.0 (g...@github.com:llvm/llvm-project.git
llvmorg-10.0.0-0-gd32170dbd on
s are working again as it
looked like the pbuilder did rebuild python after this commit. But pkg
upgrade didn't detect a new version, so I think it might be helpful to
bump the python version's so that people on CURRENT don't end up in the
same situation I was in? No
On 5/6/20 2:51 PM, Pete Wright wrote:
Hello,
I am noticing this error with xpdf recently:
$ xpdf
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even
though it was found.
This application failed to start because n
kages,
but it seems like xpdf is the only thing being effected. Anyone else
seeing this?
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
rts tree locally.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
webapp, so i'm confident it will run w/o issues.
-p
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to &qu
or you to take a
look at if that sounds good.
cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail t
g this
on my end was curios to see what experiences other have had with it.
cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubsc
independent of
this (i.e. you don't necc need debug symbols to use dtrace probes).
-p
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe,
it
updated? I e-mailed the maintainer and haven't heard back.
I'd suggest submitting a ticket in bugzilla with your update attached,
this should make it easier for the port maintainer to update on their
end. it'll also increase the visibility.
-pete
--
Pete Wright
p...@nom
you seeing with
mesa-libs?
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
ist
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailm
On 3/13/19 5:08 PM, Adam wrote:
On Wed, Mar 13, 2019 at 11:30 PM Pete Wright wrote:
i am running firefox-65.0.2,1 and notice that i can no longer use
container tabs in the application. the menu to select containers no
longer appears, and old container tabs i had open do not show up in my
this, is this expected behavior?
cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port
On 12/30/18 4:31 PM, Adam Weinberger wrote:
On Sun, Dec 30, 2018 at 5:27 PM Pete Wright wrote:
On 12/29/18 5:35 PM, Yasuhiro KIMURA wrote:
From: Adam Weinberger
Subject: Re: Request for help: remove bundler from ruby 2.6 port
Date: Sat, 29 Dec 2018 15:34:17 -0700
I think perhaps it&#
and bundler) by default. They are basic components of ruby
itself, and ports should provide //optional// newer versions of them.
From: Pete Wright
Subject: Re: Request for help: remove bundler from ruby 2.6 port
Date: Sat, 29 Dec 2018 16:41:32 -0800
+1 from me on this.
i think the benefits of lower
ng overhead combined with the
fact that most ruby envs i've supported (and currently support) are
built around the expectation that rake, gem and bundler are all
available - so this would lower my administrative overhead as well.
i will hopefully have time to give your patch a test on my e
ake that most people
won't really care about :) +1 from me!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send a
you since I don't think there is a build job dispatcher/scheduler
available in Poudriere. So for example you may find yourself in a
situation where multiple jails try building LLVM as it's first package
which wouldn't really be helpful.
-pete
--
a
"make package" in the port directory. then i can install the updated
code as a pkg for future upgrade convenience. this works great for
ports without many external dependencies at build-time, not so much when
things like llvm need to be build ;)
-pete
--
Pete Wright
p...@noma
a good improvement.
it would encourage people to get more comfortable with the pkg tool
itself while not changing the default behaviour that experienced
admins/users have gotten used to.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
free
On 04/22/2018 14:27, Eitan Adler wrote:
On 22 April 2018 at 13:20, Pete Wright wrote:
On Apr 22, 2018 12:57 PM, Eitan Adler wrote:
On 25 November 2017 at 10:50, Stefan Lambrev wrote:
Hi,
I've got the port to a working state (
https://github.com/cheffo/FreeBSD-Ports/tree/master/net
___
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"
On 03/27/2018 15:06, Guido Falsi wrote:
On 03/28/18 00:00, Pete Wright wrote:
I'm not a python expert, but I understand that python 2.7 and python 3
are two slightly different languages not fully compatible with each
other.
I also understand(but have not gone into depth about this)
ticking on the 2.x codebase
as it is reaching EOL status in 2020:
https://www.python.org/dev/peps/pep-0373/
Hopefully a solid deadline (which has already been pushed back) will
motivate developers to accelerate the task of migrating to py3 sooner
rather than late
On 03/21/2018 15:44, Ben Woods wrote:
On Thu, 22 Mar 2018 at 5:49 am, Pete Wright wrote:
Interestingly enough I'm unable to get log messages to end up in
/var/log/influxdb/influxd.log. When I manually run daemon, without any
syslog flags passed, I do see plenty of logs ending up in s
ough I'm unable to get log messages to end up in
/var/log/influxdb/influxd.log. When I manually run daemon, without any
syslog flags passed, I do see plenty of logs ending up in stdout tho.
I'm guessing I'm tired and missing something obvious - any other
influxdb people have log
ative is for FreeBSD to continue to be an
afterthought by freedesktop and Wayland community which doesn't seem
like a good long-term strategy IMHO.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
thub.com/npm/npm/releases/tag/v5.6.0
hrm i wonder if this would also resolve this PR i filed a little while ago:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223615
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.
how we build firefox but if this looks good
i can file a PR.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
logic/53e81ba377a4a475351c3b8309be7598
is this expected? maybe i missed a heads up email to this list?
cheers,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-
of several linux distros
where something like this would have saved me lots of cycles due to
having to maintain my own versions (or flavors i guess) of common packages.
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.o
e24 itself.
hope this helps,
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
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"
as i'd like to tinker with this.
cheers!
-pete
--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-port
On 06/04/2017 09:54, Kubilay Kocak wrote:
On 6/5/17 2:50 AM, Pete Wright wrote:
Hi there,
I have a webapp that is making use of textproc/py-enchant for
spellchecking in some input forms we use. when i install py-enchant via
pip it only requires some libraries that ship with textproc/enchant
build this port w/o
the wxPython dependency? I can confirm the py-enchant works fine
without wxPython when it is installed via pip inside a python venv. My
understanding is that the USE_* flags are not really meant to be
user-settable.
Cheers,
-pete
--
Pete Wright
p...@nomadlogic.or
On 02/09/2017 08:57, Andrea Venturoli wrote:
On 01/24/17 00:55, Baptiste Daroussin wrote:
Hi all,
This is a call for testing for newer Xorg along with newer drivers:
intel and
ati.
Hello.
Thanks for your work.
I'm willing to test this, since I'm experiencing frequent X lock ups
on an In
On 01/24/2017 11:26, Matthieu Volat wrote:
On Tue, 24 Jan 2017 11:12:56 -0800
Pete Wright wrote:
On 01/24/2017 00:55, Matthieu Volat wrote:
On Tue, 24 Jan 2017 00:55:16 +0100
Baptiste Daroussin wrote:
Hi all,
This is a call for testing for newer Xorg along with newer drivers: intel and
On 01/24/2017 00:55, Matthieu Volat wrote:
On Tue, 24 Jan 2017 00:55:16 +0100
Baptiste Daroussin wrote:
Hi all,
This is a call for testing for newer Xorg along with newer drivers: intel and
ati.
The patch against the head ports: https://people.freebsd.org/~bapt/newxorg.diff
Note that you
On 1/23/17 4:05 PM, Baptiste Daroussin wrote:
On Mon, Jan 23, 2017 at 04:04:10PM -0800, Pete Wright wrote:
On 1/23/17 3:55 PM, Baptiste Daroussin wrote:
Hi all,
This is a call for testing for newer Xorg along with newer drivers: intel and
ati.
The patch against the head ports: https
diff in this PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214591
cheers!
-pete
--
Pete Wright
p...@nomadlogic.org
nomadlogicLA
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe
45 matches
Mail list logo
