Current behavior is the following, when I get:
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] dev-libs/libpcre-8.30-r2 [8.12] USE="bzip2 cxx jit%* readline%* recursion-limit (unicode) zlib -pcre16% -static-libs" 1,220 kB
[ebuild R ] sys-apps/busybox-1.19.3-r1 USE="pam -ipv6 -livecd% -make-symlinks -mdev -savedconfig (-selinux) -static" 0 kB
[ebuild N ~] dev-util/fix-la-relink-command-0.1.1 5 kB
[ebuild U ~] dev-libs/libxml2-2.8.0-r1 [2.8.0_rc1] USE="icu python readline test -debug -doc -examples -ipv6 -lzma -static-libs" 4,801 kB
[ebuild U ] dev-python/pycrypto-2.6 [2.4.1] USE="gmp -doc" 434 kB
[ebuild U ] net-libs/neon-0.29.6-r1 [0.29.6] USE="nls ssl zlib -doc -expat -gnutls -kerberos -libproxy -pkcs11 -static-libs" LINGUAS="-cs -de -fr -ja -nn -pl -ru -tr -zh_CN" 0 kB
[ebuild U ] media-gfx/graphviz-2.26.3-r4 [2.26.3-r3] USE="cairo gtk nls -doc -examples -java -lasi -perl -python -ruby -static-libs -tcl" 16,692 kB
[ebuild U ] dev-util/dialog-1.1.20120215 [1.1.20110707-r1] USE="nls unicode -examples -minimal -static-libs" 431 kB
[ebuild FU ~] sci-misc/mendeleydesktop-1.5.2 [1.5.1] 29,589 kB
[ebuild U ~] app-emulation/emul-linux-x86-soundlibs-20120520-r1  USE="alsa pulseaudio* -development" 0 kB
Total: 10 packages (8 upgrades, 1 new, 1 reinstall), Size of downloads: 53,169 kB
Fetch Restriction: 1 package (1 unsatisfied)
Fetch instructions for sci-misc/mendeleydesktop-1.5.2:
* Adjusting permissions for FEATURES=ccache: '/var/tmp/tmpb2h_9o/ccache'
* Please download mendeleydesktop-1.5.2-linux-x86_64 from:
* and move it to /usr/distfiles
Would you like to merge these packages? [Yes/No]
If I let it go ahead (without downloading that file manually because I don't have time to go to download it manually), emerge will later fail because it (obviously) cannot merge that fetch restricted package.
Wouldn't be better if portage could recheck for fetch restricted packages once I decide to go ahead and simply exclude offending package from update?
Thanks a lot
You could use --keep-going. Do you want a separate option just for fetch failures?
I use it, the problem is that even with that emerge tries to merge a package that will surely fail (as fetch restriction wasn't solved) and, then, exit with error status causing other concatenated commands (with &&) to fail (revdep-rebuild, emerge -a --depclean...)
We could add a special option that prevents fetch restricted packages from affecting the return code of emerge when they can't be fetched.
Alternatively, we could add an ACCEPT_RESTRICT variable that you could use like ACCEPT_PROPERTIES to mask fetch restricted packages.