From: Markus Nigbur <pYrania@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] VERY circular dependency
Date: Sun, 28 Sep 2003 19:50:18 +0200 [thread overview]
Message-ID: <20030928195018.56ab6d14.pYrania@gentoo.org> (raw)
In-Reply-To: <3F77077F.8080306@technaut.darktalker.net>
[-- Attachment #1: Type: text/plain, Size: 1162 bytes --]
On Sun, 28 Sep 2003 11:08:31 -0500
Andrew Gaffney <agaffney@technaut.darktalker.net> wrote:
> Alexander Futasz wrote:
> > On Sun, 28 Sep 2003 01:10:09 -0500, Andrew Gaffney wrote:
> >
> >>Daniel Robbins wrote:
> >>
> >>>On Sat, 2003-09-27 at 19:48, Andrew Gaffney wrote:
> >>>
> >>>
> >>>>upstairs sys-devel # qpkg -q -nc -I gimp-print
> >>>>media-gfx/gimp-print-4.3.20
> >>>>DEPENDED ON BY:
> >>>> media-gfx/gimp-print-4.3.20
> >>>
> >>>
> >>>Due to a bug in qpkg due to it not using the Portage API directly.
> >>>If you look in the ebuild, you'll see that no such dependency
> >exists>>(it's probably getting it from "!media-gfx/gimp-print-cups".
> >>
> >>Okay. Another thing....there is no media-gfx/gimp-print-cups.
> >
> >
> > Indeed, please file a bug then. http://bugs.gentoo.org Also you have
> >
> > a look at http://bugs.gentoo.org/show_bug.cgi?id=23944 for qpkg's
> > dependency checking.
>
> Okay, I filed a bug. I know epm doesn't use the Portage API because
> its written in Perl, but does etcat?
gimp-print and gimp-print-cups were merged the other day..
removed the block.
--
Markus Nigbur
Gentoo Developer
http://www.gentoo.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-28 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 1:48 [gentoo-dev] VERY circular dependency Andrew Gaffney
2003-09-28 2:43 ` Daniel Robbins
2003-09-28 6:10 ` Andrew Gaffney
2003-09-28 8:43 ` Alexander Futasz
2003-09-28 16:08 ` Andrew Gaffney
2003-09-28 17:50 ` Markus Nigbur [this message]
2003-09-28 12:38 ` foser
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=20030928195018.56ab6d14.pYrania@gentoo.org \
--to=pyrania@gentoo.org \
--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