| View previous topic :: View next topic |
| Author |
Message |
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9911
Location: almost Mile High in the USA
|
 Posted: Sat Mar 19, 2016 6:10 pm Post subject: emerge --fetch seems to generate a different dependency list |
 |
|
portage-2.2.26 (current latest, but I've seen this behavior for past couple of versions)
For some reason
emerge --update --deep --newuse --pretend @world
will have a clean run without blocks and slot conflicts. A few packages will get rebuilt. However if I run
emerge --update --deep --newuse --fetch --pretend @world
The latter generates blocks and slot conflicts... Of course this depends on what's currently installed on the system and what's new in the portage tree, but this seems a bit weird that the two generate different results... any ideas why they would be different?
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
 |
Josef.95
Advocate
Joined: 03 Sep 2007
Posts: 4699
Location: Germany
|
| Posted: Sat Mar 19, 2016 7:16 pm Post subject: |
|
|
--fetch
is not a valid emerge option. You search presumably
--fetchonly |
|
| Back to top |
|
|
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9911
Location: almost Mile High in the USA
|
| Posted: Sat Mar 19, 2016 9:26 pm Post subject: |
|
|
Oops. Actually I am using --fetchonly, as I used the single letter options, but I figure that the long names would have been easier to figure out. However, since it aliases incorrectly, I suppose not. Oh well.
So it is indeed the problem option is --fetchonly instead of simply --fetch.
And dangit, the subject character limit means I have to delete some characters to make fetchonly fit... :(
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9911
Location: almost Mile High in the USA
|
| Posted: Sat Apr 09, 2016 6:16 pm Post subject: |
|
|
Ok, it happened again:
When I tried --fetchonly vs just pretend only, the build list differs:
emerge -uDNfp @world vs emerge -uDNp @world
-These are the packages that would be merged, in order:
+These are the packages that would be fetched, in order:
...
[ebuild U ] net-dns/avahi-0.6.32 [0.6.31-r10]
+[ebuild UD ] gnome-base/gnome-desktop-3.16.2 [3.18.2]
[ebuild U ] sys-fs/udisks-2.1.7 [2.1.4] USE="acl%*"
...
-[ebuild rR ] gnome-extra/gnome-tweak-tool-3.18.1-r1
+
So it looks like for some reason with --fetchonly, it wants to downgrade gnome...
Why, is still a mystery.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
|
Portage & Programming
