From: Philip Webb <purslow@ca.inter.net>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] weird portage warning
Date: Sat, 1 May 2010 23:19:12 -0400 [thread overview]
Message-ID: <20100502031912.GE4463@ca.inter.net> (raw)
For the past few weeks, I have noticed the following bizarre msg :
root:503 ~> emerge -Dup world
These are the packages that would be merged, in order:
Calculating dependencies |
* Please fix your ebuild to not inherit the deprecated qt3.eclass
* Please fix your ebuild to not inherit the deprecated qt3.eclass
* Please fix your ebuild to not inherit the deprecated qt3.eclass
... done!
Yes, I have the KDE 3 overlay installed,
but even so how can a mere user be expected to "fix an ebuild",
whatever that may mean anyway. Can anyone enlighten me
as to the cause &/or purpose of these repeated msgs ?
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next reply other threads:[~2010-05-02 3:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 3:19 Philip Webb [this message]
2010-05-02 6:56 ` [gentoo-user] weird portage warning Volker Armin Hemmann
2010-05-02 7:46 ` Petric Frank
2010-05-02 7:57 ` Volker Armin Hemmann
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=20100502031912.GE4463@ca.inter.net \
--to=purslow@ca.inter.net \
--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