* Neil Bothwick:
> That's because ~ doesn't mean unstable, it means testing. Stable in
> this context means less likely to change, not less likely to fall
> over. Plus the differentiation is for the ebuilds, not the software
> itself.
It is also worth mentioning that ebuilds cannot be added to
On Sun, 18 Nov 2018 00:33:41 -0500, Andrew Udvare wrote:
> I switched fully to ACCEPT_KEYWORDS="~amd64" (make.conf) after running
> mixed for a while. These kinds of issues come up too often and I don't
> have a lot of time to solve them, plus for my dev machine I just don't
> notice stable vs
On 11/17/2018 10:33 PM, Andrew Udvare wrote:
I switched fully to ACCEPT_KEYWORDS="~amd64" (make.conf) after running
mixed for a while. These kinds of issues come up too often and I don't
have a lot of time to solve them, plus for my dev machine I just don't
notice stable vs unstable most of
On 18/11/2018 00:23, Grant Taylor wrote:
>
> I'm not completely sure what that means. I'm guessing you're asking
> about accept_keywords. I'm mostly (?) running stock amd64. I have
> added ~amd64 to some packages for various reasons over the 2+ years that
> this install has been around.
I
On 11/17/2018 10:13 PM, Andrew Udvare wrote:
It looks like you need to unmask virtual/cargo because you need to have
virtual/cargo 1.30.1. These version numbers have to match.
That seems to have done it.
I added virtual/cargo to /etc/portage/package.accept_keywords/cargo
which did have
On 17/11/2018 23:53, Grant Taylor wrote:
> On 11/17/2018 07:58 PM, Adam Carter wrote:
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild N ] dev-util/cargo-0.30.0 USE="-debug -doc -libressl"
> ABI_X86="(64) -32 (-x32)"
> [ebuild N
On 11/17/2018 07:58 PM, Adam Carter wrote:
Do you have virtual/cargo installed?
Not presently.
I removed the following packages as part of troubleshooting.
dev-util/cargo virtual/cargo dev-lang/rust virtual/rust
I then (re)installed dev-lang/rust per Andrew U.'s recommendation.
Sorry
On Sun, Nov 18, 2018 at 1:55 PM Adam Carter wrote:
> On Sun, Nov 18, 2018 at 1:52 PM Grant Taylor <
> gtay...@gentoo.tnetconsulting.net> wrote:
>
>> On 11/17/2018 06:11 PM, Andrew Udvare wrote:
>> > Uninstall dev-util/cargo and emerge -1 dev-lang/rust. dev-lang/rust
>> > comes with Cargo.
>>
>>
On Sun, Nov 18, 2018 at 1:52 PM Grant Taylor <
gtay...@gentoo.tnetconsulting.net> wrote:
> On 11/17/2018 06:11 PM, Andrew Udvare wrote:
> > Uninstall dev-util/cargo and emerge -1 dev-lang/rust. dev-lang/rust
> > comes with Cargo.
>
> Hum. That didn't solve the problem.
>
Do you have
>
> > I also had to
> >
> > ln -s /usr/bin/cargo-1.30.1 /usr/bin/cargo
> >
> > To get things working, YMMV.
>
> The correct way is to run `eselect rust set 1`. There are other symlinks
> besides cargo.
>
>
That was already set for me, but i re-ran it, and atime on the symlink was
reset. Thanks.
On 11/17/2018 06:11 PM, Andrew Udvare wrote:
Uninstall dev-util/cargo and emerge -1 dev-lang/rust. dev-lang/rust
comes with Cargo.
Hum. That didn't solve the problem.
#[5828:root@alpha:~]# eselect rust list
Available Rust versions:
[1] rust-1.30.1 *
#[5829:root@alpha:~]# emerge -aDuN
> On 2018-11-17, at 20:16, Adam Carter wrote:
>
> > On 2018-11-17, at 19:24, Grant Taylor
> > wrote:
> >
> > So, will someone help me fix this cargo / rust blockage so that I can
> > finish my @world emerge?
>
> Uninstall dev-util/cargo and emerge -1 dev-lang/rust. dev-lang/rust comes
>
>
> > On 2018-11-17, at 19:24, Grant Taylor
> wrote:
> >
> > So, will someone help me fix this cargo / rust blockage so that I can
> finish my @world emerge?
>
> Uninstall dev-util/cargo and emerge -1 dev-lang/rust. dev-lang/rust comes
> with Cargo.
>
>
I also had to
ln -s /usr/bin/cargo-1.30.1
> On 2018-11-17, at 19:24, Grant Taylor
> wrote:
>
> So, will someone help me fix this cargo / rust blockage so that I can finish
> my @world emerge?
Uninstall dev-util/cargo and emerge -1 dev-lang/rust. dev-lang/rust comes with
Cargo.
--
Andrew Udvare
14 matches
Mail list logo
