i try upgrading from fam-oss-2.6.9 to fam-oss-2.6.9-r1 and this is what i get: >>> md5 ;-) fam-2.6.9.tar.gz >>> Unpacking source... >>> Unpacking fam-2.6.9.tar.gz patching file acconfig.h patching file configure.in Hunk #1 succeeded at 103 (offset 4 lines). Hunk #3 succeeded at 607 (offset 8 lines). patching file fam/DNotify.c++ patching file fam/DNotify.h patching file fam/IMon.h patching file fam/Interest.c++ Hunk #1 succeeded at 43 (offset 2 lines). Hunk #3 succeeded at 110 (offset 2 lines). Hunk #5 succeeded at 157 (offset 2 lines). patching file fam/Interest.h patching file fam/Makefile.am patching file fam/Monitor.h patching file include/BTree.h /usr/sbin/ebuild.sh: line 28: /usr/portage/app-admin/fam-oss/files/fam-oss-2.6.9-r1-gcc3.patch: No such file or directory actually in /usr/portage/app-admin/fam-oss/files/ there is a fam-oss-2.6.9-gcc3.patch file that is guess should be the one to refer to.
I get something very similar: Calculating world dependencies ...done! >>> emerge (1 of 1) app-admin/fam-oss-2.6.9-r1 to / >>> md5 ;-) fam-2.6.9.tar.gz >>> Unpacking source... >>> Unpacking fam-2.6.9.tar.gz /usr/sbin/ebuild.sh: line 27: /usr/portage/distfiles/dnotify.patch: No such file or directory !!! ERROR: app-admin/fam-oss-2.6.9-r1 failed. !!! Function src_unpack, Line 27, Exitcode 1 !!! (no error message)
While were at it =) Got the same problem . . . firefly root # emerge --deep -u world Calculating world dependencies ...done! >>> emerge (1 of 8) app-admin/fam-oss-2.6.9-r1 to / >>> md5 ;-) fam-2.6.9.tar.gz >>> Unpacking source... >>> Unpacking fam-2.6.9.tar.gz /usr/sbin/ebuild.sh: line 27: /usr/portage/distfiles/dnotify.patch: Datei oder Verzeichnis nicht gefunden !!! ERROR: app-admin/fam-oss-2.6.9-r1 failed. !!! Function src_unpack, Line 27, Exitcode 1 !!! (no error message)
I got the same error as Marco. I tried renaming the fam-oss-2.6.9-gcc3.patch file to fam-oss-2.6.9-r1-gcc3.patch, however I get a whole slew of warnings such as: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2.1/include/g++-v3/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <sstream> instead of the deprecated header <strstream.h>. To disable this warning use -Wno-deprecated. In file included from Client.h:27, from fam.c++:37: ../include/BTree.h:241: warning: `typename BTree<Key, Value>::Closure' is implicitly a typename ../include/BTree.h:241: warning: implicit typename is deprecated, please see the documentation for details ../include/BTree.h:353: warning: `typename BTree<Key, Value>::Closure' is implicitly a typename ../include/BTree.h:353: warning: implicit typename is deprecated, please see the documentation for details ../include/BTree.h:409: warning: `typename BTree<Key, Value>::Closure' is implicitly a typename ../include/BTree.h:409: warning: implicit typename is deprecated, please see the documentation for details ../include/BTree.h:504: warning: `typename BTree<Key, Value>::Status' is implicitly a typename ../include/BTree.h:504: warning: implicit typename is deprecated, please see the documentation for details ../include/BTree.h:562: warning: `typename BTree<Key, Value>::Closure' is implicitly a typename ../include/BTree.h:562: warning: implicit typename is deprecated, please see the documentation for details ../include/BTree.h:592: warning: `typename BTree<Key, Value>::Status' is implicitly a typename ../include/BTree.h:592: warning: implicit typename is deprecated, please see the documentation for details I assume some of these warnings are because it's using depreciated headers, but I don't want to just assume that renaming the patch file will work, and end up with subtle errors. I guess I'll wait until someone makes a final decision on this.
Same problem here, Gentoo 1.2 system, No Gnome for me... :( >>> emerge (1 of 70) app-admin/fam-oss-2.6.9-r1 to / >>> md5 ;-) fam-2.6.9.tar.gz >>> Unpacking source... >>> Unpacking fam-2.6.9.tar.gz /usr/sbin/ebuild.sh: /usr/portage/distfiles/dnotify.patch: No such file or directory !!! ERROR: app-admin/fam-oss-2.6.9-r1 failed. !!! Function src_unpack, Line -249, Exitcode 1 !!! (no error message)
ok, there is a major path screwup, this here should fix it: cp /usr/portage/app-admin/fam-oss/files/dnotify.patch /usr/portage/distfiles/ && cp /usr/portage/app-admin/fam-oss/files/fam-oss-2.6.9-gcc3.patch \ /usr/portage/app-admin/fam-oss/files/fam-oss-2.6.9-r1-gcc3.patch CU, Konrad
the \ is wront if you write it into one line: cp /usr/portage/app-admin/fam-oss/files/dnotify.patch /usr/portage/distfiles/ && cp /usr/portage/app-admin/fam-oss/files/fam-oss-2.6.9-gcc3.patch /usr/portage/app-admin/fam-oss/files/fam-oss-2.6.9-r1-gcc3.patch
The suggestion soln. appears to work.
Here is a patch that should fix the problem with the ebuild itself. This is assuming the 'fam-oss-2.6.9-gcc3.patch' is the correct version we want to patch fam against and a 'fam-oss-2.6.9-gcc3-rc1.patch' file wasn't supposed to be added. Also the line which points to dnotify.patch uses ${DISTDIR} but should use ${FILESDIR} instead. So without further delay, here is the patch: --- fam-oss-2.6.9-r1.ebuild.orig 2003-02-10 09:35:21.000000000 -0800 +++ fam-oss-2.6.9-r1.ebuild 2003-02-10 09:35:34.000000000 -0800 @@ -24,8 +24,8 @@ unpack ${MY_P}.tar.gz cd ${S} - patch -p1 < ${DISTDIR}/dnotify.patch || die - patch -p1 < ${FILESDIR}/${PF}-gcc3.patch || die + patch -p1 < ${FILESDIR}/dnotify.patch || die + patch -p1 < ${FILESDIR}/${P}-gcc3.patch || die # should fix the sigqueue overflow problems cd ${S}/fam
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is: * * /var/tmp/portage/fam-oss-2.6.9-r1/work/patch Presumably I have the same problem?
yeah, i figured out half an hour late. Should be fixed in the tree.
*** Bug 15469 has been marked as a duplicate of this bug. ***
