Hey Jason,

Have you uploaded  your modified nexenta-builder package, with the 2
changes? Adding the latest memtest should be fine.

~Anil

On Fri, Jan 16, 2009 at 9:34 PM, Jason Upton <wavejumpe...@gmail.com> wrote:
> OK, I have figured out most of it.  In nbld-bootstrap, I changed:
>
>  --component=main
>
> to:
>
>  --component==main,contrib,non-free
>
> And I also had to change the hardy-unstable.bootstrap file:
>
>  mirror_style main
>
> to:
>
>  mirror_style release
>
> The mirror_style of main forces debootstrap into only finding packages
> from a hard-coded main repository regardless of what --components is
> set to.
>
> This is related to the "main-only" zone install issues as well.  The
> /usr/lib/nexenta-zones/hardy-unstable.bootstrap file for the zones has
> mirror_style set to "main".  If I change that to "release" along with
> a change to /usr/lib/lu/lucreatezone to change the debootstrap option
> to "--components=main,contrib,non-free" then packages like nvi can be
> found during the zone install.
>
> The extra contrib directory hierarchy I mentioned does not seem to
> affect any of this.  The Packages file in the repository knows the
> real location and it gets passed to debootstrap properly.  So while it
> looks strange, it still works.
>
> My next problem is related to an apparent "ed" and "base-file"
> conflict - the nexenta-builder and zone install are now both failing
> due to "ed" creating /bin/ed and base-files wanting to create a
> symlink from /bin to /usr/bin.  But the dependencies are such that
> "ed" is installed before "base-files" (so the symlink creation errors
> out).  I was going to change "ed" to install to /usr/bin/ed but I
> cannot find the source package in the repo....  Anyone know where it's
> at?  Maybe I'll just re-upload it from upstream source.
>
> I will fix the nexenta-builder and nexenta-zones packages with the
> changes and upload unless someone sees a flaw/problem with what I
> mentioned.
>
> And while I'm updating nexenta-builder, does anyone object to updating
> memtest86+ to the latest version (v2.11)?  I need the latest to
> properly test one of my motherboards/chipsets.
>
> Thanks,
> Jason
>
> On Thu, Jan 15, 2009 at 8:04 PM, Jason Upton <wavejumpe...@gmail.com> wrote:
>> I'm trying to run nbld-bootstrap and notice that the dialog package
>> which is required for nexenta-install.sh is not in main anymore.
>> Seems that Ubuntu has moved it to universe (even though Debian still
>> has it in main) and thus the package is now in contrib for NCP2.  So
>> the debootstrap command inside nbld-bootstrap fails to get the dialog
>> package.
>>
>> But I noticed while digging into this that debootstrap has an option
>> "--components" that is supposed to allow us to get packages from more
>> than one place within the repository.  I tried
>> "--components=main,contrib,non-free" but still cannot get the dialog
>> package included in the bootstrap.  Maybe I misunderstand the usage...
>>
>> So I looked a bit further at the repository and see that there appears
>> to be an extra "contrib" directory under most areas.  For example,
>> under main there is main/binary-solaris-i386/misc and
>> main/binary-solaris-i386/contrib/misc directories.  And under contrib
>> there is contrib/binary-solaris-i386/misc and
>> contrib/binary-solaris-i386/contrib/misc.  The dialog package resides
>> in this apparently extra "contrib" directory:
>>
>> /tank/ncp2/dists/hardy-unstable/contrib/binary-solaris-i386/contrib/misc/dialog_1.1-20071028-3_solaris-i386.deb
>>
>> So I'm wondering if this is why debootstrap can't find the package in
>> the contrib area?  Anyone else run across this?  I know there have
>> been discussions about debootstrap only supporting main (for zone
>> installs), but it seems that this "--component" option is supposed to
>> address that.
>>
>> Thanks for any thoughts/ideas/etc,
>> Jason
>>
> _______________________________________________
> gnusol-devel mailing list
> gnusol-devel@lists.sonic.net
> http://lists.sonic.net/mailman/listinfo/gnusol-devel
>
_______________________________________________
gnusol-devel mailing list
gnusol-devel@lists.sonic.net
http://lists.sonic.net/mailman/listinfo/gnusol-devel

Reply via email to