В Mon, 18 Jan 2010 09:21:45 +0100
Hans Petter Selasky пишет:
HPS> On Monday 18 January 2010 08:47:26 Sergey V. Dyatko wrote:
HPS> > Hi,
HPS> > at 1st I want to say that I am very grateful for your work
HPS> >
HPS> > after adding video4bsd_load="YES" to loader.conf system traps
HPS> > but when I
On Monday 18 January 2010 08:47:26 Sergey V. Dyatko wrote:
> Hi,
> at 1st I want to say that I am very grateful for your work
>
> after adding video4bsd_load="YES" to loader.conf system traps but when
> I load module manualy (after login) all works fine.
>
> %uname -a
> FreeBSD notebook.minsk.dom
(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
Hi,
Boris Samorodov wrote:
> Hello Ed,
>
> thanks for your hard work!
>
> On Wed, 13 Jan 2010 20:42:54 +0100 Ed Schouten wrote:
>
>> I've noticed there is some breakage in ports, but it shouldn't be too
>> serious.
>
> Seems that emulators/virtualbox-ose is broken:
Yes, there is a pr open wit
Martin Smith wrote:
Ed Schouten wrote:
Hello everyone,
I just made various commits to FreeBSD HEAD to remove our old user
accounting database interface (see utmp(5)) and replace it by the POSIX
standardized utmpx interface (see getutxent(3)). This means we just got
rid of some annoyances that a
Ed Schouten wrote:
Hello everyone,
I just made various commits to FreeBSD HEAD to remove our old user
accounting database interface (see utmp(5)) and replace it by the POSIX
standardized utmpx interface (see getutxent(3)). This means we just got
rid of some annoyances that are as old as the Free
On Wed, Jan 13, 2010 at 08:42:54PM +0100, Ed Schouten wrote:
> Hello everyone,
>
> I just made various commits to FreeBSD HEAD to remove our old user
> accounting database interface (see utmp(5)) and replace it by the POSIX
> standardized utmpx interface (see getutxent(3)). This means we just got
On Monday 18 January 2010 09:29:45 Sergey V. Dyatko wrote:
> В Mon, 18 Jan 2010 09:21:45 +0100
> Hans Petter Selasky пишет:
>
> HPS> On Monday 18 January 2010 08:47:26 Sergey V. Dyatko wrote:
> HPS> > Hi,
> HPS> > at 1st I want to say that I am very grateful for your work
> HPS> >
> HPS> > after
Hi,
I'm seeing the following error when trying to build
foomatic-filters.
Any hint at what the problem might be? All packages are up to date
as of Dec 2009.
I've already tried portupgrade -Rf to no avail.
TIA,
--
fernan
---> Building '/freebsd/ports/print/foomatic-filters'
===> Cleaning fo
On Mon, 18 Jan 2010 16:47:46 +0100 Beat Gaetzi wrote:
> Boris Samorodov wrote:
> > Hello Ed,
> >
> > thanks for your hard work!
> >
> > On Wed, 13 Jan 2010 20:42:54 +0100 Ed Schouten wrote:
> >
> >> I've noticed there is some breakage in ports, but it shouldn't be too
> >> serious.
> >
> > Seem
Out of curiosity, was there ever an experimental pointyhat run done for
these changes? If there was not one previously, can we do one ASAP?
Doug
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubs
В Mon, 18 Jan 2010 16:49:34 +0100
Hans Petter Selasky пишет:
HPS> On Monday 18 January 2010 09:29:45 Sergey V. Dyatko wrote:
HPS> > В Mon, 18 Jan 2010 09:21:45 +0100
HPS> > Hans Petter Selasky пишет:
HPS> >
HPS> > HPS> On Monday 18 January 2010 08:47:26 Sergey V. Dyatko wrote:
HPS> > HPS> > Hi,
On Mon, Jan 18, 2010 at 12:29:24PM -0800, Doug Barton wrote:
> Out of curiosity, was there ever an experimental pointyhat run done for
> these changes? If there was not one previously, can we do one ASAP?
>
Already started.
-erwin
--
Erwin Lansing http://droso.
On 01/18/10 12:52, Erwin Lansing wrote:
> On Mon, Jan 18, 2010 at 12:29:24PM -0800, Doug Barton wrote:
>> Out of curiosity, was there ever an experimental pointyhat run done for
>> these changes? If there was not one previously, can we do one ASAP?
>>
> Already started.
Awesome, you guys rock! :)
About a month ago I proposed the following changes for the rc.d script
for quickml to bring it up to date (and probably fix it since I doubt
it's currently working properly) but I just double-checked my mail
folder and realized that I forgot to explicitly send this to the
maintainer, which I'm doin
Howdy,
I recently took over the net-p2p/rblibtorrent* ports with an eye towards
modernizing them, and my ultimate goal of getting a modern version of
qbittorrent working, which I've done.
However I apparently inherited some build problems on 6-stable that I
don't understand, and since I don't hav
Howdy,
I've noticed a lot of commits recently to use plist-sub for pkg-message
and I'm wondering if there is some overarching purpose for this, or if
it's just general cleanup? If the latter that's fine, and I am fully
supportive of efforts to keep things neat and tidy. The reason I ask is
that I
Hello,
Upon the installation (``pkg_add -r'') of postfix, I was asked, as
usual, to disable some daily routines.
> And you can disable some sendmail specific daily maintenance routines in your
> /etc/periodic.conf file:
>
> daily_clean_hoststat_enable="NO"
> daily_status_mail_rejects_enable="NO"
On Mon, 18 Jan 2010 15:17:50 -0700
Lucas Reddinger wrote:
> Hello,
>
> Upon the installation (``pkg_add -r'') of postfix, I was asked, as
> usual, to disable some daily routines.
> ...
> However, on Freebsd 8.0 release, ``/etc/periodic.conf'' does not
> exist.
Then create it.
_
On 1/18/2010 3:17 PM, Lucas Reddinger wrote:
Hello,
Upon the installation (``pkg_add -r'') of postfix, I was asked, as
usual, to disable some daily routines.
And you can disable some sendmail specific daily maintenance routines in your
/etc/periodic.conf file:
daily_clean_hoststat_enable="NO"
On Mon, Jan 18, 2010 at 2:17 PM, Lucas Reddinger wrote:
> Hello,
>
> Upon the installation (``pkg_add -r'') of postfix, I was asked, as
> usual, to disable some daily routines.
>
> > And you can disable some sendmail specific daily maintenance routines in
> your
> > /etc/periodic.conf file:
> >
>
On Mon, Jan 18, 2010 at 3:55 PM, Matt Reimer wrote:
> Create the file /etc/periodic.conf and add those assignments to it.
On Mon, Jan 18, 2010 at 3:46 PM, Eric wrote:
> i think the idea is to create /etc/periodic.conf and put the options there
Thanks, and sorry about the noise.
Lucas
_
Hi, Doug--
On Jan 18, 2010, at 1:17 PM, Doug Barton wrote:
> However I apparently inherited some build problems on 6-stable that I
> don't understand, and since I don't have a 6-stable system available I
> cannot test fixes for. The problems appear to be boost-related, both
> more or less look lik
Doug Barton wrote:
Howdy,
I've noticed a lot of commits recently to use plist-sub for pkg-message
and I'm wondering if there is some overarching purpose for this, or if
it's just general cleanup? If the latter that's fine, and I am fully
supportive of efforts to keep things neat and tidy. The re
On 01/18/10 17:23, Philip M. Gollucci wrote:
> That particular one is questionable, but I'm sure if every post-install
> message is in pkg-message or files/pkg-message.in it will help with
>
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/122877
Ok, now I see where you're going with this. :
Doug Barton wrote:
Ok, now I see where you're going with this. :) With respect to Wesley,
the approach in the patch is bass-ackwards. You don't want to do
anything with files named *pkg*message*, there are just too many
variations. The only thing you want to worry about is
/var/db/pkg/*/+DISPLAY
On 01/18/10 17:42, Philip M. Gollucci wrote:
> Doug Barton wrote:
>> Ok, now I see where you're going with this. :) With respect to Wesley,
>> the approach in the patch is bass-ackwards. You don't want to do
>> anything with files named *pkg*message*, there are just too many
>> variations. The onl
On Tue, Jan 19, 2010 at 6:30 AM, Max Brazhnikov wrote:
> The following reply was made to PR ports/142880; it has been noted by
> GNATS.
>
> From: Max Brazhnikov
> To: bug-follo...@freebsd.org, jupeng...@gmail.com, w...@freebsd.org
> Cc:
> Subject: Re: ports/142880: [REPOCOPY] chinese/stardict2-d
Hi,
This is a quick patch to cfs which stops it stalling (forever) the
system startup if mountd fails. This can happen if mountd picks a port
which is already used (no idea why it doesn't try a few times) and then
cfsd fails.. If cfsd is not running mount will try forever (by default)
to connect.
29 matches
Mail list logo