- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 15 2018
Apr 8 2018
Apr 5 2018
Apr 2 2018
Mar 31 2018
Yeah. This approach is a non-starter. Adding django bits to python.mk is probably a better route as Antoine suggests,
but that'sbasically a start-over.
Mar 30 2018
Mar 25 2018
Mar 17 2018
Mar 15 2018
Mar 12 2018
Ah -- I see cpm@ has commented on the bugzilla PR. Remember to add him to the Approved by: line when you commit.
This looks OK, on the face of it, although I'm having some (hopefully temporary) local troubles getting a test build to work.
Are you in contact with the chromium@ developers? According to https://wiki.freebsd.org/Chromium that's rene@freebsd.org or cpm@freebsd.org:
it might be worth adding them as reviewers.
Mar 7 2018
Mar 6 2018
Mar 1 2018
Feb 23 2018
Feb 22 2018
Feb 20 2018
Feb 19 2018
Feb 16 2018
Feb 9 2018
but you should create (and get reviewed) a VuXML entry for the vulnerabilities before you commit, and reference the VuXML from your commit
message. The 'Security' tab in the commit template should contain the VuXMLid, although it is frequently used for other identifying numbers.
Feb 8 2018
Feb 4 2018
Jan 29 2018
In D14102#295965, @yuri wrote:The submitter says in Bugzilla that he obtained the 0mp@FreeBSD.org address during the Google Summer of Code. He also uses this address for one other port.
Either this address can be kept as MAINTAINER, or it can also be changed to his other e-mail address.
Jan 17 2018
Jan 16 2018
LGTM, but remember that you should get maintainer approval before committing.
Considering the recent changes in ports to do with FLAVORS, which has definitively broken the 1-to-1 relation between pkg name and port origin, is this change still desirable?
Jan 11 2018
Jan 10 2018
Jan 7 2018
Jan 5 2018
Jan 4 2018
- Merge branch 'master' into arcpatch-D12592
- Add new py-django-netfields port
Jan 3 2018
- Merge branch 'master' into arcpatch-D12592
Jan 2 2018
- Merge branch 'master' into arcpatch-D12592
Jan 1 2018
- Merge branch 'master' into arcpatch-D12592
Dec 31 2017
Fix remaining build problems. Every Django related port now builds
correctly.
Major rework of the code, modelled on python.mk
Dec 29 2017
Dec 23 2017
Dec 21 2017
In D12592#283856, @mat wrote:
In D12592#283656, @ultima wrote:In D12592#283142, @matthew wrote:Merge upstream changes -- ie. package flavours. www/seahub is
problematic, causing the whole poudriere bulk to fail if included in
the list of package targets. Other than that, builds correctly with
both py27 and py36.Creating django111 and django20 flavours would be interesting, but
that implies packages with multiple flavors which is a problem.
- Use the Django pkgname prefix for dependencies
- Add django-2.0 to the list of possible versions.
ToDo:
fix www/seahub DJANGO_REL -- release value equivalent to PYTHON_RELIt maybe time to rename the port to py-seahub. Is this the issue you are running into? Seahub only runs on py27 and django 18. Let me know if there is anything I can assist with.
Dec 19 2017
Merge upstream changes -- ie. package flavours. www/seahub is
problematic, causing the whole poudriere bulk to fail if included in
the list of package targets. Other than that, builds correctly with
both py27 and py36.
Dec 13 2017
Test build shows plist problems -- seems there are files left over:
=>> Checking for extra files and directories =>> Error: Files or directories left over: @dir share/vim/vimfiles @dir share/vim/vimfiles/doc share/vim/vimfiles/doc/tags build of devel/youcompleteme | YouCompleteMe-g20171203 ended at Wed Dec 13 12:43:26 GMT 2017 build time: 00:04:55
Dec 12 2017
In D12592#281340, @mat wrote:So, this is the time to update this and make it use flavors no ?
Dec 2 2017
Dec 1 2017
Note: be sure to use ${PORTSDIR}/Tools/scripts/addport to commit your new port -- this will ensure that it gets hooked up to the ports tree correctly.
LGTM
Nov 30 2017
Nov 29 2017
Nov 27 2017
Nov 26 2017
LGTM
Nov 19 2017
Track upstream changes
Nov 17 2017
Nov 7 2017
Nov 4 2017
Nov 2 2017
Oct 31 2017
Oct 28 2017
Oct 23 2017
Oct 21 2017
The distfiles aren't fetching correctly for me:
===> License APACHE20 BSD3CLAUSE NCSA accepted by the user ===> llbuild-s.2016.11.01 depends on file: /usr/local/sbin/pkg - found => apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz doesn't seem to exist in /portdistfiles/. => Attempting to fetch https://codeload.github.com/apple/swift-llbuild/tar.gz/swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a?dummy=/apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz fetch: https://codeload.github.com/apple/swift-llbuild/tar.gz/swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a?dummy=/apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz: size unknown fetch: https://codeload.github.com/apple/swift-llbuild/tar.gz/swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a?dummy=/apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz: size of remote file is not known apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0 0 B 0 Bps => Fetched file size mismatch (expected 4718056, actual 4718070) => Trying next site => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz fetch: http://distcache.FreeBSD.org/ports-distfiles/apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz: Not Found => Attempting to fetch |/usr/games/randomapple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz fetch: |/usr/games/randomapple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz: Invalid URL scheme => Attempting to fetch -wapple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz fetch: invalid delay (apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz) => Attempting to fetch -fapple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host] [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file] [-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list] [--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer] [-o file] [--referer=URL] [-S bytes] [-T seconds] [--user-agent=agent-string] [-w seconds] URL ... fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host] [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file] [-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list] [--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer] [-o file] [--referer=URL] [-S bytes] [-T seconds] [--user-agent=agent-string] [-w seconds] -h host -f file [-c dir] => Attempting to fetch -apple-swift-llbuild-swift-DEVELOPMENT-SNAPSHOT-2016-11-01-a_GH0.tar.gz fetch: invalid option -- e usage: fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host] [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file] [-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list] [--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer] [-o file] [--referer=URL] [-S bytes] [-T seconds] [--user-agent=agent-string] [-w seconds] URL ... fetch [-146AadFlMmnPpqRrsUv] [-B bytes] [--bind-address=host] [--ca-cert=file] [--ca-path=dir] [--cert=file] [--crl=file] [-i file] [--key=file] [-N file] [--no-passive] [--no-proxy=list] [--no-sslv3] [--no-tlsv1] [--no-verify-hostname] [--no-verify-peer] [-o file] [--referer=URL] [-S bytes] [-T seconds] [--user-agent=agent-string] [-w seconds] -h host -f file [-c dir] => Couldn't fetch it - please try to retrieve this => port manually into /portdistfiles/ and try again. *** Error code 1
Since you created the PR a month ago, you can commit this now with:
- Revert accidental inclusion of sysutils/rsyslog8
- Revert accidental inclusion of devel/libfastjson
- Whitespace changes only
Merge upstream changes
Oct 20 2017
Oct 18 2017
Oct 16 2017
Oct 15 2017
Remove the '.' from the Django version in DJANGO_PKGNAMEPREFIX, so it
now looks like: py27-django111-
Oct 10 2017
www/seahub requires django-1.8
Oct 9 2017
Oct 8 2017
Make version numbers include the decimal point like so:
USES+=django:1.11 -- consistent with DEFAULT_VERSIONS. This also
affects DJANGO_PKGNAMEPREFIX, which now looks like py27-django1.11-
Oct 6 2017
In D12592#261434, @sunpoet wrote:I would suggest to use USES=django:1.11 instead of USES=django:111 to be consistent with bsd.default-versions.mk and upstream versioning,