Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 137369 - rails-1.0.0 - rails-1.0.0-rdoc-rake-0.7.patch fails
Summary: rails-1.0.0 - rails-1.0.0-rdoc-rake-0.7.patch fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: PPC Linux
: High normal (vote)
Assignee: Gentoo Ruby Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-20 06:32 UTC by roger
Modified: 2006-06-28 15:51 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
zip file containing emerge --info, emerge rails, failure output (Bug_137369.zip,2.41 KB, application/octet-stream)
2006-06-20 06:45 UTC, roger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description roger 2006-06-20 06:32:48 UTC
Im spotting an odd combination of issues with this emerge.

During the emerge I get this even though actionpack 1.12.1 is installed.  Actionpack 1.12.1 is the version thats available via emerge.

ERROR:  Error installing gem /var/tmp/portage/rails-1.0.0/distdir/rails-1.0.0[.gem]: rails requires actionpack = 1.11.2


The failure message is as follows.

 * Failed Patch: rails-1.0.0-rdoc-rake-0.7.patch !
 *  ( /var/portage/dev-ruby/rails/files/rails-1.0.0-rdoc-rake-0.7.patch )
 *

The contents of the error message/output would be
***** rails-1.0.0-rdoc-rake-0.7.patch *****

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

PATCH COMMAND:  patch -p0 -g0 -E --no-backup-if-mismatch < /var/portage/dev-ruby/rails/files/rails-1.0.0-rdoc-rake-0.7.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: rails-1.0.0/lib/tasks/documentation.rake
|===================================================================
|--- rails-1.0.0.orig/lib/tasks/documentation.rake
|+++ rails-1.0.0/lib/tasks/documentation.rake
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:  patch -p1 -g0 -E --no-backup-if-mismatch < /var/portage/dev-ruby/rails/files/rails-1.0.0-rdoc-rake-0.7.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: rails-1.0.0/lib/tasks/documentation.rake
|===================================================================
|--- rails-1.0.0.orig/lib/tasks/documentation.rake
|+++ rails-1.0.0/lib/tasks/documentation.rake
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:  patch -p2 -g0 -E --no-backup-if-mismatch < /var/portage/dev-ruby/rails/files/rails-1.0.0-rdoc-rake-0.7.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: rails-1.0.0/lib/tasks/documentation.rake
|===================================================================
|--- rails-1.0.0.orig/lib/tasks/documentation.rake
|+++ rails-1.0.0/lib/tasks/documentation.rake
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:  patch -p3 -g0 -E --no-backup-if-mismatch < /var/portage/dev-ruby/rails/files/rails-1.0.0-rdoc-rake-0.7.patch

===========================================
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: rails-1.0.0/lib/tasks/documentation.rake
|===================================================================
|--- rails-1.0.0.orig/lib/tasks/documentation.rake
|+++ rails-1.0.0/lib/tasks/documentation.rake
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
===========================================

PATCH COMMAND:  patch -p4 -g0 -E --no-backup-if-mismatch < /var/portage/dev-ruby/rails/files/rails-1.0.0-rdoc-rake-0.7.patch

===========================================
missing header for unified diff at line 5 of patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: rails-1.0.0/lib/tasks/documentation.rake
|===================================================================
|--- rails-1.0.0.orig/lib/tasks/documentation.rake
|+++ rails-1.0.0/lib/tasks/documentation.rake
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored



Portage 2.1 (!/var/overlays/20060216/profiles/kurobox, gcc-3.4.6, glibc-2.3.6-r3, 2.4.17_mvl21 ppc)
=================================================================
System uname: 2.4.17_mvl21 ppc 82xx
Gentoo Base System version 1.6.14
ccache version 2.3 [enabled]
dev-lang/python:     2.4.2
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1-r2
sys-devel/gcc-config: 1.3.13-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r4
ACCEPT_KEYWORDS="ppc"
AUTOCLEAN="yes"
CBUILD="powerpc-unknown-linux-gnu"
CFLAGS="-O2 -mcpu=603e -fno-strict-aliasing -pipe -fsigned-char"
CHOST="powerpc-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/terminfo"
CXXFLAGS="-O2 -mcpu=603e -fno-strict-aliasing -pipe -fsigned-char"
DISTDIR="/var/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j1"
PKGDIR="/var/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/var/portage"
PORTDIR_OVERLAY="/var/overlays/20060216"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="ppc X alsa apache2 berkdb bitmap-fonts cjk cli crypt cups dri eds gif gnome gpm gstreamer gtk gtk2 ipv6 isdnlog jpeg kde kuro libwww mailwrapper mbox milter motif mp3 mpeg ncurses nls ogg oggvorbis opengl pam pcre pdflib perl png ppds pppd python qt readline reflection sasl session spell spl ssl tcpd truetype truetype-fonts type1-fonts unicode vorbis xml2 xorg xv zlib elibc_glibc kernel_linux userland_GNU"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS
Comment 1 roger 2006-06-20 06:45:56 UTC
Created attachment 89625 [details]
zip file containing emerge --info, emerge rails, failure output
Comment 2 Caleb Tennis (RETIRED) gentoo-dev 2006-06-21 07:59:02 UTC
You should probably try using a more recent version of rails, like 1.1.2
Comment 3 roger 2006-06-21 10:02:37 UTC
Just a small update.
The version of rails thats in the portage build system is 1.0.0
The version of actionpack is 1.12.1.

Ill grab the latest version from the rubyrails websites and see if it compiles.
Comment 4 Caleb Tennis (RETIRED) gentoo-dev 2006-06-21 10:07:58 UTC
the latest version of rails in portage is 1.1.2, but ppc hasn't marked it stable yet.  I've just notified them to do so, though.  This is the version you want to install.
Comment 5 Stephen Tallowitz 2006-06-28 03:18:50 UTC
Well, this is actually a plain and simple dependency issue.

All recent version of the rails "stack" have been marked stable, while there is still a slottable install for the "older" version (1.0.0). To resolve the above issue I had to manually emerge (older, stable) versions of:
=actionpack-1.11.2
=actionmailer-1.1.5 (had to re-emerge even if already on system)
=actionwebservice-1.0.0 (again, re-emerge required)

The ebuild of rails-1.0.0 does not require actionpack as a direct dependency, but probably one of the other action* ebuild installs the latest stable version of actionpack as a dependency and does not look out what version of rails is or will get installed. Hence some version muddle-ups on the way.

Way to go? Probably put =actionpack-1.11.2 as a direct dependency in rails-1.0.0 ebuild and it should solve the issue.

Side note (seems to fit into the topic of several different versions of rails):  Here is some link that will probably point in the direction of saying that a multi-slotted gem-system is probably not possible without a lot of extra effort: http://duncandavidson.com/essay/2005/12/railsdeployment (Skip to lesson #7)
Comment 6 Caleb Tennis (RETIRED) gentoo-dev 2006-06-28 04:06:49 UTC
now that 1.1.2 is stable and 1.1.3 will be in portage soon, we'll probably just drop 1.0.0 and call it a day
Comment 7 roger 2006-06-28 15:51:42 UTC
The updated emerge went in fine and testing on it hasnt turned up anything obvious.