Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
net-dns/avahi-0.6.20-r1 ebuild fails when applying one of the new patches. The output is: * Applying avahi-0.6.1-no-ipv6.patch ... [ ok ] * Applying avahi-0.6.20-ui-sharp-gtk.patch ... [ ok ] * Applying avahi-0.6.20-make-known-answers-not-conflict.patch ... * Failed Patch: avahi-0.6.20-make-known-answers-not-conflict.patch ! * ( /usr/portage/net-dns/avahi/files/avahi-0.6.20-make-known-answers-not-conflict.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/net-dns/avahi-0.6.20-r1/temp/avahi-0.6.20-make-known-answers-not-conflict.patch-22040.out !!! ERROR: net-dns/avahi-0.6.20-r1 failed. Call stack: ebuild.sh, line 1621: Called dyn_unpack ebuild.sh, line 753: Called qa_call 'src_unpack' ebuild.sh, line 44: Called src_unpack avahi-0.6.20-r1.ebuild, line 103: Called epatch '/usr/portage/net-dns/avahi/files/avahi-0.6.20-make-known-answers-not-conflict.patch' eutils.eclass, line 304: Called die !!! Failed Patch: avahi-0.6.20-make-known-answers-not-conflict.patch! !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/log/portage/net-dns:avahi-0.6.20-r1:20070712-065324.log'. I will attach the output of the patch process and the ebuild log. By the way: why straight to stable w/o 30 days in ~arch? Reproducible: Always Steps to Reproduce: 1. emerge -1av avahi Actual Results: Outlined above. Expected Results: emerge just fine Portage 2.1.2.9 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, glibc-2.5-r3, 2.6.20-gentoo-r8 x86_64) ================================================================= System uname: 2.6.20-gentoo-r8 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ Gentoo Base System release 1.12.9 Timestamp of tree: Thu, 12 Jul 2007 06:00:10 +0000 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r7 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.16 sys-devel/libtool: 1.5.23b virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -O3 -pipe -fomit-frame-pointer" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=k8 -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="--with-bdeps y" FEATURES="autoaddcvs ccache collision-protect distcc distlocks fixpackages metadata-transfer sandbox sfperms strict test userfetch userpriv usersandbox" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://mirror.switch.ch/ftp/mirror/gentoo/ http://gentoo.mirror.solnet.ch http://gentoo.intergenia.de http://pandemonium.tiscali.de/pub/gentoo/" LANG="it_IT.UTF-8" LC_ALL="it_IT.UTF-8" LINGUAS="it" MAKEOPTS="-j12" PKGDIR="/usr/portage/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 --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://pedroni03/gentoo-portage" USE="X Xaw3d a52 aac aalib acpi alsa amd64 ao arts audiofile avahi bash-completion berkdb bitmap-fonts bzip2 cairo caps cddb cdparanoia cdr cli cracklib crypt cups curl dbus dga dio dri dvd dvdr dvdread emboss encode evo exif expat fam fbcon ffmpeg fftw firefox flac foomaticdb fortran ftp gd gdbm ggi gif glut gmp gnutls gphoto2 gpm gtk guile hal iconv idn ieee1394 imagemagick imlib isdnlog java javascript jbig jikes jpeg jpeg2k kde kdeenablefinal lcms libcaca libg++ libsamplerate lm_sensors lua mad maildir matroska memlimit midi mikmod mime mmap mmx mng mozilla mp3 mpeg mpi mplayer mudflap ncurses nls nptl nptlonly nsplugin offensive ogg openal openexr opengl openmp oss pam pcre pdf perl png posix ppds pppd python qt3 qt3support quicktime rdesktop readline recode reflection ruby samba sdl session sharedmem shorten sndfile sockets sox speex spell spl sse sse2 ssl startup-notification svg symlink sysvipc tcl tcpd test theora threads tidy tiff tk truetype truetype-fonts type1-fonts unicode usb vcd vorbis wmf wxwindows x264 xcomposite xine xml xorg xosd xpm xv xvid yahoo zlib" ALSA_CARDS="intel8x0 virmidi" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" CAMERAS="kodak ptp2" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="it" USERLAND="GNU" VIDEO_CARDS="fglrx" Unset: CTARGET, INSTALL_MASK, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Created an attachment (id=124608) [details] Output of the failed patch Attached for completeness
Created an attachment (id=124609) [details] emerge log for package
Meanwhile, run dos2unix on the patch (or upgrade to patch-2.5.9-r1). And we'll keep hitting this over and over again because that version needs to sit in ~arch for infinity. *sigh*
OK, after running dos2unix on the patch, the ebuild works. This begs the question of why -r1 went straight to stable without a period in ~arch.
(In reply to comment #4) > This begs the question of why -r1 went straight to stable It hasn't go straight to stable; it's been sitting in ~arch for years despite the fact the it fixes this bug. I guess you are seriously confused here.
(In reply to comment #5) > (In reply to comment #4) > > This begs the question of why -r1 went straight to stable > > It hasn't go straight to stable; it's been sitting in ~arch for years despite > the fact the it fixes this bug. I guess you are seriously confused here. I meant avahi-0.6.20-r1 went straight to stable, not patch. ;-)
Fixed. The straight to stable was an accident, didn't meant to be this way.
