I tried to report an error on an ebuild a while ago. I searched in the box for 'giflib' (the name of the ebuild in question), and it returned nothing. So, I filed the bug. Then I received an email marking it as a duplicate of another bug that HAD giflib in its summary, but didn't make it into the search results. No wonders why over 50% of the bugs filed are duplicates :) After searching for bugs on bugzilla here, I found out that I need to prefix my search with 'ALL' to find it. I tried, and it worked. Shouldn't it by default add an 'ALL' or something like that to make it easier to find bugs? This would help alot people who file duplicates. Reproducible: Always Steps to Reproduce: 1.search for giflib in the database 2. 3. Actual Results: 2 results unrelated to the problem Expected Results: all bugs concerning giflib Portage 2.0.52-r1 (default-linux/x86/2005.0, gcc-3.3.6, glibc-2.3.5-r1, 2.6.13-gentoo i686) ================================================================= System uname: 2.6.13-gentoo i686 AMD Athlon(tm) XP 2700+ Gentoo Base System version 1.12.0_pre8 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.4 [enabled] dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.13 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/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/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_US.UTF-8" LINGUAS="pt_BR" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://alpha.hospedevip/gentoo-portage" USE="x86 16bit 3dnow 3dnowext X aalib acl acpi aim alsa apache2 apm arts avi bash-completion berkdb bitmap-fonts bonobo bzip2 bzlib cddb cjk crypt cups curl eds emboss encode esd fam foomaticdb fortran gd gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml guile icq imagemagick imap imlib ipv6 irc java jpeg libg++ libwww mad mbox mikmod mime mmx mmxext mozilla moznocompose moznoirc moznomail mp3 mpeg msn mysql ncurses nis nls offensive ogg oggvorbis opengl oss pam pdflib perl php png postgres procmail python quicktime readline recode samba sdl snmp spell sse sse2 ssl svg svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts unicode vorbis xml xml2 xmms xv yahoo zlib linguas_pt_BR userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS, MAKEOPTS
(In reply to comment #0) > I tried to report an error on an ebuild a while ago. I searched in the box for > 'giflib' (the name of the ebuild in question), and it returned nothing. > After searching for bugs on bugzilla here, I found out that I need to prefix my > search with 'ALL' to find it. I tried, and it worked. http://bugs.gentoo.org/ <big bold letters snip> Note: When searching for duplicate bugs, prefix search with 'ALL' </big bold letters snip> So - what about reading instructions first and not wasting your and our time? *sigh*
I'm sorry. Marking this as resolved.
(In reply to comment #1) > > <big bold letters snip> > Note: When searching for duplicate bugs, prefix search with 'ALL' > </big bold letters snip> > > So - what about reading instructions first and not wasting your and our time? > I don't remember how it was before, but this instruction is now below the search keywords input field, in italic. This is not as readable as "big bold letters", and seeing how many duplicates bugs there are (for general bugs, dozens... -well, Jakub, you are quite aware of it, seeing you are probably the most active Gentoo Bugzilla user), it is not sufficient for most user (who should indeed at least take the two seconds needed to read the doc on the front page... -I understand your frustration-, but they don't, so something has to be done...). I suggest something like this, to be added just below the "Welcome to the Gentoo Bugtracking system." message (do not put it below the search keywords input field): <!-- Begins "ALL" keyword warning notice --> <div style="max-width: 40em; border: 2px solid black; padding: 10px; background-color: #FDD; line-height: 1.2em; letter-spacing: 0.05em;"> <!-- Icon from http://www.lullabot.com/articles/free_gpl_icons_lullacons_pack_1 (licensed under the GNU GPL) --> <img src="http://www.lullabot.com/files/icons/lullacons_pack1/large-alert.png" alt="" style="float: left; margin: 0 10px 10px 0;" /> <p style="margin: 0; padding: 0;"><strong>IMPORTANT</strong>: To search for <strong>possible duplicate bugs</strong> (that is, <em>always</em>, when you want to fill a new bug report), or <strong>when using multiple search keywords</strong>, you must prefix your entry with the keyword "<strong>ALL</strong>" (no quotes, case matters).</p> <p style="margin: 10px 0 0; padding: 0;"><strong>For example</strong>: ALL firefox deer park</p> </div> <!-- Ends "ALL" keyword warning notice --> (I found the icon from a Google search... anything similar will do... -don't forget to copy it locally and modify the link, in any case) It probably will seem overkill to most people who already know about it (if not annoying, considereing the wasted space for them), but if we want less duplicates, I guess this is a requirement: make it hard for people not to read the basic doc ^_^; (By the way, the example should probably be changed to something which returns dozens of duplicates, instead of just a few -but the example must be kept simple, and use at least two simple keywords). Note it should not be a problem to also keep the current message below the search field... Note the max-width on the main div is important, as the line-height and letter-spacing stuff.
Could this bug be: - Reopened - Assigned to "infra-bugs@gentoo.org" - Have its summary changed to something like "[bugstest] Improve frontpage doc about search for duplicate/resolved bugs" - Have its severity changed to "Enhancement" As said in my previous comment, if we want to avoid duplicates, the instruction about the "ALL" keyword, must be clear, and highly visible, as it is not an expected behaviour, and most users don't read the doc, in today society, even when written just below the search form. (To avoid some people complaining about waste of space, the option might be deactivated manually...).
