On 2020-12-27 15:49, Dan Mahoney (Gushi) wrote:
Ergo, I am wondering what the best way forward is to get a reasonably
patched version of openssl that has old ciphers turned on (since it is
still possible at compile-time, the code hasn't been outright removed),
that I can build *some* subset of
On 2020-12-02 3:50, Matthias Apitz wrote:
Thanks for all this additional clarification. In the host (where
poudriere is running) I always install some ports before running
poudriere, like
ports-mgmt/poudriere-devel
shells/bash
www/nginx
www/wget
devel/subversion
editors/vim
sysutils/tmux
You
On 2020-10-14 20:56, Robert Huff wrote:
Is anyone out there successfully using FreeBSD as a media server for
a Roku device?
Yes, with Plex Media Server. Works flawlessly, though Plex is sensitive
about its data files. Manually stopping it and snapping its data before
upgrading is key to
I want to do a poudriere bulk against 2019Q3 over the weekend, but it
appears to not exist yet? Usually the branch creation is pretty timely,
so I wanted to check to make sure I'm not missing something.
___
freebsd-ports@freebsd.org mailing list
On 2019-06-23 7:22, Carmel NY wrote:
FreeBSD 12.0-RELEASE-p6 GENERIC amd64
openssl version: OpenSSL 1.0.2s 28 May 2019
I want to use openssl111 so I can take advantage of 'tls 1.3' with
postfix and apache24. I am trying to determine the correct procedure to
use. I am using poudriere to build
On 2019-06-08 9:57, Adam Weinberger wrote:
On Sat, Jun 8, 2019 at 10:02 AM Gerald Pfeifer wrote:
In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237688 we had
a user report against lang/gcc* ports that could be traced back to
a certain functionality (option) in another port
On Nov 27, r486043 was committed to head to fix several vulnerabilities
in the Samba 4.7 and 4.8 ports, but it wasn't merged to 2018Q4. A PR
was opened, but 2018Q4 sat unfixed until it expired at the end of the year.
Filing a PR didn't help. Mentioning the PR on this list didn't help.
What
On 2018-12-22 4:02, Kurt Jaeger wrote:
Hi!
On 2018-12-12 19:19, Mel Pilgrim wrote:
Would someone work on ports/233749, please? The original security fix
was committed to head 15 days ago, but has yet to be merged to quarterly.
I realize it's the holidays, but this is a security fix
On 2018-12-12 19:19, Mel Pilgrim wrote:
Would someone work on ports/233749, please? The original security fix
was committed to head 15 days ago, but has yet to be merged to quarterly.
I realize it's the holidays, but this is a security fix for a major port.
Or is it the plan to let this go
I only need to build a single port plus the handful of private
meta-ports I use for role management. It seems a terrible waste to have
poudriere build the 500+ completely stock dependencies they pull in. Is
there a way to have poudriere install implicitly-added pkgs from
pkg.freebsd.org
Would someone work on ports/233749, please? The original security fix
was committed to head 15 days ago, but has yet to be merged to quarterly.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On 09/17/2018 17:52, Carmel NY wrote:
I have come across several ports that poudriere builds with the wrong
dependencies.
I have MySQL 8.0 installed by poudriere. I wanted to install
"databases/mysqlbackup" When built using the system "make install" command, it
works fine. However, when I
The mail/postfixadmin port was broken on the last update, and 231424
unbreaks it. I would like to get it into the tree ahead of the 2018Q4
branch so that quarterly users aren't affected. Would a committer
please take it?
Thank you
___
The bug has a maintainer-approved patch since April 3. Would someone
please commit this change? Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On 2018-04-05 12:48, Thomas Zander wrote:
Hi,
On 4 April 2018 at 11:30, Mel Pilgrim <list_free...@bluerosetech.com> wrote:
On the topic of MFH emails, were those for r453380 and r465710 (both
security updates to security/openssl with MFH tags) not sent?
Those mails were sent on Marc
On 04/04/2018 00:00, Thomas Zander wrote:
Hi,
On 2 April 2018 at 18:50, Mel Pilgrim <list_free...@bluerosetech.com> wrote:
The update to net/samba4{5,6,7} addressing CVEs went to head on March 13.
The security/openssl update to 1.0.2o was committed to head with MFH 2018Q1
explicitly
The update to net/samba4{5,6,7} addressing CVEs went to head on March
13. The security/openssl update to 1.0.2o was committed to head with
MFH 2018Q1 explicitly asked for in the commit message. In both cases,
2018Q1 expired before the MFH happened.
Last year, r453380 updated
On 2018-02-14 19:13, Janky Jay, III wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May have spoken too soon...
On 2/14/2018 7:45 PM, Janky Jay, III wrote:
Hello Mel,
On 2/13/2018 7:42 AM, Mel Pilgrim wrote:
(Putting on my mail/postfixadmin maintainer hat)
On 2018-02-11 15:24, Janky
(Putting on my mail/postfixadmin maintainer hat)
On 2018-02-11 15:24, Janky Jay, III wrote:
Hello All,
Versions:
FreeBSD - 11.1-RELEASE-p6
PostfixAdmin - 3.1
Smarty3 - 3.1.30
Postfixadmin bundles its own copy of Smarty, and in PFA 3.1 it's Smarty
3.1.29. Installing www/smarty3 isn't
In the midst of all the negative noise, I thought I'd post and say thank
you for bring in this feature. I've been chomping at the bit to try
flavours out since I heard about them. I started flavouring my
company's internal Ports Tree extension the evening after it landed.
Flavours are going
On 12/6/2017 3:40 PM, Mel Pilgrim wrote:
The last time I had a major stability problem with FreeBSD was when I
had a brand new Nocona Xeon system that would get interrupt storms
running 5.x and had to run 6-CURRENT on it for a while because 6.x
introduced MSI support.
Or was that 4.x
On 12/5/2017 2:25 PM, Baho Utot wrote:
Thank you for taking a perfectly good system and breaking it as well as
making it unusable, unstable. You just don't know of all the countless
hours spent after running an update and taking a week to get it working
again.
I manage (currently) 104
On 12/5/2017 2:09 PM, Mathieu Arnold wrote:
Le 05/12/2017 à 10:53, Aryeh Friedman a écrit :
TL;DR;
Flavors 'ed up ports and there are no good ways/alternates for how
to use the ports collection for normal everyday users/maintainers
Thank you for supporting all the hard work and countless
On 11/16/2017 11:17, Miroslav Lachman wrote:
Mel Pilgrim wrote on 2017/11/16 19:30:
I have a port that has exactly one file: an RC script provided in the
FILESDIR of the skeleton itself. I can't use metaport because I do have
to install a file.
I've had no luck finding anything
I have a port that has exactly one file: an RC script provided in the
FILESDIR of the skeleton itself. I can't use metaport because I do have
to install a file.
I've had no luck finding anything that explains how to do this, and am
meeting no end of errors when I test the port.
How do I
On 11/07/2017 07:54, Miroslav Lachman wrote:
What is the best way to maintain local ports tree changes?
I am building packages in poudriere, 4 different sets for 2 archs (8
sets in total).
I have some local ports and some changes to official ports. Now we are
planing to do some small
On 10/15/2017 11:41, Baptiste Daroussin wrote:
On Sun, Oct 15, 2017 at 06:15:24PM +, Yuri wrote:
Uses/ssl.mk allows SSL_DEFAULT=base. I know this has been discussed here
before, but why is this even allowed? If some ports are built with
SSL_DEFAULT=base, and some with SSL_DEFAULT=openssl,
On 10/11/2017 11:15, Jos Chrispijn wrote:
Dear group,
Apparently I have an issue when finalizing the ports with portmanager.
[...]
pkg: sqlite error while executing sqlite open in file pkgdb.c:1126:
unable to open database file
I checked numerous solutions, but most of them refer to a
On 10/12/2017 00:58, Guido Falsi wrote:
On 10/12/2017 01:04, Adam Weinberger wrote:
On 11 Oct, 2017, at 16:52, Mel Pilgrim <list_free...@bluerosetech.com> wrote:
Will the FLAVORS feature be MFH'd to 2017Q4, or will it first show up with
2018Q1? I'm not going to flavor public ports ju
Will the FLAVORS feature be MFH'd to 2017Q4, or will it first show up
with 2018Q1? I'm not going to flavor public ports just yet, but I have
some local ports that would benefit from the feature.
___
freebsd-ports@freebsd.org mailing list
On 09/26/2017 16:56, Greg 'groggy' Lehey wrote:
On Wednesday, 27 September 2017 at 4:39:29 +1000, Andy Farkas wrote:
On 27/09/2017 04:22, Mathieu Arnold wrote:
Please read the whole email.
What are FLAVORS and why do I need it?
Is there somewhere that explains the intent and purpose?
to compile everything from scratch
on the weekly.
Mel, the IT admin who gets to run 11-R and -CURRENT in exchange for free
books and actually helping people because she doesn't have to say things
like, "I can do that, but the licensing is half you
A PR for a port I maintain includes a patch. I'm supposed to set the
maintainer-approval flag to + to approve the patch, but it doesn't seem
to be working. When I go to the patch details page, I can set
maintainer-approval+, but it doesn't stick, even if I include a comment.
I found an older
On 01/03/2017 08:33, Miroslav Lachman wrote:
Vlad K. wrote on 2017/01/03 17:16:
I've submitted a patch for Postgres server ports with a note about
enabling checksumming
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214671). I'm now
preparing to submit a patch with a similar "Nice to know"
I track the quarterly ports branches so that I can build ports from the
same tree as binary packages so that I don't, for example, have to build
all 2783 packages on my dev VM, just the 13 where I need non-default
options. Yes I know, "That is not the intended use, ma'am," blah blah
void my
On 2015-10-28 20:54, Bryan Drewery wrote:
On 10/28/2015 5:36 PM, Mel Pilgrim wrote:
Nearly every time I send a maintainer update, there's some new method I
don't know about. There's nothing about it on ports or ports-announce
and porttools/portlint don't mention it either. I end up scanning
Nearly every time I send a maintainer update, there's some new method I
don't know about. There's nothing about it on ports or ports-announce
and porttools/portlint don't mention it either. I end up scanning
through commits to ports/head/Mk to find them after the fact.
What do I need to do
I have ports/branches/2015Q4 checked out for poudrerie thinking that it
would be aligned to what's in the quarterly pkg.freebsd.org repos, but
that doesn't seem to be the case. For example, right now
pkg.freebsd.org has dovecot2-2.2.19, but the 2015Q4 branch only has
dovecot2-2.2.18.
I
On 2015-10-20 21:02, Bryan Drewery wrote:
On 10/20/2015 1:54 AM, Mel Pilgrim wrote:
I have ports/branches/2015Q4 checked out for poudrerie thinking that it
would be aligned to what's in the quarterly pkg.freebsd.org repos, but
that doesn't seem to be the case. For example, right now
On 2015-10-09 01:49, Willem Jan Withagen (ecoRacks) wrote:
Hi,
Trying to upgrade Postfix, and this is what pkg suggests:
New packages to be INSTALLED:
jpeg-turbo: 1.4.1 [zfs.digiware.nl]
mozjpeg: 3.1_1 [FreeBSD]
pth-hard: 2.0.7_1 [FreeBSD]
pkg-devel:
On 2015-09-30 16:16, Lowell Gilbert wrote:
In short, there is nothing broken in pkg(8) per se. I am pretty sure
this problem does not come up if you do everything from quarterly or
everything from head; it's strictly an issue of conflicts between the
two.
More to the point, that using the
On 2015-09-28 21:31, Kevin Oberman wrote:
On Mon, Sep 28, 2015 at 4:41 PM, Mel Pilgrim <list_free...@bluerosetech.com>
wrote:
I'm trying to build and install security/openssh-portable, but when I do,
make errors out with:
===> openssh-portable-7.1.p1_2,1 pkg(8) must be vers
On 2015-09-29 08:24, Janky Jay, III wrote:
I ran into this exact same issue using SVN and portmaster to upgrade
'git'. Upgrading 'pkg' using portmaster (portmaster -d 'pkg-1.5.6')
before running 'portmaster -ad' fixed the issue. Generally, though,
portmaster usually updates pkg first and
I'm trying to build and install security/openssh-portable, but when I
do, make errors out with:
===> openssh-portable-7.1.p1_2,1 pkg(8) must be version 1.6.0 or
greater, but you have 1.5.6. You must upgrade the ports-mgmt/pkg port first.
*** Error code 1
Stop.
make: stopped in
On 2015-07-07 11:29, Carmel NY wrote:
On Tue, 7 Jul 2015 17:06:05 +, Brooks Davis stated:
We need a port that allows dovecot2 SASL by default. There are a bunch of
turorials on setting up such systems and all of the have to start with build
everything by hand which makes us look bad.
On 2015-04-01 13:42, Mike Clarke wrote:
Where can I now obtain the revision number for the ports tree used for the
latest
package build?
Although the above method has worked in the past it's a bit of a bodge. The
ideal
way would be if this information could be accessed directly from the
\
Observe the difference on something like x11/xorg.
--
Mel
___
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 16-6-2012 17:11, Baptiste Daroussin wrote:
On Sat, Jun 16, 2012 at 05:06:36PM +0200, Mel Flynn wrote:
On 16-6-2012 16:53, Baptiste Daroussin wrote:
On Sat, Jun 16, 2012 at 03:13:28PM +0100, Matthew Seaman wrote:
On 16/06/2012 14:18, Chris Rees wrote:
That's great-- though rather than
On 17-6-2012 21:51, Baptiste Daroussin wrote:
On Sun, Jun 17, 2012 at 08:27:33PM +0200, Mel Flynn wrote:
On 16-6-2012 17:11, Baptiste Daroussin wrote:
On Sat, Jun 16, 2012 at 05:06:36PM +0200, Mel Flynn wrote:
On 16-6-2012 16:53, Baptiste Daroussin wrote:
On Sat, Jun 16, 2012 at 03:13:28PM
kget/CMakeFiles/kgetcore.dir/verifieradaptor.o
Linking CXX shared library ../lib/libkgetcore.so
[ 12%] Built target kgetcore
1 error
*** [all] Error code 2
1 error
*** [do-build] Error code 1
Please retry as make -DDISABLE_MAKE_JOBS build.
That will show us the real error.
--
Mel
to migrate these
@${ECHO_CMD} settings?
...etc
Plus I think it would be more natural and easier for maintainers and
end-users to talk about (say) phpmyadmin rather than
databases-phpmyadmin.
I doubt UNIQUENAME is used in casual end user to maintainer
conversations. :)
--
Mel
.
You should solve this using a better index format. I figured out years
ago that the INDEX format used by the ports system is not a good format
for binary upgrades.
http://lists.freebsd.org/pipermail/freebsd-questions/2008-December/187796.html
--
Mel
On 12-6-2012 2:38, Warren Block wrote:
On Fri, 25 May 2012, Mel Flynn wrote:
On 20-5-2012 14:06, Chris Rees wrote:
Usually. Sometimes it's (ab)used to include the relevant bsd.*.mk
file without adding dependencies (WANT_GNOME), but normally that's
what WANT_ is used for.
Definitely add
on it. bsd.databases.mk will be the
victim of my first iteration.
--
Mel
___
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
the definition would look like:
OPTIONS_NONEORONE= EXAMPLE
OPTIONS_NONEORONE_EXAMPLE= BLONDE BRUNETTE
And the port's test would be:
.if ${OPTIONS:MEXAMPLE_NONE}
# yay, no work for me
.else
# crap which one he pick
.endif
--
Mel
___
freebsd-ports@freebsd.org
update or
is it permissable to pack these two into one?
It is best to put all the changes you want to make into one PR. That
will get it processed most efficiently.
And if there's a PR for the conflict problem, then mention in your
update PR that this update closes PR xx.
--
Mel
script implementation to see
what the consequences are of that.
--
Mel
___
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
, but I think adding gcc46/fortran to an already
complex tool chain should not be done if it can be avoided.
Maybe the option description can be changed to:
Enable array support through numPY
This makes it easier for people to decide whether they need it.
--
Mel
a pkg-message string?
Also, one should never touch /etc/services if nsswitch.conf does not
contain compat or files and finally, adding a single service without
/etc/services using services_mkdb is not currently possible.
--
Mel
___
freebsd-ports
the include path
correctly.
swig-1.3.40
RUBY_VER=1.9 in /etc/make.conf
RUBY config option set in graphics/gdal
Given issues described with swig 1.x earlier on this list, you may want
to investigate if swig 1.x should be removed/patched/whatever before
this sweep.
--
Mel
On 7-6-2012 21:36, Stanislav Sedov wrote:
On Thu, 07 Jun 2012 20:58:43 +0200
Mel Flynn rfl...@acsalaska.net mentioned:
Given issues described with swig 1.x earlier on this list, you may want
to investigate if swig 1.x should be removed/patched/whatever before
this sweep.
Swig 1.x
On 7-6-2012 21:55, Warren Block wrote:
gcc46, and I do have CPUTYPE?=native in make.conf...
Interesting! Built without CPUTYPE set, Firefox seems fine. Compiler bug?
Shot in the dark: SSE support? Based on threads earlier on this list
with respect to chrome.
--
Mel
On 7-6-2012 23:25, Warren Block wrote:
On Thu, 7 Jun 2012, Mel Flynn wrote:
On 7-6-2012 21:55, Warren Block wrote:
gcc46, and I do have CPUTYPE?=native in make.conf...
Interesting! Built without CPUTYPE set, Firefox seems fine.
Compiler bug?
Shot in the dark: SSE support? Based
accordingly instead of throwing an exception.
--
Mel
___
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
comes in play) is abused by Mk/
frameworks that only come in sight /after/ options.mk. This causes two
versions of UNIQUENAME in the execution stream to exist. One before the
framework is included and one after.
--
Mel
___
freebsd-ports@freebsd.org mailing
it and go look for the next.
Also, if there's automagical detection schemes in ports you know of that
do not respect WITHOUT_NLS, please file PR's for them or send me the
list. It is one of my pet-peeves to get rid of those.
--
Mel
___
freebsd-ports
simple options
with custom logic.
--
Mel
___
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 2-6-2012 15:24, Chris Rees wrote:
On Jun 2, 2012 1:57 PM, Mel Flynn rfl...@acsalaska.net wrote:
On 12-5-2012 5:41, Erwin Lansing wrote:
All the details has been documented and written down on the wiki:
http://wiki.freebsd.org/Ports/Options/OptionsNG
Sorry to jump in late, but it just
On 31-5-2012 5:00, Doug Barton wrote:
On 05/30/2012 12:32, Mel Flynn wrote:
On 29-5-2012 19:06, Doug Barton wrote:
On 5/29/2012 4:00 AM, Mel Flynn wrote:
On 29-5-2012 7:23, Doug Barton wrote:
Right. The issue I'm talking about is that fixing the problem of staying
with a version, introduces
On 29-5-2012 19:06, Doug Barton wrote:
On 5/29/2012 4:00 AM, Mel Flynn wrote:
On 29-5-2012 7:23, Doug Barton wrote:
Not too hard for leaf ports. But with ports that are depended on, there
is always a default, whether it's named that way or not. You're just
changing the problem slightly
lang/*
ports and their modules are handled across versions?
--
Mel
___
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
/share/mk/bsd.port.mk).
--
Mel
___
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
of what make
thinks CC and CPP are and backtrack where they are set.
Start with:
make -C /usr/ports/x11/libX11 -V CC -V CPP
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail
On 26-5-2012 20:40, Oliver Pinter wrote:
On 5/26/12, Mel Flynn rfl...@acsalaska.net wrote:
On 26-5-2012 19:17, Oliver Pinter wrote:
I think src.conf is relevant, while it changes the system behavior, as
changed the default cc from gcc-4.2 to clang.
Thinking it doesn't make it so. Run:
grep
by the unprivileged user and as such the package
target will fail.
I'm not aware of any downsides to making this change in bpm or am I
overlooking something?
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
= ${UID_OFFSET} # best to keep them equal
Installing for example postgresql, will now use uid/gid 20070 instead of 70.
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail
On 12-5-2012 20:24, Robert Huff wrote:
Suddenly I'm getting:
pkg_delete: the package info for package Source is corrupt
Any ideas?
Can you provide the output of:
grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS
--
Mel
On 13-5-2012 14:48, Robert Huff wrote:
Mel Flynn writes:
pkg_delete: the package info for package Source is corrupt
Any ideas?
Can you provide the output of:
grep -E '@(unexec|exec).*Source' /var/db/pkg/*/+CONTENTS
Yes.
Well, I was hoping to see some exotic exec
On 13-5-2012 21:51, Chris Rees wrote:
The quotes are from @dirrmtry, so inserted by bsd.port.mk.
Ah, shows how rusty I am. Also, why aren't they single quotes? Do we
actually support shell expansion dirrmtry?
--
Mel
___
freebsd-ports@freebsd.org
/zarafa-libvmime
https://redports.org/browser/melflynn/devel/zarafa-libical
--
Mel
___
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 4/12/2012 17:30, Jason Hellenthal wrote:
Console# sqlite3 .svn/wc.db pragma integrity_check
ok
Does that mean /usr/src/sys/.svn is a directory?
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
On 4/10/2012 06:14, Da Rock wrote:
On 04/10/12 13:14, Mel Flynn wrote:
On 4/10/2012 02:26, Da Rock wrote:
So what should the patch look like? Am I correct in my understanding of
the BUILD_DEPENDS, or have I chased a goose on that one?
I'd like to divert your attention to the libnet source
and provides a deadline for this to action to be
completed. BROKEN is supposed to be a temporary state, leading to a fix.
DEPRECATED is a temporary state leading to removal.
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman
solution (dynamically generated plist comes to mind).
--
Mel
___
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 4/10/2012 18:11, David Wolfskill wrote:
svn: E200030: sqlite: callback requested query abort
Does svn cleanup in /usr/src fix the issue?
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
On 4/10/2012 18:26, David Wolfskill wrote:
On Tue, Apr 10, 2012 at 06:22:24PM +0200, Mel Flynn wrote:
On 4/10/2012 18:11, David Wolfskill wrote:
svn: E200030: sqlite: callback requested query abort
Does svn cleanup in /usr/src fix the issue?
...
Huh -- it seems to do precisely
the configure in port A so that it doesn't autodetect for
package B. (Sometimes this can be done using a suitable CONFIGURE_ARGS,
but not in my particular situation.)
4. Add OPTION PACKAGE_B. And cripple configure through EXTRA_PATCH if
set to off.
--
Mel
into pretty
much every binary through libnetapi.
Your focus should shift to the compilation error itself, your solution
of installing the port libnet masked the actual problem.
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman
target with NOPORTDOCS.
Wrapping the install target is IMHO the preferred option, since you will
also have to disable ${MKDIR} ${DOCSDIR} if you use that.
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
for libraries that only come
in static version, like hebrew/hspell.
Or when the upstream build system only links with the static version.
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send
Hi all,
so we took this off list for a bit to work out an implementation.
On 3/29/2012 10:46, Matthew Seaman wrote:
On 28/03/2012 22:04, Mel Flynn wrote:
I'm not sure about exclusion. I have an implementation up here:
http://redports.org/browser/melflynn/net-mgmt/observium/bsd.www.mk
.
--
Mel
___
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
/en_US.ISO8859-1/books/porters-handbook/install.html#INSTALL-DOCUMENTATION
--
Mel
___
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
for
the configure: WARNING: unrecognized options: --with-apopuid
--
Mel
___
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 3/14/2012 14:53, David Southwell wrote:
On Wednesday 14 March 2012 07:17:55 Mel Flynn wrote:
On 3/13/2012 14:01, David Southwell wrote:
qpopper has been working fine (amd64 running postfix) but on portupgrade
I am Getting the following error:
set MISSING_OBJS to base64.o
set
is used.
--
Mel
Index: Makefile
===
RCS file: /home/ncvs/ports/security/openssh-portable/Makefile,v
retrieving revision 1.157
diff -u -r1.157 Makefile
--- Makefile23 Dec 2011 12:52:28 - 1.157
+++ Makefile14 Mar 2012 19
On 3/14/2012 20:00, Robert Huff wrote:
If I want to list the Type 1 fonts known to X, I can use
x11-fonts/xlsfonts.
Is there an equivalent tool for TrueType fonts?
fc-list should show them all (part of fontconfig).
--
Mel
___
freebsd
On 3/14/2012 17:27, David Southwell wrote:
That worked
It worked to confirm my suspicions. I've filed a proper fix in:
http://www.freebsd.org/cgi/query-pr.cgi?pr=166108
--
Mel
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org
and that failed attempts to log in mark a
client-id/client version invalid. When this happened to me, I used the
website password reset feature and it would then let me sign on with the
new client.
It's a shot in the dark, but worth testing.
--
Mel
___
freebsd-ports
seeing similar issues with zarafa if I do just that. If I let the
port use the provided libtool *or* use the entire autotools toolchain,
then all is well. Also, adding --with-pic to CONFIGURE_ARGS does not
change either outcome.
--
Mel
___
freebsd-ports
1 - 100 of 178 matches
Mail list logo