From: maxim wexler <blissfix@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: no ebuild what to do?
Date: Sat, 1 Oct 2005 11:20:18 -0700 (PDT) [thread overview]
Message-ID: <20051001182018.52267.qmail@web31701.mail.mud.yahoo.com> (raw)
In-Reply-To: <loom.20050930T035121-141@post.gmane.org>
>
> There is now an ebuild in Gentoo's bugzilla, so you
> could use Portdir_Overlay
> and provide some much needed testing.
Well, I found it:
http://bugs.gentoo.org/buglist.cgi?short_desc_type=allwordssubstr&short_desc=New&product=Gentoo+Linux&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=exact&email1=&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=
but only because I clicked on something at random
culled from google. Since I can't know in advance what
the bug# is, why does a search for the ebuild by name
come up empty in gentoo bugzilla?
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-01 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 17:18 [gentoo-user] no ebuild what to do? maxim wexler
2005-09-29 17:30 ` A. Khattri
2005-09-29 17:30 ` Michael Crute
2005-09-29 17:37 ` Dave Nebinger
2005-09-29 18:19 ` Yoandy Rodriguez
2005-09-29 22:05 ` Nick Rout
2005-09-30 2:04 ` [gentoo-user] " Greg Yasko
2005-09-30 2:12 ` Greg Yasko
2005-10-01 20:54 ` maxim wexler
2005-10-02 4:38 ` Nick Rout
2005-09-30 2:27 ` Nick Rout
2005-09-30 2:36 ` Greg Yasko
2005-09-30 3:59 ` Nick Rout
2005-10-01 17:50 ` maxim wexler
2005-10-01 18:20 ` maxim wexler [this message]
2005-10-03 10:53 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051001182018.52267.qmail@web31701.mail.mud.yahoo.com \
--to=blissfix@yahoo.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox