From owner-freebsd-current@FreeBSD.ORG Sat Jun 13 15:30:49 2015 Return-Path: Delivered-To: current@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 05B44B38 for ; Sat, 13 Jun 2015 15:30:49 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B3A129A for ; Sat, 13 Jun 2015 15:30:48 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by wigg3 with SMTP id g3so39317378wig.1 for ; Sat, 13 Jun 2015 08:30:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=HgDAd5lDP0b1FwkxPNd7vbTZFuhphw1xcj31iwbH9B4=; b=alWV3NhQeEjJ6DdegHCAVBucS+Uv3qZxX1mV/PdJrUoZBayAvPvzDuJpHsX65+R2Sa CXB3ZwLuCuhxuJBJflmdL+HJkyqBgNhJiV/a/5QDRuEi3whDQTX6EzR9f3smS6MEBR/O 9y9k0MRgy7CgPXxCGB1zTEaqMSQcMzp6YAMAWVOxfw9/mQsTXae8TX6chPSnU19sbVNa ak8TAooTpQv41qKc3abl16mNeB5gsJQH/9qz9181hkPD2TG9Ro+6q7pCW33t5XccP7YF rF8UCiPtSsiccK2smq8W0tRnreUn38dp7qIvA337mcuRVhcsbq56cvcF3FRI7cy3fdiI ODdQ== X-Gm-Message-State: ALoCoQlQ0Gk0S+C6sFjPceTTzriiQoNPh8omlOFtCM7va0DAS+KrJSYxzCBpIR6VzYBJHMjOEwMo MIME-Version: 1.0 X-Received: by 10.194.57.109 with SMTP id h13mr34639331wjq.67.1434209022833; Sat, 13 Jun 2015 08:23:42 -0700 (PDT) Received: by 10.194.162.225 with HTTP; Sat, 13 Jun 2015 08:23:42 -0700 (PDT) In-Reply-To: <20150613143546.GA2333@hub.FreeBSD.org> References: <20150613143546.GA2333@hub.FreeBSD.org> Date: Sat, 13 Jun 2015 17:23:42 +0200 Message-ID: Subject: Re: broken release generation when From: Oliver Pinter To: Glen Barber Cc: current@freebsd.org, FreeBSD Release Engineering Team Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jun 2015 15:30:49 -0000 On 6/13/15, Glen Barber wrote: > [re@ CC'd] > > On Sat, Jun 13, 2015 at 02:34:37PM +0200, Oliver Pinter wrote: >> Hi all! >> >> We got build error with custom BRANCH= in newvers.sh. The release >> process unable to generate the ISO files but they not stopped with >> error, just ignore them, and continue with memstick images. >> >> >> cp /jenkins/workspace/HardenedBSD-stable-master-amd64/release/rc.local >> bootonly/etc >> sh >> /jenkins/workspace/HardenedBSD-stable-master-amd64/release/amd64/mkisoimages.sh >> -b 11_0_CURRENT_HARDENEDBSD_amd64_BO bootonly.iso bootonly >> 100+0 records in >> 100+0 records out >> 409600 bytes transferred in 0.007822 secs (52361998 bytes/sec) >> newfs_msdos: cannot get number of sectors per track: Operation not >> supported >> newfs_msdos: cannot get number of heads: Operation not supported >> newfs_msdos: trim 44 sectors to adjust to a multiple of 63 >> /dev/md0: 717 sectors in 717 FAT12 clusters (512 bytes/cluster) >> BytesPerSec=512 SecPerClust=1 ResSectors=1 FATs=2 RootDirEnts=512 >> Sectors=756 Media=0xf8 FATsecs=3 SecPerTrack=63 Heads=1 HiddenSecs=0 >> makefs: error: The Disk Label must be at most 32 characters long >> usage: makefs [-t fs-type] [-o fs-options] [-d debug-mask] [-B endian] >> [-S sector-size] [-M minimum-size] [-m maximum-size] [-s image-size] >> [-b free-blocks] [-f free-files] [-F mtree-specfile] [-xZ] >> [-N userdb-dir] image-file directory | manifest [extra-directory ...] >> > > I think at this point either: > > 1) VOLUME_LABEL should be removed; or > 2) VOLUME_LABEL should be only set if 'uname -s' returns 'FreeBSD'. > > There have been multiple reports of issues with this, and the workaround > for edge cases is getting far too ugly at this point, so I prefer option > (1). > Hmm, and seems like the memstick builds are affected too: try to boot this: http://jenkins.hardenedbsd.org/builds/HardenedBSD-master-amd64/build-127/ISO-IMAGES/HardenedBSD-11-CURRENT_hardenedbsd-master-amd64-mini-memstick.img > Glen > >