First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 19193
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Philip Walls (RETIRED) <malverian@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: jochem prins <j.prins@gmx.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
libao-0.8.3-r1.patch-17707.out failed patching for emerge libao-0.8.3-r1 text/plain jochem prins 2003-04-12 06:47 0000 2.99 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 19193 depends on: Show dependency tree
Bug 19193 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-04-12 06:44 0000
After i rsynced my portage today with a server, i wanted to update libao since
there was an update for it. So i did an "emerge libao" which fetched the update.
Than just after the unpacking finished, the ebuild failed patching the source
somehow. Luckily emerge did manage to throw some output in the temporary compile
directory, which i'll put in as attachment.

Reproducible: Always
Steps to Reproduce:
1. (optional) emerge rsync
2. emerge -p libao
3. emerge libao

Actual Results:  
1. The usual emerge sync data flows over the screen
2. Emerge tells me that it wants to install libao-0.8.3-r1
3. Emerge downloads libao and doesn't download any patches. After unpacking
libao, patching is attempted but fails probably due to a ?missing patch? .

Expected Results:  
Just should have downloaded the data, unpacked libao and patch it afterwards.
After that, compiling & installing should follow.

Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.20-xfs-r2 i686 Celeron (Mendocino)
GENTOO_MIRRORS="ftp://ftp.snt.utwente.nl/pub/linux/gentoo 
http://www.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/home/portage"
PORTDIR_OVERLAY="/usr/local/portage"
USE="x86 oss avi crypt gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png
quicktime spell truetype xml2 xmms zlib gdbm berkdb slang readline tetex svga
ggi tcltk sdl gpm tcpd pam libwww ssl perl python imlib oggvorbis motif opengl
mozilla X oav -fbcon -gtk -gnome alsa -java -kde -qt -3dnow -apm -arts cdr -cups
dvd -encode ipv6 mailbox -motif-qtmt sasl samba xv"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=pentium -O3 -pipe"
CXXFLAGS="-march=pentium -O3 -pipe"
ACCEPT_KEYWORDS="x86 ~x86"
MAKEOPTS="-j2"
AUTOCLEAN="no"
SYNC="rsync://rsync.nl.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache distcc"

------- Comment #1 From jochem prins 2003-04-12 06:47:21 0000 -------
Created an attachment (id=10543) [details]
failed patching for emerge libao-0.8.3-r1

------- Comment #2 From Philip Walls (RETIRED) 2003-04-12 12:32:59 0000 -------
Well, the patch doesn't actually get downloaded, it is kept in the FILESDIR, so
if you don't mind, go ahead and rsync one more time, in case for some reason
the patch got commited too late to get propagated at the same time as the
patch, and then run:

> md5sum /usr/portage/media-libs/libao/files/libao-0.8.3-r1.patch 

I get the following md5sum, and patching goes through without a hitch:

5f642fcbb8941a2f070cce0697f218fd


However, judging from the output, it looks that the patch is there, but perhaps
corrupt, or for some reason S is not being defined properly.

Please try removing the patch if it does exist and rsyncing again.

------- Comment #3 From Roger Hawley 2003-04-12 20:52:57 0000 -------
5:35pm PST
I get the same as Jochem. MD5SUM matched. Deleted the patch,synced and emerge failed again.
el lodger

------- Comment #4 From Mikael Andersson 2003-04-12 23:09:15 0000 -------
when im graing to install gnome i get 

bash-2.05b# emerge gnome
Calculating dependencies ...done!
>>> emerge (1 of 5) media-libs/libao-0.8.3 to /
>>> md5 ;-) libao-0.8.3.tar.gz
>>> Unpacking source...
>>> Unpacking libao-0.8.3.tar.gz to /var/tmp/portage/libao-0.8.3/work
>>> Source unpacked.
/usr/sbin/ebuild.sh: line 20: cd: /var/tmp/portage/libao-0.8.3/work/libao-0.8.3-r0: No such file or directory

 * Cannot find $EPATCH_SOURCE!  Value for $EPATCH_SOURCE is:
 * 
 *   /usr/portage/media-libs/libao/files/libao-0.8.3.patch


!!! ERROR: media-libs/libao-0.8.3 failed.
!!! Function epatch, Line 214, Exitcode 0
!!! Cannot find $EPATCH_SOURCE!


md5sum /usr/portage/media-libs/libao/files/libao-0.8.3-r1.patch
5f642fcbb8941a2f070cce0697f218fd  /usr/portage/media-libs/libao/files/libao-0.8.3-r1.patch


i haw updatedb and locate libao and delited all whit the name libao and emerge rsunc i get the error aneyway


------- Comment #5 From Philip Walls (RETIRED) 2003-04-13 07:38:29 0000 -------
Ah, I'm sorry guys, I see the problem. The ~x86 version of this package works
fine. The problem is that in the 0.8.3 version it tries to find the patch as
${P}-${PR} .. obviously there is no revision for 0.8.3

The second problem is that there is no patch for this version of libao.
I've fixed both problems and cleaned up the ebuild in general. Let me know if
you have any other problems.

------- Comment #6 From Martin Holzer (RETIRED) 2003-04-13 11:21:10 0000 -------
*** Bug 19242 has been marked as a duplicate of this bug. ***

------- Comment #7 From Heinrich Wendel (RETIRED) 2003-04-13 11:24:33 0000 -------
there is still a problem with the patch, it tries to apply to an absolute path

/var/tmp/portage/libao-0.8.3-r1/work/libao-0.8.3/src/plugins/alsa09/ao_alsa09.c

but if you have your portage tmp dir somewhere else it fails, so please change the path to

src/plugins/alsa09/ao_alsa09.c

First Last Prev Next    No search results available      Search page      Enter new bug