Re: [CFT] SSP Package Repository available

2014-09-22 Thread Michael Jung 

On 2014-08-20 12:34, Bryan Drewery wrote:

On 9/21/2013 5:49 AM, Bryan Drewery wrote:

Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.

Support may be added for earlier i386 releases once all ports properly
respect LDFLAGS.

To enable, just add WITH_SSP=yes to your make.conf and rebuild all 
ports.


The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all
may optionally be set instead.

Please help test this on your system. We would like to eventually 
enable
this by default, but need to identify any major ports that have 
run-time

issues due to it.

[1] https://en.wikipedia.org/wiki/Buffer_overflow_protection



We have not had any feedback on this yet and want to get it enabled by
default for ports and packages.

We now have a repository that you can use rather than the default to
help test. We need your help to identify any issues before switching 
the

default.

This repository is available for:

head
10.0
9.1,9.2,9.3

It is not available for 8.4. If someone is willing to test on 8.4 I 
will

build a repository for it.

Place this in /usr/local/etc/pkgs/repos/FreeBSD_ssp.conf:

FreeBSD: { enabled: no }
FreeBSD_ssp: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/ssp";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

Once that is done you should force reinstall packages from this 
repository:


  pkg update
  pkg upgrade -f

Thanks for your help!
Bryan Drewery
On behalf of portmgr.


I have been building (poudriere) and running some 1100+ ports 
WITH_SSP_PORT=yes under 10-STABLE and CURRENT without issue. This is 
using both our local repository and the ssp repository listed above.


--mikej
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

ports/ make fetch Mk/ failures

2014-09-22 Thread Julian H. Stacey 
Hi po...@freebsd.org,
For later local builds of releases, & as some distfiles disappear, I do:
uname -r # 9.3-RELEASE
cd /pri/FreeBSD/branches/amd64/-current/ports; setenv PORTSDIR `pwd`
make -j 3 -k fetch BATCH=YES# Or make checksum 

Some ports always fail, fetch depending on an install !
- Running as root would solve it, but would pollute the system,
  (ports wanted here are already installed: `ls /var/db/pkg | wc -l` ~1000 ).
- A cludge would be: A chroot followed by a discard of junk installed.
- Nicest : A crontab driven checker on freebsd.org ?


Also Mk/ emits false noise, eg:
  cd graphics/linux-f10-ungif; make fetch
You are about to convert your system to pkg while you have ports/packages
installed with the old pkg_install tools.
Stop 

ports/Mk should not assume all systems use or want packages.  
Systems here are built & installed exclusively from ports/ sources, no pkg*.

Cheers,
Julian
-- 
Julian Stacey, BSD Linux Unix'78 C Sys Eng Consultant Munich http://berklix.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[Bug 178364] [patch] Port dns/adns add option to apply patch

2014-09-22 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=178364

Tilman Keskinoz  changed:

   What|Removed |Added

 CC||ar...@freebsd.org
   Assignee|freebsd-ports@FreeBSD.org   |freebsd-ports-bugs@FreeBSD.
   ||org

--- Comment #7 from Tilman Keskinoz  ---
fix default assignee

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: roundcube and php 5.4.33: fgets(): SSL read operation timed out

2014-09-22 Thread Michael Grimm 
JFTR:

On 20.09.2014, at 13:17, Michael Grimm  wrote:

> My setup: roundcube-1.0.2 + nginx-1.6.2 in a FreeBSD-10 jail. RC will connect 
> to a recent dovecot server in another jail at the same host.
> 
> Recently, after upgrading php from 5.4.32 to 5.4.33 roundcube will refuse to 
> connect to dovecot:
> 
> | roundcube: PHP Warning:  fgets(): SSL read operation timed out in \
> | /...path2rc.../roundcube/program/lib/Roundcube/rcube_imap_generic.php 
> on line 200
> 
> Recompiling every port involved and restarting both involved jails hasn't 
> been successful. Only, reverting back to php 5.4.32 made RC work again.
> 
> Is anyone running into this as well?
> Any idea how to debug this?

Someone at the RC mailing list directed me to 
https://bugs.php.net/bug.php?id=41631
Reading all those related comments, it seems to me rather a PHP and not a RC 
issue:
http://news.php.net/php.bugs/187641

(I did try to apply that patch, but failed on its second trunk :-( That might 
be beyond my capabilities, though.)

Regards,
Michael
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Patch] Using MACHINE_ARCH identifiers in pkg

2014-09-22 Thread Nathan Whitehorn 
Baptiste, have you had a chance to look at this? I'd like to at least 
merge the changes to the bootstrapper in base so that it doesn't seg 
fault at start on armeb, but want to make sure the URLs are finalized 
before doing that.

-Nathan

On 09/17/14 11:28, olli hauer wrote:

On 2014-09-16 18:05, Nathan Whitehorn wrote:
< snip very long conversation>
http://lists.freebsd.org/pipermail/freebsd-ports/2014-September/095521.html



I've made a third version of the patch that chases some recent updates to the 
ports tree and can be found at:
http://people.freebsd.org/~nwhitehorn/pkg-new-abi-v3.diff

Please let me know if you run into any difficulties.
-Nathan


Short success summary for patch pkg-new-abi-v3.diff

The following tests where done on FrreeBSD-10 (amd64) with poudriere-devel for 
package building


Package building.

build 1: 10amd64-default-abi1
  - package build (without pkg-new-abi-v3.diff)

apply pkg-new-abi-v3.diff after build 1.

build 2: 10amd64-default-abi2
  - $ cpdup 10amd64-default-abi1 10amd64-default-abi2
  - rebuild pkg (pkg-1.3.7_1)

build 3: 10amd64-default-abi3
  - $ cpdup 10amd64-default-abi2 10amd64-default-abi3
  - remove some packages to force rebuild (pcre, and some others)
  - rebuild missing packages

build 4: 10amd64-default-abi4
  - fresh build (all packages with applied pkg-new-abi-v3.diff)


Setup apache based repo:

# old ABI
Alias /pkg/freebsd:10:x86:64/abi1/ $path_to/10amd64-default-abi1/

# new ABI
# Note: both abi1 aliases are required for the upgrade / downgrade
# test and until all systems running the new patched pkg
Alias /pkg/FreeBSD:10:amd64/abi1/  $path_to/10amd64-default-abi1/
Alias /pkg/FreeBSD:10:amd64/abi2/  $path_to/10amd64-default-abi2/
Alias /pkg/FreeBSD:10:amd64/abi3/  $path_to/10amd64-default-abi3/
Alias /pkg/FreeBSD:10:amd64/abi4/  $path_to/10amd64-default-abi4/


$ cat pkg/repos/abi.conf
FreeBSD: { enabled: no }
abi: {
  url: "http://$repo-host/pkg/${ABI}/abi1";, <= changed during the tests
  enabled : yes,
  mirror_type : none
}


start:
- install packages from abi1 on fresh system

test 1:
- change repo to abi2 + pkg update / upgrade to patched pkg
   ==> OK, no issues

test 2:
- remove some ports, reinstall them again, pkg upgrade -f
   ==> OK, no issues

test 3:
- change repo to abi3 + repead all tests
   ==> OK, no issues

test 4:
- change repo to abi4 + repead all tests
   ==> OK, no issues

test 5:
- change repo back to abi1 + repead all tests (downgraded pkg)
   ==> OK, no issues


Short summary:
- update / upgrade / downgrade worked as expected between every build.
- packages are reporting on every test the old ABI (Architecture: 
freebsd:10:x86:64)
- issues found in patch v1/v2 are no longer present and fixed


I think the patch works as expected, but please test yourself!

If someone is interested to get the packages from the builds 1-4 send me a PM, 
I have them available as archive (~120MB).




___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [HEADSUP] pkg(8) is now the only package management tool

2014-09-22 Thread Bryan Drewery 
On 9/21/2014 6:53 PM, Michelle Sullivan wrote:
> Michelle Sullivan wrote:
>> Baptiste Daroussin wrote:
>>   
>>> Hi all,
>>>
>>> The ports tree has been modified to only support pkg(8) as package 
>>> management
>>> system for all supported version of FreeBSD.
>>>
>>> if you were still using pkg_install (pkg_* tools) you will have to upgrade 
>>> your
>>> system.
>>>
>>> The simplest way is
>>> cd /usr/ports/ports-mgmt/pkg
>>> make install
>>> then run 
>>> pkg2ng
>>>
>>> 
> 
> So despite being told 'use the quarterly, patches can be applied to it
> if requested' and updating ports I maintain asking specifically for the
> patches to be merged...
> 
> Still all broken (though patches applied to HEAD)...  Nice one...
> 

Which ports and PR?

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

x11/libXcm: r351936 and using libtool

2014-09-22 Thread Boris Samorodov 
Hi Tijl, All,

The revision 351936 only bumped PORTREVISION. Assume that
"USES=libtool:keepla" should be added too.

Now, AFAIK no port uses those *.la file I try to go to
"USES=libtool". However I get:
-
libtool: install: /usr/bin/install -c .libs/libXcmEDID.lai
/usr/ports/x11/libXcm/work/stage/usr/local/lib/libXcmEDID.la
-

For now I leave "USES=libtool:keepla".

Any help is appreciated. Thanks.

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: x11/libXcm: r351936 and using libtool

2014-09-22 Thread Tijl Coosemans 
On Mon, 22 Sep 2014 22:07:58 +0400 Boris Samorodov  wrote:
> Hi Tijl, All,
> 
> The revision 351936 only bumped PORTREVISION. Assume that
> "USES=libtool:keepla" should be added too.
> 
> Now, AFAIK no port uses those *.la file I try to go to
> "USES=libtool". However I get:
> -
> libtool: install: /usr/bin/install -c .libs/libXcmEDID.lai
> /usr/ports/x11/libXcm/work/stage/usr/local/lib/libXcmEDID.la
> -
> 
> For now I leave "USES=libtool:keepla".
> 
> Any help is appreciated. Thanks.

The Makefile contains XORG_CAT=lib which causes Mk/bsd.xorg.mk to
add USES=libtool:keepla.  I'm not sure if XORG_CAT is correct for
this port.  It isn't part of the Xorg project is it?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: x11/libXcm: r351936 and using libtool

2014-09-22 Thread Boris Samorodov 
22.09.2014 22:20, Tijl Coosemans пишет:
> On Mon, 22 Sep 2014 22:07:58 +0400 Boris Samorodov  wrote:
>> Hi Tijl, All,
>>
>> The revision 351936 only bumped PORTREVISION. Assume that
>> "USES=libtool:keepla" should be added too.
>>
>> Now, AFAIK no port uses those *.la file I try to go to
>> "USES=libtool". However I get:
>> -
>> libtool: install: /usr/bin/install -c .libs/libXcmEDID.lai
>> /usr/ports/x11/libXcm/work/stage/usr/local/lib/libXcmEDID.la
>> -
>>
>> For now I leave "USES=libtool:keepla".
>>
>> Any help is appreciated. Thanks.
> 
> The Makefile contains XORG_CAT=lib which causes Mk/bsd.xorg.mk to
> add USES=libtool:keepla.  I'm not sure if XORG_CAT is correct for
> this port.  It isn't part of the Xorg project is it?

It is not part of Xorg, it's a standalone library.
Seems that I should try to remove XORG_CAT.
Thanks!

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: x11/libXcm: r351936 and using libtool

2014-09-22 Thread Boris Samorodov 
22.09.2014 22:27, Boris Samorodov пишет:
> 22.09.2014 22:20, Tijl Coosemans пишет:
>> On Mon, 22 Sep 2014 22:07:58 +0400 Boris Samorodov  wrote:
>>> Hi Tijl, All,
>>>
>>> The revision 351936 only bumped PORTREVISION. Assume that
>>> "USES=libtool:keepla" should be added too.
>>>
>>> Now, AFAIK no port uses those *.la file I try to go to
>>> "USES=libtool". However I get:
>>> -
>>> libtool: install: /usr/bin/install -c .libs/libXcmEDID.lai
>>> /usr/ports/x11/libXcm/work/stage/usr/local/lib/libXcmEDID.la
>>> -
>>>
>>> For now I leave "USES=libtool:keepla".
>>>
>>> Any help is appreciated. Thanks.
>>
>> The Makefile contains XORG_CAT=lib which causes Mk/bsd.xorg.mk to
>> add USES=libtool:keepla.  I'm not sure if XORG_CAT is correct for
>> this port.  It isn't part of the Xorg project is it?
> 
> It is not part of Xorg, it's a standalone library.
> Seems that I should try to remove XORG_CAT.

OK, done.

Tijl, thank you for your prompt help!

-- 
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Lusca off from ports

2014-09-22 Thread EnioRM 
Have you any information about why lusca was removed from ports/pkg

TKZ

-- 
*EnioRM *
*B**ackup na nuvem **com o Dropbox *
*Não perca suas anotações. Use o Evernote
*
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Lusca off from ports

2014-09-22 Thread A.J. 'Fonz' van Werven 
EnioRM wrote:

> Have you any information about why lusca was removed from ports/pkg

If you mean www/lusca-head, it was removed because nobody converted it to
support STAGEDIR. You could have found that information on Freshports.

If you feel like resurrecting it, you'll need to either retrieve the old
Makefile from e.g. SVN or a ports tree from a release before September 1st
and convert it to support staging, or create a new port from scratch.

AvW

-- 
Imbibo, ergo sum.


pgp2YvlWp8OvY.pgp
Description: PGP signature

Re: Lusca off from ports

2014-09-22 Thread Lowell Gilbert 
EnioRM  writes:

> Have you any information about why lusca was removed from ports/pkg

$ cd /usr/ports/
$ make search name=lusca
Port:   www/lusca-head
Moved:
Date:   2014-09-01
Reason: Not staged

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

[Bug 193849] www/xpi-conkeror builds from very old source code

2014-09-22 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193849

roo4...@gmail.com changed:

   What|Removed |Added

 CC||freebsd-ports@FreeBSD.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Mk/Uses/pgsql.mk wants 9.3 but 9.3.5 is installed

2014-09-22 Thread Jason E. Hale 
You probably need to add:

DEFAULT_VERSIONS= pgsql:9.3

to your /etc/make.conf because pgsql 9.2 is the current default.
Mk/Uses/pgsql.mk compares your installed version with the default or
whatever you set as the default.  If they are not equal, you will get
an IGNORE message.  If you already have a DEFAULT_VERSIONS line in
/etc/make.conf, just append pgsql:9.3 to the end of the list.

On Sun, Sep 21, 2014 at 2:13 PM, Axel Rau  wrote:
> Hi all,
>
> I have
> USES=   pgsql:9.0+
> in my Makefile and get the error
> cannot install: the port wants postgresql-client version 9.0 9.1 9.2 
> 9.3 9.4 and you have version 9.3 installed.
> I have postgresql93-client-9.3.5 installed.
> Any workarounds?
>
> Thanks, Axel
> ---
> PGP-Key:29E99DD6  ☀ +49 151 2300 9283  ☀ computing @ chaos claudius
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

games/linux-nwnclient with c6

2014-09-22 Thread Sean C. Farley 
I am currently testing the switch of f10 to c6 for the Linux base with 
games/linux-nwnclient.  One component that it requires is libglu.  This 
is provided by graphics/linux-f10-libGLU or graphics/linux-c6-dri.  I am 
unable to install this game as is.


Error:
===>  linux-nwnclient-1.69_1 bsd.linux-apps.mk test failed: The 
component libglu is not defined for LINUX_DIST_SUFFIX=-c6 (the 
corresponding variable libglu_c6_FILE is not defined). This usually 
means that the current port should be used with non default linux base 
and/or infrastructure port(s).


This is due to the fact that I am using the nvidia-driver in c6 (using 
the patch from bug 193832[1]).


How should I request libGLU in c6 with and without nvidia-driver? 
Currently, the port sets USE_LINUX_APPS to either libglu or dri 
depending upon the driver.


Sean
  1. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193832
--
s...@freebsd.org
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"