Bugzilla Bug 132208

On a server I have no X support, thus, the X use flag is deactivated.
media-libs/libdc1394-1.2.1 failes to apply the nox11 patch:

>>> Unpacking source...
>>> Unpacking libdc1394-1.2.1.tar.gz to /var/tmp/portage/libdc1394-1.2.1/work
 * Applying nox11.patch ...

 * Failed Patch: nox11.patch !
 *  ( /usr/portage/media-libs/libdc1394/files/nox11.patch )
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/libdc1394-1.2.1/temp/nox11.patch-1660.out


!!! ERROR: media-libs/libdc1394-1.2.1 failed.
!!! Function epatch, Line 339, Exitcode 0
!!! Failed Patch: nox11.patch!
!!! If you need support, post the topmost build error, NOT this status message.


# emerge --info
Portage 2203-svn (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.6-r3, 2.6.15.1
i686)
=================================================================
System uname: 2.6.15.1 i686 Pentium III (Coppermine)
Gentoo Base System version 1.6.14
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632)
[disabled]
dev-lang/python:     2.4.2
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.12
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
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium3 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium3 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://192.168.178.21 http://pandemonium.tiscali.de/pub/gentoo/
http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/
http://mirror.switch.ch/ftp/mirror/gentoo/ http://gentoo.intergenia.de"
LINGUAS="de us"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://192.168.178.21/gentoo-portage"
USE="x86 X509 a52 aac acl alsa apache2 audiofile avi berkdb big-tables bzip2
cdparanoia chroot cli cpudetection crypt cups curl dri dts dv dvd dvdread eds
emacs emboss encode esd exif expat fame ffmpeg flac flash foomaticdb fortran
gdbm gif gmp gnutls gpm gs gstreamer gtk2 guile hpn idn ieee1394 imagemagick
imap imlib isdnlog java jbig jpeg junit latex lcms ldap libg++ libwww live lzo
mad mailwrapper matroska mhash mikmod ming mjpeg mmx mp3 mpeg mysql nas ncurses
network nls nptl nsplugin objc ogg opengl pam pcre pdflib perl php png ppds
pppd profile python quicktime readline recode reflection rle rtc ruby samba
sasl sdl session sftplogging slp speex spell spl sse ssl svga tcpd theora
threads tiff udev unicode usb utf8 vorbis wmf xml xml2 xorg xv xvid yv12 zlib
linguas_de linguas_us userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS

Created an attachment (id=86342) [edit]
Newly created patch

I've manually changed everything in the old patch file and created a new one.
I've successfully installed the package with it.
Since the patch for 1.0.0 is different to the patch for 1.2.1 I suggest to
use full qualified names for the patches.
So you will have to change the ebuild that it fits the new patch file name.

I just got this error too.

Any chance to have this fixed in the main portage tree?

Same problem here!
But the workaround with Andre's manually created patch run fine. Thanks Andre!

I would be very pleased if the maintainers would integrate it into portage, it
should be done within 5 to 10 minutes work... ;-)

Thanks a lot!


(In reply to comment #1)
> Created an attachment (id=86342) [edit]
> Newly created patch
> 
> I've manually changed everything in the old patch file and created a new one.
> I've successfully installed the package with it.
> Since the patch for 1.0.0 is different to the patch for 1.2.1 I suggest to
> use full qualified names for the patches.

ugh, I keep intending to do this.  on thursday, I'll have reliable internet
access again, so I'll put that into portage (will try tonight, though hotel
wireless seems spotty at best).

hey it's in cvs!

listen peoploe. don't be afraid to just ping me on irc or send me an email with
"hey fool, check that in already" type messages (but be a little more polite
than that :P).

Thanks!