On Friday 07 December 2012 08:37:46 Rainer Hurling wrote:
> On 07.12.2012 12:25 (UTC+2), Tilman Keskinöz wrote:
> > * ajtiM [Thu, 6 Dec 2012 17:36:40 -0600]:
> >> I got an email about last fm and a new version:
> >>
> >> "We're writing you to let you know that there will soon be a change to
> >> L
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
On 07.12.2012 12:25 (UTC+2), Tilman Keskinöz wrote:
> * ajtiM [Thu, 6 Dec 2012 17:36:40 -0600]:
>
>> I got an email about last fm and a new version:
>>
>> "We're writing you to let you know that there will soon be a change to
>> Last.fm
>> radio that may affect you. Our stats show that you've li
On 07/12/2012 11:09, Kimmo Paasiala wrote:
> With the latest 3.0 version of p5-FreeBSD-PortIndex I get an error at
> the end of portindex run:
>
> Accumulating dependency information:
> .[1000].[2000].[3000].[4000].[5000].[6000].[7000]..
* ajtiM [Thu, 6 Dec 2012 17:36:40 -0600]:
> I got an email about last fm and a new version:
>
> "We're writing you to let you know that there will soon be a change to
> Last.fm
> radio that may affect you. Our stats show that you've listened to radio
> through
> an application that uses our o
On Sun, Dec 2, 2012 at 11:47 AM, Matthew Seaman
wrote:
> On 02/12/2012 09:32, Ion-Mihai Tetcu wrote:
>>> If you're running 2.9 OPTIONSng should be handled correctly. It
>>> > doesn't matter much: the exact format of the OPTIONS variables
>>> > doesn't make much difference to building the INDEX, o
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
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 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 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
10 matches
Mail list logo