public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Edward Muller <edwardam@interlix.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] bugs.gentoo.org
Date: 12 Feb 2002 23:15:50 -0500	[thread overview]
Message-ID: <1013573750.31845.21.camel@palin> (raw)

I can't seem to attach an ebuild to a bug. I keep trying to attach my
update ebuilds to bug #672, but all I get is ...

'No file was provided, or it was empty'.

I get this with mozilla and opera, so it's not a browser issue.

I've specified the file name
/usr/portage/gnome-base/bonobo/bonobo-1.0.19.ebuild ... I gave it a
description and a mime-type ...

Just no go.

Is bugzilla broken at the moment?

Or am I doign something wrong?





             reply	other threads:[~2002-02-13  4:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13  4:15 Edward Muller [this message]
2002-02-13  4:54 ` [gentoo-dev] bugs.gentoo.org Arcady Genkin
2002-02-13 11:49   ` Bart Verwilst
2002-02-13 14:32     ` Arcady Genkin
2002-02-13 14:47       ` Edward Muller
  -- strict thread matches above, loose matches on Subject: below --
2003-07-04 22:08 rob holland
2003-07-05  1:49 ` Brett I. Holcomb
2003-07-05  2:02   ` Grant Goodyear
2003-11-23 18:43 Benjamin Coles

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=1013573750.31845.21.camel@palin \
    --to=edwardam@interlix.com \
    --cc=gentoo-dev@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