Zack Medico
Post details: Handling File Collisions Between Blocking Packages
9 May , 2008
Handling File Collisions Between Blocking Packages
If one package blocks another package, the two packages conflict such that they cannot be installed simultaneously. These conflicts are often due to file collisions. In some cases, packages that block each other can be temporarily installed simultaneously. In order to resolve file collisions that occur between two blocking packages that are installed simultaneously, the overlapping files must be removed from the contents list of the package which was installed first.
Some cases may exist such that temporary simultaneous installation of blocking packages will cause some sort of problem. However, this type of solution will only be chosen for blockers that can not be satisfied in any other way, such as by simple adjustment of merge order. In addition, this type of solution will not be chosen if a blocking package will overwrite files belonging to packages from the system set, or packages that are runtime dependencies of Portage itself. These constraints serve to limit the probability that a chosen solution will cause an unforeseen problem.
gtk-doc-am vs. gtk-doc-1.8-r2
These are the packages that would be merged, in reverse order: Calculating dependencies... done! [blocks b ] dev-util/gtk-doc-am (is blocking dev-util/gtk-doc-1.8-r2) [uninstall ] dev-util/gtk-doc-1.8-r2 USE="emacs -debug -doc" [nomerge ] x11-libs/gtk+-2.12.9-r2 USE="X cups jpeg tiff xinerama -debug -doc -vim-syntax" [ebuild N ] dev-util/gtk-doc-am-1.10-r1 0 kB Total: 1 package (1 new, 1 uninstall), Size of downloads: 0 kB Conflict: 1 block
coreutils vs. mktemp
These are the packages that would be merged, in reverse order: Calculating dependencies... done! [nomerge ] sys-apps/coreutils-6.11 [6.9-r1] USE="acl nls xattr (-selinux) -static -vanilla%" [blocks b ] sys-apps/mktemp (is blocking sys-apps/coreutils-6.11) [blocks b ] >=sys-apps/coreutils-6.10 (is blocking sys-apps/mktemp-1.5) [uninstall ] sys-apps/mktemp-1.5 [ebuild U ] sys-apps/coreutils-6.11 [6.9-r1] USE="acl nls xattr (-selinux) -static -vanilla%" 0 kB Total: 1 package (1 upgrade, 1 uninstall), Size of downloads: 0 kB Conflict: 2 blocks
Trackback address for this post:
http://planet.gentoo.org/developers/htsrv/trackback.php/1521
Comments, Trackbacks:
Permalink
10 May , 2008 @ 03:54 · http://dev.gentoo.org/~zmedico/ Permalink
10 May , 2008 @ 04:02 Well done for getting the automatic uninstall, man, and thanks from someone who'll save a lot of time as a result.
Permalink
10 May , 2008 @ 04:53 · http://dev.gentoo.org/~zmedico/ In some cases, the smoothest way to perform an upgrade is to merge the new package files into place and then remove any files that belong to the old package (only the ones that do no overlap with the new package). That's how portage has always done it for normal upgrades within a package slot.
Now, in some cases, we have similar behavior with packages that block each other, so the "smooth upgrade" process is no longer confined to a single package slot. The process can be spread over multiple packages that block each other.
Permalink
10 May , 2008 @ 05:39 Permalink
10 May , 2008 @ 09:21 And thanks for looking at that, definitely an itchy spot there.
Permalink
13 May , 2008 @ 02:14 · http://dev.gentoo.org/~zmedico/ Indeed, some cases may exist such that temporary simultaneous installation of blocking packages will cause some sort of problem. However, the solver will only choose this type of solution for blockers that it is not able to satisfy in any other way, such as by simple adjustment of merge order. In addition, it will not choose this type of solution if a blocking package will overwrite files belonging to either of the following types of packages:
- Those that belong to the system set.
- Required runtime dependencies of portage itself.
The above constraints serve to limit the probability that the chosen solution will cause some sort of problem. If testing shows that these constraints are not sufficient to separate good solutions from bad solutions in a significant number of cases, then we will have to devise additional constraints if possible, or else extend blocker syntax to indicate which type of solution is appropriate for a given blocker relationship.
Permalink
13 May , 2008 @ 04:55 I tried both pkgcore and paludis, and while they are nice in their own ways, I just feel more comfortable with portage on production machines, and I'm very glad it's getting some love, too. Keep up the good work!
Permalink
4 June, 2008 @ 13:09 Just saw this referenced in GMN, looks fantastic, but after a sync, emerge -s only offers portage 2.1.4.4 as listed... I have that version installed, and it doesn't do blocker removal.
When/where do we get Portage 2.1.5?
ART
Permalink
5 June, 2008 @ 20:09 · http://dev.gentoo.org/~zmedico/ echo "=sys-apps/portage-2.1.5*" >> /etc/portage/package.keywords
See the Test Particular Versions part of the Handbook for more information about keywords.
Portage 2.1.5.4 is probably good enough to be marked stable but it needs a couple more weeks of testing first.
Permalink
5 June, 2008 @ 20:52 Leave a comment:
Zack Medico
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| << < | ||||||
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 | |||
Search
Archives
- May 2008 (2)
- April 2008 (1)
- August 2007 (1)
- More...
Misc
XML Feeds
What is RSS?
Who's Online?
- Guest Users: 61
powered by
