On Mon, Mar 31, 2014 at 4:13 PM, Ross Penner wrote:
>
>
> On Sat, 15 Mar 2014, at 08:47 AM, Scot Hetzel wrote:
>> On Fri, Mar 14, 2014 at 9:55 PM, Ross Penner wrote:
>> > When I try to build prosody (on FreeBSD 9.2-RELEASE-p3), I get the
>> > following error once it gets to the installation phase
On 3/31/14 3:47 PM, Kevin Oberman wrote:
> This is something I've wanted to have for quite a while, but never
> enough to dig through the Makefiles.
>
> I think the proper way would be for "make showconfig" to print out the
> current config as it does now, but to tag default options (e.g. '+') so
> On Mar 31, 2014, at 20:32, Jamie Landeg-Jones wrote:
>
> Hi. Many ports that require gnutls fail if security/gnutls3 and not
> security/gnutls are installed.
>
> ( E.G. http://www.freebsd.org/cgi/query-pr.cgi?pr=186785 )
>
> Whilst seemingly gnutls and gnutls3 can co-exist, the ports
> that
Hi. Many ports that require gnutls fail if security/gnutls3 and not
security/gnutls are installed.
( E.G. http://www.freebsd.org/cgi/query-pr.cgi?pr=186785 )
Whilst seemingly gnutls and gnutls3 can co-exist, the ports
that depend on gnutls being installed pass the lib dependency
when seeing the g
Hi. Many ports that require gnutls fail if security/gnutls3 and not
security/gnutls are installed.
( E.G. http://www.freebsd.org/cgi/query-pr.cgi?pr=186785 )
Whilst seemingly gnutls and gnutls3 can co-exist, the ports
that depend on gnutls being installed pass the lib dependency
when seeing the g
On Mar 27, 2014, at 18:51, Darren Pilgrim wrote:
>
> I hate to nag about this, but can we get this fixed sometime soon? In the
> three weeks since Mark's email, osa updated the port to 1.4.7, but didn't
> bother fixing this issue. What happened to this being a showstopper in a
> major port?
On Sat, 15 Mar 2014, at 08:47 AM, Scot Hetzel wrote:
> On Fri, Mar 14, 2014 at 9:55 PM, Ross Penner wrote:
> > When I try to build prosody (on FreeBSD 9.2-RELEASE-p3), I get the
> > following error once it gets to the installation phase. The error
> > references already having a prosody user and
Am 31.03.2014 01:23, schrieb olli hauer:
> On 2014-03-30 23:35, Sahil Tandon wrote:
>> On Sun, 2014-03-30 at 21:40:25 +0200, olli hauer wrote:
>>
>>> long time ago I shaped a patch for postfix-2.10 to support staging,
>>> if required I can create a new patch for 2.11.
>>
>> Could you send a patch v
On Mon, Mar 31, 2014 at 7:47 AM, John W. O'Brien wrote:
> On 3/30/14 10:21 PM, Randy Pratt wrote:
> > On Sun, 30 Mar 2014 17:13:15 -0400
> > "John W. O'Brien" wrote:
> >
> >> [blah blah blah]
> >>
> [...]
> >> The first part of my solution to these problems is to store only the
> >> options that
Am Mon, 31 Mar 2014 12:19:48 +1100
schrieb Dewayne Geraghty :
>
> On 31/03/2014 5:38 AM, Dimitry Andric wrote:
> > On 30 Mar 2014, at 16:43, Dr. Peter Voigt wrote:
> >> I am running 10.0-RELEASE and when trying to upgrade
> >> freeradius-2.2.3_1 to freeradius-2.2.4 after the latest update of
> >
Antoine Brodin wrote:
> Would you like to take maintainership of this port, and add stage
> support to it?
In and of itself, sure, of course. But I'd need some time to thoroughly
check and sort out this port: stagify, check for a newer upstream version,
see if there's really no WWW, (as Kurt Jag
Hi!
> The port mail/xmailbox is set to be removed soon because it has been
> unmaintained since 2000. In this case, does "unmaintained" refer to just
> the FreeBSD port, or to the software itself?
Both.
> And in either case, is there anything that can be done to prevent removal?
Yes, apply to b
On 3/31/2014 16:57, A.J. 'Fonz' van Werven wrote:
> Hi all,
>
> The port mail/xmailbox is set to be removed soon because it has been
> unmaintained since 2000. In this case, does "unmaintained" refer to just
> the FreeBSD port, or to the software itself? And in either case, is there
> anything tha
- Add staging support
- Make RUN_DEPENDS path independent
-
Build ID: 20140331141400-24758
Job owner: pa...@freebsd.org
Buildtime: 55 minutes
Enddate: Mon, 31 Mar 2014 15:08:57 GMT
Rev
On Mon, Mar 31, 2014 at 4:57 PM, A.J. 'Fonz' van Werven
wrote:
> Hi all,
>
> The port mail/xmailbox is set to be removed soon because it has been
> unmaintained since 2000. In this case, does "unmaintained" refer to just
> the FreeBSD port, or to the software itself? And in either case, is there
>
Hi all,
The port mail/xmailbox is set to be removed soon because it has been
unmaintained since 2000. In this case, does "unmaintained" refer to just
the FreeBSD port, or to the software itself? And in either case, is there
anything that can be done to prevent removal?
AvW
--
I'm not completely
On 3/30/14 10:21 PM, Randy Pratt wrote:
> On Sun, 30 Mar 2014 17:13:15 -0400
> "John W. O'Brien" wrote:
>
>> [blah blah blah]
>>
[...]
>> The first part of my solution to these problems is to store only the
>> options that I know I care about. That is, I know I need to find out
>> where a stored
On Monday 31 March 2014 14:16:34 you wrote:
> 31.03.2014 13:56, Ajtim пишет:
> > On Monday 31 March 2014 12:00:51 Boris Samorodov wrote:
> >> 31.03.2014 11:38, Johan Hendriks пишет:
> >>> Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts
> >>> with cups-image-1.5.4_1 (installs
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsol
31.03.2014 13:56, Ajtim пишет:
> On Monday 31 March 2014 12:00:51 Boris Samorodov wrote:
>> 31.03.2014 11:38, Johan Hendriks пишет:
>>> Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts
>>> with cups-image-1.5.4_1 (installs files into the same place).
>>> Problematic file: /usr
On Monday 31 March 2014 12:00:51 Boris Samorodov wrote:
> 31.03.2014 11:38, Johan Hendriks пишет:
> > Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts
> > with cups-image-1.5.4_1 (installs files into the same place).
> > Problematic file: /usr/local/include/cups/raster.h
>
>
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
31.03.2014 12:26, Johan Hendriks пишет:
> Boris Samorodov schreef:
>> 31.03.2014 11:38, Johan Hendriks пишет:
>>
>>> Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts
>>> with cups-image-1.5.4_1 (installs files into the same place).
>>> Problematic file: /usr/local/include/cups
Boris Samorodov schreef:
31.03.2014 11:38, Johan Hendriks пишет:
Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts
with cups-image-1.5.4_1 (installs files into the same place).
Problematic file: /usr/local/include/cups/raster.h
Yep, the problematic file has moved form cups
31.03.2014 11:38, Johan Hendriks пишет:
> Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts
> with cups-image-1.5.4_1 (installs files into the same place).
> Problematic file: /usr/local/include/cups/raster.h
Yep, the problematic file has moved form cups-image (1.5.x) to
c
Ajtim schreef:
Hi!
I try to update:
===>>> The following actions will be taken if you choose to proceed:
Upgrade cups-base-1.5.4_1 to cups-base-1.7.1
Upgrade cups-client-1.5.4_1 to cups-client-1.7.1
Upgrade cups-image-1.5.4_1 to cups-image-1.7.1
Upgrade py27-
Dear FreeBSD Community,
Please note that the submission date for the 2014Q1 aka. January to
March 2014 Quarterly Status Reports is, April 7th, 2014, only 1 week
away. Please consult my earlier message for the details:
2014-03-08 10:24 GMT+01:00 Gabor Pali :
> They do not have to be very long --
27 matches
Mail list logo
