Summary of experiences upgrading xorg -> 7.4 with nvidia-driver without hal
I have had many misadventures in upgrading to xorg 7.4 with nvidia-driver.
This is a summary of what worked. Most of these things are not original
but have been derived of things posted here and to the ports mailing lis
2009/2/12 Lars Eighner :
>
> Summary of experiences upgrading xorg -> 7.4 with nvidia-driver without hal
>
> I have had many misadventures in upgrading to xorg 7.4 with nvidia-driver.
> This is a summary of what worked. Most of these things are not original
> but have been derived of things posted
On Thu, 12 Feb 2009, Olivier SMEDTS wrote:
2009/2/12 Lars Eighner :
Summary of experiences upgrading xorg -> 7.4 with nvidia-driver without hal
I have had many misadventures in upgrading to xorg 7.4 with nvidia-driver.
This is a summary of what worked. Most of these things are not original
b
[Cc: trimmed]
On Sat, Feb 07, 2009 at 05:44:13PM +0100, Gerald Pfeifer wrote:
> We really shouldn't have so many ports without a real maintainer properly
> taking care.
>
> The amount of bitrot in the tree is worrisome [...]
Agreed; however, in the past the question has been, "who decides what
p
On Wed, Feb 11, 2009 at 12:55:39PM +0100, Angelo Turetta wrote:
> What I understand from this page:
>
> https://www.isc.org/software/dhcp/versions
>
> is that the only version of isc-dhcp-server currently available from
> ports is EOL and soon-to-be deprecated (dhcp31 and dhcp40 are marked
> BR
On Thu, Feb 12, 2009 at 9:33 AM, Lars Eighner wrote:
> On Thu, 12 Feb 2009, Olivier SMEDTS wrote:
>
> 2009/2/12 Lars Eighner :
>>
>>>
>>> Summary of experiences upgrading xorg -> 7.4 with nvidia-driver without
>>> hal
>>>
>>> I have had many misadventures in upgrading to xorg 7.4 with
>>> nvidia-
The PR about updating ruby18 to 1.8.7 says that the update breaks rails.
It was noted "We're not going to update to 1.8.7-p17" and then 3 days
later the commit upgrading to p72 took place.
http://www.freebsd.org/cgi/query-pr.cgi?pr=124837
Is there a part of the discussion I'm missing? Is p72 guar
I am also having this problem on a freshly installed system. Have you had
any luck with this?
Jan, Do you have any plans to update the port? It's a bit out of date now.
On Mon, February 9, 2009 6:27 am, Johan Hendriks wrote:
> Hello all.
>
> I have updated my perl from 5.8.8 to 5.8.9 on some mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Feb 2009 16:30:03 + (UTC)
Stef mentioned:
> The PR about updating ruby18 to 1.8.7 says that the update breaks rails.
> It was noted "We're not going to update to 1.8.7-p17" and then 3 days
> later the commit upgrading to p72 took place
Stanislav Sedov wrote:
The main concern with ruby-1.8.7 was it's incompatibility with rails, and
some stability problems. All of them was resolved. Today, 1.8.7 is recommended
for rails, as noted on their site.
It might work with rails, but you definitely have to change code.
see http://ridechar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This topic came up in IRC, and I was encouraged to go out, and find some new
maintainers.
At any given time, approximately 20 - 25% of all ports are unmaintained. Not
all unmaintained ports need updating, but some do. That is where you folks
come i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Feb 2009 12:17:12 -0500
"Philip M. Gollucci" mentioned:
> Stanislav Sedov wrote:
> > The main concern with ruby-1.8.7 was it's incompatibility with rails, and
> > some stability problems. All of them was resolved. Today, 1.8.7 is
> > reco
On Thu, 12 Feb 2009 01:42:42 +0100 (CET)
Gerald Pfeifer wrote:
> On Wed, 11 Feb 2009, q...@freebsd.org wrote:
> > checking for ATL_xerbla in -latlas... no
> > checking for sgemm_ in -lblas... no
> > checking for dgemm_ in -lblas... no
> > configure: error: cannot find any BLAS library, which is r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Abthorpe wrote:
>
> The gauntlet has been thrown down, who among you is prepared to pick it up?
I will!
Pr submitted to take over dns/py-dnspython.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (FreeBSD)
Comment: Using GnuPG with Mozilla
On Thu, Feb 12, 2009 at 6:32 PM, Thomas Abthorpe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This topic came up in IRC, and I was encouraged to go out, and find some new
> maintainers.
>
> At any given time, approximately 20 - 25% of all ports are unmaintained. Not
> all unmaintai
On Thu, Feb 12, 2009 at 07:39:15PM +0100, Marius N?nnerich wrote:
> On Thu, Feb 12, 2009 at 6:32 PM, Thomas Abthorpe
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > This topic came up in IRC, and I was encouraged to go out, and find some new
> > maintainers.
> >
> > At any
On Thu, Feb 12, 2009 at 01:37:15PM -0500, Andy Greenwood wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thomas Abthorpe wrote:
> >
> > The gauntlet has been thrown down, who among you is prepared to pick it up?
> I will!
>
> Pr submitted to take over dns/py-dnspython.
Committed.
* Thomas Abthorpe [2009-02-12 12:32:13 -0500]:
At any given time, approximately 20 - 25% of all ports are unmaintained. Not
all unmaintained ports need updating, but some do. That is where you folks
come in.
There are a bunch of you out there who are subscribers to this list (and other
Fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 01:52:43 pm Charlie Kester wrote:
> I plead guilty and will look through the list of unmaintained ports to
> see if there are any where my skills and interests are a good fit.
That is great, thanks Charlie!
Thomas
- --
Thomas
Thomas Abthorpe wrote:
> The gauntlet has been thrown down, who among you is prepared to pick it up?
Please, when volunteering to maintain up a port, also check the open
error reports and problem reports for this port - as listed on Portsmon,
http://portsmon.freebsd.org/ and other locations.
Tha
On Thursday 12 February 2009 3:32:13 pm Thomas Abthorpe wrote:
> This topic came up in IRC, and I was encouraged to go out, and find some
> new maintainers.
>
> At any given time, approximately 20 - 25% of all ports are unmaintained.
> Not all unmaintained ports need updating, but some do. That is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 02:26:21 pm Johan van Selst wrote:
> Please, when volunteering to maintain up a port, also check the open
> error reports and problem reports for this port - as listed on Portsmon,
> http://portsmon.freebsd.org/ and other locations
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 02:44:08 pm Gonzalo Nemmi wrote:
> Will try to write back soon with some work already done.
Thanks Gonzalo, look forward to seeing your PR :)
Thomas
- --
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.org | ht
--On Thursday, February 12, 2009 11:32:13 -0600 Thomas Abthorpe
wrote:
The gauntlet has been thrown down, who among you is prepared to pick it up?
How about providing a list of the ports that need maintainers? I already have
15. I might take some more, but not until I know what they are
* Thomas Abthorpe [2009-02-12 14:20:31 -0500]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 01:52:43 pm Charlie Kester wrote:
I plead guilty and will look through the list of unmaintained ports to
see if there are any where my skills and interests are a good fit.
That
* Paul Schmehl [2009-02-12 13:26:46 -0600]:
--On Thursday, February 12, 2009 11:32:13 -0600 Thomas Abthorpe
wrote:
The gauntlet has been thrown down, who among you is prepared to pick it up?
How about providing a list of the ports that need maintainers? I
already have 15. I might tak
On Thu, Feb 12, 2009 at 12:10:28PM -0800, Charlie Kester wrote:
> * Paul Schmehl [2009-02-12 13:26:46 -0600]:
>
> > --On Thursday, February 12, 2009 11:32:13 -0600 Thomas Abthorpe
> > wrote:
> >
> >>
> >> The gauntlet has been thrown down, who among you is prepared to pick it up?
> >>
> >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 02:26:46 pm Paul Schmehl wrote:
> How about providing a list of the ports that need maintainers? I already
> have 15. I might take some more, but not until I know what they are.
Thanks for the nudge, Paul!
Instead of a list of
On Thu, Feb 12, 2009 at 03:24:21PM -0500, Thomas Abthorpe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On February 12, 2009 02:26:46 pm Paul Schmehl wrote:
> > How about providing a list of the ports that need maintainers? ?I already
> > have 15. ?I might take some more, but not un
--On Thursday, February 12, 2009 14:24:21 -0600 Thomas Abthorpe
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 02:26:46 pm Paul Schmehl wrote:
How about providing a list of the ports that need maintainers? I already
have 15. I might take some more, but not until
Thomas Abthorpe (Thu 02/12/09 12:32):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This topic came up in IRC, and I was encouraged to go out, and find some new
> maintainers.
>
> At any given time, approximately 20 - 25% of all ports are unmaintained. Not
> all unmaintained ports need
On Thu, Feb 12, 2009 at 12:32 PM, Thomas Abthorpe wrote:
> The gauntlet has been thrown down, who among you is prepared to pick it up?
I'll take the following:
lang/open-cobol
lang/tinycobol
devel/c_c++_reference
Should I submit a separate PR for each?
--
Glen Barber
_
(Resending, I did not see it posted earlier)
ffmpeg has 3 announced vulnerabilities in this past month.
Here is the latest...
09.6.23 CVE: Not Available
Platform: Cross Platform
Title: FFmpeg "libavformat/4xm.c" Remote Code Execution
Description: FFmpeg is an application used to record, convert, a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 04:18:44 pm Paul Schmehl wrote:
> I might also point out that it's perfectly fine to submit PRs for ports you
> do not maintain. So, even if you think you can't or don't have the time to
> be a maintainer, you can always submit pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 04:38:21 pm hideo wrote:
> I can take pacpl and it's dependencies:
>
> audio/pacpl
> audio/kexis
> audio/p5-Audio-Musepack
> audio/laudio
> audio/lpac
> audio/optimfrog
> audi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 05:04:07 pm Glen Barber wrote:
> I'll take the following:
> lang/open-cobol
> lang/tinycobol
> devel/c_c++_reference
>
> Should I submit a separate PR for each?
Thanks Glen
In this case, a PR is not necessary, we will qu
On Thu, Feb 12, 2009 at 5:41 PM, Thomas Abthorpe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On February 12, 2009 05:04:07 pm Glen Barber wrote:
>> I'll take the following:
>>lang/open-cobol
>>lang/tinycobol
>>devel/c_c++_reference
>>
>> Should I submit a separate PR f
Thomas Abthorpe 2009-02-12:
> This topic came up in IRC, and I was encouraged to go out, and find some new
> maintainers.
>
> At any given time, approximately 20 - 25% of all ports are unmaintained. Not
> all unmaintained ports need updating, but some do. That is where you folks
> come in.
>
Hello,
I'm looking through the RC script used to manage PostgreSQL 8.3 and
I'm curious about the defaults used for the postgresql_flags variable.
The script sets the default value to "-w -s -m fast". What were these
supposed to do?
Both -w and -m appear to be invalid flags for postgresql
Hello,
Please disregard my previous email. I just realized that these
switches are being passed to "pg_ctl" not to "postgres" directly.
Cheers,
Joe
Hello,
I'm looking through the RC script used to manage PostgreSQL 8.3 and
I'm curious about the defaults used for the postgresql_flags
Thomas Abthorpe wrote:
> The gauntlet has been thrown down, who among you is prepared to pick it up?
I'll take x11/xclip in addition to what I currently maintain. I'm
looking through the others and will submit a followup email soon.
--
Eitan Adler
"Security is increased by designing for the way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 04:38:21 pm hideo wrote:
> I can take pacpl and it's dependencies:
>
> audio/pacpl
> audio/kexis
> audio/p5-Audio-Musepack
> audio/laudio
> audio/lpac
> audio/optimfrog
> audi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 05:04:07 pm Glen Barber wrote:
> I'll take the following:
> lang/open-cobol
> lang/tinycobol
> devel/c_c++_reference
Committed, they are now yours!
Thomas
- --
Thomas Abthorpe | FreeBSD Committer
tabtho...@fre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 05:51:26 pm Glen Barber wrote:
> databases/kmysqladmin
> palm/palmpower
> palm/palmos-sdk
> palm/prc-tools
> security/portsentry
These too, are yours!
Thomas
- --
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 06:14:04 pm Daniel Roethlisberger wrote:
> I'll adopt these two additional ports:
>
> security/md4coll
> security/fragrouter
>
> Thanks!
Hi Daniel, these ports are now yours!
Thomas
- --
Thomas Abthorpe | FreeBSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 12, 2009 07:15:50 pm Eitan Adler wrote:
> I'll take x11/xclip in addition to what I currently maintain. I'm
> looking through the others and will submit a followup email soon.
Hi Eitan
They are now yours!
Thomas
- --
Thomas Abthorpe
Stanislav Sedov wrote:
> On Thu, 12 Feb 2009 16:30:03 + (UTC)
> Stef mentioned:
>> Devs of the systems I maintain are saying that they can't use 1.8.7 due
>> to incompatibilities with rails and other breakages, and now suddenly
>> there's no version of 1.8.6 in ports.
>
>> I'm not ruby guy my
On Thu, Feb 12, 2009 at 01:59:19AM -0600 I heard the voice of
Lars Eighner, and lo! it spake thus:
>
> 1. If you have previously built xorg with hal, beware of manually
> changing /var/db/ports/xorg/options manually unless you know what
> you are doing.
In fact, don't even consider it in the fir
And for me too:
audio/id3v2
audio/pysol-sound-server
databases/p5-Mysql
emulators/mtools
games/pysol
graphics/flphoto
sysutils/dvdbackup
sysutils/mbmon
sysutils/xmbmon
www/p5-Apache-Radius
Most of them are dead, but still working for me quite well. ;-)
I'll try to keep it building until I can do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 13 Feb 2009 02:27:11 + (UTC)
Stef mentioned:
> Stanislav Sedov wrote:
> > On Thu, 12 Feb 2009 16:30:03 + (UTC)
> > Stef mentioned:
> >> Devs of the systems I maintain are saying that they can't use 1.8.7 due
> >> to incompatibilities
50 matches
Mail list logo