From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ebuild for x11-libs/qt-3.3.8-r3 is missing after portage update but required by the system configuration
Date: Mon, 2 Feb 2009 23:48:55 +0000 [thread overview]
Message-ID: <20090202234855.28f211d6@krikkit> (raw)
In-Reply-To: <3743861a0902021437s2e1849bdo6a256cc4ce96c1c9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
On Tue, 3 Feb 2009 00:37:51 +0200, Dimitris Kavadas wrote:
> emerge: there are no ebuilds to satisfy "=x11-libs/qt-3.3.8-r3".
> (dependency required by
> "net-wireless/kdebluetooth-1.0_beta1-r2" [installed]) (dependency
> required by "world" [argument])
>
> So, what seems to be the problem?
Try kdebluetooth-1.0_beta8, it's been in the tree for more than
three months (emerged on 20-11-08 here) and causes no such problem.
--
Neil Bothwick
I'm as confused as a baby in a topless bar.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-02-02 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 22:37 [gentoo-user] ebuild for x11-libs/qt-3.3.8-r3 is missing after portage update but required by the system configuration Dimitris Kavadas
2009-02-02 23:48 ` Neil Bothwick [this message]
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=20090202234855.28f211d6@krikkit \
--to=neil@digimed.co.uk \
--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