Quantum-9999

[ghost]

• Messages for package net-misc/quantum-9999:
• Failed Patch: server-setup-disable-initd-install.patch !
• ( /var/lib/layman/openstack/net-misc/quantum/files/server-setup-disable-initd-install.patch ) *
• Include in your bugreport the contents of: *
• /var/tmp/portage/net-misc/quantum-9999/temp/server-setup-disable-initd-install.patch.out
• ERROR: net-misc/quantum-9999 failed (prepare phase):
• Failed Patch: server-setup-disable-initd-install.patch! *
• Call stack:
• ebuild.sh, line 93: Called src_prepare
• environment, line 5390: Called epatch '/var/lib/layman/openstack/net-misc/quantum/files/server-setup-disable-initd-install.patch'
• environment, line 1948: Called die
• The specific snippet of code:
• die "Failed Patch: ${patchname}!"; *
• If you need support, post the output of emerge --info '=net-misc/quantum-9999',
• the complete build log and the output of emerge -pqv '=net-misc/quantum-9999'.
• This ebuild used the following eclasses from overlays:
• /var/lib/layman/openstack/eclass/user.eclass
• This ebuild is from an overlay named 'x-openstack': '/var/lib/layman/openstack/'
• The complete build log is located at '/var/tmp/portage/net-misc/quantum-9999/temp/build.log'.
• The ebuild environment file is located at '/var/tmp/portage/net-misc/quantum-9999/temp/environment'.
• Working directory: '/var/tmp/portage/net-misc/quantum-9999/work/quantum-9999'
• S: '/var/tmp/portage/net-misc/quantum-9999/work/quantum-9999'

[ghost]

ah the patch is just old...

* server-setup-disable-initd-install.patch * PWD: /var/tmp/portage/net-misc/quantum-9999/work/quantum-9999

PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/openstack/net-misc/quantum/files/server-setup-disable-initd-install.patch'

checking file setup.py Hunk #1 FAILED at 66. 1 out of 1 hunk FAILED

patch program exited with status 1

PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/openstack/net-misc/quantum/files/server-setup-disable-initd-install.patch'

can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

|--- setup.py.orig 2012-02-02 12:26:50.000000000 +0100

|+++ setup.py 2012-02-02 13:05:46.000000000 +0100

No file to patch. Skipping patch. 1 out of 1 hunk ignored

patch program exited with status 1

PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/openstack/net-misc/quantum/files/server-setup-disable-initd-install.patch'

can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

|--- setup.py.orig 2012-02-02 12:26:50.000000000 +0100

|+++ setup.py 2012-02-02 13:05:46.000000000 +0100

No file to patch. Skipping patch. 1 out of 1 hunk ignored

patch program exited with status 1

PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/openstack/net-misc/quantum/files/server-setup-disable-initd-install.patch'

can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

|--- setup.py.orig 2012-02-02 12:26:50.000000000 +0100

|+++ setup.py 2012-02-02 13:05:46.000000000 +0100

No file to patch. Skipping patch. 1 out of 1 hunk ignored

patch program exited with status 1

PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < '/var/lib/layman/openstack/net-misc/quantum/files/server-setup-disable-initd-install.patch'

can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

|--- setup.py.orig 2012-02-02 12:26:50.000000000 +0100

|+++ setup.py 2012-02-02 13:05:46.000000000 +0100

No file to patch. Skipping patch. 1 out of 1 hunk ignored

patch program exited with status 1 77,1 Bot

[ghost]

it seems like theres a mainline version of quantum in portage do you guys reccomend that

[ghost]

personally I'd prefer bleeding edge

[lensen]

We haven't started using Quantum yet, so we haven't really looked at this ebuild for quite some time.