From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: KDE update revdep-rebuild.sh fail
Date: Tue, 3 Apr 2018 12:57:23 -0700 [thread overview]
Message-ID: <dbc907bb-4a8f-b920-f488-4c6543d08315@gmail.com> (raw)
In-Reply-To: <1548742.7Vs5ckz6QP@ares-linux>
On 04/03/18 09:39, Elijah Mark Anderson wrote:
> I'm pretty sure Nikos is correct. When running revdep-rebuild, you'll get the
> following message that pretty much indicates the shell script version is being
> retired:
>
> * This is the new python coded version
> * Please report any bugs found using it.
> * The original revdep-rebuild script is installed as revdep-rebuild.sh
> * Please file bugs at: https://bugs.gentoo.org/
>
> On Tuesday, April 3, 2018 11:29:21 AM CDT Nikos Chantziaras wrote:
>> On 03/04/18 04:45, Daniel Frey wrote:
>>> I updated my PC today, and there was a lot of KDE-related packages being
>>> updated.
>>>
>>> As part of my usual update procedure I depclean'ed and ran
>>> revdep-rebuild.sh - and it wants to rebuild every single package on my
>>> system? Surely that has to be some kind of mistake?
>>>
>>> Anyone have any insight?
>>> [...]
>>
>> I ran into this problem too. revdep-rebuild works fine though (note the
>> lack of a ".sh" extension.)
>>
>> I think revdep-rebuild.sh is being retired in favor of revdep-rebuild,
>> and sometimes the old version acts funny.
Well, nuts. I wasn't using the new script because it always issued
warnings and other crap and that drove me crazy. I guess I'll have to
try the new script later.
Dan
next prev parent reply other threads:[~2018-04-03 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 1:45 [gentoo-user] KDE update revdep-rebuild.sh fail Daniel Frey
2018-04-03 16:29 ` [gentoo-user] " Nikos Chantziaras
2018-04-03 16:39 ` Elijah Mark Anderson
2018-04-03 19:57 ` Daniel Frey [this message]
2018-04-03 22:45 ` 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=dbc907bb-4a8f-b920-f488-4c6543d08315@gmail.com \
--to=djqfrey@gmail.com \
--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