When upgrading my box with paludis, openmotif-2.3.1 emerge and emerge infinitely in loop. It don't occure with portage. Reproducible: Always
Confirming this bug occurs for >1 person. To elaborate on the problem, there is not a problem with openmotif merging as such ( so don't confuse it with that compilation failure that was posted for openmotif several hours after this ), moreso that once openmotif is in fact merged, paludis keeps deciding it needs to be repeatedly merged, so that everything you merge basically will result in merging openmotif. I think this makes this a paludis bug, but its hard to say the cause.
(In reply to comment #1) > Confirming this bug occurs for >1 person. To elaborate on the problem, there is > not a problem with openmotif merging as such ( so don't confuse it with that > compilation failure that was posted for openmotif several hours after this ), > moreso that once openmotif is in fact merged, paludis keeps deciding it needs > to be repeatedly merged, so that everything you merge basically will result in > merging openmotif. > > I think this makes this a paludis bug, but its hard to say the cause. > The problem has disappeared this morning after syncing or upgrading my system but I don't know how nor why.
I suspect that this is connected to the removal of the old-style virtual/motif. Changing all packages' dependencies couldn't be done with one atomic commit, so maybe you were unlucky and synced with an intermediate state of the Portage tree. @Kent: I've now removed the virtual from profiles; can you please re-sync in a few hours, and drop a note here if the problem still persists?
(In reply to comment #3) > I suspect that this is connected to the removal of the old-style virtual/motif. > Changing all packages' dependencies couldn't be done with one atomic commit, so > maybe you were unlucky and synced with an intermediate state of the Portage > tree. Yes I remember that paludis show reason for (re)compiling openmotif : virtual/motif. Thanks Ulrich.
Please make use of the Paludis bug tracker.
(In reply to comment #3) > I suspect that this is connected to the removal of the old-style virtual/motif. > Changing all packages' dependencies couldn't be done with one atomic commit, so > maybe you were unlucky and synced with an intermediate state of the Portage > tree. > > @Kent: I've now removed the virtual from profiles; can you please re-sync in a > few hours, and drop a note here if the problem still persists? > Problem Gone. @Carsten Only myself commented here after seeing it fly past on #gentoo-bugs ;) Had I not seen it there this little inconvenience may have gone completely ignored :)
Reopening for proper closing.
