Hi!
I rebuilt whole x11/xorg (due to problem with google earth - it's been
missing earth picture)
but i didn't solve that problem.
Even more, now I'm trying to startx with empty ~/.xinitrc (twm should be run
as default WM), but twm won't start.
X server just shut down without errors.
With "exec tw
On Sun, Aug 09, 2009 at 10:16:44AM +0200, Klaus Koch wrote:
> as of 6th of August, there's a possible remote code execution exploit
> known in both "Sun JDK and JRE 6 Update 14 and earlier" and "Sun JDK
> and JRE 5.0 Update 19 and earlier" [...] I didn't get any notifications
> with portaudit yet.
Doug Barton wrote:
Thomas Backman wrote:
Thanks, guys!
However, a new issue appeared... Kind of. I know I read something about
portsnap and INDEX on the -current list recently, so I'm guessing this
is related? Maybe not, though (see later in the mail).
[r...@chaos /usr/ports/ports-mgmt]# por
Folks,
Am compiling KDE4 (from scratch) & am getting a stop in kdebase4-workspace.
Stop is due to a missing xml file
/usr/local/kde4/share/dbus-1/interfaces/org.kde.NotificationItemWatcher.xml.
I believe I have compiled the dependencies with all the latest sources..
What am I missing
Thank yo
On Sat, 15 Aug 2009 13:06:56 -0700
Doug Barton wrote:
> Jason J. Hellenthal wrote:
>
> > Why not just add weekly_status_pkg_enable="YES" to /etc/periodic.conf.local
> > and youll be informed of packages that need updating.
>
> Sorry to pick on your response, but this thread is a good time to
>
Jason J. Hellenthal wrote:
> Why not just add weekly_status_pkg_enable="YES" to /etc/periodic.conf.local
> and youll be informed of packages that need updating.
Sorry to pick on your response, but this thread is a good time to
remind people of some basic mailing list etiquette:
1. Read the whol
On Sat, 15 Aug 2009 20:48:53 +0200
Thomas Backman wrote:
>
> On Aug 15, 2009, at 20:31, Miroslav Lachman wrote:
>
> > Thomas Backman wrote:
> > [...]
> >> [r...@chaos ~]# pkgdb -aF
> >> ---> Checking the package registry database
> >> [r...@chaos ~]# portversion -l '<'
> >> dnsmasq
Thomas Backman wrote:
> Thanks, guys!
> However, a new issue appeared... Kind of. I know I read something about
> portsnap and INDEX on the -current list recently, so I'm guessing this
> is related? Maybe not, though (see later in the mail).
>
> [r...@chaos /usr/ports/ports-mgmt]# portsnap -I fet
Thomas Backman wrote:
However, a new issue appeared... Kind of. I know I read something about
portsnap and INDEX on the -current list recently, so I'm guessing this
is related? Maybe not, though (see later in the mail).
libtool-1.5.26 ! Comparison failed
This is beca
In message <6b5b7698-ccd8-48ff-a5fb-0349d4cc1...@exscape.org>,
Thomas Backman (seren...@exscape.org) wrote:
>
> On Aug 15, 2009, at 20:31, Miroslav Lachman wrote:
> > Thomas Backman wrote:
> > [...]
> >> [r...@chaos ~]# pkgdb -aF
> >> ---> Checking the package registry database
> >> [r...
On Aug 15, 2009, at 20:31, Miroslav Lachman wrote:
Thomas Backman wrote:
[...]
[r...@chaos ~]# pkgdb -aF
---> Checking the package registry database
[r...@chaos ~]# portversion -l '<'
dnsmasq <
ezm3<
libtool <
python26
Thomas Backman wrote:
[...]
[r...@chaos ~]# pkgdb -aF
---> Checking the package registry database
[r...@chaos ~]# portversion -l '<'
dnsmasq <
ezm3<
libtool <
python26<
[r...@chaos ~]# pkg_version | awk '$2 !~ /=
Thomas Backman wrote:
> First off: not subscribed to this list, please make sure to Cc me or I
> won't see your answers! :)
>
> Oh, and I use portsnap, in crontab:
> 0 19 * * * portsnap -I cron update
>
> So, long story short:
>
> [r...@chaos ~]# pkgdb -aF
> ---> Checking the package registry
N.J. Mann wrote:
> Some years ago I tried using portupgrade, but had all sorts of problems
> with its database getting corrupted. In desparation I tried portmaster
> and have been a very happy since. (Thanks Doug!).
Well I don't know about the desperation part, but you're welcome in
any case. :
In message ,
Thomas Backman (seren...@exscape.org) wrote:
> First off: not subscribed to this list, please make sure to Cc me or I
> won't see your answers! :)
>
> Oh, and I use portsnap, in crontab:
> 0 19 * * * portsnap -I cron update
>
> So, long story short:
>
> [r...@chaos ~]# pk
First off: not subscribed to this list, please make sure to Cc me or I
won't see your answers! :)
Oh, and I use portsnap, in crontab:
0 19 * * * portsnap -I cron update
So, long story short:
[r...@chaos ~]# pkgdb -aF
---> Checking the package registry database
[r...@chaos ~]# portversion -l
On Sat, Aug 15, 2009 at 02:01:27PM +0200, Oliver Heesakkers wrote:
> The configuration file of dovecot 1.1 will most likely not work for Dovecot
> 1.2
>
> Shouldn't this be mentioned in UPDATING?
>
> See: http://wiki.dovecot.org/Upgrading/1.2
Yes, I will get something in there now. Sorry for th
The configuration file of dovecot 1.1 will most likely not work for Dovecot
1.2
Shouldn't this be mentioned in UPDATING?
See: http://wiki.dovecot.org/Upgrading/1.2
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fre
Dear Sir/Madam,
Please, publish in the official ports build patch system, the patch
bellow for the problem
that manifest itself only on the amd64 platform, and it is one and the
same for both the
flow-tools and flow-tools-ng - i.e. flow-capture eats all of the RAM
and SWAP of the
machine, until ki
19 matches
Mail list logo
