On Wed, Oct 20, 2010 at 1:46 AM, Jason Helfman
wrote:
>
> Hi,
>
> I believe I may have come across a potential bug in pkg_add, but wanted
> to write my findings out to see if anyone has seen this issue, or knows
> of something I may be doing wrong.
>
> I wrote a port that uses USERS/GROUPS functio
On Wed, 20 Oct 2010 01:11:35 +0200 (CEST)
Barbara articulated:
> $ date
> Wed Oct 20 01:11:10 CEST 2010
>
> # portsnap fetch update
> Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
> Fetching snapshot tag from portsnap5.FreeBSD.org... failed.
> Fetching snapshot tag from portsnap6.F
Fyi,
Mozilla just release a SA for firefox , thunderbird and seamonkey [1]
affecting the current versions in ports. The CVE record seems to be under
validation.
[1] http://www.mozilla.org/security/announce/2010/mfsa2010-71.html
regards
Rodrigo
__
"Rodrigo OSORIO (ros)" writes:
> Mozilla just release a SA for firefox , thunderbird and seamonkey [1]
> affecting the current versions in ports. The CVE record seems to be under
> validation.
The ports have already been updated.
___
freebsd-ports@fre
On Wed, 20 Oct 2010 09:13:32 +0100
Florent Thoumie wrote:
> On Wed, Oct 20, 2010 at 1:46 AM, Jason Helfman
> wrote:
> >
> > Hi,
> >
> > I believe I may have come across a potential bug in pkg_add, but
> > wanted to write my findings out to see if anyone has seen this
> > issue, or knows of somet
> On Wed, 20 Oct 2010 01:11:35 +0200 (CEST)
> Barbara articulated:
>
>> $ date
>> Wed Oct 20 01:11:10 CEST 2010
>>
>> # portsnap fetch update
>> Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
>> Fetching snapshot tag from portsnap5.FreeBSD.org... failed.
>> Fetching snapshot tag fro
On Wed, Oct 20, 2010 at 09:53:24PM +0200, Barbara wrote:
> > On Wed, 20 Oct 2010 01:11:35 +0200 (CEST)
> > Barbara articulated:
> >
> >> $ date
> >> Wed Oct 20 01:11:10 CEST 2010
> >>
> >> # portsnap fetch update
> >> Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found.
> >> Fetching snap
With the help of jhb@, I have a port of gdb 7.1 that has been modified to
recognize freebsd threads. I would like to get this added to the ports tree
but I would like some feedback as to how it should be added.
Currently, the latest version of gdb in the ports tree is 6.6 and its under
devel/gdb
Quoth Barbara on Wednesday, 20 October 2010:
>
> My only intention was to report that and not complaining about the annoyance.
> I just wanted to alter people maintaining #5.
> If it's "expected", no problem.
>
Was "alter" a parapraxis?
--
Sterling (Chip) Camden| sterl...@camdensoftware.co
On 10/20/10 7:14 PM, Chip Camden wrote:
> Quoth Barbara on Wednesday, 20 October 2010:
>>
>> My only intention was to report that and not complaining about the annoyance.
>> I just wanted to alter people maintaining #5.
>> If it's "expected", no problem.
>>
>
> Was "alter" a parapraxis?
>
I'd im
INDEX build failed with errors:
Generating INDEX-6 - please wait..cannot open
/local0/portmgr/tindex/ports/multimedia/pvr250/work/pkg-descr: No such file or
directory
===> multimedia/pvr250 failed
*** Error code 1
*** Error code 1
Stop in /local0/portmgr/tindex/ports.
*** Error code 1
Stop in /
INDEX build failed with errors:
Generating INDEX-6 - please wait..cannot open
/local0/portmgr/tindex/ports/multimedia/pvr250/work/pkg-descr: No such file or
directory
===> multimedia/pvr250 failed
*** Error code 1
*** Error code 1
Stop in /local0/portmgr/tindex/ports.
*** Error code 1
Stop in /
The above subject listed bug has been found in portmaster with cause
unknown. portmaster(8) at this point fails to continue because it is
waiting on a pipe for whatever reason. This also happens in
'/usr/src/bin/csh' and I am not sure if there is other directories this
happens in.
~25 lines of o
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
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
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
INDEX build failed with errors:
Generating INDEX-6 - please wait..cannot open
/local0/portmgr/tindex/ports/multimedia/pvr250/work/pkg-descr: No such file or
directory
===> multimedia/pvr250 failed
*** Error code 1
*** Error code 1
Stop in /local0/portmgr/tindex/ports.
*** Error code 1
Stop in /
Oops... Fixing now.
--
Edwin Groothuis Website: http://www.mavetju.org/
ed...@mavetju.org Weblog: http://www.mavetju.org/weblog/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubsc
21 matches
Mail list logo