Re: PACKAGESITE spam

On Sun, 22 Dec 2013 15:48:49 +0400, Gleb Smirnoff wrote: > Steve, > > On Sat, Dec 21, 2013 at 12:14:03PM -0800, Steve Kargl wrote: S> It did > not ask how to stop this stupidity. I asked to have S> this stupidity > stopped by default. The spewing of this S> information in > /var/log/messages pr

Re: 10.0-RELEASE cycle status update

On Tue, 19 Nov 2013 11:22:05 -0500, Glen Barber wrote: > As some may have noticed, the 10.0-RELEASE cycle has slipped a bit > behind schedule. No worries; release it when it's ready. Many thanks to all concerned for their efforts. ___ freebsd-current@f

Re: Official FreeBSD Binary Packages now available for pkgng

On Sat, 02 Nov 2013 09:01:56 -0500, Eric van Gyzen wrote: > On 11/02/2013 07:28 AM, Matthew Seaman wrote: >> I feel no obligation to do anything to encourage people that >> deliberately break the DNS. They've made their bed, and now they have >> to lie in it. > > Eric Camachat didn't break the

Re: libexecinfo?

On Wed, 18 Sep 2013 19:11:50 +0200, Baptiste Daroussin wrote: > On Wed, Sep 18, 2013 at 04:57:35PM +0000, Walter Hurry wrote: >> We had a recent issue with libiconv now being included in base, thus >> rendering the port superfluous. >> >> Does a similar situation exis

libexecinfo?

We had a recent issue with libiconv now being included in base, thus rendering the port superfluous. Does a similar situation exist with libexecinfo? I don't seem to need the port on on 10.0-ALPHA1 r255587, and htop and ruby both build quite happily without it. The library is /usr/lib/libexecin

Re: dns/libidn puzzle

On Fri, 13 Sep 2013 02:44:57 +0200, Matthias Andree wrote: > Am 12.09.2013 23:44, schrieb Walter Hurry: >> On 9.1, if I cd to /usr/ports/dns/libidn and issue 'sudo make config', >> I get a dialog asking me whether I want DOCS and/or NLS. >> >> Howeve

dns/libidn puzzle

On 9.1, if I cd to /usr/ports/dns/libidn and issue 'sudo make config', I get a dialog asking me whether I want DOCS and/or NLS. However, on 10-CURRENT (r255358) I get this: $ cd /usr/ports/dns/libidn $ sudo make config ===> Options unchanged $ Why the difference? _

Re: Problem with virtualbox-ose-additions

On Wed, 11 Sep 2013 00:20:09 +0200, Guido Falsi wrote: > On 09/10/13 23:58, Walter Hurry wrote: >> I have upgraded to r255358, rebuilt world and kernel, and dealt with >> the iconv issues. In the process I had to delete a handful of ports, am >> now trying to reinstall them,

Problem with virtualbox-ose-additions

I have upgraded to r255358, rebuilt world and kernel, and dealt with the iconv issues. In the process I had to delete a handful of ports, am now trying to reinstall them, and am running into a problem: FreeBSD freebsd.vm 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r255358: Sat Sep 7 22:28:09 BST 2013

Re: Ports with daemons on uninstall...

On Mon, 15 Jul 2013 08:34:05 -0500, Mark Felder wrote: > As long as this behavior only happens during pkg installs and never with > ports, I'm OK. The worst is when a coworker forgets that the mysql port > stops the daemon and my coworker upgrades with portmaster... the daemon > is off the entire

Question about portsdb (part of ports-mgmt/portupgrade)

On 9.1-RELEASE, when I follow 'portsnap fetch update' with 'portsdb -u', it updates the INDEX-9 and INDEX-9.db files in /usr/ports for me. But the corresponding action doesn't happen on 10.0-CURRENT (r251572) until I do a 'portsdb -Fu'. Why the difference? Obviously it's no big deal, but I'm ra

Re: Can't compile lxpanel

On Fri, 07 Jun 2013 01:07:26 +0200, Dimitry Andric wrote: > On Jun 6, 2013, at 18:21, Walter Hurry wrote: >> On Thu, 06 Jun 2013 09:19:20 -0600, asomers wrote: >>> Looks like a bug upstream. If this port worked in FreeBSD-9, then the >>> difference might be the swi

Re: Cannot startx on FreeBSD10 Current

On Sun, 16 Jun 2013 11:27:36 +0100, Anton Shterenlikht wrote: > From: Walter Hurry > Subject: Re: Cannot startx on FreeBSD10 Current Date: Fri, 14 Jun 2013 > 20:50:59 + (UTC) > > On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote: > > &

Re: Cannot startx on FreeBSD10 Current

On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote: > On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry > wrote: > >> I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM. >> >> > Recently, I started mentoring a Google Summer of Code stu

SOLVED: Cannot startx on FreeBSD10 Current

On Fri, 14 Jun 2013 14:21:46 -0400, Jung-uk Kim wrote: > > I had a similar problem a week ago. Basically, that Clang version > mis-compiles xorg-server. You may want to try the latest Clang on - > -CURRENT or build it with "make USE_GCC=any". > Thenk you so much! Yes, recompiling xorg-server

Re: Cannot startx on FreeBSD10 Current

On Fri, 14 Jun 2013 18:20:32 +0200, Koop Mast wrote: > On 14-6-2013 18:11, Walter Hurry wrote: >> On Fri, 14 Jun 2013 15:56:26 +, Miguel Clara wrote: >>> I had the same issue the first time I've built Xorg, when I've first >>> read: >>> "

Re: Cannot startx on FreeBSD10 Current

On Fri, 14 Jun 2013 15:56:26 +, Miguel Clara wrote: > > I had the same issue the first time I've built Xorg, when I've first > read: > "As of revision r235859 of FreeBSD 10.0-CURRENT, no patches should be > needed to get GEM/KMS. See Intel_GPU > for more de

Cannot startx on FreeBSD10 Current

I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM. Everything seems to work properly, except that I cannot 'startx'. All I get is a blank screen and an apparently hung box. The only way out of it is Machine -> Close -> Send the shutdown signal. The following appears in /var/lo

Re: Can't compile lxpanel

On Fri, 07 Jun 2013 13:58:50 -0700, Jakub Lach wrote: > Sorry for being so sparse, but I was just talking about general > impression from few tries I gave it. > > /proc wasn't main problem, usually I didn;t have any use for it. > > Basically it wasn't for me what it aimed to be- a frugal replace

Re: Can't compile lxpanel

On Thu, 06 Jun 2013 08:37:10 -0700, Jakub Lach wrote: > Last time I've checked lxde was unfortunately not worth hassle. > > e.g. it depends on /proc > Sorry, I'm no expert, but is that a problem? I routinely mount proc on /proc in fstab. Is that what you are referring to? Is it undesirable to d

Re: Can't compile lxpanel

On Thu, 06 Jun 2013 09:19:20 -0600, asomers wrote: > Looks like a bug upstream. If this port worked in FreeBSD-9, then the > difference might be the switch from gcc to clang. You could try > compiling the port with gcc. Just add these lines to /etc/make.conf > > CC=gcc CXX=g++ > CPP=gcpp > >

Can't compile lxpanel

I'm running 10.0-CORRENT on amd64. Ports and source are both up to date. When I try to compile x11/lxpanel I get this: -- gmake[4]: Entering directory `/usr/ports/x11/lxpanel/work/lxpanel-0.5.12/ src/plugins/volume' CC volume_la-volume.lo volume.c:19

Re: Can't compile databases/py-sqlite3

On Tue, 04 Jun 2013 21:53:57 +0200, Dimitry Andric wrote: > On Jun 4, 2013, at 21:15, Walter Hurry wrote: >> I'm running 10.0-CORRENT on amd64. Ports and source are both up to >> date. >> >> When I try a 'make install' in /usr/ports/databa

Can't compile databases/py-sqlite3

I'm running 10.0-CORRENT on amd64. Ports and source are both up to date. When I try a 'make install' in /usr/ports/databases/py-sqlite3 I get this very early on: ===> FreeBSD 10 autotools fix applied to /usr/ports/databases/py- sqlite3/work/Python-2.7.5/configure running config : /usr/src/lib/