Re: libidn2 drags in ruby and friends

2017-07-28 Thread Randy Bush 
repo head is 446595, which does not have this patch.  i plead for
someone to commit?  pretty please? :)

thanks

randy

> Attached an updated patch. I will also send it to sunpoet (maintainer)
> and will ask for approval.
> 
> Greetings,
> Torsten
> -- 
> Support me at:
> https://www.patreon.com/TorstenZuehlsdorff
> [2 libidn2-with-docs-option.diff ]
> Index: Makefile
> ===
> --- Makefile  (Revision 446668)
> +++ Makefile  (Arbeitskopie)
> @@ -12,11 +12,16 @@
>  LICENSE= GPLv3
>  LICENSE_FILE=${WRKSRC}/COPYING
>  
> -BUILD_DEPENDS=   ronn:textproc/rubygem-ronn
>  LIB_DEPENDS= libunistring.so:devel/libunistring
>  
> +OPTIONS_DEFINE=  DOCS
> +DOCS_BUILD_DEPENDS=  ronn:textproc/rubygem-ronn
> +
>  CONFIGURE_ARGS=  --disable-nls \
>   --with-libunistring-prefix=${LOCALBASE}
> +
> +DOCS_CONFIGURE_OFF=  --disable-doc
> +
>  GNU_CONFIGURE=   yes
>  INSTALL_TARGET=  install-strip
>  USE_LDCONFIG=yes
> Index: pkg-plist
> ===
> --- pkg-plist (Revision 446668)
> +++ pkg-plist (Arbeitskopie)
> @@ -5,35 +5,35 @@
>  lib/libidn2.so.0
>  lib/libidn2.so.0.3.2
>  libdata/pkgconfig/libidn2.pc
> -man/man1/idn2.1.gz
> -man/man3/idn2_check_version.3.gz
> -man/man3/idn2_free.3.gz
> -man/man3/idn2_lookup_u8.3.gz
> -man/man3/idn2_lookup_ul.3.gz
> -man/man3/idn2_register_u8.3.gz
> -man/man3/idn2_register_ul.3.gz
> -man/man3/idn2_strerror.3.gz
> -man/man3/idn2_strerror_name.3.gz
> -man/man3/idn2_to_ascii_4i.3.gz
> -man/man3/idn2_to_ascii_4z.3.gz
> -man/man3/idn2_to_ascii_8z.3.gz
> -man/man3/idn2_to_ascii_lz.3.gz
> -man/man3/idn2_to_unicode_44i.3.gz
> -man/man3/idn2_to_unicode_4z4z.3.gz
> -man/man3/idn2_to_unicode_8z4z.3.gz
> -man/man3/idn2_to_unicode_8z8z.3.gz
> -man/man3/idn2_to_unicode_8zlz.3.gz
> -man/man3/idn2_to_unicode_lzlz.3.gz
> -share/gtk-doc/html/libidn2/api-index-full.html
> -share/gtk-doc/html/libidn2/home.png
> -share/gtk-doc/html/libidn2/index.html
> -share/gtk-doc/html/libidn2/left-insensitive.png
> -share/gtk-doc/html/libidn2/left.png
> -share/gtk-doc/html/libidn2/libidn2-idn2.html
> -share/gtk-doc/html/libidn2/libidn2.devhelp2
> -share/gtk-doc/html/libidn2/libidn2.html
> -share/gtk-doc/html/libidn2/right-insensitive.png
> -share/gtk-doc/html/libidn2/right.png
> -share/gtk-doc/html/libidn2/style.css
> -share/gtk-doc/html/libidn2/up-insensitive.png
> -share/gtk-doc/html/libidn2/up.png
> +%%PORTDOCS%%man/man1/idn2.1.gz
> +%%PORTDOCS%%man/man3/idn2_check_version.3.gz
> +%%PORTDOCS%%man/man3/idn2_free.3.gz
> +%%PORTDOCS%%man/man3/idn2_lookup_u8.3.gz
> +%%PORTDOCS%%man/man3/idn2_lookup_ul.3.gz
> +%%PORTDOCS%%man/man3/idn2_register_u8.3.gz
> +%%PORTDOCS%%man/man3/idn2_register_ul.3.gz
> +%%PORTDOCS%%man/man3/idn2_strerror.3.gz
> +%%PORTDOCS%%man/man3/idn2_strerror_name.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_ascii_4i.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_ascii_4z.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_ascii_8z.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_ascii_lz.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_unicode_44i.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_unicode_4z4z.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_unicode_8z4z.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_unicode_8z8z.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_unicode_8zlz.3.gz
> +%%PORTDOCS%%man/man3/idn2_to_unicode_lzlz.3.gz
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/api-index-full.html
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/home.png
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/index.html
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/left-insensitive.png
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/left.png
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/libidn2-idn2.html
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/libidn2.devhelp2
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/libidn2.html
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/right-insensitive.png
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/right.png
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/style.css
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/up-insensitive.png
> +%%PORTDOCS%%share/gtk-doc/html/libidn2/up.png
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

PR commit request

2017-07-28 Thread Yasuhiro KIMURA 
Dear committers,

Would someone please commit following PR?

Bug 220609 - security/logcheck: Update to 1.3.18
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220609

Best regards.

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

Clang5 crashing on RPI2 compiling gnome3

2017-07-28 Thread bob prohaska 
Attempts to compile gnome3 on an RPI2 have run hard aground on

:57:6: note: expanded from here
Assertion failed: (0 <= N && N < static_cast(m_byteToColumn.size())), 
function byteToContainingColumn, file 
/usr/src/contrib/llvm/tools/clang/lib/Frontend/TextDiagnostic.cpp, line 281.
cc: error: unable to execute command: Abort trap (core dumped)
cc: error: clang frontend command failed due to signal (use -v to see 
invocation)
FreeBSD clang version 5.0.0 (trunk 308421) (based on LLVM 5.0.0svn)
Target: armv6-unknown-freebsd12.0-gnueabihf
Thread model: posix
InstalledDir: /usr/bin

Does anybody recognize this as a known problem? I seem to recall similar
messages, but those were on clang 4.something.

Is there a workaround?

Thanks for reading,

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

Re: FreeBSD Port: MailScanner-5.0.3

2017-07-28 Thread DutchDaemon - FreeBSD Forums Administrator 
On 28-7-2017 22:48, Chris Rees wrote:
> I've committed a fix using @sample for the config files, and fixed the
> regexes for paths.  @sample keyword was made for ports like this...
> 
> The port will no longer destroy your configuration.
> 
> Cheers,
> 
> Chris 

Good news, Chris. Thanks for your efforts!




signature.asc
Description: OpenPGP digital signature

Re: FreeBSD Port: MailScanner-5.0.3

2017-07-28 Thread Chris Rees 

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

Re: Trying to get poudriere to start

2017-07-28 Thread Chris Rees 

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

Re: Configuring options/knobs without `make config`

2017-07-28 Thread Chris Rees 

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

Re: FreeBSD Port: MailScanner-5.0.3

2017-07-28 Thread Chris Rees 

Hi all,

I have to say that actually the entire port is now a train wreck... the 
config directory is completely overwritten on install, and deleted on 
deinstall.  Config files should never go into pkg-plist directly!  I 
don't really understand why the previous method was changed as that has 
worked well.


I've marked it IGNORE and will fix it as quickly as I can.

Cheers,

Crhis

DutchDaemon - FreeBSD Forums Administrator wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
  
On 19-6-2017 07:18, Jeff Sickel wrote:

The MailScanner-5.0.3 update didn’t keep the /usr/local and other FreeBSD 
standard namespace in place.  I spent quite a bit of time correcting the perl 
scripts to pick up the /usr/local install locations after the upgrade.  The 
configuration files and other core pieces of MailScanner seem to keep more 
standard Linux namespaces with this release.  An upgrade from earlier versions 
is not recommended on FreeBSD until the correct file locations are handled by 
default.

Yeah .. https://forums.freebsd.org/threads/61298/
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
  
iQEcBAEBCAAGBQJZR772AAoJEA9a9BMWOKcx4u4IALFdgmHYH78bvPlL8ALqZiLw

4Ma9mS73sP98XuSWcKUWzI3c+6piT0Qk1RAn/+OGEK2hj99TNTDWQjOt9Ttlr4TN
iOiA3e9+gsKW3M9TrCzoOTGYj7sDagdzLgU3mH/xfTeHWKyM7J3KFEdqIpV267g6
3Ft69e6A3aUIrqMEtGx6qFl/F2NegoEZrmwMdDGiHceZlPn8wRoc0GPRCZUOZS2B
DvEZuU7tARQ8PaH0H84NL9r7t9e3N84328sPwqll2YyAsymU1Cjvi0MjKppqtFgz
KfwCrIi6AM/h6dkz1vR0eB4HoM/MfC1in0gQSR8nlCStT9iLvFePyOiRmjs0svc=
=HMeS
-END PGP SIGNATURE-

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



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

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

New port www/mod_security-devel

2017-07-28 Thread Marius Halden 
Hi,

I have created a new port for ModSecurity 3 which is currently under
development, but has better support for non-apache webservers as it's
now a library. I also have a patch to add support for the nginx
connector to the nginx port. I would like some help getting this
committed to the ports tree.

 * ModSecurity3 port:
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220352
 * Nginx connector:
 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220353

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

Re: Pkg does not upgrade if more than one repository is defined

2017-07-28 Thread Franco Fichtner 

> On 28. Jul 2017, at 1:13 PM, Matt Smith  wrote:
> 
> This might also be related to the CONSERVATIVE_UPGRADE setting of pkg.conf. 
> According to the man page:
> 
> CONSERVATIVE_UPGRADE: boolean
> Ensure in multi repository mode that the priority is
> given as much as possible to the repository where a
> package was first installed from.  Default: YES.

Is it still blindly updating from other repositories when a newer
version was found there?  In that case COSERVATIVE_UPGRADE still
doesn't work in most scenarios.


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

Re: Pkg does not upgrade if more than one repository is defined

2017-07-28 Thread Matt Smith 

On Jul 28 11:40, Miroslav Lachman wrote:

Matthias Fechner wrote on 2017/07/28 10:55:

Dear all,

I have a problem with pkg and I'm not sure if it is a bug in pkg or a
configuration issue.
I work on new version on ports which are in a separate poudriere
repository (to be able to easily test it).

I have now two configuration files in /usr/local/etc/pkg/repos,
poudriere.conf:
poudriere: {
url: "https://pkg.fechner.net/packages/110amd64-default;,
mirror_type: "pkg+http",
signature_type: "pubkey",
pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
enabled: yes,
priority: 1
}

this is the standard repo which contains all stable packages.
Now I have a new version (in this case for gitlab) at gitlab.conf:
gitlab: {
url: "https://pkg.fechner.net/packages/110amd64-gitlab;,
mirror_type: "pkg+http",
signature_type: "pubkey",
pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
enabled: yes,
priority: 10
}

The priority is higher and some package there have a higher version number.

But if I execute now 'pkg upgrade' pkg does not upgrade packages which
have a higher version from the gitlab repository, but stick to the
poudriere repository.

I also tried to do a 'pkg update -f; pkg upgrade' but it does not help.

Is there something wrong with my configuration or is this a bug in pkg?


If I understand you correctly, you have package A-1.0 installed from 
repo "poudriere" and now you have package A-1.1 in repo "gitlab" and 
you want to upgrade this package "A" to version 1.1.

Is it right?

I think that crossrepo upgrade is not automatic if package is in both 
repositories but it work if package is missing from previous repo and 
it it intentional.
I have more repositories too (different PHP version, different python 
versions but common utilities etc.) so packages are not 
unintentionally upgraded / downgraded.


But if you want to upgrade package A from different repo, you can 
choose the repo:


-r reponame, --repository reponame
 Install packages from only the named repository, irrespective
 of the configured ``active'' status from repo.conf.

You can try
  pkg install -r gitlab -f A

or
  pkg upgrade -r gitlab -f A

where A is you package(s) name.

Miroslav Lachman



This might also be related to the CONSERVATIVE_UPGRADE setting of 
pkg.conf. According to the man page:


CONSERVATIVE_UPGRADE: boolean
Ensure in multi repository mode that the priority is
given as much as possible to the repository where a
package was first installed from.  Default: YES.


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

Re: Pkg does not upgrade if more than one repository is defined

2017-07-28 Thread Miroslav Lachman 

Matthias Fechner wrote on 2017/07/28 10:55:

Dear all,

I have a problem with pkg and I'm not sure if it is a bug in pkg or a
configuration issue.
I work on new version on ports which are in a separate poudriere
repository (to be able to easily test it).

I have now two configuration files in /usr/local/etc/pkg/repos,
poudriere.conf:
poudriere: {
 url: "https://pkg.fechner.net/packages/110amd64-default;,
 mirror_type: "pkg+http",
 signature_type: "pubkey",
 pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
 enabled: yes,
 priority: 1
}

this is the standard repo which contains all stable packages.
Now I have a new version (in this case for gitlab) at gitlab.conf:
gitlab: {
 url: "https://pkg.fechner.net/packages/110amd64-gitlab;,
 mirror_type: "pkg+http",
 signature_type: "pubkey",
 pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
 enabled: yes,
 priority: 10
}

The priority is higher and some package there have a higher version number.

But if I execute now 'pkg upgrade' pkg does not upgrade packages which
have a higher version from the gitlab repository, but stick to the
poudriere repository.

I also tried to do a 'pkg update -f; pkg upgrade' but it does not help.

Is there something wrong with my configuration or is this a bug in pkg?


If I understand you correctly, you have package A-1.0 installed from 
repo "poudriere" and now you have package A-1.1 in repo "gitlab" and you 
want to upgrade this package "A" to version 1.1.

Is it right?

I think that crossrepo upgrade is not automatic if package is in both 
repositories but it work if package is missing from previous repo and it 
it intentional.
I have more repositories too (different PHP version, different python 
versions but common utilities etc.) so packages are not unintentionally 
upgraded / downgraded.


But if you want to upgrade package A from different repo, you can choose 
the repo:


-r reponame, --repository reponame
  Install packages from only the named repository, irrespective
  of the configured ``active'' status from repo.conf.

You can try
   pkg install -r gitlab -f A

or
   pkg upgrade -r gitlab -f A

where A is you package(s) name.

Miroslav Lachman

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

Pkg does not upgrade if more than one repository is defined

2017-07-28 Thread Matthias Fechner 

Dear all,

I have a problem with pkg and I'm not sure if it is a bug in pkg or a 
configuration issue.
I work on new version on ports which are in a separate poudriere 
repository (to be able to easily test it).


I have now two configuration files in /usr/local/etc/pkg/repos, 
poudriere.conf:

poudriere: {
url: "https://pkg.fechner.net/packages/110amd64-default;,
mirror_type: "pkg+http",
signature_type: "pubkey",
pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
enabled: yes,
priority: 1
}

this is the standard repo which contains all stable packages.
Now I have a new version (in this case for gitlab) at gitlab.conf:
gitlab: {
url: "https://pkg.fechner.net/packages/110amd64-gitlab;,
mirror_type: "pkg+http",
signature_type: "pubkey",
pubkey: "/usr/local/etc/ssl/certs/pkg.cert",
enabled: yes,
priority: 10
}

The priority is higher and some package there have a higher version 
number.


But if I execute now 'pkg upgrade' pkg does not upgrade packages which 
have a higher version from the gitlab repository, but stick to the 
poudriere repository.


I also tried to do a 'pkg update -f; pkg upgrade' but it does not help.

Is there something wrong with my configuration or is this a bug in pkg?


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

Re: Trying to get poudriere to start

2017-07-28 Thread Willem Jan Withagen 
On 28-7-2017 09:21, Shane Ambler wrote:
> On 27/07/2017 09:30, Willem Jan Withagen wrote:
>> On 27-7-2017 01:43, mokhi wrote:
>>> Aha,
>>> Okay...
>>> Good if it works :)
>>>
>>
>> It is a gross hack, but it gets me going for the time being.
>>
>> Also needed to fight with ninja.
>> Turns out that somebody changed my old port to include noninja, without
>> telling me... :(
> 
> That change would be related to r444324
> http://leader/viewvc/viewvc.cgi/FreeBSD-ports?view=revision=444324
> 
> Your port uses cmake, which previously would use make to build your
> port. The options to use ninja instead of make was an option but is now
> the default as speed improvements on larger projects were found. The
> addition of USES= cmake:noninja means your port failed using ninja
> during the tests of that change, which means it was left to build the
> same way it was before the change.

ninja complains about problems with $'s.
And since this project also needs to work with cmake/gmake on Linux, I'm
not even going to try to meddle with this.
Assuming that the current combo is going to stay workable?

--WjW

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

Re: Trying to get poudriere to start

2017-07-28 Thread Shane Ambler 

On 28/07/2017 16:51, Shane Ambler wrote:

On 27/07/2017 09:30, Willem Jan Withagen wrote:

On 27-7-2017 01:43, mokhi wrote:

Aha,
Okay...
Good if it works :)



It is a gross hack, but it gets me going for the time being.

Also needed to fight with ninja.
Turns out that somebody changed my old port to include noninja, without
telling me... :(


That change would be related to r444324
http://leader/viewvc/viewvc.cgi/FreeBSD-ports?view=revision=444324


Sorry, ignore that link, it should be
https://svnweb.freebsd.org/ports/head/Mk/Uses/cmake.mk?revision=444324=markup


Your port uses cmake, which previously would use make to build your
port. The options to use ninja instead of make was an option but is now
the default as speed improvements on larger projects were found. The
addition of USES= cmake:noninja means your port failed using ninja
during the tests of that change, which means it was left to build the
same way it was before the change.





--
FreeBSD - the place to B...Software Developing

Shane Ambler

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

Re: Trying to get poudriere to start

2017-07-28 Thread Shane Ambler 

On 27/07/2017 09:30, Willem Jan Withagen wrote:

On 27-7-2017 01:43, mokhi wrote:

Aha,
Okay...
Good if it works :)



It is a gross hack, but it gets me going for the time being.

Also needed to fight with ninja.
Turns out that somebody changed my old port to include noninja, without
telling me... :(


That change would be related to r444324
http://leader/viewvc/viewvc.cgi/FreeBSD-ports?view=revision=444324

Your port uses cmake, which previously would use make to build your
port. The options to use ninja instead of make was an option but is now
the default as speed improvements on larger projects were found. The
addition of USES= cmake:noninja means your port failed using ninja
during the tests of that change, which means it was left to build the
same way it was before the change.


--
FreeBSD - the place to B...Software Developing

Shane Ambler

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