On Wed, Apr 22, 2015 at 06:33:00PM +0300, Slawa Olhovchenkov wrote:> On Wed, Apr 22, 2015 at 12:10:37PM +0000, Glen Barber wrote: > > > On Wed, Apr 22, 2015 at 03:07:06PM +0300, Slawa Olhovchenkov wrote: > > > On Wed, Apr 22, 2015 at 11:55:59AM +0000, Glen Barber wrote: > > > > > > > On Wed, Apr 22, 2015 at 02:28:22PM +0300, Slawa Olhovchenkov wrote: > > > > > On Wed, Apr 22, 2015 at 11:18:44AM +0000, Glen Barber wrote: > > > > > > > bsdinstall don't ask about kernel.VSTREAM and don't install kernel.VSTREAM. > > > > > > > > > > > > > > What I miss? > > > > > > > > > > > > Currently, the installer only installs GENERIC. > > > > > > > > > > > > I have fixes for this in a projects branch, but it's not ready to merge > > > > > > back to head just yet. (^/projects/release-install-debug if you're > > > > > > interested.) > > > > > > > > > > I think also exist bug in scripts/make-manifest.sh: > > > > > > > > > > [...] > > > > > eval: ${kernel....}: Bad substitution > > > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > > > > Yes, you are correct. This is also fixed in the projects branch. > > > > > > O, I see. > > > Can you also patch release/Makefile? > > > > > > ==> > > .if !empty(TARGET:M${_V}) > > > OSRELEASE= ${TYPE}-${REVISION}-${BRANCH}-${TARGET} > > > VOLUME_LABEL= ${REVISION:C/[.-]/_/g}_${BRANCH:C/[.-]/_/g}_${TARGET} > > > .else > > > OSRELEASE= ${TYPE}-${REVISION}-${BRANCH}-${TARGET}-${TARGET_ARCH} > > > VOLUME_LABEL= ${REVISION:C/[.-]/_/g}_${BRANCH:C/[.-]/_/g}_${TARGET_ARCH} > > > .endif > > > ==> > > > > > For BRANCH/REVISION like 10.1-RELEASE-p276179 label exceed limit: > > > length(10_1_RELEASE_p281264_amd64_UEFIBO) = 33. > > > > > > > I'm not sure there's much we really can do about this just yet. The > > only solution I have for you at the moment is to set VOLUME_LABEL in > > your build environment to exclude the patch version. > > Can you see to 'release.sh'? > release.sh do 'make -C release release' w/o `make -C release clean`. > As result don't rebuild images. >This is actually intentional, so a subsequent invocation of release.sh does not clobber an existing build. Glen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20150422/e0377548/attachment.sig>
On Wed, Apr 22, 2015 at 03:43:25PM +0000, Glen Barber wrote:> On Wed, Apr 22, 2015 at 06:33:00PM +0300, Slawa Olhovchenkov wrote: > > On Wed, Apr 22, 2015 at 12:10:37PM +0000, Glen Barber wrote: > > > > > On Wed, Apr 22, 2015 at 03:07:06PM +0300, Slawa Olhovchenkov wrote: > > > > On Wed, Apr 22, 2015 at 11:55:59AM +0000, Glen Barber wrote: > > > > > > > > > On Wed, Apr 22, 2015 at 02:28:22PM +0300, Slawa Olhovchenkov wrote: > > > > > > On Wed, Apr 22, 2015 at 11:18:44AM +0000, Glen Barber wrote: > > > > > > > > bsdinstall don't ask about kernel.VSTREAM and don't install kernel.VSTREAM. > > > > > > > > > > > > > > > > What I miss? > > > > > > > > > > > > > > Currently, the installer only installs GENERIC. > > > > > > > > > > > > > > I have fixes for this in a projects branch, but it's not ready to merge > > > > > > > back to head just yet. (^/projects/release-install-debug if you're > > > > > > > interested.) > > > > > > > > > > > > I think also exist bug in scripts/make-manifest.sh: > > > > > > > > > > > > [...] > > > > > > eval: ${kernel....}: Bad substitution > > > > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > > > > > > > Yes, you are correct. This is also fixed in the projects branch. > > > > > > > > O, I see. > > > > Can you also patch release/Makefile? > > > > > > > > ==> > > > .if !empty(TARGET:M${_V}) > > > > OSRELEASE= ${TYPE}-${REVISION}-${BRANCH}-${TARGET} > > > > VOLUME_LABEL= ${REVISION:C/[.-]/_/g}_${BRANCH:C/[.-]/_/g}_${TARGET} > > > > .else > > > > OSRELEASE= ${TYPE}-${REVISION}-${BRANCH}-${TARGET}-${TARGET_ARCH} > > > > VOLUME_LABEL= ${REVISION:C/[.-]/_/g}_${BRANCH:C/[.-]/_/g}_${TARGET_ARCH} > > > > .endif > > > > ==> > > > > > > > For BRANCH/REVISION like 10.1-RELEASE-p276179 label exceed limit: > > > > length(10_1_RELEASE_p281264_amd64_UEFIBO) = 33. > > > > > > > > > > I'm not sure there's much we really can do about this just yet. The > > > only solution I have for you at the moment is to set VOLUME_LABEL in > > > your build environment to exclude the patch version. > > > > Can you see to 'release.sh'? > > release.sh do 'make -C release release' w/o `make -C release clean`. > > As result don't rebuild images. > > > > This is actually intentional, so a subsequent invocation of release.sh > does not clobber an existing build. >What purpose? Do all makes and don't make new images?