[OmniOS-discuss] Problem with using omnios-build

[Carl Brunning]

HI just to say I've fixed it
so it all good now

thanks
Carl Brunning
________________________________________
From: Carl Brunning
Sent: 26 March 2014 22:45
To: Carl Brunning; Dan McDonald
Cc: omnios-discuss at lists.omniti.com
Subject: RE: [OmniOS-discuss] Problem with using omnios-build

Anyone
Sorry if am pain just want to learn from this
And why it not work

Thanks
carl brunning

-----Original Message-----
From: OmniOS-discuss [mailto:omnios-discuss-bounces at lists.omniti.com] On Behalf Of Carl Brunning
Sent: 26 March 2014 11:13
To: Dan McDonald
Cc: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] Problem with using omnios-build

Thanks for that yes that help me a little more Now I just got to work out why it has a problem uploading to the repo This is the error I get

PATH=/tmp/build_admin/pkg-1.0/pkg/src/pkg/../../proto/root_i386/usr/bin:/usr/sbin:/usr/bin  PYTHONPATH=/tmp/build_admin/pkg-1.0/pkg/src/pkg/../../proto/root_i386/usr/lib/python2.6/vendor-packages pkgsend -s http://repo.flamewarestudios.com:10000/ publish -d /tmp/build_admin/pkg-1.0/pkg/src/pkg/../../proto/root_i386 \
        -d license_files -T \*.py --fmri-in-manifest  \
        pkgtmp/SUNWipkg-brand.dep.res
pkgsend: Transfer from 'http://repo.removeed failed: api_errors.InvalidP5IFile:. (happened 4 times)

the repo is a openindiana system
could this be my problem now
I have got most of the other package compile and up load with no problems Just pkg one is the problem

Thanks

Carl Brunning
-----Original Message-----
From: Dan McDonald [mailto:danmcd at omniti.com]
Sent: 25 March 2014 17:15
To: Carl Brunning
Cc: omnios-discuss at lists.omniti.com
Subject: Re: [OmniOS-discuss] Problem with using omnios-build


On Mar 25, 2014, at 12:27 PM, Carl Brunning <carlb at flamewarestudios.com> wrote:

> HI
> am playing with the omnios-build
> but when trying to do pkg build i find on the git clone it having a
> problem the line is this logcmd $GIT clone -b $PKG_BRANCH
> src at src.omniti.com:~omnios/core/pkg
>
> the branch is r151006

I fixed some things in "master" to this.  It should've just swapped out "src@" for "anon@".

> this is wanting a password but I don't know what it is i did see on
> the latest version of the build you have changed to this
>
> logcmd  $GIT clone -b omni
> anon at src.omniti.com:~omnios/core/illumos-omni-os

Hmmm.  This is a very old artifact.  The "master" version has this changeset:

osdev2(build/pkg)[0]% git show --stat 85f25c28 commit 85f25c28969c859fb9bc838a6779dd3a70286896
Author: Theo Schlossnagle <jesus at omniti.com>
Date:   Sat Mar 24 20:06:12 2012 +0000

    move pkg to git and make it work

 build/pkg/build.sh | 47 ++++++++++++++++++++++++++++-------------------
 1 file changed, 28 insertions(+), 19 deletions(-) osdev2(build/pkg)[0]%

that eliminates the need for the clone to happen.

Generally speaking, though, it's illumos-omnios:

        anon at src.omniti.com:~omnios/core/illumos-omnios

Perhaps fixing that will work?

> so why it asking for a password for the first one lol

That's a bug.  I didn't fix it in anywhere other than master, though.

> and what is it
> and i hope you fix it all

I'm curious if pkg can be re-rewhacked to use headers from a completed omnios build?  I'm introducing new features into omnios-build to make it completely fire-and-forget.  One new feature not yet back is the PREBUILT_OMNIOS feature, that can point packages that depend on a populated illumos-omnios proto area.  Perhaps I should include PREBUILT_OMNIOS support in pkg as well?!

Pardon any slowness on my part.  I'm new at pkg, and at the build outside of illumos-omnios itself.

Thanks,
Dan



_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss