-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Zac Medico wrote: > >> what I am going to propose here is a resolution strategy for this >> (although this whole thing simply tells me that portage misses some >> knowledge about the problem, like for example that dependencies should >> be enforced only at transaction boundaries, or simply that we have a >> class of dependencies that is irrelevant while system is in transient >> state) >> >> but, without trying to introduce overcomplicated solutions, as an >> user, I could solve the initial problem very easily: >> resolution strategy for it is to unmerge the old synce-0.13 packages, >> then the user will be able to install 0.14 packages. > > As said above, the problem is in the synce-gnomevfs-0.13 > dependencies, and there's nothing portage can do to change that. >
ok, after discussion on IRC came out that the SynCE 0.14 suite didn't include a synce-gnomevfs-0.14 package (so it has implicitly needed to be uninstalled the old 0.13 version). unfortunately portage doesn't handle this situation automatically. I had to add a !app-pda/synce-gnomevfs dep to synce-0.14. this will be never handled automatically by portage unfortunately, because synce-gnomevfs has no reverse-depend on anything (my fault!), so a user generally puts into the world set. the user will see a blocker when upgrading, but that's little pain. cheers - -- Federico Ferri -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkp5/sIACgkQV/B5axfzrPsIvgCfUFlEIwfZRsFxsMIKwrCzxwUQ rAcAnAsj9ej5d4n14LqjL7/tvLAwAv7z =hOZH -----END PGP SIGNATURE-----
