From: Helmut Jarausch <jarausch@igpm.rwth-aachen.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --update - why doesn't it update my kde packages
Date: Tue, 04 May 2010 12:09:25 +0200 (CEST) [thread overview]
Message-ID: <tkrat.1e717c2b351899e1@igpm.rwth-aachen.de> (raw)
In-Reply-To: <20100504094354.GA6232@gentoo_schaapje.arnhem.chello.nl>
On 4 May, Bert Swart wrote:
> On Tue, May 04, 2010 at 10:57:10AM +0200, Helmut Jarausch wrote:
>> Hi,
>> the following situation puzzles me a lot.
>>
>> My 'standard' way of updating is
>> emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree @system @world
>>
>> but it didn't update anything.
>>
>> Still, eix confirmed there were quite a lot of kde packages which have
>> newer versions, and indeed,
>> emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/)
>> upgraded 24 packages.
>>
>> Where does this discrepancy come from?
> Do you have --with-bdep set in /etc/make.conf?
No. Are you saying that
emerge --keep-going -j4 -1 --ask --update --newuse --deep --tree --with-bdeps y @system @world
would have updated my kde packages, as well?
Thanks,
Helmut.
--
Helmut Jarausch
Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
next prev parent reply other threads:[~2010-05-04 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 8:57 [gentoo-user] emerge --update - why doesn't it update my kde packages Helmut Jarausch
2010-05-04 9:43 ` Bert Swart
2010-05-04 10:09 ` Helmut Jarausch [this message]
2010-05-04 10:17 ` Bert Swart
2010-05-04 10:29 ` KH
2010-05-04 13:16 ` Alex Schuster
2010-05-04 16:19 ` Paul Hartman
2010-05-04 16:29 ` KH
[not found] <eGm8V-4DS-1@gated-at.bofh.it>
2010-05-04 14:59 ` David W Noon
2010-05-04 15:48 ` KH
2010-05-04 19:41 ` Dale
2010-05-04 20:02 ` KH
2010-05-04 23:10 ` Alex Schuster
2010-05-05 0:23 ` Dale
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=tkrat.1e717c2b351899e1@igpm.rwth-aachen.de \
--to=jarausch@igpm.rwth-aachen.de \
--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