Re: what is the purpose of the quarterly ports branches?

2016-12-06 Thread Jason Unovitch
On Mon, Dec 05, 2016 at 10:48:20PM +, Ben Woods wrote:
> On Tue., 6 Dec. 2016 at 4:44 am, Julian Elischer  wrote:
> 
> > they are effectively useless because the results are not archived, and
> > the quarterly pkg branch actually changes day by day, so making two
> > machines from the same quarterly branch can give you different
> > machines (making it useless for paying work)
> >
> > not to mention that if you use the quarterly pkg branch you run he
> > risk of it completely changing if you happen to be unlucky enough to
> > be doing it across a quarterly boundary. then you end up with a
> > completely messed up system. (from experience).
> >

If you are handling the burden of support for a customer then perhaps
Poudriere and building internally is the best option. Then if you want
to stay on an older quarterly because none of what you deploy to
customers is impacted by security issues you can roll them at your own
pace.

> > But the big question still remains..
> >
> > What do you think you are solving and why are they changing? shouldn't
> > a snapshot be stable?


Think releng compared to stable in the src repo rather than
release/stable.  They change in the same fashion to get SA (in the form
of VuXML) and errata worthy fixes.
___
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: Security Update roundcube

2016-12-04 Thread Jason Unovitch
On Sat, Dec 03, 2016 at 01:01:23PM +0100, Matthias Fechner wrote:
> Dear all,
> 
> 
> could a commiter please priorities:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214925
> 
> 
> It is a security related fix:
> 
> https://vuxml.freebsd.org/freebsd/125f5958-b611-11e6-a9a5-b499baebfeaf.html
> 
> 
> Thanks a lot!
> 
> 
> Gruß
> Matthias

Matthias,
The update has been committed and merged to quarterly.

Thanks!
___
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: Commit request mail/py-milter

2016-12-01 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Thu, Dec 01, 2016 at 07:38:59AM +0100, Gerhard Schmidt wrote:
> Hi
> 
> could a committer please spare a moment an look at
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214317
> 
> it's straight forward patch to fix a minor bug in py-milter with IPv6.
> 
> Regards
>Estartu
> 
Hello, the patch has been committed with minor changes for portlint.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJYQLjxXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NURGNTQ1OTkzQkJFMzc3OTNDQUNERUU2
RkQ0OUMzMDE2MUNBQTZFAAoJEG/UnDAWHKpuGJIIALMSnKuIUn5FeAbl7jPtLA/1
kD8fS8RiumAWbM6kzuwyRPsuPybLeIofgHObkvTEp3qK9VzsGWjIUN4WS39M4Cqt
wdtuBkSD4eudOB5jWmBmgvDgEHqaiRysl0HyekZLYmh2Hs4cgIffe2769aOCa1iB
9EtTEfdodTfXc/TRLgYKdZkfmGPXgITTr03RheAY/Fvwy80OQ8lHmSnKJ6SdY2pW
YOB5T06VZgcqC/YATaPdEURG3BdSiFsEQqMNDVKQfsXUo+dF/QX1pFXtpBZ1hB7S
9jdWXn9bmTqNxw5H9f+vJHAca3xf1qLPgNuqYVMWTVpb1fQyz7ZtHJHRtTLhPa0=
=GvnZ
-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"


Re: Request for Committer for chkrootkit patch

2016-11-28 Thread Jason Unovitch
On Mon, Nov 28, 2016 at 07:27:13AM -0800, Lacey Powers wrote:
> Hello,
> 
> If someone had the time, I'd be grateful if they could take a look at
> this and commit it if there are no problems with it:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214416
> 
> Best,
> 
> Lacey
> 
Committed.  Thank you Lacey!
___
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: Multiple security vulnerabilities in net/samba36

2016-08-05 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Fri, Aug 05, 2016 at 03:23:49PM -0700, iceflatline wrote:
> Apologies in advance if this message should be directed to another
> mailing list. pkg audit has been complaining about multiple
> vulnerabilities in samba36 (samba36-3.6.25_3) for quite awhile.
> 
> See: 
> https://vuxml.FreeBSD.org/freebsd/a636fc26-00d9-11e6-b704-000c292e4fd8.html
> 
> Anyone have a sense on when the port will be updated to address these issues?
> 
> Andy
> ___

Hi, Samba 3.6 has been EOL'd by upstream as of 2015-03-04 per
https://wiki.samba.org/index.php/Samba_Release_Planning. It was removed
from ports but re-added in https://svnweb.FreeBSD.org/changeset/ports/415328
as unfortunately there were still some ports that required it as a dependency.
If you are not impacted by needing it as a dependency I would advise moving
to one of the supported versions.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJXpTsmXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NURGNTQ1OTkzQkJFMzc3OTNDQUNERUU2
RkQ0OUMzMDE2MUNBQTZFAAoJEG/UnDAWHKpuGi4H/RzHLwnawHO/KERWWckbKJf+
Fb5LY+b8SEZ7yC1DpdY91gB9y80siLU/9enhJw8B4IwEex/wUa4Y0RxGirgXou0i
5mlAQ7c6bpI+iKId3V98tAw4sEV/6yvMIQYLlCfW3DomOUEkd5KEvTH3XtfkEsnW
vP2kIqYqQaE3neWI1rkjjj8BfQ9h1kAA8gZc1Lavx/u/43YXEgYbzp2b+nliqcTC
HgnJGmJkVBm5QTS5MuASwhauWxlLiZqWQKQQG42IqCvajTHU0Q6VqOApWggAX9VX
JbZ1+7geecQ6flFDTKgmErSfZYm4dwlD+jS48oFaeuiOLubwqNbhII5U0TwQ4zY=
=d4kF
-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"


Re: Unexpected output from "pkg updating -d 20160626"

2016-06-28 Thread Jason Unovitch
On Tue, Jun 28, 2016 at 04:44:33AM -0700, David Wolfskill wrote:
> As part of my daily update of FreeBSD on my laptop, on the first reboot
> after installing the freshly-built kernel & world, I use portmaster to
> update any installed ports that have been updated since I last updated.
> 
> This morning, for the first time in ... months, I think, the "pkg
> updating -d ..." command I run to start the process actually generated
> some output -- quite a bit of it.
> 
> But I'm at a loss to understand why it did: only one of the ports it
> mentioned is installed, and that one didn't get updated by "portmaster
> -ad"; the others aren't installed at all.
> 
> My ports working copy is ports/head, at r417708.
> 
> I'm running:
> FreeBSD g1-252.catwhisker.org 10.3-STABLE FreeBSD 10.3-STABLE #406  
> r302244M/302246:1003505: Tue Jun 28 04:11:52 PDT 2016 
> r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY  amd64
> 
> now; when I ran "pkg updating -d ...", I was running:
> FreeBSD g1-252.catwhisker.org 10.3-STABLE FreeBSD 10.3-STABLE #405  
> r302220M/30:1003504: Mon Jun 27 04:03:47 PDT 2016 
> r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY  amd64
> 
> and pkg reports:
> g1-252(10.3-S)[2] pkg --version
> 1.8.6
> 
> The "pkg updating" command I issued was: pkg updating -d 20160626

Hello David,
I did replicate this and it seemed related to a handful of recent
UDPATING entries that were made without a trailing colon after the date.
I normalized all the entries for consistency and am seeing `pkg updating
-d 20160626` return the expected output for me. Please see if that
resolved the issue for you as well.

Jason
___
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: samba43-4.3.9

2016-06-21 Thread Jason Unovitch
On Tue, Jun 21, 2016 at 8:54 PM, Hans-Ulrich Meyer
 wrote:
> Hello Timur,
>
> after installation of samba43 by pkg I got the following start error:
>
> Starting smbd.
> Shared object "libpam.so.6" not found, required by "libauth-samba4.so"
> /usr/local/etc/rc.d/samba_server: WARNING: failed to start smbd
>
> This error is reproduceable and i can't find the missing library.
> Can you please give me a hint to fix the problem?
>
> Regards,
>
> Hans-Ulrich Meyer
> Admin edesign-net
> ___
Hello,
The shlib version for base libpam was bumped in r301602 [1]. You'll
need to update your base system to a revision later than that.

[1] https://svnweb.freebsd.org/changeset/base/301602
___
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: what for is the "gogs" UID/GID

2016-05-03 Thread Jason Unovitch
On Tue, May 3, 2016 at 8:28 PM, Vick Khera  wrote:
> I'm checking out some git web interfaces, and I stumbled upon the
> registered UID/GID for "gogs" which is one of the tools I am investigating.
>
> I'm curious why there's an entry for it but no corresponding port. In fact,
> the only reference in all of the ports tree is just those two entries.
> ___

The commit message that added it was part of
https://bugs.FreeBSD.org/207206 and based on that it was added for
https://bugs.FreeBSD.org/205283 which has yet to be committed to the
ports tree.
___
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: PR ready for commit

2016-02-14 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Sun, Feb 14, 2016 at 04:11:07PM -0500, Randy Westlund wrote:
> This is just waiting on a committer:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205052
> 
> Randy

Done! Thanks for the quick response on the requested QA and for taking
over the port from ports@!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJWwQGyXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NURGNTQ1OTkzQkJFMzc3OTNDQUNERUU2
RkQ0OUMzMDE2MUNBQTZFAAoJEG/UnDAWHKpubDkH/iffQ7XFDaXO4J8rZhFiFsJP
t2kAphW/dX+rJ95HvOowfOnltvqi3gz2C62A7ao7KmmLVGqKcYGXgOqcJz2Izp+9
6G3gKgEN/K2JeiwqatJebtRkPhJ6ELz2Q6hI9787G8IFguwHB+DqCz6pC+5yJRuI
AMUC9RBzfZ6C0ckSoqcbLzyY+BfvObwpiXbr752ul8zN4koF4IJg8JG+QsPaR7qO
80uaYjV4dd2wB5BkeX+A9U1FUsLQWhgDr8FqoubqEmsA1krs/r8LUEo4f61MQIcG
+hbWe9v1ehzgEIpPfzcJwSkjnbYp0yA/UR3jjuvPgkQLDbBalBd9ZGT68pvz+XQ=
=aCdj
-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"


Re: Recent update of security/nettle broke security/keepassx2

2016-02-14 Thread Jason Unovitch
On Sun, Feb 14, 2016 at 11:48 AM, Lars Engels  wrote:
> On Fri, Feb 12, 2016 at 11:59:26AM -0500, Richard Kuhns wrote:
>> Apologies; it was apparently libgcrypt, not nettle.
>>
>> On 02/12/16 09:29, Richard Kuhns wrote:
>> > Hi all,
>> >
>> > After updating security/nettle, when I try to start keepassx2 I get:
>> >
>> > : rjk$~; keepassx
>> > O j: Assertion `ctx->unused < 64' failed
>> > (salsa20.c:400:salsa20_do_encrypt_stream)
>> > Abort trap
>> >
>
> I can confirm this. :-/

See https://bugs.FreeBSD.org/207042 and by extension
https://bugs.FreeBSD.org/207107.
___
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: Using pkg to fetch packages for different ABI

2016-02-02 Thread Jason Unovitch
On Tue, Feb 2, 2016 at 8:21 PM, Daniel Eischen  wrote:
> I want to use pkg to maintain a set of packages for nanobsd
> systems that are a different OS version and ABI than the
> host system.  Basically, I want to be able to do:
>
>   # pkg fetch -d -r FreeBSD_10x_32 -o ./ 
>
> and have it fetch all the required packages for .
>
> The host system is 10.2-RELEASE-p9 amd64, the target system
> in this case is similar, but just x86, not amd64.  pkg is
> version 1.6.2.
>
> Trying to initially update the repo catalog gives this:
>
>   # cat /usr/local/etc/pkg/repos/FreeBSD_10x_32.conf
>   FreeBSD_10x_32: {
> ABI: "FreeBSD:x86:32"
> url: "pkg+http://pkg.FreeBSD.org/freebsd:10:x86:32/latest;,
> mirror_type: "srv",
> signature_type: "fingerprints",
> fingerprints: "/usr/share/keys/pkg",
> enabled: yes
>   }
>
>   # pkg update -r FreeBSD_10x_32
>   Updating FreeBSD_10x_32 repository catalogue...
>   Fetching meta.txz: 100%944 B   0.9kB/s00:01
>   Fetching packagesite.txz: 100%5 MiB   2.8MB/s00:02
>   Processing entries:   0%
>   pkg: wrong architecture: freebsd:10:x86:32 instead of FreeBSD:10:amd64
>   pkg: repository FreeBSD_10x_32 contains packages with wrong ABI:
> freebsd:10:x86:32
>   Processing entries: 100%
>   Unable to update repository FreeBSD_10x_32
>
> Why does 'pkg' care what the ABI is unless we try to actually
> install the packages?
>
> --
> DE

Set it via an environmental variable:
setenv ABI freebsd:10:x86:32

ABI can be overridden with environmental variables or via `-o
ABI=freebsd:10:x86:32'.  I'm actually using environmental variables on
a CentOS box with a locally compiled pkg to do a pkg fetch and pkg
repo to store a couple packages for internal use.
___
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: devel/lpc21isp needs an update

2015-12-22 Thread Jason Unovitch
On Tue, Dec 22, 2015 at 3:04 PM, Poul-Henning Kamp  wrote:
> There's a new version 1.97 which is much better.

Better is good! Updated to 1.97 in r404274.
___
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: I fixed devel/tkmerge master site

2015-12-16 Thread Jason Unovitch
On Wed, Dec 16, 2015 at 12:08 PM, Bob Willcox  wrote:
> Somehow, a symlink had gotten lost on my site that caused tkmerge to be
> unfetchable. I have since fixed this, so could some kind soul remove the
> BROKEN attribute from its Makefile?
>
> Thanks,
> Bob
>
> --
> Bob Willcox| A bird in hand is safer than one overhead.
> b...@immure.com |
> Austin, TX |

Bob,
It's been fixed. Thanks for looking into it!
___
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: Creating new port for gogs, put poudriere fail to clone github repo while build is running

2015-12-12 Thread Jason Unovitch
On Sat, Dec 12, 2015 at 9:14 AM, Matthias Fechner  wrote:
> Dear all,
>
> I started a long time ago a new port for gogs and had now time to
> continue on the port.
> The current version can be found here:
> https://github.com/idefix6/gogs-freebsdport
>
> But I face the problem that during the build process git cannot make a
> clone.
> For logfile please see here:
>> http://pkg.fechner.net/data/102amd64-default/2015-12-12_14h52m18s/logs/errors/gogs-0.7.19.log
>
> I test the build using poudrier with the command:
> poudriere testport -j 102amd64 -s -i -o devel/gogs
>
> and then type in the interactive console the command:
>> git clone https://github.com/codegangsta/cli 
>> /wrkdirs/usr/ports/devel/gogs/work/src/github.com/codegangsta/cli
>
> Then clone is fine.
>
> Maybe someone would be so nice and help me a little bit how to solve the
> problem?

Build requisites must be retrieved during the fetch phase as there is
no network access during the build phase.  Else a package could end up
changing or having security flaws slipped in based solely on when it
was built rather than what distinfo was listed as being the valid
source of the package.
___
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: Fwd: Memory leak or misconfiguration: Repeated allocation of very large block

2015-12-08 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On December 5, 2015 6:43:55 AM EST, Sebastian Wolfgarten 
 wrote:
>Any views on this?
>
>> Anfang der weitergeleiteten Nachricht:
>>
>> Von: Sebastian Wolfgarten 
>> Datum: 25. Oktober 2015 um 11:55:42 MEZ
>> An: po...@freebsd.org
>> Betreff: Wtr: Memory leak or misconfiguration: Repeated allocation of
>very large block
>>
>> To whom it may concern,
>>
>> in view of the discussion below may I suggest we remove the --with-gc
>option from the Dovecot default options?
>>
>> Thanks.
>>
>> Kind regards
>> Sebastian
>>
>>> Anfang der weitergeleiteten Nachricht:
>>>
>>> Von: Sebastian Wolfgarten >
>>> Datum: 25. Oktober 2015 um 11:54:15 MEZ
>>> An: Timo Sirainen >
>>> Kopie: dove...@dovecot.org 
>>> Betreff: Aw: Memory leak or misconfiguration: Repeated allocation of
>very large block
>>>
>>> Hi Timo,
>>>
>>> alright, thanks I will recompile without gc - this is a standard
>build option on FreeBSD but I will get the port maintainer to maybe
>change this.
>>>
>>> Best regards
>>> Sebastian
>>>
 Am 24.10.2015 um 23:19 schrieb Timo Sirainen >:

 On 24 Oct 2015, at 14:59, Sebastian Wolfgarten
>> wrote:
>
> Dear all,
>
> I am using Dovecot 2.2.19 and I keep on getting the following
>warnings in my mail.log file on FreeBSD 10:
>
> Oct 24 10:45:28 server1 dovecot: imap: Error: GC Warning: Repeated
>allocation of very large block (appr. size 20480):
> Oct 24 10:45:28 server1 dovecot: imap: Error: May lead to memory
>leak and poor performance.
>
> I am wondering whether this is a configuration issue (i.e. a
>mistake in my current config) or whether I am hitting a bug. What’s the
>best way of figuring this one out? I tried increasing the verbosity of
>the logs but it did not really provide me with further information.

 I guess you have configured Dovecot --with-gc? I guess it's
>possible this is a bug, but it could just as well be a false alarm. In
>general I don't recommend/support --with-gc option (and I should
>probably just remove it altogether). The easiest and the most usable
>way of finding memory leaks is to run with valgrind (which must be done
>without-gc):

 service imap {
 executable = /usr/bin/valgrind -q --show-reachable=yes
>--leak-check=full /usr/libexec/dovecot/imap
 }

 I'm not aware of any memory leaks right now.

>>>
>>

Have you filed a PR for the issue and/or reported this to the mail/dovecot2 
maintainer?
-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxKhxKYXNvbiBVbm92aXRjaCA8amFzb24udW5vdml0Y2hAZ21haWwu
Y29tPgUCVmcNXAAKCRBv1JwwFhyqbuCBB/0Yqw6Bhecsegznzx21WxZD+aJzd9k5
8OPUT3VbTtkK33BKgozZYFzEW0+9XSdU6vK+AreuBcWAtMb34F5W6H3uqfezv0by
HvdftdIbUao1TYUhGlDL21k1PaNNPpfoDkqpTTV0eEAuM0p3ZZP3YWwWSXGzmvgu
KGZKdx3SF/oy6Ut2DHYZIj5JQVBd20wZrFtKt6/orudn12eFEfWcB9fTqQ1ESJBf
Q1Ue2zsPUQn7AcbP/UW99CdgV+BTM5rI7yZu8ohnJWj0rimSmWMWY5cqbzbBkTem
hBRdJ+KMD0SpdOHw7zGMHKN+MHLWCBl+4ZmIUxOEPbolLoljAdvbTt4i
=FN+e
-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"

Re: ${PYTHON_CMD}/${PERL} in _CONFIGURE_WITH not working

2015-11-20 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Sat, Nov 21, 2015 at 02:05:14PM +1100, Kubilay Kocak wrote:
> On 20/11/2015 4:02 PM, Jan Beich wrote:
> > Jason Unovitch <junovi...@freebsd.org> writes:

> Can you create an issue to fix this + MFH please?
> 
> ./koobs

Done!  https://bugs.FreeBSD.org/204708 has the link to the mailing list
archive, Jan's incomplete patch, and is set as a blocker for bug 204220
where I ran into the issue.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJWT+R3XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NURGNTQ1OTkzQkJFMzc3OTNDQUNERUU2
RkQ0OUMzMDE2MUNBQTZFAAoJEG/UnDAWHKpuFzAIAIueINn/YtLi63Zxked15Jaq
ua2oOdIXyLaQx7oG3gk/MIHs7LkI23lUaTSSClX0HWfyd9lcjNph8s8Cpv0cBFYY
RKqJ0fKzOL8ViqQDajP4bLqwMbqGNAt1uZI9dxESRX8saBL9mdSsFka9LDGPn5MT
k2iqLygQ7WM7Hhv1XLriO0wBaS5PlBoZo/tns+j0Mc4DPynQbmDIy/KCdPas4dkV
hEiWe45hNal0Y/8+BbRj/GvMUGBEwJotjCVLlGrNopYXhQQ/j7vXWgcPNQWJgD/a
U3C6cHNORibmsXuCth1Wf65gWZJ/TR0RXh8Buz+SepvsZ2UgcAhyM+Sppaufm9U=
=iQ2g
-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"


Re: ${PYTHON_CMD}/${PERL} in _CONFIGURE_WITH not working

2015-11-20 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Fri, Nov 20, 2015 at 06:02:41AM +0100, Jan Beich wrote:
> Jason Unovitch <junovi...@freebsd.org> writes:
> > PERL_USES=  perl5
> > PERL_CONFIGURE_ENABLE=  perl
> > PERL_CONFIGURE_WITH=perl=${PERL} perl-bindings
> > PYTHON_USES=python:2
> > PYTHON_CONFIGURE_ENABLE=python
> > PYTHON_CONFIGURE_WITH=  python=${PYTHON_CMD}
> [...]
> > % make -VCONFIGURE_ARGS
> > "--enable-python --with-python= "
> > "--enable-perl --with-perl= --with-perl-bindings"
> 
> It appears bsd.option.mk expands _WITH and _ENABLE twice unlike _ON/_OFF:
> once in .for loop and once (lazily) when CONFIGURE_ARGS is referenced.
> Try using $${PERL} and $${PYTHON_CMD} or the following patch:

Yes, this $$ variant fixes CONFIGURE_ARGS and allows a successful build.

% make -VPERL_CONFIGURE_WITH
perl=${PERL} perl-bindings
% make -VPYTHON_CONFIGURE_WITH
python=${PYTHON_CMD}
% make -VCONFIGURE_ARGS
- --with-perl=/usr/local/bin/perl --with-perl-bindings 
- --with-python=/usr/local/bin/python2.7

> # XXX incomplete as there're more cases with premature expansion
> Index: Mk/bsd.options.mk
> ===
> --- Mk/bsd.options.mk (revision 401846)
> +++ Mk/bsd.options.mk (working copy)
> @@ -491,16 +491,8 @@ ${_u:tu}=
> ${${opt}_VARS:M${var}=*:C/[^=]*=//:C/^"
>  .endif
>  .  endfor
>  .endif
> -.if defined(${opt}_CONFIGURE_ENABLE)
> -.  for iopt in ${${opt}_CONFIGURE_ENABLE}
> -CONFIGURE_ARGS+= --enable-${iopt}
> -.  endfor
> -.endif
> -.if defined(${opt}_CONFIGURE_WITH)
> -.  for iopt in ${${opt}_CONFIGURE_WITH}
> -CONFIGURE_ARGS+= --with-${iopt}
> -.  endfor
> -.endif
> +CONFIGURE_ARGS+= ${${opt}_CONFIGURE_ENABLE:C/.+/--enable-&/}
> +CONFIGURE_ARGS+= ${${opt}_CONFIGURE_WITH:C/.+/--with-&/}
>  .for configure in CONFIGURE CMAKE QMAKE
>  .  if defined(${opt}_${configure}_ON)
>  ${configure}_ARGS+=  ${${opt}_${configure}_ON}
> @@ -539,16 +531,8 @@ ${_u:tu}=
> ${${opt}_VARS_OFF:M${var}=*:C/[^=]*=//:
>  .endif
>  .  endfor
>  .endif
> -.if defined(${opt}_CONFIGURE_ENABLE)
> -.  for iopt in ${${opt}_CONFIGURE_ENABLE}
> -CONFIGURE_ARGS+= --disable-${iopt:C/=.*//}
> -.  endfor
> -.endif
> -.if defined(${opt}_CONFIGURE_WITH)
> -.  for iopt in ${${opt}_CONFIGURE_WITH}
> -CONFIGURE_ARGS+= --without-${iopt:C/=.*//}
> -.  endfor
> -.endif
> +CONFIGURE_ARGS+= ${${opt}_CONFIGURE_ENABLE:C/=.*//:C/.+/--disable-&/}
> +CONFIGURE_ARGS+= ${${opt}_CONFIGURE_WITH:C/=.*//:C/.+/--without-&/}
>  .for configure in CONFIGURE CMAKE QMAKE
>  .  if defined(${opt}_${configure}_OFF)
>  ${configure}_ARGS+=  ${${opt}_${configure}_OFF}

This patch does indeed fix the issues.  I haven't checked for further
regressions past this however.

% make -VPERL_CONFIGURE_WITH
perl=/usr/local/bin/perl perl-bindings
% make -VPYTHON_CONFIGURE_WITH
python=/usr/local/bin/python2.7
% make -VCONFIGURE_ARGS
- --with-perl=/usr/local/bin/perl --with-perl-bindings
- --with-python=/usr/local/bin/python2.7 

Thanks for the assist, Jan!  Any recommendations on the best way ahead?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJWT97qXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NURGNTQ1OTkzQkJFMzc3OTNDQUNERUU2
RkQ0OUMzMDE2MUNBQTZFAAoJEG/UnDAWHKpuBYsH/0nnh4dBBUKa1nQv0+lzMVhd
C/2dFymXlMIyZcka3s0s1V7CIjsE5ZEipqYeZv7Cf6zxc2Vg56cJOjmkUGKZvqM1
0jJ7uEz/lF/YNtAiFq6u3KcHDvRiA/ciGcn9o9CMiSadZc+/+fgGE2V9ZflZr+yx
s6auJE78hjYDn00iKd5MyXJg+rSQ/JQiYUQH7bL9q4BOH9rLIqXf6Pi24m+Eck5s
hNSjr09rExDiciY6Gp4kDoqwWS9kTwP1lJkGupQvEreLmBd9Vjhb9m0iK9/0MSr2
rZSstm1/JfX8LxwJRBe5+7WlfnqYNhmFGY6l1Ejy4PRcm/Mecu46Z8deuRlI8z0=
=tG1V
-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"


${PYTHON_CMD}/${PERL} in _CONFIGURE_WITH not working

2015-11-19 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,
I seem to be missing something simple found while converting
net-mgmt/collectd5 over to option helpers.  I've been using the
following Makefile entries.

PERL_USES=  perl5
PERL_CONFIGURE_ENABLE=  perl
PERL_CONFIGURE_WITH=perl=${PERL} perl-bindings
PYTHON_USES=python:2
PYTHON_CONFIGURE_ENABLE=python
PYTHON_CONFIGURE_WITH=  python=${PYTHON_CMD}

Everything looks good for the _WITH variables.  The correct variable
expansion appears to be taking place:

% make -VPERL_CONFIGURE_WITH
 
perl=/usr/local/bin/perl perl-bindings
% make -VPYTHON_CONFIGURE_WITH  
 
python=/usr/local/bin/python2.7

However, for CONFIGURE_ARGS the ${PERL} and ${PYTHON_CMD} variables are
getting swallowed up.  The port will fail to compile because of this.

% make -VCONFIGURE_ARGS
"--enable-python --with-python= "
"--enable-perl --with-perl= --with-perl-bindings"

Any ideas or suggestions on where to look for this?  Thanks!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJWTo6CXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NURGNTQ1OTkzQkJFMzc3OTNDQUNERUU2
RkQ0OUMzMDE2MUNBQTZFAAoJEG/UnDAWHKpuUGkH/3Cl+zox7vdGnA382G+BjtdU
R7ChX/QM92Ml3LZsrmnJZO7rqGoK7V8hgd2LYxDJtlPF5f6lVpDFtFYfd0HSqnvR
aAxBkN0zX/qcS2J2f9sxtT9/H8DVQ0NIdVAYe3yypqXsPp3T25zO8i63nyy4v1UI
gdt5alEc+9CJAtyt7EQ41NDT6IUsQFoGF7k+0VPo7cppnnX1QxL4J2Vs1nZyGd2l
OXyL5Xclz5biAuYX8zVy7RbuTe5NEhm3twbo2/+TmcJyiNdhcXBTBcpPRWnEf9Ew
XncFKMJ0Og7RE6zRC9Cw6PbP4MB6zdRnQc7VKlx+fjsoy8rAXLSJFWcn+k4wasg=
=B+EW
-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"


Re: Port Vulnerabilities | php5-phar-5.4.45

2015-11-07 Thread Jason Unovitch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Sat, Nov 07, 2015 at 08:23:48PM +0100, JosC wrote:
> Dear port maintainer,
> 
> Can you check this port as it shows to have some vulnerabilities:
> 
> Checking for packages with security vulnerabilities:
> 
> Database fetched: Fri Nov 6 01:06:33 CET 2015
> php5-phar-5.4.45
> 
> Thanks,
> Jos Chrispijn

Jos,
See http://www.php.net/eol.php

PHP 5.4 is no longer supported by the PHP project as of 3 September
2015. Please update to a supported PHP release, such as the ports
default version--PHP 5.6, using the steps in /usr/ports/UPDATING entry
20150220.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJWPn7XXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NURGNTQ1OTkzQkJFMzc3OTNDQUNERUU2
RkQ0OUMzMDE2MUNBQTZFAAoJEG/UnDAWHKpuU/YH/2z3PLeYvd6QJrxmbnBPyFve
k4p5+3mskTN6S2rMxXuUUMHUxWVCoIuw816DeBuCw4HCZEIfhTuEOkLzLz5fCJxW
cxcUqTsKafGZVcbbnONH/g0zLIVXUJeuT6pwBlH0qJcc33XE5q97OBERUmw2YNRZ
0M1hWcr8o9bgSRjfwrfRBxCWI6JdU6dI8DwFT/V+N3Nmbk74XBM91h6rguApklCc
DK008Gc4cyCc8o1DyU1qYqqzIXTFjW3+2K+pUUWLwZPoGZKOVUpt8Hj6Px9+GdQd
CufUPHJKHs0xa6EOYQ9MHM2xrfEkUjhtwtH+7bDxPCGoEsZF932pGvob4vyqxGc=
=NGar
-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"


Re: php5-phar-5.4.45

2015-10-27 Thread Jason Unovitch
On Oct 27, 2015 7:19 AM, "Kurt Jaeger"  wrote:
>
> Hi!
>
> > Checking for packages with security vulnerabilities:
> > Database fetched: Mon Oct 26 00:09:27 CET 2015
> > php5-phar-5.4.45
> >
> > Can you tell when we can expect the update of this port?
>
> Is there an application that does not cope with newer versions of PHP ?
>

As mentioned above, PHP 5.4 passed end of life and there was no upstream
release to go along with the recent 5.5 and 5.6 updates. If there are any
applications that do not cope with newer PHP versions, your assistance to
identify it and a PR to document it would be helpful!

Thanks!
___
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: HELP: Bacula compile with older version installed

2015-10-09 Thread Jason Unovitch
For sysutils/openipmi in PR 396109 the fix was this.  However that was
before USES= localbase hit the tree which according to the commit
message should prevent ports from picking up their own headers from
old versions in LOCALBASE.

CPPFLAGS+=  -I../include -I${LOCALBASE}/include

On Fri, Oct 9, 2015 at 7:59 PM, Larry Rosenman <l...@lerctr.org> wrote:
> On 2015-10-09 18:55, Per olof Ljungmark wrote:
>>
>> On 2015-10-10 01:19, Larry Rosenman wrote:
>>>
>>> Related to BZ# 193641, the new 7.2.0 bacula port doesn't link if the
>>> 7.0.5 packages are installed.
>>>
>>> we get:
>>> ==>Entering directory
>>>
>>> /var/ports/basejail/usr/ports/sysutils/bacula-server/work/bacula-7.2.0/src/dird
>>>
>>> --- bacula-dir ---
>>> Linking bacula-dir ...
>>>
>>> /var/ports/basejail/usr/ports/sysutils/bacula-server/work/bacula-7.2.0/libtool
>>> --silent --tag=CXX --mode=link /usr/bin/c++ -L../lib -L../cats
>>> -L../findlib  -L/usr/local/lib  -L/usr/local/lib -fstack-protector -o
>>> bacula-dir dird.o admin.o authenticate.o autoprune.o backup.o bsr.o
>>> catreq.o dir_plugins.o dird_conf.o expand.o fd_cmds.o getmsg.o
>>> inc_conf.o job.o jobq.o mac.o mac_sql.o mountreq.o msgchan.o next_vol.o
>>> newvol.o recycle.o restore.o run_conf.o scheduler.o ua_acl.o ua_cmds.o
>>> ua_dotcmds.o ua_query.o ua_input.o ua_label.o ua_output.o ua_prune.o
>>> ua_purge.o ua_restore.o ua_run.o ua_select.o ua_server.o snapshot.o
>>> ua_status.o ua_tree.o ua_update.o vbackup.o verify.o  -lbacfind -lbacsql
>>> -lbaccats -lbaccfg -lbac -lm   -lpthread  -lintl  -lwrap
>>> /usr/local/lib/libintl.so -Wl,-rpath -Wl,/usr/local/lib -lssl -lcrypto
>>> dird.o: In function `main':
>>
>>
>> pkg delete the old version first?
>> ___
>> 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"
>
> That works, but we (dvl@ and I) would like to get it work without having to
> do that.
>
> Jason Unovitch suggested USES= localbase, but that didn't help either.
>
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
> US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
> ___
> 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"
___
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: HELP: Bacula compile with older version installed

2015-10-09 Thread Jason Unovitch
On Fri, Oct 9, 2015 at 8:11 PM, Larry Rosenman <l...@lerctr.org> wrote:
> On 2015-10-09 19:09, Jason Unovitch wrote:
>>
>> For sysutils/openipmi in PR 396109 the fix was this.  However that was
>> before USES= localbase hit the tree which according to the commit
>> message should prevent ports from picking up their own headers from
>> old versions in LOCALBASE.
>>
>> CPPFLAGS+=  -I../include -I${LOCALBASE}/include
>
>
> This is a LINK issue, NOT a compile issue.
>

Apologies for the misdirection.  It's been one of those long weeks
where no commits before coffee applies.

>
>>
>> On Fri, Oct 9, 2015 at 7:59 PM, Larry Rosenman <l...@lerctr.org> wrote:
>>>
>>> On 2015-10-09 18:55, Per olof Ljungmark wrote:
>>>>
>>>>
>>>> On 2015-10-10 01:19, Larry Rosenman wrote:
>>>>>
>>>>>
>>>>> Related to BZ# 193641, the new 7.2.0 bacula port doesn't link if the
>>>>> 7.0.5 packages are installed.
>>>>>
>>>>> we get:
>>>>> ==>Entering directory
>>>>>
>>>>>
>>>>> /var/ports/basejail/usr/ports/sysutils/bacula-server/work/bacula-7.2.0/src/dird
>>>>>
>>>>> --- bacula-dir ---
>>>>> Linking bacula-dir ...
>>>>>
>>>>>
>>>>> /var/ports/basejail/usr/ports/sysutils/bacula-server/work/bacula-7.2.0/libtool
>>>>> --silent --tag=CXX --mode=link /usr/bin/c++ -L../lib -L../cats
>>>>> -L../findlib  -L/usr/local/lib  -L/usr/local/lib -fstack-protector -o
>>>>> bacula-dir dird.o admin.o authenticate.o autoprune.o backup.o bsr.o
>>>>> catreq.o dir_plugins.o dird_conf.o expand.o fd_cmds.o getmsg.o
>>>>> inc_conf.o job.o jobq.o mac.o mac_sql.o mountreq.o msgchan.o next_vol.o
>>>>> newvol.o recycle.o restore.o run_conf.o scheduler.o ua_acl.o ua_cmds.o
>>>>> ua_dotcmds.o ua_query.o ua_input.o ua_label.o ua_output.o ua_prune.o
>>>>> ua_purge.o ua_restore.o ua_run.o ua_select.o ua_server.o snapshot.o
>>>>> ua_status.o ua_tree.o ua_update.o vbackup.o verify.o  -lbacfind
>>>>> -lbacsql
>>>>> -lbaccats -lbaccfg -lbac -lm   -lpthread  -lintl  -lwrap
>>>>> /usr/local/lib/libintl.so -Wl,-rpath -Wl,/usr/local/lib -lssl -lcrypto
>>>>> dird.o: In function `main':
>>>>
>>>>
>>>>
>>>> pkg delete the old version first?
>>>> ___
>>>> 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"
>>>
>>>
>>> That works, but we (dvl@ and I) would like to get it work without having
>>> to
>>> do that.
>>>
>>> Jason Unovitch suggested USES= localbase, but that didn't help either.
>>>
>>>
>>> --
>>> Larry Rosenman http://www.lerctr.org/~ler
>>> Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
>>> US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
>>> ___
>>> 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"
>
>
> --
> Larry Rosenman http://www.lerctr.org/~ler
> Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
> US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
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: Working of "pkg audit "

2015-10-07 Thread Jason Unovitch
On Wed, Oct 07, 2015 at 04:02:25PM -1000, p...@pair.com wrote:
> (Sent to -questions@ on Oct 3 but hadn't got any reply, so sending
> to @ports now. Also, situation below is before www/firefox was
> updated to 41.0.)
> 
> I want to know if running "pkg audit" makes any sense for a port
> installed that has not been updated officially yet. Also, is it
> possible to supplement the vuxml catalog for such ports installed?
> 
> Firefox 39 or 40 had been installed from ports. I got tired of
> seeing package being vulnerable on every ports tree update process
> that rebuilds "security/vuxml". As the "www/firefox" port has not
> been updated yet, so I fetched source of firefox 41.0.1; updated
> distinfo; installed (after rebuilding databases/sqlite3 with DBSTAT
> option & moving out "files/patch-bug702179" out of "files").
> 
> Now I see vulnerability warnings going back to 2004, which are
> just useless & rather amusing. At least the installed firefox is not
> vulnerable any more (yet).
> 
> Apparently per pkg-version
> 
>   # pkg version -t 41.0.1 41.0,1
>   <

The PORTEPOCH here (the ,1) will always make the second version newer than
the first.  If you do any local updates then keep the PORTEPOCH and it
would work as intended.  If you do a local update, don't forget the most
import step... the patch to Bugzilla of course.
___
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: New pkg audit / vuln.xml failures (php55, unzoo)

2015-05-23 Thread Jason Unovitch
On Sat, May 23, 2015 at 11:30 AM, Roger Marquis marq...@roble.com wrote:
 If you find a vulnerability such as a new CVE or mailing list
 announcement please send it to the port maintainer and
 ports-sect...@freebsd.org as quickly as possible.  They are whoefully
 understaffed and need our help.  Though freebsd.org indicates that
 security alerts should be sent to sect...@freebsd.org this is
 incorrect.  If the vulnerability is in a port or package send an alert to
 ports-secteam@ and NOT secteam@ as the secteam will generally not reply
 to your email or forward the alerts to ports-secteam.

 Roger


I've attempted to knock out a couple of these over the past 2 days.
There's certainly a non-trivial amount of PRs stuck in Bugzilla that
mention security or CVE that need some care and attention.  Here's a
few that are now ready for the taking.

vuxml patch ready:
emulators/virtualbox-ose -- https://bugs.freebsd.org/200311
databases/cassandra -- https://bugs.freebsd.org/199091
databases/cassandra2 -- https://bugs.freebsd.org/200414 (refers to
vuxml patch in PR 199091)
sysutils/py-salt -- https://bugs.freebsd.org/200172

vuxml previously done and update patch ready:
net/chrony -- https://bugs.freebsd.org/199508

both vuxml and update patch ready:
mail/davmail -- https://bugs.freebsd.org/198297

Jason
___
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