Re: How to escalate? ports/159276 - cmake

On 28.08.2011 02:33, Raphael Kubo da Costa wrote: > Igor Soumenkov <2igo...@gmail.com> writes: > >> The same effect can be achieved by specifying >> CMAKE_C(XX)_FLAGS_{RELEASE,DEBUG} in command line. >> So, I suggest removing the patch from >> ports/devel/cmake/files/patch-Modules_Compiler_GNU.cmak

Missing libproxy.la?

Hi all, I read UPDATING and did a: # portupgrade -rf libnotify-0.\* libproxy-0.\* and this mostly succeeded except where it failed. In particular x11/gnome-panel complains: CCLD clock-applet gnome-libtool: link: cannot find the library `/usr/local/lib/libproxy.la' or unhandled argument

Re: Missing libproxy.la?

Hi, On 28/08/2011 15:55, Jonathan Chen wrote: Hi all, I read UPDATING and did a: # portupgrade -rf libnotify-0.\* libproxy-0.\* and this mostly succeeded except where it failed. In particular x11/gnome-panel complains: CCLD clock-applet gnome-libtool: link: cannot find the library `/usr/local/

Re: fusefs-kmod on recent -current

On Sun, Aug 7, 2011 at 2:17 PM, Fabian Keil wrote: > Michael Butler wrote: > >> Seems that the change to the mount flags in recent -current has broken >> the compilation of sysutils/fusefs-kmod :-( >> >> It now needs something like the attached to compile, > > The attachment didn't make it. Anywa

Re: [kde-freebsd] devel/cmake bug: "-pthread; -D_THREAD_SAFE" emitted instead of "-pthread -D_THREAD_SAFE"

Rene Ladan writes: > somehow devel/cmake outputs "-pthread;-D_THREAD_SAFE" instead of > "-pthread -D_THREAD_SAFE" to the generated Makefiles (note the semicolon). > > This means some list is passed verbatim to the compiler, causing the > shell to execute the wrong commands. I have looked into the

Re: mail/postfix-policyd-spf relies on vulnerable mail/libspf2-10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/27/2011 15:36, Uffe R. B. Andersen wrote: > Den 27-08-2011 23:05, Doug Barton skrev: >>> libspf2 port is currently libspf2-1.2.9_1 and according to the >>> page you refer to, the vulnerability affects libspf2 <1.2.8. > >> Yes, that was my poin

Re: How to escalate? ports/159276 - cmake

On Sat, Aug 27, 2011 at 03:35:29PM -0400, Jerry wrote: > FreeBSD prefers to tell others about how great it is and conveniently > hides its deficiencies. There's been plenty of honest discussion on several public mailing lists in the past 2 weeks that made some good points about what we're lacking.

Re: mail/postfix-policyd-spf relies on vulnerable mail/libspf2-10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Den 27-08-2011 23:05, Doug Barton skrev: >> libspf2 port is currently libspf2-1.2.9_1 and according to the >> page you refer to, the vulnerability affects libspf2 <1.2.8. > > Yes, that was my point. :) mail/libspf2-10 and mail/libspf2 are > differen

Re: How to escalate? ports/159276 - cmake

Igor Soumenkov <2igo...@gmail.com> writes: > The same effect can be achieved by specifying > CMAKE_C(XX)_FLAGS_{RELEASE,DEBUG} in command line. > So, I suggest removing the patch from > ports/devel/cmake/files/patch-Modules_Compiler_GNU.cmake and patching > ports/Mk/bsd.cmake.mk instead (attached)

Re: mail/postfix-policyd-spf relies on vulnerable mail/libspf2-10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/27/2011 11:07, Uffe R. B. Andersen wrote: > Den 26-08-2011 22:22, Doug Barton skrev: >> Howdy, > >> Doing some port updates and noticed that mail/postfix-policyd-spf >> relies on mail/libspf2-10, which according to >> http://portaudit.FreeBSD

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

On Sat, 27 Aug 2011 11:24:38 -0400 Steve Wills wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 08/27/11 10:37, Conrad J. Sabatier wrote: > > On Sat, 27 Aug 2011 12:22:56 +0300 > > Andriy Gapon wrote: > > > >> on 27/08/2011 12:03 Matthias Andree said the following: > >> ... > >>

Re: How to escalate? ports/159276 - cmake

On Sat, 27 Aug 2011 14:10:49 -0500 Mark Linimon articulated: > Well, in FreeBSD, there's really not an "escalate", since we're not a > hierarchy. The best thing you can do is what you've already done: > contact the maintainer and, if you don't get a response, either file > a PR with the suggested

Re: How to escalate? ports/159276 - cmake

On 27.08.2011 23:10, Mark Linimon wrote: > Well, in FreeBSD, there's really not an "escalate", since we're not a > hierarchy. The best thing you can do is what you've already done: > contact the maintainer and, if you don't get a response, either file > a PR with the suggested patch (which can lat

Re: How to escalate? ports/159276 - cmake

Well, in FreeBSD, there's really not an "escalate", since we're not a hierarchy. The best thing you can do is what you've already done: contact the maintainer and, if you don't get a response, either file a PR with the suggested patch (which can later be committed via maintainer-timeout), or post

Re: How to escalate? ports/159276 - cmake

On 27.08.2011 21:33, Igor Soumenkov wrote: > >> Igor Soumenkov <2igosha at gmail.com >> > writes: >> >> >/ Unfortunately, one of them ( Max Brazhnikov (makc@) ) is the committer I >> />/ am writing about. >> />/ And I CC:ed the kde@ mailing

Re: mail/postfix-policyd-spf relies on vulnerable mail/libspf2-10

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Den 26-08-2011 22:22, Doug Barton skrev: > Howdy, > > Doing some port updates and noticed that mail/postfix-policyd-spf > relies on mail/libspf2-10, which according to > http://portaudit.FreeBSD.org/2ddbfd29-a455-11dd-a55e-00163e16.html > > is v

Re: How to escalate? ports/159276 - cmake

> Igor Soumenkov <2igosha at gmail.com > > writes: > > >/ Unfortunately, one of them ( Max Brazhnikov (makc@) ) is the committer I > />/ am writing about. > />/ And I CC:ed the kde@ mailing list, but got reply only from Max. I quoted > />/

Re: How to escalate? ports/159276 - cmake

Igor Soumenkov <2igo...@gmail.com> writes: > Unfortunately, one of them ( Max Brazhnikov (makc@) ) is the committer I > am writing about. > And I CC:ed the kde@ mailing list, but got reply only from Max. I quoted > it here ("we can't just remove it...") - he is not going to fix it, and > he is no

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

On Sat, 27 Aug 2011 16:02:45 +0100 Chris Rees wrote: > On 27 August 2011 15:59, Conrad J. Sabatier wrote: > > On Sat, 27 Aug 2011 15:42:09 +0100 > > Chris Rees wrote: > > > >> On 27 August 2011 15:37, Conrad J. Sabatier > >> wrote: > >> > On Sat, 27 Aug 2011 12:22:56 +0300 > >> > Andriy Gapon

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/27/11 10:37, Conrad J. Sabatier wrote: > On Sat, 27 Aug 2011 12:22:56 +0300 > Andriy Gapon wrote: > >> on 27/08/2011 12:03 Matthias Andree said the following: >> ... >>> .if ${RUBY_VER} == 1.9 >>> BROKEN= does not build with ruby 1.9 >>

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

On 27 August 2011 15:59, Conrad J. Sabatier wrote: > On Sat, 27 Aug 2011 15:42:09 +0100 > Chris Rees wrote: > >> On 27 August 2011 15:37, Conrad J. Sabatier wrote: >> > On Sat, 27 Aug 2011 12:22:56 +0300 >> > Andriy Gapon wrote: >> >> >> >> I'd think that it would be sufficient to fix the reaso

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

On Sat, 27 Aug 2011 15:42:09 +0100 Chris Rees wrote: > On 27 August 2011 15:37, Conrad J. Sabatier wrote: > > On Sat, 27 Aug 2011 12:22:56 +0300 > > Andriy Gapon wrote: > >> > >> I'd think that it would be sufficient to fix the reason why the > >> BROKEN line was added in the first place. > >>

Annoying portupgrade behavior

This is annoying: root@kg-v2# portupgrade -rf libnotify-0.\* libproxy-0.\* : Permission denied ** There are errors in a meta info for ruby18-alexandria-0.6.6 ** Run 'pkgdb -F' to interactively fix them. Yes, I have ruby18-alexandria installed, and would like to keep it that way. root@kg-v2# pkgdb

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

On 27 August 2011 15:37, Conrad J. Sabatier wrote: > On Sat, 27 Aug 2011 12:22:56 +0300 > Andriy Gapon wrote: > >> on 27/08/2011 12:03 Matthias Andree said the following: >> ... >> > .if ${RUBY_VER} == 1.9 >> > BROKEN=     does not build with ruby 1.9 >>             ^^

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

On Sat, 27 Aug 2011 12:22:56 +0300 Andriy Gapon wrote: > on 27/08/2011 12:03 Matthias Andree said the following: > ... > > .if ${RUBY_VER} == 1.9 > > BROKEN= does not build with ruby 1.9 > > > .endif > ... > > - does your newly-built Amarok _us

Re: How to escalate? ports/159276 - cmake

On 27.08.2011 18:17, Sam Cassiba wrote: > On 08/27/11 08:40, Igor Soumenkov wrote: >> >> On 27.08.2011 17:25, Sam Cassiba wrote: >>> On 08/27/11 03:11, Igor Soumenkov wrote: Dear all, How can I escalate the issue related to one of the ports? Cmake in ports sets different cflag

Re: Problem with nvidia-driver and "X" after upgrade

On Sat, 27 Aug 2011 13:27:29 +0100 Chris Rees articulated: > On 27 Aug 2011 13:02, "Test Rat" wrote: > > > > Carmel writes: > > > > > On Sat, 27 Aug 2011 01:45:48 +0200 > > > Michal Varga articulated: > > >> > So, after rebuild World/Kernel and installing same and then > > >> > rebuilding the nv

Re: How to escalate? ports/159276 - cmake

On 08/27/11 08:40, Igor Soumenkov wrote: On 27.08.2011 17:25, Sam Cassiba wrote: On 08/27/11 03:11, Igor Soumenkov wrote: Dear all, How can I escalate the issue related to one of the ports? Cmake in ports sets different cflags than the original one. It seems that the comitter who introduced t

Re: How to escalate? ports/159276 - cmake

On 27.08.2011 17:25, Sam Cassiba wrote: > On 08/27/11 03:11, Igor Soumenkov wrote: >> Dear all, >> >> How can I escalate the issue related to one of the ports? >> Cmake in ports sets different cflags than the original one. It seems >> that the comitter who introduced this problem with a patch >> (

Re: Problem with nvidia-driver and "X" after upgrade

On 27 Aug 2011 14:08, "Test Rat" wrote: > > Chris Rees writes: > > >> >> Carmel writes: > >> >> > So, after rebuild World/Kernel and installing same and then > >> >> > rebuilding the nvidia-driver, all is well again. > >> >> > > >> >> > Now, in my not so humble opinion, there should be some sort

Re: How to escalate? ports/159276 - cmake

On 08/27/11 03:11, Igor Soumenkov wrote: Dear all, How can I escalate the issue related to one of the ports? Cmake in ports sets different cflags than the original one. It seems that the comitter who introduced this problem with a patch (http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/cmake/fi

Re: Problem with nvidia-driver and "X" after upgrade

Michal Varga articulated: >> This is a known phenomena with everything when having your OS sources >> and your live OS out of sync. > > Define "everything" Obviously, not everything suffers from this > problem. In fact, lacking proof otherwise, I would tend to > believe that this is a niche pr

Re: Problem with nvidia-driver and "X" after upgrade

Chris Rees writes: >> >> Carmel writes: >> >> > So, after rebuild World/Kernel and installing same and then >> >> > rebuilding the nvidia-driver, all is well again. >> >> > >> >> > Now, in my not so humble opinion, there should be some sort of >> >> > warning in the driver dialog, or at least in

Re: Problem with nvidia-driver and "X" after upgrade

On 27 Aug 2011 13:02, "Test Rat" wrote: > > Carmel writes: > > > On Sat, 27 Aug 2011 01:45:48 +0200 > > Michal Varga articulated: > >> > So, after rebuild World/Kernel and installing same and then > >> > rebuilding the nvidia-driver, all is well again. > >> > > >> > Now, in my not so humble opini

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

On 27 Aug 2011 11:10, "Conrad J. Sabatier" wrote: > > On Sat, 27 Aug 2011 11:03:46 +0200 > Matthias Andree wrote: > > > Am 27.08.2011 10:52, schrieb Conrad J. Sabatier: > > > As the subject line states, I just managed to rebuild and reinstall > > > audio/amarok with no glitches whatsoever. > > >

Re: Problem with nvidia-driver and "X" after upgrade

Carmel writes: > On Sat, 27 Aug 2011 01:45:48 +0200 > Michal Varga articulated: >> > So, after rebuild World/Kernel and installing same and then >> > rebuilding the nvidia-driver, all is well again. >> > >> > Now, in my not so humble opinion, there should be some sort of >> > warning in the driv

Re: Problem with nvidia-driver and "X" after upgrade

On Sat, 27 Aug 2011 01:45:48 +0200 Michal Varga articulated: > On Fri, 2011-08-26 at 18:51 -0400, Carmel wrote: > > > I found the problem. I had downloaded the source files for BSD a few > > days ago; however, I never rebuild the kernel or world. When the > > nvidia driver got rebuild it was evid

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

On Sat, 27 Aug 2011 11:03:46 +0200 Matthias Andree wrote: > Am 27.08.2011 10:52, schrieb Conrad J. Sabatier: > > As the subject line states, I just managed to rebuild and reinstall > > audio/amarok with no glitches whatsoever. > > > > # uname -a > > FreeBSD serene.no-ip.org 9.0-BETA1 FreeBSD 9.0

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

on 27/08/2011 12:03 Matthias Andree said the following: ... > .if ${RUBY_VER} == 1.9 > BROKEN= does not build with ruby 1.9 > .endif ... > - does your newly-built Amarok _use_ Ruby? Or did the configuration or > build weazel out of it? > > - d

Re: audio/amarok: make TRYBROKEN=yes reinstall worked!

Am 27.08.2011 10:52, schrieb Conrad J. Sabatier: > As the subject line states, I just managed to rebuild and reinstall > audio/amarok with no glitches whatsoever. > > # uname -a > FreeBSD serene.no-ip.org 9.0-BETA1 FreeBSD 9.0-BETA1 #7: Thu Aug 25 > 01:47:03 CDT 2011 > conr...@serene.no-ip.org:/us

audio/amarok: make TRYBROKEN=yes reinstall worked!

As the subject line states, I just managed to rebuild and reinstall audio/amarok with no glitches whatsoever. # uname -a FreeBSD serene.no-ip.org 9.0-BETA1 FreeBSD 9.0-BETA1 #7: Thu Aug 25 01:47:03 CDT 2011 conr...@serene.no-ip.org:/usr/obj/usr/src/sys/CUSTOM amd64 So, what exactly is broken abo

Re: ghostscript9 installed; OK for ghostscript8 dependency?

On 8/26/2011 10:27 PM, Mike Brown wrote: > I had ghostscript8 installed, but after an ordinary upgrade (I think, I mean, > I don't recall doing anything unusual), I ended up with ghostscript9. After > that, portmaster complained that ghostscript8 was a dependency for a couple > of > the other i

Re: How to escalate? ports/159276 - cmake

On Sat, Aug 27, 2011 at 12:11 PM, Igor Soumenkov <2igo...@gmail.com> wrote: > Dear all, > > How can I escalate the issue related to one of the ports? > Cmake in ports sets different cflags than the original one. It seems > that the comitter who introduced this problem with a patch > ( > http://www

How to escalate? ports/159276 - cmake

Dear all, How can I escalate the issue related to one of the ports? Cmake in ports sets different cflags than the original one. It seems that the comitter who introduced this problem with a patch (http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/cmake/files/patch-Modules_Compiler_GNU.cmake?rev=1.

Re: FreeBSD Port of sc-7.61_1

On 27 August 2011 07:44, Ruslan Mahmatkhanov wrote: > David T-G wrote on 27.08.2011 00:59: >> >> Ruslan, et al -- >> >> ...and then David T-G said... >> % >> ... >> % In the mean time, since this looks like an ordinary tarball of source >> % code, I'll try extracting it in a tmp dir and doing a re