As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
We use a bunch of HP and Xerox printers across our network, all capable
of being accessed via network over IPP protocoall (so they claim).
Printing worked for me flawless on FreeBSD 8.2-STABLE, 9.0-CURRENT, now
9.0-STABLE on all boxes in question. Since updating cups to revision
1.5.0 (this is th
On Tue, 7 Feb 2012 15:53:55 +1100, richo wrote
Hi Richo,
> Did you get a chance to look at this?
Yes, sorry, I did not get back to you. This has been part of the 4.2.0
libdvdnav/libdvdread update, see :
http://www.freebsd.org/cgi/cvsweb.cgi/ports/multimedia/libdvdread/Makefile#rev1.40
I have f
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: xapian-omega10-1.0.22: no entry for
/usr/ports/databases/xapian-core10
make_index: xapian-omega10-1.0.22: no entry for
/usr/ports/databases/xapian-core10
make_index: vindaloo-0.2_6: no entry for /usr/ports
make_i
I would like to ask you to review and test the port in this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=164843
I also would to discuss with the port's users the best approach to updating it.
Thank you.
--
Andriy Gapon
___
freebsd-ports@freebsd.org
On 02/07/12 18:40, O. Hartmann wrote:
We use a bunch of HP and Xerox printers across our network, all capable
of being accessed via network over IPP protocoall (so they claim).
Printing worked for me flawless on FreeBSD 8.2-STABLE, 9.0-CURRENT, now
9.0-STABLE on all boxes in question. Since upd
On 07.02.2012 02:18, rfl...@acsalaska.net wrote:
Hi,
Thanks for starting to work on it! I've added a link from
WantedPorts
to that
mail.
Currently stuck on the absence of xlocale(3). Is there any chance
these
get MFC'd to RELENG_9 and RELENG_8? Or should I try implementing them
in platform
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: vindaloo-0.2_6: no entry for /usr/ports
make_index: vindaloo-0.2_6: no entry for /usr/ports
Committers on the hook:
bapt bf blackend crees dhn dinoex dougb eadler ehaupt flo glewis gordon miwi
pav pgollucci romai
> mail/postfix and its derivatives are interactive when ALL of the
> following conditions are true:
>
> - PACKAGE_BUILDING is undefined
> - /etc/mail/mailer.conf exists
> - /etc/mail/mailer.conf contains a line beginning with 'purgestat'
- POSTFIX_DEFAULT_MTA is unset
And that one seems the
> On 07.02.2012 02:18, rfl...@acsalaska.net wrote:
>> Hi,
>>
>>> Thanks for starting to work on it! I've added a link from
>>> WantedPorts
>>> to that
>>> mail.
>>
>> Currently stuck on the absence of xlocale(3). Is there any chance
>> these
>> get MFC'd to RELENG_9 and RELENG_8? Or should I try im
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: vindaloo-0.2_6: no entry for /usr/ports
make_index: vindaloo-0.2_6: no entry for /usr/ports
Committers on the hook:
bapt bf blackend crees dhn dinoex dougb eadler ehaupt erwin flo glewis gordon
miwi pav pgollucci
INDEX build failed with errors:
Generating INDEX-7 - please wait.. Done.
make_index: vindaloo-0.2_6: no entry for /usr/ports
make_index: vindaloo-0.2_6: no entry for /usr/ports
make_index: blocksshd-1.3: no entry for /usr/ports/net/p5-Net-Subnets
Committers on the hook:
bapt bf blackend crees dhn
On 7 February 2012 19:40, Erwin Lansing wrote:
> INDEX build failed with errors:
> Generating INDEX-7 - please wait.. Done.
> make_index: vindaloo-0.2_6: no entry for /usr/ports
> make_index: vindaloo-0.2_6: no entry for /usr/ports
> make_index: blocksshd-1.3: no entry for /usr/ports/net/p5-Net-Su
On Feb 7, 2012, at 9:44 AM, rfl...@acsalaska.net wrote:
>> mail/postfix and its derivatives are interactive when ALL of the
>> following conditions are true:
>>
>> - PACKAGE_BUILDING is undefined
>> - /etc/mail/mailer.conf exists
>> - /etc/mail/mailer.conf contains a line beginning with 'purgesta
On Tue, Feb 7, 2012 at 12:37 PM, Sahil Tandon wrote:
> On Feb 7, 2012, at 9:44 AM, rfl...@acsalaska.net wrote:
>
>>> mail/postfix and its derivatives are interactive when ALL of the
>>> following conditions are true:
>>>
>>> - PACKAGE_BUILDING is undefined
>>> - /etc/mail/mailer.conf exists
>>> -
> On Feb 7, 2012, at 9:44 AM, rfl...@acsalaska.net wrote:
>
>>> mail/postfix and its derivatives are interactive when ALL of the
>>> following conditions are true:
>>>
>>> - PACKAGE_BUILDING is undefined
>>> - /etc/mail/mailer.conf exists
>>> - /etc/mail/mailer.conf contains a line beginning with '
On 7 February 2012 02:04, Sahil Tandon wrote:
> mail/postfix and its derivatives are interactive when ALL of the
> following conditions are true:
>
> - PACKAGE_BUILDING is undefined
> - /etc/mail/mailer.conf exists
> - /etc/mail/mailer.conf contains a line beginning with 'purgestat'
>
> The way
On 2012-02-06 01:57, Doug Barton wrote:
> Howdy,
>
> This section:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/using-php.html
>
> is out of date, as the very first bit mentions a bunch of old apache
> stuff. I'm happy to help update it if someone can say authoritatively
>
___
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"
Hello
Is there any port that I can compile Kamailio 3.2.2 ?
Could you send me Kamailio port Makefile please ?
Regards
Serhat AKCA
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscr
On 02/07/2012 13:18, Freddie Cash wrote:
> On Tue, Feb 7, 2012 at 12:37 PM, Sahil Tandon wrote:
>> On Feb 7, 2012, at 9:44 AM, rfl...@acsalaska.net wrote:
>>
mail/postfix and its derivatives are interactive when ALL of the
following conditions are true:
- PACKAGE_BUILDING is un
2012/2/7 :
> The ports, and the reason and date that they have been scheduled
> for removal, are listed below. If no one has stepped forward before
> that time to propose a way to fix the problems (such as via a PR),
> the ports will be deleted.
>
> portname: lang/php52
> description:
On 02/07/2012 02:49, Andriy Gapon wrote:
>
> I would like to ask you to review and test the port in this PR:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=164843
Using the latest shar on up to date 8-stable i386 it seems to run fine.
FWIW I'm using the port with all of the OPTIONS UNchecked.
A co
On 02/07/2012 17:13, Svyatoslav Lempert wrote:
> 2012/2/7 :
>> The ports, and the reason and date that they have been scheduled
>> for removal, are listed below. If no one has stepped forward before
>> that time to propose a way to fix the problems (such as via a PR),
>> the ports will be deleted
any GOOD way to do this without spawing a shell?
SVN_PORTVERSION!=cd ${SVN_PORTDIR} && ${MAKE} -V PORTVERSION
by looking for this, its a pretty common thing: I played around for 2
hours and gave up.
grep -R -- 'MAKE. -V PORT' /usr/ports
./devel/git-merge-changelog/Makefile:GNULIB_PORTVER
On 02/07/2012 17:43, Michael Scheidell wrote:
> if a certain port needs to be kept in sync with another portversion,
> other than putting a comment in the main port "# must bump portversion
> in port..." where you have two maintainers, is there a better way to do
> this?
Take a look at editors/xxe
On 2/7/12 8:48 PM, Doug Barton wrote:
On 02/07/2012 17:43, Michael Scheidell wrote:
if a certain port needs to be kept in sync with another portversion,
other than putting a comment in the main port "# must bump portversion
in port..." where you have two maintainers, is there a better way to d
On 02/07/2012 17:50, Philip M. Gollucci wrote:
> On 02/08/12 01:48, Doug Barton wrote:
>> On 02/07/2012 17:43, Michael Scheidell wrote:
>>> if a certain port needs to be kept in sync with another portversion,
>>> other than putting a comment in the main port "# must bump portversion
>>> in port..."
On 02/07/2012 17:52, Michael Scheidell wrote:
>
>
> On 2/7/12 8:48 PM, Doug Barton wrote:
>> On 02/07/2012 17:43, Michael Scheidell wrote:
>>> if a certain port needs to be kept in sync with another portversion,
>>> other than putting a comment in the main port "# must bump portversion
>>> in por
On 02/08/12 01:52, Michael Scheidell wrote:
>
>
> On 2/7/12 8:48 PM, Doug Barton wrote:
>> On 02/07/2012 17:43, Michael Scheidell wrote:
>>> if a certain port needs to be kept in sync with another portversion,
>>> other than putting a comment in the main port "# must bump portversion
>>> in port.
On 2/7/12 8:57 PM, Doug Barton wrote:
ok, but I said these are two maintainers,
Before I maintained either they were both maintained by 2 different
people. :)
Well yeah, but so what? Most people who maintain ports are
cooperative/friendly and are willing to listen to reasoned arguments
about s
On 02/07/2012 18:07, Michael Scheidell wrote:
>
>
> On 2/7/12 8:57 PM, Doug Barton wrote:
>>
>> ok, but I said these are two maintainers,
>> Before I maintained either they were both maintained by 2 different
>> people. :)
>> Well yeah, but so what? Most people who maintain ports are
>> cooperati
On 02/08/12 01:48, Doug Barton wrote:
> On 02/07/2012 17:43, Michael Scheidell wrote:
>> if a certain port needs to be kept in sync with another portversion,
>> other than putting a comment in the main port "# must bump portversion
>> in port..." where you have two maintainers, is there a better wa
On 02/07/2012 14:09, Olli Hauer wrote:
> On 2012-02-06 01:57, Doug Barton wrote:
>> Howdy,
>>
>> This section:
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/using-php.html
>>
>> is out of date, as the very first bit mentions a bunch of old apache
>> stuff. I'm happy to help u
On 2/7/12 9:16 PM, Doug Barton wrote:
No. Please actually LOOK CAREFULLY at the example I gave you. It does
the right thing.
you mean talk to lev (maintainer of ../subversion16) and ask for a
Makefile.inc, right?
so his Makefile.common will call his Makefile.inc and my Makefile will
.includ
On 02/07/2012 18:30, Michael Scheidell wrote:
>
>
> On 2/7/12 9:16 PM, Doug Barton wrote:
>> No. Please actually LOOK CAREFULLY at the example I gave you. It does
>> the right thing.
>>
> you mean talk to lev (maintainer of ../subversion16) and ask for a
> Makefile.inc, right?
> so his Makefile.c
On Tue, 2012-02-07 at 12:27:31 -0900, rfl...@acsalaska.net wrote:
> > On Feb 7, 2012, at 9:44 AM, rfl...@acsalaska.net wrote:
> >
> >>> mail/postfix and its derivatives are interactive when ALL of the
> >>> following conditions are true:
> >>>
> >>> - PACKAGE_BUILDING is undefined - /etc/mail/mail
lini...@freebsd.org wrote:
> portname: graphics/vrml2pov
> description:Convert VRML files to POVRay source
> maintainer: po...@freebsd.org
> status: BROKEN
> deprecated because: unfetchable
This seems to be a ports-infrastructure problem, rather than a
proble
Following up to my previous post about "Why isn't WWWDIR_REL in the
default PLIST_SUB I broke open bsd.port.mk and found this:
PLIST_SUB+= DOCSDIR="${DOCSDIR_REL}" \
EXAMPLESDIR="${EXAMPLESDIR_REL}" \
DATADIR="${DATADIR_REL}" \
WWWDIR="${WWWDIR_R
On 02/08/2012 02:12, per...@pluto.rain.com wrote:
> lini...@freebsd.org wrote:
>
>> portname: graphics/vrml2pov
>> description:Convert VRML files to POVRay source
>> maintainer: po...@freebsd.org
>> status: BROKEN
>> deprecated because: unfetchable
>
> This s
Makes sense to me.
I might even see about doing the nitty gritty.
On 02/08/12 03:28, Doug Barton wrote:
> Following up to my previous post about "Why isn't WWWDIR_REL in the
> default PLIST_SUB I broke open bsd.port.mk and found this:
>
> PLIST_SUB+= DOCSDIR="${DOCSDIR_REL}" \
>
Hello.
On 02/07/2012 12:29, lini...@freebsd.org wrote:
portname: databases/p5-postgresql-plperl
description:Write SQL functions for PostgreSQL using Perl5
maintainer:p...@freebsd.org
deprecated because: No longer supported by upstream-- upgrade to later
ver
On 02/08/2012 10:10, Chad Perrin wrote:
On Wed, Feb 08, 2012 at 09:41:04AM +0400, Alexander Pyhalov wrote:
Hello.
On 02/07/2012 12:29, lini...@freebsd.org wrote:
portname: databases/p5-postgresql-plperl
description:Write SQL functions for PostgreSQL using Perl5
maintainer:p..
On 8 Feb 2012 06:26, "Alexander Pyhalov" wrote:
>
> On 02/08/2012 10:10, Chad Perrin wrote:
>>
>> On Wed, Feb 08, 2012 at 09:41:04AM +0400, Alexander Pyhalov wrote:
>>>
>>> Hello.
>>>
>>> On 02/07/2012 12:29, lini...@freebsd.org wrote:
portname: databases/p5-postgresql-plperl
>
47 matches
Mail list logo
