I might be rushing into things, so I apologize if that's the case. Upon emerging updates for @world, I noticed I can't update to dev-lang/rust-1.23.0 because the virtual/rust package for the same version is missing. Is this intentional or was it forgotten in the bump process? Thanks in advance! Reproducible: Always
same here. added ~amd for dev-lang/rust dev-util/cargo virtual/rust and got: dev-lang/rust:stable (dev-lang/rust-1.23.0:stable/1.23::gentoo, ebuild scheduled for merge) conflicts with =dev-lang/rust-1.19.0* required by (virtual/rust-1.19.0:0/0::gentoo, ebuild scheduled for merge)
is there anything against to do a simple bump virtual/rust-1.23.0 I would be interested to try rust-1.23 with today coming firefox-58.0
(In reply to Ulenrich from comment #2) > is there anything against to do a simple bump > virtual/rust-1.23.0 > > I would be interested to try rust-1.23 with today coming firefox-58.0 The comments in https://bugs.gentoo.org/645416, particularly comment #1, might be useful here. There is nothing to stop you from manually installing rust-1.23 (without it being pulled in by a bumped virtual, I mean) and then 'eselect rust ...' to set that version as the system default. This worked here, but I don't know if doing it this way might short-circuit any dependency planning. Ditto, installing a bumped rust virtual in a local overlay, for example.
I have a virtual/rust bump ready, but that requires a bump to rust-bin, which had some ugly repoman warnings. I should be able to update rust-bin and virtual/rust tonight.
This has since been added by Patrick McLean (chutzpah).
