Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 86255

Summary: mail-client/evolution-2.2.1.1 works on amd64
Product: Gentoo Linux Reporter: FieldySnuts <sgtphou>
Component: New packagesAssignee: Gentoo Linux Gnome Desktop Team <gnome>
Status: RESOLVED INVALID    
Severity: enhancement    
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description FieldySnuts 2005-03-22 06:15:20 UTC
Just wanted to drop a note that mail-client/evolution-2.2.1.1 works for me. Well done!

Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.4.3-20050110, glibc-2.3.4.20050125-r0, 2.6.11.5-grsec-200503212014 i686)
=================================================================
System uname: 2.6.11.5-grsec-200503212014 i686 AMD Athlon(TM) XP 1800+
Gentoo Base System version 1.6.9
Python:              dev-lang/python-2.3.5 [2.3.5 (#1, Mar  8 2005, 09:23:44)]
ccache version 2.4 [enabled]
dev-lang/python:     2.3.5
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r4
sys-devel/libtool:   1.5.10-r5
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig buildpkg ccache distlocks notitles sandbox sfperms"
GENTOO_MIRRORS="ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/ http://gentoo.blueyonder.co.uk ftp://mirror.iawnet.sandia.gov/pub/gentoo/"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="x86 3dnow X aalib alsa apm avi berkdb bitmap-fonts cdr chroot crypt curl dv dvd dvdr emboss encode fam flac font-server foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 hal imagemagick imlib java jpeg kde ldap libg++ libwww mad mikmod mmx motif mozilla mp3 mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png pwdb python qt quicktime readline samba sdl slang spell sse ssl svga tcltk tcpd tiff truetype truetype-fonts type1-fonts xml2 xmms xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Comment 1 Sven 2005-03-22 11:30:18 UTC
ugly, this is the first time i see a bugzilla used to post "it works for me" - that should be the normal case or?

you can do me a favour if you read this one http://bugzilla.ximian.com/show_bug.cgi?id=73957

please tell me if this works well for you or not.
Comment 2 FieldySnuts 2005-03-22 12:34:33 UTC
It's quite common for amd64, which I realise this isn't but thought it might be helpful. If it's not, let me know so I don't do it in the future :)

I don't have any accounts that require smtp authentication, so I don't think I can test this one out.
Comment 3 Simon Stelling (RETIRED) gentoo-dev 2005-03-22 12:57:34 UTC
i'm sure you wanted to file a bug like the ones described here: http://www.gentoo.org/proj/en/base/amd64/technotes.xml?part=1&chap=3
Comment 4 FieldySnuts 2005-03-22 13:08:03 UTC
Actually no, I'm x86. I should have said *similar* to amd64 does. I guess this can be closed? Sounds like I'm causing more trouble than helping, which was not my intention.
Comment 5 Mike Gardiner (RETIRED) gentoo-dev 2005-03-22 18:23:58 UTC
Basically, if you've tested out an application that wasn't previously keyworded ~amd64 (by editing the ebuild and adding the keywords yourself), and it works fine, then it's perfectly fine to post a "Please mark <application> ~amd64" bug, saying that you've keyworded and tested it and it works fine.

For applications that are allready keyworded, they'll get to stable when we deem them ready, so there's no need to post bugs on them.

Thanks.