Re: PHP version retirement

Hi Dan, > Am 16.08.2019 um 08:07 schrieb Dan Mahoney : > > Martin and others, > > I don’t have a good answer for this, other than to say that PHP has been the > bane of my existence for a while. As a admin, I’ve lost more hours and sleep > on PHP scripts than any other tool. PHP is the

Re: PHP version retirement

> Am 13.08.2019 um 08:13 schrieb @lbutlr : > > On 12 Aug 19, at 01:04 , Martin Waschbüsch wrote: >> So, I find it wrong to say, as I understood you, to remove a package from >> the ports tree because otherwise others people, for instance users of >> FreeBSD,

Re: PHP version retirement

Hi Adam, > Am 12.08.2019 um 15:29 schrieb Adam Weinberger : > > On Mon, Aug 12, 2019 at 1:04 AM Martin Waschbüsch > wrote: >>>>>> Furthermore, the argument that it is more more work to maintain an >>>>>> abandoned version is silly because it’s

Re: PHP version retirement

Hi Adam, > Am 12.08.2019 um 02:17 schrieb Adam Weinberger : > > On Sun, Aug 11, 2019 at 5:50 PM Martin Waschbüsch > wrote: >> >> Hi Adam, >> >>> Am 11.08.2019 um 23:22 schrieb Adam Weinberger : >>> >>> On Sun, Aug 11, 2019 at

Re: PHP version retirement

Hi Adam, > Am 11.08.2019 um 23:22 schrieb Adam Weinberger : > > On Sun, Aug 11, 2019 at 1:05 PM Franco Fichtner wrote: >> >> Quarterly is essentially useless if the decision is to immediately axe a >> deprecated release. 3 months are nothing in production environments, if you >> get 3 months

Re: PHP version retirement

> Am 11.08.2019 um 23:31 schrieb Wolfgang Zenker : > > * Martin Waschbüsch [190811 20:41]: >> [..] >>> You could also have used the quarterly branch, which keeps software till >>> the end of the quarter. In the case of php 5.6 it would have given you >>

Re: PHP version retirement

Hi Wolfgang, > Am 11.08.2019 um 01:12 schrieb Wolfgang Zenker : > > * Martin Waschbüsch [190811 00:47]: >>> Am 10.08.2019 um 20:18 schrieb Patrick Powell : >>> >>> Umm this was just the kick in the pants that I needed to switch to PHP 7. >>

Re: PHP version retirement

> Am 10.08.2019 um 20:18 schrieb Patrick Powell : > > Umm this was just the kick in the pants that I needed to switch to PHP 7. > See https://www.glaver.org/blog/?p=1109 for a desperation 'I need PHP5.6' > hack which I used during this update. Thank you, Patrick, that is a work-around I also

Re: PHP version retirement

> Am 10.08.2019 um 12:53 schrieb Carmel NY : > > On Sat, 10 Aug 2019 10:17:44 +0200, Martin Waschbüsch stated: >> Would it not be better to have, say, the last two versions before >> current stable still in ports but with a huge disclaimer saying: use >> at your own

PHP version retirement

Hi all, At least the last two versions of PHP, 5.6 & 7.0, were removed from ports as soon as (or even shortly before) they were no longer actively maintained upstream. I am unsure what the exact reasoning behind this was, but I do not think it is a good idea moving forward: I suppose it is

Re: Committer TLC needed for ports devel/sope4, www/sogo4 and www/sogo4-activesync

> Am 13.05.2018 um 11:55 schrieb Kurt Jaeger : > > Hi! > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227578 > > There's a devel/sope4 already in the ports. Can you provide a > diff if it needs an update or can we close this PR ? > >>

Re: Committer TLC needed for ports devel/sope4, www/sogo4 and www/sogo4-activesync

> Am 13.05.2018 um 11:55 schrieb Kurt Jaeger : > > Hi! > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227578 > > There's a devel/sope4 already in the ports. Can you provide a > diff if it needs an update or can we close this PR ? I’ll look into it. My best guess is

Re: Committer TLC needed for ports devel/sope4, www/sogo4 and www/sogo4-activesync

> Am 13.05.2018 um 11:43 schrieb Martin Waschbüsch <mar...@waschbuesch.de>: > > Hi all, > > if a committer could have a look at these PRs by Euan Thoms: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227578 > <https://bugs.freebsd.org/bugzill

Committer TLC needed for ports devel/sope4, www/sogo4 and www/sogo4-activesync

Hi all, if a committer could have a look at these PRs by Euan Thoms: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227578 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227579

Re: unable to set maintainer-approval?

> Am 25.03.2018 um 19:03 schrieb Ultima : > > Fairly certain this is because the maintainer approval must be requested > before it can be approved. > > Hope this helps, > Richard Gallamore You're right, of course. Thanks for pointing it out. I was wracking my brains but

unable to set maintainer-approval?

Hi, can anyone tell me why I am unable to set the maintainer approval flag for the proposed patch in PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225377 ? Thanks, Martin ___ freebsd-ports@freebsd.org mailing list

archivers/liblz4 help needed with cross-compiling (PR 225377)

Hi all, If someone with knowledge on cross-compiling could have a look at PR 225377, I would be very grateful. I am the maintainer of the port concerned) and I understand the concern of the reporter. For all I know, the solution proposed in the PR is just a band-aid that would hide the issue

Re: Cross-compiling a port

> > Am 18.02.2018 um 07:22 schrieb Martin Waschbüsch <mar...@waschbuesch.de>: > > Hi there, > > how would I go about cross-compilinga port for another ARCH? > E.g. I am running 11.1-RELEASE on amd64 and would like to compile a port for > i386. > It does not

Cross-compiling a port

Hi there, how would I go about cross-compilinga port for another ARCH? E.g. I am running 11.1-RELEASE on amd64 and would like to compile a port for i386. It does not seem to be enough to set the ARCH and TARGET_ARCH environment variables: e.g. something like cd /usr/ports/archivers/zip env

Re: Help with versioning scheme

Hi Adam, > Am 17.01.2018 um 19:49 schrieb Adam Weinberger : > > In general, I recommend against doing clever things. It's too easy to > outsmart yourself. > > It's not terribly difficult to edit the plist and increase a number. I > recommend clear over clever every time. > >

Re: Help with versioning scheme

Thanks, Freddie, > Am 17.01.2018 um 19:35 schrieb Freddie Cash <fjwc...@gmail.com>: > > On Wed, Jan 17, 2018 at 10:29 AM, Martin Waschbüsch <mar...@waschbuesch.de > <mailto:mar...@waschbuesch.de>> wrote: > Hi Adam, > > Am 17.01.2018 um 19:19 s

Re: Help with versioning scheme

Hi Adam, > Am 17.01.2018 um 19:19 schrieb Adam Weinberger : > Hi Martin, > > You don't want to use the upstream version to represent PORTREVISION. > PORTREVISION is for when you need to force rebuilds of the port itself, and > so tying it to upstream would make it impossible to

Help with versioning scheme

Hi there, I am preparing a patch for a port (archivers/libz4) that I am maintaining. The versioning scheme upstream originally used was for instance: rXXX e.g. r123 When they changed to vX.Y.Z e.g. v1.8.1 I had to up PORTEPOCH in order not to get wrong warnings about new versions available.

Re: Qupzilla 2.x

> Am 12.09.2017 um 21:47 schrieb Martin Waschbüsch <mar...@waschbuesch.de>: > > Hi all, > > Now that we have qt5-webengine (as of > https://svnweb.freebsd.org/ports?view=revision=448132), I wondered > if anyone is working on porting qupzilla 2.x? Hoping I am no

Qupzilla 2.x

Hi all, Now that we have qt5-webengine (as of https://svnweb.freebsd.org/ports?view=revision=448132 ), I wondered if anyone is working on porting qupzilla 2.x? ___ freebsd-ports@freebsd.org

Re: PRs in need of some TLC

> Am 27.06.2017 um 00:33 schrieb Greg 'groggy' Lehey <g...@freebsd.org>: > > On Monday, 26 June 2017 at 21:48:14 +0200, Martin Waschbüsch wrote: >> Hi all, >> >> could someone have a look at these PRs (they are linked) and provide >> some tender loving ca

Re: PRs in need of some TLC

> Am 27.06.2017 um 00:56 schrieb Kurt Jaeger : > > Hi! > >> could someone have a look at these PRs (they are linked) and provide some >> tender loving care? ;-) >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220177 > > This is missing a patch, isn't it ? You’re

PRs in need of some TLC

Hi all, could someone have a look at these PRs (they are linked) and provide some tender loving care? ;-) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220177 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220190 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220191 Thanks!! Martin

Re: "clamav-unofficial-sigs" error message

> Am 25.06.2017 um 12:24 schrieb Carmel NY : > > I recently installed clamav-unofficial-sigs via the ports system. The > port version is quite old,v5.3.2, while the current version is v5.6.2. > In any case, I am receiving the following error message repeatedly: > > Jun

Re: [RFC] Why FreeBSD ports should have branches by OS version

> Am 23.06.2017 um 23:53 schrieb Michelle Sullivan : > > Matt Smith wrote: >> >> I use FreeBSD *precisely* because it mostly keeps up with the latest stable >> versions of things. I have postfix 3.2, pgsql 9.6, nginx 1.13, libressl 2.5 >> etc. It's usually impossible to do

PR 213270 is overcome by events.

The version in ports is currently 3.2.8. ___ 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: ports and dependency hell

> Am 09.02.2017 um 18:14 schrieb Julian Elischer : > > Commercial products are Hardly EVER rolling releases. > they lurch from point of stability to point of stability, with large amounts > of testing between releases. >>> On the pkg side of things we need the ability for

TLC required for PR 216599

Hi there, could a committer please provide TLC for the mentioned PR? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216599 Thanks a lot, Martin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To

TLC required for PR 215440

Hi there, could a committer please provide TLC for the mentioned PR? Thx, Martin smime.p7s Description: S/MIME cryptographic signature

Re: WIP: lang/php71

> Am 26.10.2016 um 14:28 schrieb Torsten Zuehlsdorff : > > Aloha, > > PHP 7.1 RC5 was released and it will hopefully not too far until the full > release. Therefore i started some work on the new port. > > Sadly i haven't had much time in the last, so its not too much.

Re: Jive prejudices

> Am 23.10.2016 um 20:00 schrieb scratch65...@att.net: > > For policy, I'd suggest the creation of a flag "Socially > deprecated" that would leave it in the tree but clue people up > that there's potentially something unsavory about it. As others have already said, it is unlikely that we could

Re: ec2-eu-west-1.portsnap.freebsd.org is not up to date

> Am 05.09.2016 um 09:44 schrieb Henk van Oers : > > > The portsnap.FreeBSD.org on IP-nr 46.137.83.240 > is not serving updates anymore. > > What other server can I use? The list of mirrors is updated by portsnap and stored in /var/db/portsnap/serverlist You can try any of

Re: Maintainership Status for PHP 5.6

> Am 31.08.2016 um 15:03 schrieb Torsten Zuehlsdorff > : > > On 26.08.2016 21:38, Kurt Jaeger wrote: >> Hi! >> About resetting the maintainer, I'll ask around. >> >>> The rules are pretty clear: >>>

PR 211844 in need of TLC from a committer... ;-)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211844 Thanks, 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: questions about Makefile

> Am 14.08.2016 um 15:37 schrieb Mathieu Arnold <m...@freebsd.org>: > > +--On 13 août 2016 10:34:27 +0200 Martin Waschbüsch > <mar...@waschbuesch.de> wrote: > | Hi all, > | > | I am in the process of creating a port for a module / plugin for > | net-mgmt/zabb

questions about Makefile

Hi all, I am in the process of creating a port for a module / plugin for net-mgmt/zabbix-agent. I tried to follow the Porter's Handbook, but still have three items I am uncertain about: 1) The plugin (obviously) relies on the zabbix-agent sources. I added BUILD_DEPENDS=

Re: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency

> Am 14.07.2016 um 23:29 schrieb Euan Thoms : > > > On Friday, July 15, 2016 01:11 SGT, Walter Schwarzenfeld > wrote: > >> I think this statements should be only warnings. Cause not all of these >> statements are right and each maintianer

Re: Committer needed for PR 208029

> 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 > > > ...

Re: Committer needed for PR 208029

> 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. >

Committer needed for PR 208029

Hi all, 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

Re: Bug in poudriere?

> Am 02.04.2016 um 00:50 schrieb Bryan Drewery <bdrew...@freebsd.org>: > > On 4/1/16 12:31 AM, Martin Waschbüsch wrote: >> Hi all, >> >> I just noticed that while just running: >> >> root@dev:~# poudriere >> >> lists >> >>

Bug in poudriere?

Hi all, I just noticed that while just running: root@dev:~# poudriere lists daemon -- Launch the poudriere daemon among possible commands, the manpage does not mention this at all. Personally, I'd consider this a bug, but am unsure how best to file a PR for this? Best, Martin

Re: Future of pecl ports

> Am 14.03.2016 um 11:37 schrieb Gasol Wu : > > Hi miwi, > > First of all, I'm appreciated for your PHP support in FreeBSD. > > I have received many outdated notices regarding the PECL ports from > portscout because I'm the maintainer. > I saw the same problem here when I

Re: print/cups overhaul (PR 207746) side-effects

> Am 12.03.2016 um 16:51 schrieb Walter Schwarzenfeld > : > > Where is the problem? There is only one "big" port (llvm36). Will be sstimate > 1 !/2 hours. Poudriere and more synth often wants more. Re-reading the messages, I realize that I blew this out of

Re: print/cups overhaul (PR 207746) side-effects

> Am 12.03.2016 um 14:10 schrieb Tijl Coosemans <t...@freebsd.org>: > > On Fri, 11 Mar 2016 20:52:08 +0100 Martin Waschbüsch <mar...@waschbuesch.de> > wrote: >> I just did a rebuild of packages for my webservers with poudriere. >> What I noticed was that

Re: print/cups overhaul (PR 207746) side-effects

> Am 11.03.2016 um 21:10 schrieb Jim Ohlstein <j...@ohlste.in>: > > Hello, > > > > Jim Ohlstein >> On Mar 11, 2016, at 2:52 PM, Martin Waschbüsch <mar...@waschbuesch.de> wrote: >> If I wanted to adjust an existing port to be less greedy with r

print/cups overhaul (PR 207746) side-effects

Hi all, I just did a rebuild of packages for my webservers with poudriere. What I noticed was that via the print/cups overhaul (see PR 207746), quite a lot (>50) of additional dependencies are added to the system, including lots of x11 related libs, avahi, dbus, cairo, opengl, etc. This stems

Re: FreeBSD ports you maintain which are out of date

> Am 11.03.2016 um 13:41 schrieb Ryan Steinmetz : > > > On (03/11/16 12:35), Raphael Kubo da Costa wrote: >> Mathieu Arnold writes: >>> Someone already put: >>> >>> PORTSCOUT= ignore >> >> I did that in r410199, and tried a different approach first in

Re: cairo w/ x11

> Am 08.03.2016 um 05:03 schrieb Randy Bush : > > even if i turn them all on as you did, run make config again and x11 is > off, though the others are on. > >> Is your port tree updated? > > very Maybe you have WITHOUT_X11=yes in /etc/make.conf ? Martin

Re: automation of perl port creation from cpan

> > Am 24.02.2016 um 11:40 schrieb Dave Cottlehuber : > > Hi, Hi Dave, > I have a perl app that I'd like to move to FreeBSD. It currently has a > whole list of cpan dependencies. Is there any partial automation of > generating ports from CPAN directly? Something similar to

Re: [exp - 103i386-default-build-as-user][mail/libdomainkeys] Failed for libdomainkeys-0.69 in build

> Am 24.02.2016 um 01:15 schrieb pkg-fall...@freebsd.org: > > You are receiving this mail as a port that you maintain > is failing to build on the FreeBSD package build server. > Please investigate the failure and submit a PR to fix > build. > > Maintainer: po...@freebsd.org > Last

Zabbix 3.0 Port?

Hey there, Zabbix 3.0 got released and I am wondering if anyone is working on porting it? I'll gladly help any ongoing efforts. Martin ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe,

Re: FreeBSD Port: cairo-1.14.2,2

> Am 08.11.2015 um 15:17 schrieb Martin Waschbüsch <mar...@waschbuesch.de>: > > >> Am 08.11.2015 um 14:53 schrieb Sergey Masharov <se...@expir.org>: > > Hi Sergey, > >> I think, something wrong has happened with dependencies in the latest >>

Re: FreeBSD Port: cairo-1.14.2,2

> Am 08.11.2015 um 14:53 schrieb Sergey Masharov : Hi Sergey, > I think, something wrong has happened with dependencies in the latest > major upgrade, because in the official release I see only: > > Dependency Changes > -- > > Cairo now requires glib 2.14

Re: Building mongodb with Poudriere?

Am 21.10.2015 um 18:53 schrieb Daniel Morante : > > I apologize for replying to an old thread, but it seems that this is still an > issue with Poudriere. > I have 6 GB of RAM on FreeBSD 10.1 64-bit and it still fails. > > However, I do not believe that this is a problem with

Re: Building mongodb with Poudriere?

> Am 21.10.2015 um 21:59 schrieb Martin Waschbüsch <mar...@waschbuesch.de>: > > I just tested with 10.2 amd64 and the build completed without errors. > Will setup a 10.1 jail and report my findings. Just finished testing the build on 10.1. I setup a clean ports tree

Re: FreeBSD Port: pgadmin3-1.20.0_1

> Am 19.10.2015 um 08:04 schrieb Christoph Moench-Tegeder : > > ## Daniel Malaby (d...@malaby.com): > >> Is there a way to get this to use postgres9.4 instead of 9.3? > > Add "postgresql=9.4" to DEFAULT_VERSIONS, e.g. in make.conf. Actually, the way I read

Obsolete PR 188752

Hi all, Just stumbled across PR 188752 which is in progress since 2014-04-18 and to me looks obsolete: The request seems to have been to update www/p5-CGI to a version greater than 3.63 (current at that time maybe?). Since the version the current port provides is the latest upstream version

Commiter needed for PR 200652

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200652 It's glue to use the existing ports p5-CGI-ExtDirect p5-RPC-ExtDirect with plack environment. It's been open since June, so perhaps someone could take pity and commit it? :-D Thanks! Martin signature.asc Description: Message signed