Re: New FreeBSD snapshots available: head (20160701 r302303)
On Sat, Jul 02, 2016 at 09:26:14AM +0300, Ivan Klymenko wrote:
> On Sat, 2 Jul 2016 06:19:58 +
> Glen Barber wrote:
> ivan@nonamehost:/ % ftp
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/11.0-ALPHA6 Trying
> 77.88.40.106:21 ... Connected to ftp.geo.freebsd.org.
> 220 This is ftp0.ydx.freebsd.org - hosted at Yandex.
> 331 Please specify the password.
> 230-
> 230-This is ftp0.ydx.FreeBSD.org, graciously hosted by Yandex.
> 230-
> 230-FreeBSD files can be found in the /pub/FreeBSD directory.
> 230-
> 230 Login successful.
> Remote system type is UNIX.
> Using binary mode to transfer files.
> 200 Switching to Binary mode.
> 250 Directory successfully changed.
> 250-ISO images of FreeBSD releases may be found in the
> releases/ISO-IMAGES 250-directory. For independent files and tarballs,
> see individual 250-releases/${machine}/${machine_arch} directories.
> For example, 250-releases/amd64/amd64 and releases/powerpc/powerpc64.
> 250 Directory successfully changed.
> 250 Directory successfully changed.
> 250 Directory successfully changed.
> local: 11.0-ALPHA6 remote: 11.0-ALPHA6
> ftp: Can't access `11.0-ALPHA6': Permission denied
> 221 Goodbye.
These are snapshots, not official releases. Again:
Please be patient if your local FTP mirror has not yet caught
up with the changes.
Glen
signature.asc
Description: PGP signature
Re: New FreeBSD snapshots available: head (20160701 r302303)
On Sat, 2 Jul 2016 06:19:58 +
Glen Barber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> New FreeBSD development branch installation ISOs and virtual machine
> disk images have been uploaded to the FTP mirrors.
>
> As with any development branch, the installation snapshots are not
> intended for use on production systems. We do, however, encourage
> testing on non-production systems as much as possible.
>
> Please also consider installing the sysutils/panicmail port, which can
> help in providing FreeBSD developers the necessary information
> regarding system crashes.
>
> Checksums for the installation ISOs and the VM disk images follow at
> the end of this email.
>
ivan@nonamehost:/ % ftp
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/11.0-ALPHA6 Trying
77.88.40.106:21 ... Connected to ftp.geo.freebsd.org.
220 This is ftp0.ydx.freebsd.org - hosted at Yandex.
331 Please specify the password.
230-
230-This is ftp0.ydx.FreeBSD.org, graciously hosted by Yandex.
230-
230-FreeBSD files can be found in the /pub/FreeBSD directory.
230-
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
200 Switching to Binary mode.
250 Directory successfully changed.
250-ISO images of FreeBSD releases may be found in the
releases/ISO-IMAGES 250-directory. For independent files and tarballs,
see individual 250-releases/${machine}/${machine_arch} directories.
For example, 250-releases/amd64/amd64 and releases/powerpc/powerpc64.
250 Directory successfully changed.
250 Directory successfully changed.
250 Directory successfully changed.
local: 11.0-ALPHA6 remote: 11.0-ALPHA6
ftp: Can't access `11.0-ALPHA6': Permission denied
221 Goodbye.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Unable to 'make config' ports under FreeBSD current
On 2016-07-01 10:56, Larry Baird wrote: > I recently installed FreebSD current using a snapshot ISO. I then used svnlite > to bring FreeBSD source up to date. I then used portsnap fetch extract to > bring my ports tree up todate. I was surprised I got errors doing 'make > config' > for a port. I assumed it was a transitory problem. I have brought my system > and ports up to date several times over the last few weeks, but the issue > remains. The fix to the Makefile for the port to fix the issue is pretty > simple. I figured I would soon see other people complainging about the issue. > Since nobody has, I wonder if it is something in my environment. Is anybody > else having this issue? > > uname -a shows I am running > > FreeBSD snake32.gta.com 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #0 r302305: Fri Jul > 1 03:45:06 EDT 2016 > r...@snake32.gta.com:/usr/obj/usr/src/sys/GENERIC-NODEBUG i386 > > > make config > ===> Building/installing dialog4ports as it is required for the config dialog > ===> Cleaning for dialog4ports-0.1.5_2 > ===> License BSD2CLAUSE accepted by the user > ===> dialog4ports-0.1.5_2 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by dialog4ports-0.1.5_2 for building > ===> Extracting for dialog4ports-0.1.5_2 > => SHA256 Checksum OK for dialog4ports-0.1.5.tar.gz. > ===> Patching for dialog4ports-0.1.5_2 > ===> Configuring for dialog4ports-0.1.5_2 > ===> Building for dialog4ports-0.1.5_2 > make[3]: "/usr/src/share/mk/src.libnames.mk" line 390: > /usr/ports/ports-mgmt/dialog4ports/work/dialog4ports-0.1.5: These libraries > should be LIBADD+=foo rather than DPADD/LDADD+=-lfoo: ncursesw m dialog > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make[2]: stopped in /usr/ports/ports-mgmt/dialog4ports > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/ports-mgmt/dialog4ports > ===> Options unchanged > > Are you sure the portsnap process finished successfully? It appears to be trying to use the FreeBSD 9.x/10.x syntax for adding the dependencies of dialog4ports, rather than the 11.x method. -- Allan Jude signature.asc Description: OpenPGP digital signature
Unable to 'make config' ports under FreeBSD current
I recently installed FreebSD current using a snapshot ISO. I then used svnlite to bring FreeBSD source up to date. I then used portsnap fetch extract to bring my ports tree up todate. I was surprised I got errors doing 'make config' for a port. I assumed it was a transitory problem. I have brought my system and ports up to date several times over the last few weeks, but the issue remains. The fix to the Makefile for the port to fix the issue is pretty simple. I figured I would soon see other people complainging about the issue. Since nobody has, I wonder if it is something in my environment. Is anybody else having this issue? uname -a shows I am running FreeBSD snake32.gta.com 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #0 r302305: Fri Jul 1 03:45:06 EDT 2016 r...@snake32.gta.com:/usr/obj/usr/src/sys/GENERIC-NODEBUG i386 make config ===> Building/installing dialog4ports as it is required for the config dialog ===> Cleaning for dialog4ports-0.1.5_2 ===> License BSD2CLAUSE accepted by the user ===> dialog4ports-0.1.5_2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by dialog4ports-0.1.5_2 for building ===> Extracting for dialog4ports-0.1.5_2 => SHA256 Checksum OK for dialog4ports-0.1.5.tar.gz. ===> Patching for dialog4ports-0.1.5_2 ===> Configuring for dialog4ports-0.1.5_2 ===> Building for dialog4ports-0.1.5_2 make[3]: "/usr/src/share/mk/src.libnames.mk" line 390: /usr/ports/ports-mgmt/dialog4ports/work/dialog4ports-0.1.5: These libraries should be LIBADD+=foo rather than DPADD/LDADD+=-lfoo: ncursesw m dialog ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[2]: stopped in /usr/ports/ports-mgmt/dialog4ports *** Error code 1 Stop. make[1]: stopped in /usr/ports/ports-mgmt/dialog4ports ===> Options unchanged -- Larry Baird Global Technology Associates, Inc. 1992-2012| http://www.gta.com Celebrating Twenty Years of Software Innovation | Orlando, FL Email: l...@gta.com | TEL 407-380-0220 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
