I submitted the send-pr patch for stable a long time ago. It must not have
been committed? I will resend.
Nick
--Original Message--
From: Doug Barton
To: James Chang
Cc: freebsd-ports
Cc: n...@rogness.net
Subject: Re: About snort_inline in FreeBSD port tree
Sent: Apr 21, 2010 11:39 PM
not changing options
but selecting "OK" (note the "ruby+nopthreads" bits):
# This file is auto-generated by 'make config'.
# No user-servicable parts inside!
# Options for ruby+nopthreads-1.8.7.160_3,1
_OPTIONS_READ=ruby+nopthreads-1.8.7.160_3,1
WITHOUT_ONIGURUMA=
On Mon, 2009-06-22 at 15:37 -0700, Doug Barton wrote:
> Nick Withers wrote:
> > Hello all!
> >
> > I was surprised to see, when trying to update lang/ruby18 today, that
> > the to-be-installed package would be named "ruby
> > +nopthreads-1.8.7.160_3,
p
security/osslsigncode
sysutils/apt
sysutils/farbot
sysutils/ipmi-kmod
Thanks much!
Nick
Index: net/splatd/Makefile
===
RCS file: /home/pcvs/ports/net/splatd/Makefile,v
retrieving revision 1.9
diff -u -r1.9 Makefile
--- net/splatd/Make
I'm having the same problem as outlined in this thread...
http://forums.freebsd.org/showthread.php?t=9280
In short, using the freeradius perl module in conjunction with a perl script
that requires perl modules that use shared libraries seems to be
problematic. Identical setup worked fine under Fr
I installed FreeBSD 8.0-RELEASE from official ISO and used pkg_add -r to
install the packages. I also tried building my own packages from ports tree
and got the same result.
On Tue, Jan 5, 2010 at 12:52 PM, Garrett Cooper wrote:
> Sent from my iPhone
>
>
> On Jan 5, 2010, at 10
I started a thread discussing a similar problem a few days ago but I would
like to repost a more concise statement and a way to replicate easily.
There seems to be some kind of shared library linking issue between the
freeradius2 and perl packages compiled from RELEASE_8_0 ports tree branch.
If on
I've tried using portupgrade to build and install the freeradius2 package on
a fresh 8.0-RELEASE install with latest ports tree and that did not seem to
change anything.
On Tue, Jan 5, 2010 at 2:04 PM, Jerry wrote:
> On Tue, 5 Jan 2010 15:21:04 -0500 Nick Rogers
> articulat
/* HAVE_LT_DLADVISE_INIT */
#endif /* WITHOUT_LIBLTDL */
static int virtual_server_idx(const char *name)
On Thu, Jan 7, 2010 at 3:30 PM, Nick Rogers wrote:
> I've tried using portupgrade to build and install the freeradius2 package
> on a fresh 8.0-RELEASE install with latest ports tree and that d
*/
#endif /* WITHOUT_LIBLTDL */
static int virtual_server_idx(const char *name)
On Thu, Jan 7, 2010 at 8:19 AM, Nick Rogers wrote:
> I started a thread discussing a similar problem a few days ago but I would
> like to repost a more concise statement and a way to replicate easily.
>
I just replied to a similar thread on this list and included my private copy
of the port. It doesn't seem like the maintainer is responding or has
upgraded to 2.1.8.
On Tue, Feb 2, 2010 at 2:19 AM, Roar Pettersen wrote:
> Hi Nick !
>
>
> upgrade the freeradius2 port to version
I had pretty much the same problem. To solve it and get a workable package I
had to manually upgrade the current port to 2.1.8, which involved updating
the port's plist, distinfo and of course the version. I also had to add the
below patch which was pointed out to me by Alan DeKok over at the FreeR
> I've attached a copy of the port directory that I used to build a working
> 2.1.8 package in case anyone wants to give that a go. I'm not 100% sure the
> new PLIST is correct but the important part is the new "patch-libltdl-api"
> file that I added. It would be great if the port maintainer could
On Tue, Feb 2, 2010 at 10:02 AM, Nick Rogers wrote:
>
> I've attached a copy of the port directory that I used to build a working
>> 2.1.8 package in case anyone wants to give that a go. I'm not 100% sure the
>> new PLIST is correct but the important part is the new
>
>
> Please see the second patch in ports/140897.
>
> The maintainer has not responded so I will be committing that shortly.
>
> -- WXS
>
Thanks a bunch. I've also just filed PR ports/143493 to try and address a
problem with rlm_perl.
___
freebsd-ports@
d out in the next couple of days, along with the drupal6 update.
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On 11/02/2012 21:57, Darrel wrote:
> Just checking that you had seen the updates.
http://www.freebsd.org/cgi/query-pr.cgi?pr=165101
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscr
On 13/12/2010 12:47, Andrea Venturoli wrote:
Since I'd like to use Flyspray and Postgres, I'm looking into some insight
on this: is this only a limitation of the port?
yup. I was just too lazy to look at supporting it. If you want to submit
some patches, that would be go
On 2 Jan 2011, at 15:40, David Southwell ARPS wrote:
> Any chance of a ports upgrade to drupal 6.20
Someone submitted a pr for this earlier this morning. I'll take a look at it
later
Nick
>
___
freebsd-ports@freebsd.org mailin
t; drupal7 is
completed.
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ge in
the near future. So, unless anyone has any overriding objections, my
preference would be to see it deleted on or around 2011/06/01, i.e. 5
months after drupal7 is released, and about 2 months from now.
Nick
___
freebsd-ports@freebsd.org mailing
's a
new patch. I'll submit it to GNATS.
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On 23/10/2012 10:27, Nick Hilliard wrote:
> Damn, the patch submission process turned all the CRLFs into LFs. Here's a
> new patch. I'll submit it to GNATS.
ports/172976
Nick
___
freebsd-ports@freebsd.org mailing list
http://l
you!
-Nick
___
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 Wed, Feb 6, 2019 at 1:59 PM Kevin Oberman wrote:
> On Wed, Feb 6, 2019 at 7:55 AM Nick Rogers wrote:
>
>> I am wondering if it is wise or possible to use libressl for only a single
>> installed port, while continuing to use OpenSSL from Base for all
>> remaining
>
On Wed, Feb 6, 2019 at 5:32 PM Nick Rogers wrote:
>
>
> On Wed, Feb 6, 2019 at 1:59 PM Kevin Oberman wrote:
>
>> On Wed, Feb 6, 2019 at 7:55 AM Nick Rogers wrote:
>>
>>> I am wondering if it is wise or possible to use libressl for only a
>>> single
&
...
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?
Thanks,
-Nick
___
freebsd-ports@
Sounds like something the foundation might be able to help with.
On Mon, Dec 30, 2019 at 6:41 AM Carmel NY wrote:
> On Sun, 29 Dec 2019 18:51:41 -0700, Adam Weinberger stated:
> >On Sun, Dec 29, 2019 at 6:38 PM Kevin P. Neal
> >wrote:
> >>
> >> On Sat, Dec 28, 2019 at 01:01:52AM -0600, Greg Ri
ve successfully used PKG_NOCOMPRESS in make.conf. and not sure what I'm
doing wrong here.
Thanks,
Nick Wolff
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail t
Thanks that gives me a real good starting point.
On Thu, Jan 9, 2020 at 8:02 AM Mathieu Arnold wrote:
> On Wed, Jan 08, 2020 at 12:37:55PM -0500, Nick Wolff wrote:
> > I'm trying to get zstd packages built locally with poudriere but
> something
> > is failing. I'
Hi All,
Alex S has done a lot of hard work on a steam port and many other things on
freebsd in this area. Can we get some eyeballs on his steam port. Much
Appreciated.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244207
Hope you don't mind this email alex just saw lack of response for some
r
Hello Adriaan ,
https://svnweb.freebsd.org/ports?view=revision&revision=560251 Seems to
cause poudriere to puke due to a missing line in graphics/Makefile for new
port dependency you added.
You might have already seen/been alerted of this/fixed it. But either way
below is the patch I did to fix
e any way of fixing an installation of v 1.0.2?
I'll take a look at porting 1.0.3 shortly (i.e. this week).
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "
e any way of fixing an installation of v 1.0.2?
netdot-1.0.4 has just been committed to ports. You should upgrade.
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to &q
Hi,
mail/dovecot2 got upgraded to 2.2.2 which breaks this port.
Rgds,
N.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
security/openvpn-auth-ldap has failed to build for some time due to a minor
change in the layout of the openvpn sources. I prepared a fix for this but
haven’t yet found someone to commit it for me, and also made it so the port can
build on 9.x and later, along with a couple of other small fixes.
> On Jan 2, 2014, at 1:15, Matthias Andree wrote:
>
> Am 01.01.2014 23:58, schrieb Nick Barkas:
>
>> security/openvpn-auth-ldap has failed to build for some time due to a
>> minor change in the layout of the openvpn sources. I prepared a fix
>> for this but haven
On Mon, Jan 26, 2015 at 12:25 PM, Marko Cupać wrote:
> On Mon, 26 Jan 2015 16:20:46 +
> Matthew Seaman wrote:
>
> > >> > Also, is there a chance they will be pushed to freebsd-update?
> >
> > No. Unless these are either security fixes or fixes for a major
> > regression (which this is not)
On Fri, Jan 30, 2015 at 8:51 PM, Kevin Oberman wrote:
> On Wed, Jan 28, 2015 at 6:58 AM, Dr. Peter Voigt wrote:
>
> > On Tue, 27 Jan 2015 11:51:51 +0100
> > Marko Cupać wrote:
> >
> > > On Tue, 27 Jan 2015 07:11:10 +
> > > Matthew Seaman wrote:
> > >
> > > > On 2015/01/27 03:52, Kurt Jaege
we want to keep 3.4 as the "stable"
version for a while. I am just wondering because I would like to move my
production environment from squid 3.4 to 3.5, and am happy to contribute
patches to the ports tree, but am not sure what the plans are.
Than
ns/
>
> I would recommend removing all the older unsupported versions except 3.5.
I agree, although it looks like www/squid was just updated to 3.4.12.
https://svnweb.freebsd.org/ports?view=revision&revision=379384
>
> On Wed, Feb 18, 2015 at 8:50 PM, Nick Rogers wrote:
&g
On Fri, Feb 20, 2015 at 11:28 PM, Marko Cupać wrote:
> On Thu, 19 Feb 2015 21:23:15 -0500
> Robert Simmons wrote:
>
>
> > That is true. It looks like an update to both 3.5 and 3.4 were
> > released on the same day. How about dropping www/squid33 and creating
> > a www/squid34 port. Then updating
On Mon, Feb 23, 2015 at 8:18 AM, Johan Hendriks
wrote:
>
> Op 23-02-15 om 16:31 schreef Marko Cupać:
>
>> On Sat, 21 Feb 2015 08:28:40 +0100
>> Marko Cupać wrote:
>>
>> On Thu, 19 Feb 2015 21:23:15 -0500
>>> Robert Simmons wrote:
>>>
>>>
>>> That is true. It looks like an update to both 3.5 a
e
root# netstat -rn | grep default
default192.168.92.2 UGS em0
I am hoping someone can shed some light on this issue. Thank you.
-Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
On Tue, Jun 30, 2015 at 11:54 AM, Dimitry Andric wrote:
> On 30 Jun 2015, at 18:48, Nick Rogers wrote:
> ...
> > I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where
> > tcp_outgoing_address correctly rewrites the source address of outgoing
> > packet
On Tue, Jun 30, 2015 at 2:36 PM, Nick Rogers wrote:
>
>
> On Tue, Jun 30, 2015 at 11:54 AM, Dimitry Andric wrote:
>
>> On 30 Jun 2015, at 18:48, Nick Rogers wrote:
>> ...
>> > I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where
>> > t
On Wed, Jul 15, 2015 at 7:33 AM, timp wrote:
> > > Ok, so you don't see the difference too, do you?
> >
> > Actually I do see the difference - I think the current layout is
> > better. My point was that "I can't see any difference" isn't a good
> > argument for making disruptive change.
> >
> >
>
On Thu, Jul 16, 2015 at 1:05 AM, timp wrote:
> Hi Nick!
>
> > FWIW, I have the squid port installed on hundreds of systems, however I
> do
> > not use the port defaults and have logs and cache on a separate
> filesystem
> > mounted in /squid (i.e., /squid/logs, /s
code.
https://github.com/freebsd/pkg/commit/7e5152d942cba492142c7a226974913b9d38af21
The list of packages that are left-out is the same every time, but I do not
notice any correlation between them as far as how they are named or what
not, but there must be some similarity.
Hoping someone can shed so
.tar.gz respectively.
Is there any way someone could update this is the ports tree? It would be great
to be able to run the emulator on my machine.
Thanks for any help in advance :)
Kind regards,
Nick
___
freebsd-ports@freebsd.org mailing list
https
Hi Lowell,
Apologies - ntpd wasn’t set up properly so my portsnap cronjob was failing - I
thought my ports were up to date.
Kind regards,
Nick
> On 27 Dec 2015, at 19:35, Lowell Gilbert
> wrote:
>
> Nick Date writes:
>
>> Hi there,
>>
>> I was just tryin
I've submitted a PR with an update: http://www.freebsd.org/cgi/query-
pr.cgi?pr=79
Thanks
Nick
On Mar 31, 2007, at 11:42 PM, Thomas Schürmann wrote:
Hello,
From otrs.org
2007-03-05 OTRS 2.1.6 (Playa Esmeralda) is released!
Can you make an update?
gree
Try increasing the amount of memory available to PHP processes in php.ini;
i.e.
memory_limit = 32M
Nick
Paul Schmehl wrote:
Tried to portupgrade pear-Image-Graph and got the following fatal error:
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to
allocate 86 bytes) in
including bsd.port.pre.mk, see here: http://www.freebsd.org/cgi/query-
pr.cgi?pr=106557. I took a look at recent commits to bsd.port.mk but
cannot determine what would be causing these later USE_PHP
definitions to now cause portlint to complain. Anyone have ideas as
to what might be the troub
be be possible to
tell which.
Could someone consider doing a mass commit to each of these ports to bump
PORTREVISION so that any potential breakage is flushed out of the pkg repos?
Nick
astro/py-aipy
audio/jokosher
audio/mpdbrowser
audio/picard
audio/puddletag
audio/py-fastaudio
audio/py-musi
On 22/07/2014 18:43, Antoine Brodin wrote:
> But I can still bump PORTREVISION on py-salt as for this specific port
> the missing egginfo is harmful? (for most other ports it's harmless)
that would be great, thanks.
Nick
___
freebsd-ports@
a new maintainer for the FreeBSD port.
Thanks.
-Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On Tue, Oct 21, 2014 at 6:29 PM, Chris H wrote:
> On Tue, 21 Oct 2014 09:39:30 +0200 Marko Cupać
> wrote
>
> > On Mon, 20 Oct 2014 17:47:19 -0700
> > "Chris H" wrote:
> >
> > > Unless theirs any objection. I'll take it. I'll open a pr(1)
> > > with a shar(1) ready, in about an hour.
> > >
> > >
equirements" script has
been removed entirely, and from what I can tell a failure in the
pre-install script does not halt pkg add.
Thanks.
-Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To uns
On Wed, Oct 29, 2014 at 1:02 PM, Baptiste Daroussin
wrote:
> On Wed, Oct 29, 2014 at 12:44:21PM -0700, Nick Rogers wrote:
> > Hello,
> >
> > I am in the process of upgrading some proprietary software that has
> always
> > been deployed via a "custom" p
On Wed, Oct 29, 2014 at 5:44 PM, Baptiste Daroussin
wrote:
> On Wed, Oct 29, 2014 at 01:43:27PM -0700, Nick Rogers wrote:
> > On Wed, Oct 29, 2014 at 1:02 PM, Baptiste Daroussin
> > wrote:
> >
> > > On Wed, Oct 29, 2014 at 12:44:21PM -0700, Nick Rogers wrote:
>
Hello,
I opened this issue on pkg github the other day. Hoping someone on this
list may have some input.
https://github.com/freebsd/pkg/issues/1070
Thanks,
-Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
be able to post a complete version, sometime
> tomorrow.
>
Hey Chris. Any luck getting your new dansguardian port to work? I can't
find a PR for it. Just wondering if theres anything I can do to help test
or if it would be worth my while to just submit a PR with the last-known
www/dansgu
y cleanly.
=> Patch(es) patch-configure applied cleanly.
*** Error code 1
Stop.
make: stopped in /usr/ports/ftp/curl
-Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail
On Mon, Nov 24, 2014 at 10:57 AM, Sunpoet Po-Chuan Hsieh <
sunp...@freebsd.org> wrote:
> On Tue, Nov 25, 2014 at 2:49 AM, Nick Rogers wrote:
>
>> It appears that the ftp/curl port was broken with the very-recent commit
>> update to 7.39.0. I happened to do a svn up an
On Sun, Nov 2, 2014 at 1:00 PM, Chris H wrote:
> On Fri, 31 Oct 2014 16:55:47 -0700 Nick Rogers wrote
>
> > On Tue, Oct 21, 2014 at 6:29 PM, Chris H wrote:
> >
> > > On Tue, 21 Oct 2014 09:39:30 +0200 Marko Cupać
> > > wrote
> > >
> > >
led TP_PF in my make.conf.
I was able to fix my issue by recompiling without the TP_IP and TP_IPF
options, but I believe more thought/discussion should be given to all the
new options that are now enabled by default in the port.
Thanks!
-Nick
___
free
On Tue, Apr 26, 2016 at 1:31 AM, Pavel Timofeev wrote:
> 2016-04-26 1:32 GMT+03:00 Nick Rogers :
> > Hello,
> >
> > I just recompiled my www/squid port to the latest 3.5.17 version. Prior
> to
> > this I was running 3.5.14. I immediately noticed that my transparen
h Supermicro IPMI modules and motherboards. It looks
like there have not been any significant changes to the IMPI code in
- -CURRENT recently that might fix this, either. I do see a note in the
"Fixes and Enhancements" section on the latest BIOS download page from
Dell for the SC1425 that
he commits to the IPMI code in -
current, and can update the sysutils/ipmi-kmod port with a new
snapshot when that new code gets in.
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
powers in CVS
could fix would be wonderful! :-)
Ta
--
Nick Withers
email: [EMAIL PROTECTED]
Web: http://www.nickwithers.com
Mobile: +61 414 397 446
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
The new version of the port seems to work fine on my test amd64 and
i386 machines running 6.1. Both of those have Supermicro motherboards
and IPMI modules. Hopefully it will work with these newer Dell BIOS
releases, too!
Nick
On Sep 19, 2006, at 10:03 AM, Doug Ambrisko wrote:
Michael Grazi
Doh, forgot to actually attach the patch. Sorry!
ipmi-kmod.patch
Description: Binary data
On Sep 27, 2006, at 2:01 AM, Nick Barkas wrote:
I've updated the sysutils/ipmi-kmod port to contain the new ipmi
code committed to -current the other day. Here's the PR containing
a patch
sn't English.
Any thoughts on whether this would be a good change? I will file a PR
with my patch tomorrow unless someone has a better solution.
Nick
bsd.port.mk.patch
Description: Binary data
___
freebsd-ports@freebsd.org mailing lis
l get a PR filed next
week to upgrade to 4.5.0. This port is not going to deal gracefully with
upgrades, so anyone with a current 3.5.1 installation should use the
in-line upgrade mechanism to upgrade to 4.5.0 instead of portupgrade.
Nick
[upgrading to something more recent] is something
ommit my patch?
http://www.freebsd.org/cgi/query-pr.cgi?pr=106790
Thanks!
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
of notification, I'm waiting for the SugarCRM people to release
4.5.1 before creating a PR for this.
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to &q
Any chance to get an Port for Drupal 5.x soon?
Yes, I intend to submit a PR later today.
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ded to use apt on
FreeBSD, and I unfortunately don't have the time to put into maintaining it
now.
Any takers? Please CC me as I'm not on the list.
Thanks!
Nick
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
79 matches
Mail list logo
