SliTaz Forum

jfreivald

Member

Registered: 2012-05-28

Posts: 8

Http 401 when cooking new spice packages I'm working on

I'm creating taz packages for the spice client for running SliTaz under a spice-based hypervisor.

The spice-protocol package built without a hitch.  I'm working on the spice-vdagent package and when I cook it I get an HTTP/1.1 416.  If I copy and paste the wget line to the shell prompt it works fine.  I looked at the cook script, but I don't see anything out of the ordinary there.  Any help would be appreciated.

Here is the error and the receipts for the spice-protocol and spice-vdagent packages:

------------BEGIN---------------

root@slitaz-dev:/home/slitaz/wok# cook spice-vdagent

Setup aufs chroot...

Cook: spice-vdagent 0.10.1

================================================================================

QA: checking package receipt...

Checking build dependencies...

Extracting: spice-vdagent-0.10.1.tar.bz2

Connecting to spice-space.org (209.132.180.99:80)

wget: server returned error: HTTP/1.1 416 Requested Range Not Satisfiable

ERROR: wget http://spice-space.org/download/releases/spice-vdagent-0.10.1.tar.bz2

Extracting: spice-vdagent-0.10.1.tar.bz2

ERROR: cook failed

Debug information

================================================================================

Cook date: 2012-06-07 17:22

ERROR: wget http://spice-space.org/download/releases/spice-vdagent-0.10.1.tar.bz2

ERROR: cook failed

wget: server returned error: HTTP/1.1 416 Requested Range Not Satisfiable

================================================================================

Leaving aufs chroot...

-------------END----------------

------------BEGIN---------------

# SliTaz package receipt.

PACKAGE="spice-protocol"

VERSION="0.10.1"

CATEGORY="x-window"

SHORT_DESC="Spice protocol for spice-based virtual displays"

MAINTAINER="Joseph Freivald"

WEB_SITE="http://spice-space.org"

TARBALL="$PACKAGE-$VERSION.tar.bz2"

WGET_URL="http://spice-space.org/download/releases/$TARBALL"

DEPENDS=""

BUILD_DEPENDS=""

# Rules to configure and make the package.

compile_rules()

{

    cd $src

    ./configure \

        --prefix=/usr \

        --sysconfdir=/etc \

        --mandir=/usr/share/man \

        --localstatedir=/var \

        $CONFIGURE_ARGS &&

    make && make DESTDIR=$PWD/_pkg install

}

# Rules to gen a SliTaz package suitable for Tazpkg.

genpkg_rules()

{

    cp -a $install/* $fs

}

-------------END----------------

------------BEGIN---------------

# SliTaz package receipt.

PACKAGE="spice-vdagent"

VERSION="0.10.1"

CATEGORY="x-window"

SHORT_DESC="VDAgent for spice clients"

MAINTAINER="Joseph Freivald"

DEPENDS="dbus xorg-libpciaccess"

BUILD_DEPENDS="spice-protocol dbus-dev xorg-libpciaccess-dev"

TARBALL="$PACKAGE-$VERSION.tar.bz2"

WEB_SITE="http://spice-space.org"

WGET_URL="http://spice-space.org/download/releases/$TARBALL"

# Rules to configure and make the package.

compile_rules()

{

    cd $src

    ./configure \

        --prefix=/usr \

        --sysconfdir=/etc \

        --mandir=/usr/share/man \

        --localstatedir=/var \

        $CONFIGURE_ARGS &&

    make && make DESTDIR=$PWD/_pkg install

}

# Rules to gen a SliTaz package suitable for Tazpkg.

genpkg_rules()

{

    cp -a $install/* $fs

}

-------------END----------------

pipein

Member

Registered: 2012-05-30

Posts: 46

Re: Http 401 when cooking new spice packages I'm working on

@jfreivald

I'm not getting your error here (I created new empty packages in Cook and pasted your receipts from your post).

As you said spice-protocol cooks without problems.

spice-vdagent retrieved the tarball fine here without error, but has other errors in the configure step (not unexpecting if its still a work in progress).  You'll see it soon enough, but the first error is re: checking for X.

jfreivald

Member

Registered: 2012-05-28

Posts: 8

Re: Http 401 when cooking new spice packages I'm working on

Yep. I hadn't started the dependencies list yet.

It's such a weird error.  It's acting as if the wget is requesting a file chunk that is past the end of the file.

jfreivald

Member

Registered: 2012-05-28

Posts: 8

Re: Http 401 when cooking new spice packages I'm working on

I tried two things with the script:

1) using the non-busybox wget - no effect

2) removing the -c switch from the command line in /usr/bin/cook, line 207 - This removed the error and the package built successfully.

Odd.

--JATF

pipein

Member

Registered: 2012-05-30

Posts: 46

Re: Http 401 when cooking new spice packages I'm working on

@jfreivald

I was just typing when you posted.

Since pasting the wget line works in the shell, and the non-busybox wget had no change, that rules out the common causes of the error.  Something odd there somewhere.

Maybe a binary/control/non-printable character crept into the receipt file?  Particularly around the end of the wget line.

PS

I had to add xorg-libXrandr-dev to the BUILD-DEPENDS line for the build to complete here without error.

jfreivald

Member

Registered: 2012-05-28

Posts: 8

Re: Http 401 when cooking new spice packages I'm working on

I'm just leaving out the -c in my cook script for now so that I can move on.  I'll get back to it later when I cook from a fresh install.

A tangential question:

I'm trying to get the spice server to build and it depends on a library called slirp.  The build page for the spice server gives a git repository for it, but I can't find the upstream source.  There are 3 slirp applications/libraries that I've located and none of them are the right ones.  I was trying to use a wget with the git:// prefix, and it does download the source and create the tarball, but the cook dies because it then tries to wget the tarball from mirror.slitaz.org.  Is there a way to tell it to use the local source package instead of trying to hit the mirror when using a git source?

--JATF

pipein

Member

Registered: 2012-05-30

Posts: 46

Re: Http 401 when cooking new spice packages I'm working on

@jfreivald

I'm not expert in cooking packages with these tools, but thought I'd share what I have in the interim while waiting for a guru to assist.

Sorry if this is bleedingly obvious to you.

I guess the first port of call re: using git with wget in a receipt is the existing documentation like:

http://doc.slitaz.org/en:devnotes:new-tazwok-illustrated

Next would be looking at existing receipts which use git within wget_url and the use of the standard variables, e.g.:

- yagl http://pkgs.slitaz.org/search.sh?receipt=yajl&version=s

- pyrRadio http://pkgs.slitaz.org/search.sh?receipt=pyradio&version=s

I had assumed that the local copy of the source (correctly named/located) would get picked up.

There is always the remote possibilty that something is screwy in your environment, .

I found an http url for a slirp tarball, it thats any use in the short term.

http://cgit.freedesktop.org/spice/slirp/snapshot/slirp-master.tar.gz

pipein

Member

Registered: 2012-05-30

Posts: 46

Re: Http 401 when cooking new spice packages I'm working on

... of course that should be yajl and pyradio

bellard

Administrator

Registered: 2011-03-28

Posts: 657

Re: Http 401 when cooking new spice packages I'm working on

Try this:

# rm -f /home/slitaz/src/spice-vdagent-0.10.1.tar.bz2

# cook spice-vdagent

If you push your work in the undigest wok, every body will be able to help you.

http://hg.slitaz.org/wok-undigest/

jfreivald

Member

Registered: 2012-05-28

Posts: 8

Re: Http 401 when cooking new spice packages I'm working on

Will do.

My son is in port this weekend so it will have to wait until Monday.  Thanks for the help.

--JATF