While attempting to upgrade coreutils with selinux profile, and it attempts to patch, I get this error: * Applying coreutils-5.0-selinux.patch.bz2... * Failed Patch: coreutils-5.0-selinux.patch.bz2! * * Include in your bugreport the contents of: * * /var/tmp/portage/coreutils-5.0-r2/temp/coreutils-5.0-selinux.patch.bz2-26259.out Reproducible: Always Steps to Reproduce: 1. 2. 3. Emerge Info: Portage 2.0.49 (selinux-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.20-hardened-r4) ================================================================= System uname: 2.4.20-hardened-r4 i686 AMD Athlon(tm) XP 1700+ ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O2 -pipe -fstack-protector" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/confi g /usr/kde/3/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linu x/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="crypt ncurses selinux zlib gdbm berkdb readline tcpd pam libwww ssl perl py thon imap spell -nls -X -gtk -gnome -alsa -kde -qt mysql -apache2 gd png jpeg gi f xml xml2 x86" Contents of /var/tmp/portage/coreutils-5.0-r2/temp/coreutils-5.0-selinux.patch.bz2-26259.out: ***** coreutils-5.0-selinux.patch.bz2 ***** =========================================== PIPE_COMMAND: bzip2 -dc /usr/portage/distfiles/coreutils-5.0-selinux.patch.bz2 > /var/tmp/portage/coreutils-5.0-r2/temp/26259.patch PATCH COMMAND: patch -p0 < /var/tmp/portage/coreutils-5.0-r2/temp/26259.patch =========================================== can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN coreutils-5.0/README coreutils-5.0-selinux/README |--- coreutils-5.0/README 2003-03-29 08:24:00.000000000 -0600 |+++ coreutils-5.0-selinux/README 2003-04-04 23:37:09.000000000 -0600 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 21 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN coreutils-5.0/lib/Makefile.am coreutils-5.0-selinux/lib/Makefile.am |--- coreutils-5.0/lib/Makefile.am 2003-04-02 04:16:19.000000000 -0600 |+++ coreutils-5.0-selinux/lib/Makefile.am 2003-04-04 23:37:09.000000000 -0600 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 35 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN coreutils-5.0/lib/Makefile.in coreutils-5.0-selinux/lib/Makefile.in |--- coreutils-5.0/lib/Makefile.in 2003-04-02 08:28:42.000000000 -0600 |+++ coreutils-5.0-selinux/lib/Makefile.in 2003-04-04 23:37:09.000000000 -0600 -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 56 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN coreutils-5.0/lib/makepath.c coreutils-5.0-selinux/lib/makepath.c |--- coreutils-5.0/lib/makepath.c 2003-03-04 15:19:25.000000000 -0600 |+++ coreutils-5.0-selinux/lib/makepath.c 2003-04-04 23:37:09.000000000 -0600 -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 131 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -urN coreutils-5.0/man/Makefile.am coreutils-5.0-selinux/man/Makefile.am |--- coreutils-5.0/man/Makefile.am 2003-04-02 04:19:34.000000000 -0600 |+++ coreutils-5.0-selinux/man/Makefile.am 2003-04-04 23:37:09.000000000 -0600 -------------------------- (Continues on like this for many many lines)
Ok, I updated the patch, now it should work. Please try and report results.
Nice, working great. Bug can be closed.
good. closing
