www/nginx-devel redis module fetch error

[Jim Ohlstein]

Hello,

After the recent bump of the third party redis module to 0.3.9, I've
found it to be un-fetchable. See below:


=> ngx_http_redis-0.3.9.tar.gz doesn't seem to exist in /portdistfiles/.
=> Attempting to fetch
http://distcache.FreeBSD.org/local-distfiles/osa/ngx_http_redis-0.3.9.tar.gz
fetch:
http://distcache.FreeBSD.org/local-distfiles/osa/ngx_http_redis-0.3.9.tar.gz:
Not Found
=> Attempting to fetch
http://distcache.us-east.FreeBSD.org/local-distfiles/osa/ngx_http_redis-0.3.9.tar.gz
fetch:
http://distcache.us-east.FreeBSD.org/local-distfiles/osa/ngx_http_redis-0.3.9.tar.gz:
Not Found
=> Attempting to fetch
http://distcache.eu.FreeBSD.org/local-distfiles/osa/ngx_http_redis-0.3.9.tar.gz
fetch:
http://distcache.eu.FreeBSD.org/local-distfiles/osa/ngx_http_redis-0.3.9.tar.gz:
Not Found
=> Attempting to fetch
http://distcache.us-west.FreeBSD.org/local-distfiles/osa/ngx_http_redis-0.3.9.tar.gz
fetch:
http://distcache.us-west.FreeBSD.org/local-distfiles/osa/ngx_http_redis-0.3.9.tar.gz:
Not Found
=> Attempting to fetch
http://distcache.FreeBSD.org/ports-distfiles/ngx_http_redis-0.3.9.tar.gz
fetch:
http://distcache.FreeBSD.org/ports-distfiles/ngx_http_redis-0.3.9.tar.gz:
Not Found
=> Couldn't fetch it - please try to retrieve this
=> port manually into /portdistfiles/ and try again.
*** Error code 1

Stop.
make: stopped in /usr/ports/www/nginx-devel
=>> Cleaning up wrkdir
===>  Cleaning for nginx-devel-1.14.0_8
build of www/nginx-devel | nginx-devel-1.14.0_8 ended at Tue May 15
12:21:11 EDT 2018
build time: 00:00:30
!!! build failure encountered !!!

-- 
Jim Ohlstein
Professional Mailman Hosting
https://mailman-hosting.com



signature.asc
Description: OpenPGP digital signature

Re: sysutils/ansible and FLAVOR (Python 3.6 support)

[Christopher Hall]

Hello Kubilay,

On Tue, 15 May 2018 18:06:26 +1000, Kubilay Kocak 
wrote:

> On 15/05/2018 5:02 pm, Christopher Hall wrote:
> > Hello everyone,  
> 
> Hi Christopher,
> 
> > I am looking at which is the best way to modify the sysutils/ansible
> > port so that it will use Python3.6. Currently it has the "noflavors"
> > option in the USE_PYTHON line son only a single packages with
> > Python2.7 exists in the pkg repo.  
> 
> tldr: Add PYTHON_PKGNAMEPREFIX to the port if you want to produce a
> py3x version of the port. If you/we/users also want it from the
> official package repositories, remove noflavors.
> 
> > Should it be renamed to sysutils/py-ansible and "noflavors" removed?
> > To produce both py27-ansible and py36-ansible packages in repo,
> > allowing a choice of Python version  
> 
> The name of the directory is less relevant than whether a/the port
> uses PYTHON_PKGNAMEPREFIX (to differentiate package names when built
> with/for different Python versions. The current ansible port doesn't
> do this and it should (since it correctly allows all python versions
> with USES=python, without qualification)

Thanks for this, I put a patch in:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228268

> 
> > Alternatively, is it better to keep the name as sysutils/ansible and
> > just change the "USES=python" to "USES=python:3.6+".  However this
> > would make it a Python3 only package.
> > 
> > Any suggestions as to which approach would be preferable?  
> 
> The Python team recommends that if a Python package supports multiple
> Python versions (ansible does), then the port should reflect that and
> not force one version or another, and use PYTHON_PKGNAMEPREFIX. This
> includes Python packages supporting 2 & 3, and forcing 3.x or the
> reverse, forcing 2.x.
> 
> This at *least* allows a user to select which version of the
> port/package they want, using DEFAULT_VERSIONS overrides.
> 
> Separately, on the multiple flavours/package creation question in the
> official package repositories, we also recommend that noflavors only
> be used in the *very* rare cases where it is *entirely* irrelevant
> which Python version is used, and where there isn't any value
> *whatsoever* in having multiple packages, say if a user wants to
> transition between using a 2.x version to 3.x on their own time at
> their own pace.
> 
> tldr, for maintainers:
> 
> - User choice should not be removed/precluded
> - Be declarative, not imperative for Python ports/packages
> - If it supports > 1 Python versions (any combination), use
> PYTHON_PKGNAMEPREFIX


-- 
Best Regards.
Christopher Hall.
___
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 you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
deskutils/recoll| 1.23.7  | 1.24.1
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

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: sysutils/ansible and FLAVOR (Python 3.6 support)

[Matthew Seaman]

On 15/05/2018 08:02, Christopher Hall wrote:

Hello everyone,

I am looking at which is the best way to modify the sysutils/ansible
port so that it will use Python3.6. Currently it has the "noflavors"
option in the USE_PYTHON line son only a single packages with
Python2.7 exists in the pkg repo.


Should it be renamed to sysutils/py-ansible and "noflavors" removed?
To produce both py27-ansible and py36-ansible packages in repo,
allowing a choice of Python version

Alternatively, is it better to keep the name as sysutils/ansible and
just change the "USES=python" to "USES=python:3.6+".  However this would
make it a Python3 only package.

Any suggestions as to which approach would be preferable?



Having python-3.6 versions of ansible avaialbe in the default package 
repos is a good idea -- it's already easy enough to build-you-own 
ansible packages against python-3.6 and that works fine.  It's also fine 
to use that python-3.6-ized ansible against a host with only python-2.7 
installed.


Take a look at eg. the databases/phpmyadmin port for an example of a 
flavoured port that doesn't have a language dependent (in this case 
php-) prefix.  Just add PKGNAMESUFFIX and take away the noflavors from 
USES, plus add flavour markers to any dependencies that need them.


You'll end up with packages called ansible-py27 and ansible-py36.

Cheers,

Matthew
___
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: sysutils/ansible and FLAVOR (Python 3.6 support)

[Kubilay Kocak]

On 15/05/2018 5:02 pm, Christopher Hall wrote:
> Hello everyone,

Hi Christopher,

> I am looking at which is the best way to modify the sysutils/ansible
> port so that it will use Python3.6. Currently it has the "noflavors"
> option in the USE_PYTHON line son only a single packages with
> Python2.7 exists in the pkg repo.

tldr: Add PYTHON_PKGNAMEPREFIX to the port if you want to produce a py3x
version of the port. If you/we/users also want it from the official
package repositories, remove noflavors.

> Should it be renamed to sysutils/py-ansible and "noflavors" removed?
> To produce both py27-ansible and py36-ansible packages in repo,
> allowing a choice of Python version

The name of the directory is less relevant than whether a/the port uses
PYTHON_PKGNAMEPREFIX (to differentiate package names when built with/for
different Python versions. The current ansible port doesn't do this and
it should (since it correctly allows all python versions with
USES=python, without qualification)

> Alternatively, is it better to keep the name as sysutils/ansible and
> just change the "USES=python" to "USES=python:3.6+".  However this would
> make it a Python3 only package.
> 
> Any suggestions as to which approach would be preferable?

The Python team recommends that if a Python package supports multiple
Python versions (ansible does), then the port should reflect that and
not force one version or another, and use PYTHON_PKGNAMEPREFIX. This
includes Python packages supporting 2 & 3, and forcing 3.x or the
reverse, forcing 2.x.

This at *least* allows a user to select which version of the
port/package they want, using DEFAULT_VERSIONS overrides.

Separately, on the multiple flavours/package creation question in the
official package repositories, we also recommend that noflavors only be
used in the *very* rare cases where it is *entirely* irrelevant which
Python version is used, and where there isn't any value *whatsoever* in
having multiple packages, say if a user wants to transition between
using a 2.x version to 3.x on their own time at their own pace.

tldr, for maintainers:

- User choice should not be removed/precluded
- Be declarative, not imperative for Python ports/packages
- If it supports > 1 Python versions (any combination), use
PYTHON_PKGNAMEPREFIX
___
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"

sysutils/ansible and FLAVOR (Python 3.6 support)

[Christopher Hall]

Hello everyone,

I am looking at which is the best way to modify the sysutils/ansible
port so that it will use Python3.6. Currently it has the "noflavors"
option in the USE_PYTHON line son only a single packages with
Python2.7 exists in the pkg repo.


Should it be renamed to sysutils/py-ansible and "noflavors" removed?
To produce both py27-ansible and py36-ansible packages in repo,
allowing a choice of Python version

Alternatively, is it better to keep the name as sysutils/ansible and
just change the "USES=python" to "USES=python:3.6+".  However this would
make it a Python3 only package.

Any suggestions as to which approach would be preferable?

-- 
Best Regards.
Christopher Hall.
___
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"