Re: Committer needed: x11-wm/ctwm, PR 251520

[Matthew D. Fuller]

On Sun, Dec 20, 2020 at 10:18:23AM +0100 I heard the voice of
Kurt Jaeger, and lo! it spake thus:
> > 
> > Can somebody land the patch in the approved attachment to
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251520
> > ?
> 
> Done.

Thanks!


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
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: Committer needed: x11-wm/ctwm, PR 251520

[Kurt Jaeger]

Hi!

> ctwm's build-time detection of the manpage location is being defeated
> by the minimalist /usr/local available in poudriere builds, so it
> needs to be nudged in the right direction.
> 
> Can somebody land the patch in the approved attachment to
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251520
> ?

Done.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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: Committer needed for PR 249433

[Kurt Jaeger]

Hi!

> Can I get a committer to take a look at PR 249433?  I'd kind of
> like to get these cleanups in before the Q4 branch is split.

Done.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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: Committer needed: multimedia/emby-server Update to 4.4.2.0

[Kurt Jaeger]

Hi!

> Could a committer take a look at the following PR please?
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245333

Done, thanks!

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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: Committer needed: www/p5-Net-Curl build breakage

[Kurt Jaeger]

Hi!

> I've made a patch to update p5-Net-Curl to fix the failing build.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245322
> 
> If a committer could please take care of this, it would be much appreciated.

Done.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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: Committer needed multimedia/emby-server update to 4.1.1.0

[Kurt Jaeger]

Hi!

> Can a committer take a look at the following PR:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237801

Done.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
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: Committer needed: New port java/wildfly16

[Kurt Jaeger]

Hi!

> Could a committer be so kind to review and if it is OK to commit PR236464?
> 
> It's the new version of Wildfly application server, this version does not
> superseded former versions.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236464

Done.

-- 
p...@opsec.eu+49 171 3101372One year to go !
___
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: Committer needed

[Kurt Jaeger]

Hi!

> Can a committer take a look at the following PR 231852.

Can you all please, in the name of compassion, state the
subject of the PR, if you raise it on ports@ ?

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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: Committer needed: archivers/urbackup-server

[Kurt Jaeger]

Hi!

> Can someone please take a look at this PR? It's been sitting for about 3
> months.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227853

Done.

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
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: Committer needed: mail/roundcube-thunderbird_labels, mail/roundcube-contextmenu

[Kurt Jaeger]

Hi!

> Can someone please take a look at the patches?
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228020

Done. Thanks for the PR!

-- 
p...@freebsd.org +49 171 3101372  2 years to go !
___
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: Committer needed: net/kamailio

[Kurt Jaeger]

Hi!

> I???ve patched net/kamailio and raised a ticket:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227677 
> 

Sorry for the delay, I'll work it in.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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: Committer needed: update lang/J

[João Neves]

Thanks!

Re: release notes and changelogs. Will do. Unfortunately the J
documentation is all sorts of scattered and outdated and I haven't managed
to find any release or change notes.

For the next update I will try to actively ask upstream where those can be
found if they have them.

Cheers,

/Joao

--
João Neves

On 17 April 2018 at 18:54, Kurt Jaeger  wrote:

> Hi!
>
> > I have a pending patch to update lang/J to the latest version. The
> updated
> > version seems to also remove some problematic code that makes the package
> > for 10.3 fail to build currently.
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227395
>
> Committed. Please try to find links to release notes or changelogs
> for the next updates. Without those, it's difficult to understand
> what happened.
>
> --
> p...@opsec.eu+49 171 31013722 years to go !
>
___
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: Committer needed: update lang/J

[Kurt Jaeger]

Hi!

> I have a pending patch to update lang/J to the latest version. The updated
> version seems to also remove some problematic code that makes the package
> for 10.3 fail to build currently.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227395

Committed. Please try to find links to release notes or changelogs
for the next updates. Without those, it's difficult to understand
what happened.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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: Committer needed for new ports: archivers/urbackup-server and archivers/urbackup-client

[Kurt Jaeger]

Hi!

> > > archivers/urbackup-server: The server component from urbackup.org
> > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
> > > (pending since 03/23)

Done (version 2.2.10)

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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: Committer needed for new ports: archivers/urbackup-server and archivers/urbackup-client

[Kirk Coombs]

> > archivers/urbackup-server: The server component from urbackup.org
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
> > (pending since 03/23)
>
> portlint -AC says that it needs files/urbackup_server.in --
> can you provide that startup-script ?
>

Sorry, I forgot to 'svn add' the script prior to diff'ing. Fixed.

Thanks!

Kirk

On Sun, Apr 15, 2018 at 9:59 AM, Kurt Jaeger  wrote:

> Hi!
>
> > archivers/urbackup-server: The server component from urbackup.org
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
> > (pending since 03/23)
>
> portlint -AC says that it needs files/urbackup_server.in --
> can you provide that startup-script ?
>
> > archivers/urbackup-client: The client component of the UrBackup backup
> > system
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227154
> > (pending since 04/01)
>
> testbuilds@work.
>
> --
> p...@opsec.eu+49 171 31013722 years to go !
>
___
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: Committer needed for new ports: archivers/urbackup-server and archivers/urbackup-client

[Kurt Jaeger]

Hi!

> archivers/urbackup-server: The server component from urbackup.org
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225148
> (pending since 03/23)

portlint -AC says that it needs files/urbackup_server.in --
can you provide that startup-script ?

> archivers/urbackup-client: The client component of the UrBackup backup
> system
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227154
> (pending since 04/01)

testbuilds@work.

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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: Committer needed

[Andreas Andersson]

Bumping this, does anyone have the time to look at them?

/Andreas

2018-04-03 9:54 GMT+02:00 Andreas Andersson :

> Can anyone take a look at the following:
>
> New port (written in c) net-mgmt/carbon-c-relay
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227120
>
> Updated port: net-mgmt/carbon-relay-ng
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227208
>
> Thank you!
>
___
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: Committer needed for new port (lang/J)

[João Neves]

Thanks for the quick turnaround!

--
João Neves

On 8 April 2018 at 11:41, Kurt Jaeger  wrote:

> Hi!
>
> > I submitted a port a while ago and I'd appreciate if someone with some
> > spare cycles could take a look at it and, if there are no objections,
> > commit it into the tree.
> >
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226186
>
> Done, thanks!
>
> --
> p...@opsec.eu+49 171 31013722 years to go !
>
___
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: Committer needed for new port (lang/J)

[Kurt Jaeger]

Hi!

> I submitted a port a while ago and I'd appreciate if someone with some
> spare cycles could take a look at it and, if there are no objections,
> commit it into the tree.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226186

Done, thanks!

-- 
p...@opsec.eu+49 171 31013722 years to go !
___
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: Committer needed for security/owasp-dependency-check

[Kurt Jaeger]

Hi!

> [New port] security/owasp-dependency-check: Detects publicly disclosed 
> vulnerabilities in project dependencies
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226206

@work. Please note that the shar file is somehow invalid, extracting
it dies in the middle. One needs to manually remove the .git related
files from the .shar.

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: Committer needed for upgrade of port of Perl library List-Compare

[Kurt Jaeger]

Hi!

> > I filed this BZ ticket two months ago, but it has not been responded to::
> > 
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225469
> > misc/p5-List-Compare: update to 0.53
> > 
> > Could someone please investigate?
> 
> I'm looking into this. As the version step-up is several versions,
> did you investigate if dependent ports still build ?

Well, there are only two depends. Committed, thanks!

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: Committer needed for upgrade of port of Perl library List-Compare

[Kurt Jaeger]

Hi!

> I filed this BZ ticket two months ago, but it has not been responded to::
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225469
> misc/p5-List-Compare: update to 0.53
> 
> Could someone please investigate?

I'm looking into this. As the version step-up is several versions,
did you investigate if dependent ports still build ?

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: Committer needed for new port (net/nuster)

[Felix Hanley]

On Thu, Mar 22, 2018 at 07:06:55PM +0100, Matthias Andree wrote:
> Am 21.03.2018 um 00:39 schrieb Felix Hanley:
> > There is a new port (net/nuster) awaiting approval at
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225721 If there are no
> > suggestions could someone commit it please.
> 
> Committed (r465301).

Thank you for the commit and the clean up.

-felix
___
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: Committer needed for new port (net/nuster)

[Matthias Andree]

Am 21.03.2018 um 00:39 schrieb Felix Hanley:
> There is a new port (net/nuster) awaiting approval at
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225721 If there are no
> suggestions could someone commit it please.

Committed (r465301).

___
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: Committer needed

[Andreas Andersson]

Thank you!

2018-03-21 18:04 GMT+01:00 Kurt Jaeger :

> Hi!
>
> > I've submitted three ports that relates to carbon, but with go
> > implementations. Could anyone take a look at them?
>
> All done.
>
> --
> p...@opsec.eu+49 171 3101372 2 years to
> go !
>
___
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: Committer needed

[Kurt Jaeger]

Hi!

> I've submitted three ports that relates to carbon, but with go
> implementations. Could anyone take a look at them?

All done.

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: committer needed for new port sysutils/tmux23

[Miroslav Lachman]

Matthias Andree wrote on 2018/03/20 10:44:

yuri@ has committed this, thanks.


Thank you!
___
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: committer needed for new port sysutils/tmux23

[Matthias Andree]

yuri@ has committed this, 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: Committer needed for new port (databases/go-carbon)

[Kurt Jaeger]

Hi!

> Can someone take a look at
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226732 suggestions for
> improvements are welcome.

Done.

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: Committer needed for #221810 - converters/osm2pgrouting, Import OSM data into pgRouting Database

[L.Bartoletti]

Thanks yuri@ !


On 12.01.2018 06:33, L.Bartoletti wrote:

Hi,

Can someone check and commit this PR 
?


Thanks in advance.

Regards.

Loïc

___
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: committer needed for update of security/base-audit

[Miroslav Lachman]

Kurt Jaeger wrote on 2018/01/12 16:29:

Hi!


Can somebody commit update to my port security/base-audit please?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224239


Done.


Thank you!

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"

Re: committer needed for update of security/base-audit

[Kurt Jaeger]

Hi!

> Can somebody commit update to my port security/base-audit please?
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224239

Done.

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
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: Committer needed for [Bug 222185] devel/tig: update to 2.2.2

[Sebastian Schwarz]

On 2017-10-01, Sebastian Schwarz wrote:
> Can some commit this to the ports tree?

Can *someone* commit this...
___
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: Committer needed

[Andreas Andersson]

Buid-issues fixed with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215524

2017-08-10 9:33 GMT+02:00 Torsten Zuehlsdorff :

> On 10.08.2017 07:34, Andreas Andersson wrote:
>
>> Can someone please take a look at these two?:
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215524
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221313
>>
>
> I will take care of them.
>
> Greetings,
> Torsten
> --
> Support me at:
> https://www.patreon.com/TorstenZuehlsdorff
>
___
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: Committer needed

[Torsten Zuehlsdorff]

On 10.08.2017 07:34, Andreas Andersson wrote:

Can someone please take a look at these two?:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215524
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221313


I will take care of them.

Greetings,
Torsten
--
Support me at:
https://www.patreon.com/TorstenZuehlsdorff
___
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: committer needed for new ports: Search Guard for Kibana and Elasticsearch

[Torsten Zuehlsdorff]

Aloha,


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219739


I take this one!

Greetings,
Torsten

--
Support me at:
https://www.patreon.com/TorstenZuehlsdorff
___
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: Committer needed for new port

[Kurt Jaeger]

Hi!

> This is ready to go, just needs someone to drop it in the tree.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212514

Done.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Committer needed for new perl5 ports

[Danny Warren]

On 8/28/2016 12:06 AM, Kurt Jaeger wrote:

Hi!


Hi all!  I have a few new perl5 ports that could use a committer.

Each of these has a successful poudriere log attached, no complaints
from portlint and dependencies met.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212206


Done. The distinfo files do not have the TIMESTAMP element,
which is now required. Please add that element in future PRs.

Another issue: Do not attach build-logs to the PRs per default, as it
blows up the bugzilla database. If the build is fine, mention it
in the PR, like:

poudriere testbuild on 10.3-amd64, 11.0-RC2-i386 is ok.


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209191
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212209
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212210
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209187
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209189


I'll work on those in the next few hours.


Thanks Kurt!  I'll make sure to use "make distinfo" next time, and I'll 
refrain from spamming bugzilla with buildlogs.  Appreciate the pointers.


___
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: Committer needed for new perl5 ports

[Kurt Jaeger]

Hi!

> Hi all!  I have a few new perl5 ports that could use a committer.
> 
> Each of these has a successful poudriere log attached, no complaints 
> from portlint and dependencies met.
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212206

Done. The distinfo files do not have the TIMESTAMP element,
which is now required. Please add that element in future PRs.

Another issue: Do not attach build-logs to the PRs per default, as it
blows up the bugzilla database. If the build is fine, mention it
in the PR, like:

poudriere testbuild on 10.3-amd64, 11.0-RC2-i386 is ok.

> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209191
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212209
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212210
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209187
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209189

I'll work on those in the next few hours.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Committer needed for PR 208029

[Michelle Sullivan]

Jim Ohlstein wrote:

Hello,

On 4/6/16 12:39 PM, Mathieu Arnold wrote:

+--On 6 avril 2016 12:00:47 -0400 Jim Ohlstein  wrote:
| Hello,
|
|> On Apr 6, 2016, at 11:37 AM, Mathieu Arnold  wrote:
|>
|> +--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein  wrote:
|> | Hello,
|> |
|> | On 4/6/16 12:44 AM, Kurt Jaeger wrote:
|> |> Hi!
|> |>
|> |>> Actually, I just noticed (when compiling the port), that the 
Makefile

|> |>> now says:
|> |>>
|> |>> WITH_OPENSSL_PORT=yes
|> |>
|> |> Yes, sorry, my fault. Fixed, and as suggested by mat: It is
|> |> now as IGNORE with a message explaining how to do it for 9.x.
|> |>
|> |
|> | This is much ado about nothing. The "WITH_OPENSSL_PORT" option 
is there

|> | for just this purpose and is used in many ports.
|>
|> No, the WITH_OPENSSL_PORT knob is a global one, and must not be 
used in
|> ports makefiles.  The fact is, there are ports using it, true, it 
does

|> not mean it is the right thing to do.
|>
|
| Then there are many ports being committed incorrectly, as well as, no
| doubt, many *official* packages.
|
| I really have no dog in this fight. I use it globally and build all 
of my
| own packages with poudriere, but either it shouldn't be there at 
all, or
| it should be ok to use. Having it available as an option to porters 
and

| then saying it shouldn't be used seems a bit silly.

Well, it is not available for the porters as it is a global 
directive, they

use it anyway.

Anyway, like I said, working on it.



Maybe an edit to portlint is in order. That way they might know. As of 
now, portlint does not so much as emit a warning.


I don't entirely disagree with the premise that all ports that require 
OpenSSL should be built against the version in ports. As I said, I do 
it and it also makes port maintenance simpler. However, as long as it 
is actually an option, as it is now, then it should be availed when 
desired.
I don't agree or disagree for what it's worth... What I do say though is 
where ever possible all ports should be compiled against one version.. 
of course GSSAPI support is a 'special case' in point that might have to 
break that rule of thumb.




Further down the road (but not all that far) I foresee other, perhaps 
bigger problems if using this strategy. OpenSSL 1.1.0 is in beta and 
will be released within the next month or two. It is not completely 
backward compatible. 


100% there...!

At some point it will become the official ports version and/or two 
versions will need to be maintained in ports, 1.0.2 (LTS until 2019) 
and 1.1.x. This will create the problem of some/many ports not 
building against 1.1.x and some ports or port options _requiring_ 
1.1.x. Assuming 1.1.x is the main OpenSSL in ports, there will be 
ports that would build properly against OpenSSL in base (but cannot be 
built that way if using the ports version is mandated), and do not 
compile against OpenSSL 1.1.x. Most can no doubt be patched, but 
waiting for upstream providers to do so may be problematic, and many 
porters lack the skills.


Personally I'm surprised there is not more than one major version of 
openssl in the ports tree already.. perhaps there should be...


--
Michelle Sullivan
http://www.mhix.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: Committer needed for PR 208029

[Michelle Sullivan]

Kurt Jaeger wrote:

Hi!


This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
for just this purpose and is used in many ports.

In 9.x this is sometimes a problem, if port X builds in variant 1
and port Y depends/links on X, but builds in variant 2. So it's
a temporary solution for 9.x and will be solved when 9.x is EOL'ed.


I have run into exactly this.


I'm not sure how this is solved in 10.x/11.x, probably the base SSL
is much more up2date.


Still has the same problem... though at the moment with 10.x being so up 
to date its not noticable when OpenSSL 1.0.3+ comes out it'll only be a 
matter of time before the same problems come up... and for the record, I 
think based on the FreeBSD policy, putting in an IGNORE or BROKEN for a 
too early version of openssl in base is the best policy ... not 
forgetting that the user doesn't have to specify system-wide options, 
they can do it on the command line.



Forcing users who want to use this port to use OpenSSL from ports for
ALL ports is overkill.
Think about official packages. Are ALL packages built against OpenSSL
from ports, or only those that need them? It's the latter, of course.
Are they incompatible in production? No.
Actually I think you'll find with the intent of compiling and using the 
new pkg (at least until variants are done) it's a hell of a lot worse 
(you can't use pkg upgrade with the risk of something that you need 
getting replaced by something you have chosen to configure... that 
said.. you have the same problem even if you have USE_OPENSSL_PORTS 
defined anyhow...)



There are grey areas, and I guess it will be like that for 9.x.




--
Michelle Sullivan
http://www.mhix.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: Committer needed for PR 208029

[Jim Ohlstein]

Hello,

On 4/6/16 12:39 PM, Mathieu Arnold wrote:

+--On 6 avril 2016 12:00:47 -0400 Jim Ohlstein  wrote:
| Hello,
|
|> On Apr 6, 2016, at 11:37 AM, Mathieu Arnold  wrote:
|>
|> +--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein  wrote:
|> | Hello,
|> |
|> | On 4/6/16 12:44 AM, Kurt Jaeger wrote:
|> |> Hi!
|> |>
|> |>> Actually, I just noticed (when compiling the port), that the Makefile
|> |>> now says:
|> |>>
|> |>> WITH_OPENSSL_PORT=yes
|> |>
|> |> Yes, sorry, my fault. Fixed, and as suggested by mat: It is
|> |> now as IGNORE with a message explaining how to do it for 9.x.
|> |>
|> |
|> | This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
|> | for just this purpose and is used in many ports.
|>
|> No, the WITH_OPENSSL_PORT knob is a global one, and must not be used in
|> ports makefiles.  The fact is, there are ports using it, true, it does
|> not mean it is the right thing to do.
|>
|
| Then there are many ports being committed incorrectly, as well as, no
| doubt, many *official* packages.
|
| I really have no dog in this fight. I use it globally and build all of my
| own packages with poudriere, but either it shouldn't be there at all, or
| it should be ok to use. Having it available as an option to porters and
| then saying it shouldn't be used seems a bit silly.

Well, it is not available for the porters as it is a global directive, they
use it anyway.

Anyway, like I said, working on it.



Maybe an edit to portlint is in order. That way they might know. As of 
now, portlint does not so much as emit a warning.


I don't entirely disagree with the premise that all ports that require 
OpenSSL should be built against the version in ports. As I said, I do it 
and it also makes port maintenance simpler. However, as long as it is 
actually an option, as it is now, then it should be availed when desired.


Further down the road (but not all that far) I foresee other, perhaps 
bigger problems if using this strategy. OpenSSL 1.1.0 is in beta and 
will be released within the next month or two. It is not completely 
backward compatible. At some point it will become the official ports 
version and/or two versions will need to be maintained in ports, 1.0.2 
(LTS until 2019) and 1.1.x. This will create the problem of some/many 
ports not building against 1.1.x and some ports or port options 
_requiring_ 1.1.x. Assuming 1.1.x is the main OpenSSL in ports, there 
will be ports that would build properly against OpenSSL in base (but 
cannot be built that way if using the ports version is mandated), and do 
not compile against OpenSSL 1.1.x. Most can no doubt be patched, but 
waiting for upstream providers to do so may be problematic, and many 
porters lack the skills.


--
Jim Ohlstein


"Never argue with a fool, onlookers may not be able to tell the 
difference." - Mark Twain

___
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: Committer needed for PR 208029

[Mathieu Arnold]

+--On 6 avril 2016 12:00:47 -0400 Jim Ohlstein  wrote:
| Hello,
| 
|> On Apr 6, 2016, at 11:37 AM, Mathieu Arnold  wrote:
|> 
|> +--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein  wrote:
|> | Hello,
|> | 
|> | On 4/6/16 12:44 AM, Kurt Jaeger wrote:
|> |> Hi!
|> |> 
|> |>> Actually, I just noticed (when compiling the port), that the Makefile
|> |>> now says:
|> |>> 
|> |>> WITH_OPENSSL_PORT=yes
|> |> 
|> |> Yes, sorry, my fault. Fixed, and as suggested by mat: It is
|> |> now as IGNORE with a message explaining how to do it for 9.x.
|> |> 
|> | 
|> | This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
|> | for just this purpose and is used in many ports.
|> 
|> No, the WITH_OPENSSL_PORT knob is a global one, and must not be used in
|> ports makefiles.  The fact is, there are ports using it, true, it does
|> not mean it is the right thing to do.
|> 
| 
| Then there are many ports being committed incorrectly, as well as, no
| doubt, many *official* packages. 
| 
| I really have no dog in this fight. I use it globally and build all of my
| own packages with poudriere, but either it shouldn't be there at all, or
| it should be ok to use. Having it available as an option to porters and
| then saying it shouldn't be used seems a bit silly. 

Well, it is not available for the porters as it is a global directive, they
use it anyway.

Anyway, like I said, working on it.

-- 
Mathieu Arnold

pgpsUuW01kLS1.pgp
Description: PGP signature

Re: Committer needed for PR 208029

[Christoph Moench-Tegeder]

## Kurt Jaeger (li...@opsec.eu):

> In 9.x this is sometimes a problem, if port X builds in variant 1
> and port Y depends/links on X, but builds in variant 2. So it's
> a temporary solution for 9.x and will be solved when 9.x is EOL'ed.

We have also seen that problem on 10.x:
https://lists.freebsd.org/pipermail/freebsd-emulation/2015-March/012390.html

Regards,
Christoph

-- 
Spare Space
___
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: Committer needed for PR 208029

[Jim Ohlstein]

Hello,

> On Apr 6, 2016, at 11:37 AM, Mathieu Arnold  wrote:
> 
> +--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein  wrote:
> | Hello,
> | 
> | On 4/6/16 12:44 AM, Kurt Jaeger wrote:
> |> Hi!
> |> 
> |>> Actually, I just noticed (when compiling the port), that the Makefile
> |>> now says:
> |>> 
> |>> WITH_OPENSSL_PORT=yes
> |> 
> |> Yes, sorry, my fault. Fixed, and as suggested by mat: It is
> |> now as IGNORE with a message explaining how to do it for 9.x.
> |> 
> | 
> | This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
> | for just this purpose and is used in many ports.
> 
> No, the WITH_OPENSSL_PORT knob is a global one, and must not be used in
> ports makefiles.  The fact is, there are ports using it, true, it does not
> mean it is the right thing to do.
> 

Then there are many ports being committed incorrectly, as well as, no doubt, 
many *official* packages. 

I really have no dog in this fight. I use it globally and build all of my own 
packages with poudriere, but either it shouldn't be there at all, or it should 
be ok to use. Having it available as an option to porters and then saying it 
shouldn't be used seems a bit silly. 

> There is work going on to always use OpenSSL from ports, but it also needs
> to take into account GSSAPI, and it's a mess.

--
Jim
___
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: Committer needed for PR 208029

[Mathieu Arnold]

+--On 6 avril 2016 10:06:41 -0400 Jim Ohlstein  wrote:
| Hello,
| 
| On 4/6/16 12:44 AM, Kurt Jaeger wrote:
|> Hi!
|> 
|>> Actually, I just noticed (when compiling the port), that the Makefile
|>> now says:
|>> 
|>> WITH_OPENSSL_PORT=yes
|> 
|> Yes, sorry, my fault. Fixed, and as suggested by mat: It is
|> now as IGNORE with a message explaining how to do it for 9.x.
|> 
| 
| This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there
| for just this purpose and is used in many ports.

No, the WITH_OPENSSL_PORT knob is a global one, and must not be used in
ports makefiles.  The fact is, there are ports using it, true, it does not
mean it is the right thing to do.

There is work going on to always use OpenSSL from ports, but it also needs
to take into account GSSAPI, and it's a mess.

-- 
Mathieu Arnold

pgpaLDaT4nC3w.pgp
Description: PGP signature

Re: Committer needed for PR 208029

[Jim Ohlstein]

Hello,

> On Apr 6, 2016, at 10:47 AM, Kurt Jaeger  wrote:
> 
> Hi!
> 
>> This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there 
>> for just this purpose and is used in many ports.
> 
> In 9.x this is sometimes a problem, if port X builds in variant 1
> and port Y depends/links on X, but builds in variant 2. So it's
> a temporary solution for 9.x and will be solved when 9.x is EOL'ed.
> 
> I'm not sure how this is solved in 10.x/11.x, probably the base SSL
> is much more up2date.
> 
>> Forcing users who want to use this port to use OpenSSL from ports for 
>> ALL ports is overkill.
> 
>> Think about official packages. Are ALL packages built against OpenSSL 
>> from ports, or only those that need them? It's the latter, of course. 
>> Are they incompatible in production? No.
> 
> There are grey areas, and I guess it will be like that for 9.x.

Not only 9.x. 10.x has OpenSSL 1.0.1. Some ports require 1.0.2 which is in 
ports. Openssl 1.1.0 is soon to be released but almost certainly won't be in 
11. It's likely to always be an issue. It's up to each individual maintainer to 
make certain his or her ports behave correctly if binaries link to one another. 
For a port like this the proper solution is to use the least intrusive option. 

--
Jim
___
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: Committer needed for PR 208029

[Kurt Jaeger]

Hi!

> This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there 
> for just this purpose and is used in many ports.

In 9.x this is sometimes a problem, if port X builds in variant 1
and port Y depends/links on X, but builds in variant 2. So it's
a temporary solution for 9.x and will be solved when 9.x is EOL'ed.

I'm not sure how this is solved in 10.x/11.x, probably the base SSL
is much more up2date.

> Forcing users who want to use this port to use OpenSSL from ports for 
> ALL ports is overkill.

> Think about official packages. Are ALL packages built against OpenSSL 
> from ports, or only those that need them? It's the latter, of course. 
> Are they incompatible in production? No.

There are grey areas, and I guess it will be like that for 9.x.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Committer needed for PR 208029

[Jim Ohlstein]

Hello,

On 4/6/16 12:44 AM, Kurt Jaeger wrote:

Hi!


Actually, I just noticed (when compiling the port), that the Makefile now says:

WITH_OPENSSL_PORT=yes


Yes, sorry, my fault. Fixed, and as suggested by mat: It is
now as IGNORE with a message explaining how to do it for 9.x.



This is much ado about nothing. The "WITH_OPENSSL_PORT" option is there 
for just this purpose and is used in many ports. There's no reason some 
binaries can't be linked to one version of OpenSSL and others to 
another, so long as they aren't expected to work as one (I'd imagine a 
dynamically loaded module that is linked to a different library might 
cause a problem). That is the reason that ports contains a more current 
version than base. This is from the ports/www directory:


#  grep WITH_OPENSSL_PORT */Makefile
aws/Makefile:WITH_OPENSSL_PORT= yes
drood/Makefile:WITH_OPENSSL_PORT=   yes
h2o/Makefile:WITH_OPENSSL_PORT= no
h2o/Makefile:WITH_OPENSSL_PORT= yes
mod_tsa/Makefile:WITH_OPENSSL_PORT= yes
nginx-devel/Makefile:WITH_OPENSSL_PORT= yes
nginx-devel/Makefile:WITH_OPENSSL_PORT= yes
nginx/Makefile:WITH_OPENSSL_PORT=   yes
nginx/Makefile:WITH_OPENSSL_PORT=   yes
obhttpd/Makefile:WITH_OPENSSL_PORT=yes
owncloud/Makefile:WITH_OPENSSL_PORT=yes
spdylay/Makefile:.if ${OSVERSION} < 100 && !defined(WITH_OPENSSL_PORT)
tengine/Makefile:WITH_OPENSSL_PORT= yes
tomcat-native/Makefile:WITH_OPENSSL_PORT=   yes

I'm sure there are dozens of others.

Forcing users who want to use this port to use OpenSSL from ports for 
ALL ports is overkill.


Think about official packages. Are ALL packages built against OpenSSL 
from ports, or only those that need them? It's the latter, of course. 
Are they incompatible in production? No.


--
Jim Ohlstein


"Never argue with a fool, onlookers may not be able to tell the 
difference." - Mark Twain

___
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: Committer needed for PR 208029

[Mathieu Arnold]

+--On 6 avril 2016 07:33:50 +0200 Michelle Sullivan 
wrote:
| Kurt Jaeger wrote:
|> Hi!
|> 
|>> Actually, I just noticed (when compiling the port), that the Makefile
|>> now says:
|>> 
|>> WITH_OPENSSL_PORT=yes
|> Yes, sorry, my fault. Fixed, and as suggested by mat: It is
|> now as IGNORE with a message explaining how to do it for 9.x.
|> 
| Not sure about the IGNORE vs BROKEN but looks a *lot* better now. Would
| be interested as to an explanation of why the distinction between the
| two... especially as the port is 'broken' if you try and compile it
| against the wrong version of SSL...  Mathieu?

I'm sorry, I don't understand what you are asking.

-- 
Mathieu Arnold

pgpGkL3SlHb9m.pgp
Description: PGP signature

Re: Committer needed for PR 208029

[Michelle Sullivan]

Kurt Jaeger wrote:

Hi!


Actually, I just noticed (when compiling the port), that the Makefile now says:

WITH_OPENSSL_PORT=yes

Yes, sorry, my fault. Fixed, and as suggested by mat: It is
now as IGNORE with a message explaining how to do it for 9.x.

Not sure about the IGNORE vs BROKEN but looks a *lot* better now. Would 
be interested as to an explanation of why the distinction between the 
two... especially as the port is 'broken' if you try and compile it 
against the wrong version of SSL...  Mathieu?


--
Michelle Sullivan
http://www.mhix.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: Committer needed for PR 208029

[Kurt Jaeger]

Hi!

> Actually, I just noticed (when compiling the port), that the Makefile now 
> says:
> 
> WITH_OPENSSL_PORT=yes

Yes, sorry, my fault. Fixed, and as suggested by mat: It is
now as IGNORE with a message explaining how to do it for 9.x.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Committer needed for PR 208029

[Michelle Sullivan]

Martin Waschbüsch wrote:

Umm probably a really bad idea...  consider this or something more 
creative/descriptive:

.if ${OPSYS} == FreeBSD && ${OSVERSION} < 100 && ${WITH_OPENSSL_PORT} != 
"yes"
BROKEN= You must set WITH_OPENSSL_PORT=yes in /etc/make.conf on Pre 10.x
.endif


... the idea instead of silently turning it on which could cause a myriad of 
hell for production systems where some ports are compiled against 
security/openssl and some against the base openssl... stop the compile and tell 
the user what they have to do to resolve it... which will then make anything 
else use the same openssl and lessen the dependency/library issues that could 
happen.

Actually, I just noticed (when compiling the port), that the Makefile now says:

WITH_OPENSSL_PORT=yes

GNUTLS_CONFIGURE_WITH=  gnutls
GNUTLS_LIB_DEPENDS= libgnutls.so:security/gnutls

POLARSSL_CONFIGURE_WITH=mbedtls
POLARSSL_LIB_DEPENDS=   libmbedtls.so:security/polarssl13

.include 

.if ${OPSYS} == FreeBSD && ${OSVERSION} < 100
WITH_OPENSSL_PORT=yes
.endif

Which means that the ports version is used regardless of OSVERSION...
Yup... which is so much worse in so many other ways.. (IMHO) ... I mean 
why would you want to turn on openssl in any way if you have gnutls or 
polarssl on...  I suspect the whole set of options and way its 
configured should be looked at a little more closely and have an option 
openssl as well ... or at least the broken= so that it will inform the 
user if the wrong version of openssl is attempted... and considering 
FreeBSD policy over base libraries and major releases maybe an option to 
set for including the ports version of openssl as well (so that a 
compile on 10.x while may work, if there is a security issue the 
prompting for openssl from ports will allow a person to patch up without 
necessarily knowing the significance... you know give the users a chance 
rather than leaving it to the FreeBSD Devs to say you are better off 
doing what we tell you.)




Shall I open a PR for it and incorporate the BROKEN= approach?

I'm not the right person to ask over that question, I'm just throwing a 
suggestion on how you might consider handling it and other similar 
issues in ways that are a lot more useful and less error/dependency 
prone.  Bad things/assumptions in makefiles end up with version lock-in 
and/or broken linking/compiles when something needs to be upgraded... 
and the all singing all dancing pkg system is no better than the old 
system of pkg_add when it comes to these problems (in fact in some ways 
its worse... because it tries to do the right thing when the right thing 
is actually impossible until someone changes compile options.)


--
Michelle Sullivan
http://www.mhix.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: Committer needed for PR 208029

[Martin Waschbüsch]

> Umm probably a really bad idea...  consider this or something more 
> creative/descriptive:
> 
> .if ${OPSYS} == FreeBSD && ${OSVERSION} < 100 && ${WITH_OPENSSL_PORT} != 
> "yes"
> BROKEN=   You must set WITH_OPENSSL_PORT=yes in /etc/make.conf on 
> Pre 10.x
> .endif
> 
> 
> ... the idea instead of silently turning it on which could cause a myriad of 
> hell for production systems where some ports are compiled against 
> security/openssl and some against the base openssl... stop the compile and 
> tell the user what they have to do to resolve it... which will then make 
> anything else use the same openssl and lessen the dependency/library issues 
> that could happen.

Actually, I just noticed (when compiling the port), that the Makefile now says:

WITH_OPENSSL_PORT=yes

GNUTLS_CONFIGURE_WITH=  gnutls
GNUTLS_LIB_DEPENDS= libgnutls.so:security/gnutls

POLARSSL_CONFIGURE_WITH=mbedtls
POLARSSL_LIB_DEPENDS=   libmbedtls.so:security/polarssl13

.include 

.if ${OPSYS} == FreeBSD && ${OSVERSION} < 100
WITH_OPENSSL_PORT=yes
.endif

Which means that the ports version is used regardless of OSVERSION...

Shall I open a PR for it and incorporate the BROKEN= approach?

Martin
___
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: Committer needed for PR 208029

[Michelle Sullivan]

Kurt Jaeger wrote:

Hi!


I'm testbuilding those ports right now and find that
they fail on 9.3amd64 with:

With this in the -server Makefile, all is fine.

.if ${OPSYS} == FreeBSD && ${OSVERSION} < 100
WITH_OPENSSL_PORT=yes
.endif

Umm probably a really bad idea...  consider this or something more 
creative/descriptive:


.if ${OPSYS} == FreeBSD && ${OSVERSION} < 100 && ${WITH_OPENSSL_PORT} != 
"yes"
BROKEN= You must set WITH_OPENSSL_PORT=yes in /etc/make.conf on Pre 10.x
.endif


... the idea instead of silently turning it on which could cause a 
myriad of hell for production systems where some ports are compiled 
against security/openssl and some against the base openssl... stop the 
compile and tell the user what they have to do to resolve it... which 
will then make anything else use the same openssl and lessen the 
dependency/library issues that could happen.


Regards,

--
Michelle Sullivan
http://www.mhix.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: Committer needed for PR 208029

[Michelle Sullivan]

Kurt Jaeger wrote:

Hi!


Could someone please have a look at this one.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029

All patches got approval from the maintainer.
For all I can see this should be ready to be committed.

If I overlooked anything or more information is needed,
please let me know and I'll try my best to fix this.

I'm testbuilding those ports right now and find that
they fail on 9.3amd64 with:

checking for OpenSSL support... yes
configure: error: OpenSSL library version requirement not met (>= 1.0.1)

So it seems that OpenSSL and 9.3amd64 do not build ? Should the
default for 9.3 probably be something else like gnutls or polarssl ?

OPENSSL from Ports is newer and will compile on 9.3amd64... the base 
OpenSSL is too old and 9.3 is legacy... according to re@


--
Michelle Sullivan
http://www.mhix.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: Committer needed for PR 208029

[Martin Waschbüsch]

> Am 05.04.2016 um 22:15 schrieb Kurt Jaeger :
> 
> Hi!
> 
>> Could someone please have a look at this one.
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029
>> 
>> All patches got approval from the maintainer.
>> For all I can see this should be ready to be committed.
> 
> Done.

Thanks a lot, Kurt!

Best,

Martin
___
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: Committer needed for PR 208029

[Kurt Jaeger]

Hi!

> Could someone please have a look at this one.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029
> 
> All patches got approval from the maintainer.
> For all I can see this should be ready to be committed.

Done.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Committer needed for PR 208029

[Kurt Jaeger]

Hi!

> I'm testbuilding those ports right now and find that
> they fail on 9.3amd64 with:

With this in the -server Makefile, all is fine.

.if ${OPSYS} == FreeBSD && ${OSVERSION} < 100
WITH_OPENSSL_PORT=yes
.endif

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Committer needed for PR 208029

[Kurt Jaeger]

Hi!

> I'm testbuilding those ports right now and find that
> they fail on 9.3amd64 with:
> 
> checking for OpenSSL support... yes
> configure: error: OpenSSL library version requirement not met (>= 1.0.1)
> 
> So it seems that OpenSSL and 9.3amd64 do not build ? Should the
> default for 9.3 probably be something else like gnutls or polarssl ?

gnutls works fine:

cur 93a 103 10i done
cur 93a 103 10i done
cur 93a 103 10i done

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Committer needed for PR 208029

[Kurt Jaeger]

Hi!

> Could someone please have a look at this one.
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208029
> 
> All patches got approval from the maintainer.
> For all I can see this should be ready to be committed.
> 
> If I overlooked anything or more information is needed,
> please let me know and I'll try my best to fix this.

I'm testbuilding those ports right now and find that
they fail on 9.3amd64 with:

checking for OpenSSL support... yes
configure: error: OpenSSL library version requirement not met (>= 1.0.1)

So it seems that OpenSSL and 9.3amd64 do not build ? Should the
default for 9.3 probably be something else like gnutls or polarssl ?

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Committer needed for PR201175: Update graphics/synfigstudio to 1.0.1

[Kurt Jaeger]

Hi!

> Yes, as maintainer I can confirm this is broken on FreeBSD 9. I am
> continuing to investigate, as per my comments at the end of PR199802, but
> this will not be a quick fix.
> 
> Can we please commit this as is, and declare this broken on FreeBSD 9 amd64?

Done 8-)

In future PRs, please provide links to changelogs so that
we can reference them in the commit message.

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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: Committer needed for PR201175: Update graphics/synfigstudio to 1.0.1

[Kurt Jaeger]

Hi!

> > Yes, as maintainer I can confirm this is broken on FreeBSD 9. I am
> > continuing to investigate, as per my comments at the end of PR199802, but
> > this will not be a quick fix.

Can you add a pointer of the problem and the PR at freedesktop.org ?

https://bugs.freedesktop.org/buglist.cgi?quicksearch=liboil

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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: Committer needed for PR201175: Update graphics/synfigstudio to 1.0.1

[Ben Woods]

On Friday, 2 October 2015, Kurt Jaeger  wrote:

> Hi!
>
> > graphics/synfigstudio fails to build on 9.3-amd64, see the build-log at
> >
> >
> http://people.freebsd.org/~pi/logs/graphics__synfigstudio-93a-1443720936.txt
> >
> > Everything else builds fine. Any quick fix ?
>
> One quick fix: If you as maintainer declare it as broken on 9,
> we can commit the update and work on the fix later.
>
> Just sayin' 8-}
>

Hi Kurt,

Yes, as maintainer I can confirm this is broken on FreeBSD 9. I am
continuing to investigate, as per my comments at the end of PR199802, but
this will not be a quick fix.

Can we please commit this as is, and declare this broken on FreeBSD 9 amd64?

Regards,
Ben



-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Committer needed for PR201175: Update graphics/synfigstudio to 1.0.1

[Kurt Jaeger]

Hi!

> Are there any ports committers that could take a look at this bug
> report please?
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201175

I build-tested this on 11, 10.2a+1, 9.3a.

graphics/synfigstudio fails to build on 9.3-amd64, see the build-log at

http://people.freebsd.org/~pi/logs/graphics__synfigstudio-93a-1443720936.txt

Everything else builds fine. Any quick fix ?

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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: Committer needed for PR201175: Update graphics/synfigstudio to 1.0.1

[Kurt Jaeger]

Hi!

> graphics/synfigstudio fails to build on 9.3-amd64, see the build-log at
> 
> http://people.freebsd.org/~pi/logs/graphics__synfigstudio-93a-1443720936.txt
> 
> Everything else builds fine. Any quick fix ?

One quick fix: If you as maintainer declare it as broken on 9,
we can commit the update and work on the fix later.

Just sayin' 8-}

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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: Committer needed: Update multimedia/emby-server

[Kurt Jaeger]

Hi!

> Are any committers able to have a look at this simple PR for me?
> 
> It a run of the mill update of multimedia/emby-server which has been
> waiting a couple of weeks:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202928

Done. I took the liberty to upgrade to 3.0.5724.5 (not .4).

-- 
p...@opsec.eu+49 171 3101372 5 years to go !
___
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: Committer needed: Update multimedia/emby-server

[Ben Woods]

On Wednesday, 23 September 2015, Kurt Jaeger  wrote:

> Hi!
>
> > Are any committers able to have a look at this simple PR for me?
> >
> > It a run of the mill update of multimedia/emby-server which has been
> > waiting a couple of weeks:
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202928
>
> Done. I took the liberty to upgrade to 3.0.5724.5 (not .4).
>

Thanks - I hadn't even spotted the .5 release yet :)

Cheers,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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: Committer needed for PR199802: update synfigstudio

[Ben Woods]

On Tuesday, August 11, 2015, Ben Woods woods...@gmail.com wrote:

 Hey everyone,

 Can a committer please take a look at PR199082, which updates the
 following related ports:
 graphics/synfigstudio: Update to 1.0
 graphics/synfigstudio: Update to 1.0
 devel/etl: Update to 0.04.18

 It was waiting for 3.5 months on the maintainer (dhn@) but he has
 since relinquished his maintainership (I will take it on for these
 three now).

 Cheers,
 Ben


Hey folks,

Are any committers able to help me out with this one?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199802

Regards,
Ben


-- 

--
From: Benjamin Woods
woods...@gmail.com
___
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