1 |
On 01/15/2017 12:39 PM, wabe wrote: |
2 |
> Daniel Frey <djqfrey@×××××.com> wrote: |
3 |
> |
4 |
>> On 2017-01-15 11:28 AM, wabe wrote: |
5 |
>> |
6 |
>>> Since some days, portage moans about a dependency conflict when I |
7 |
>>> update my system: |
8 |
>>> |
9 |
>>> |
10 |
>>> These are the packages that would be merged, in order: |
11 |
>>> |
12 |
>>> Calculating dependencies... done! |
13 |
>>> |
14 |
>>> Total: 0 packages, Size of downloads: 0 KiB |
15 |
>>> |
16 |
>>> WARNING: One or more updates/rebuilds have been skipped due to a |
17 |
>>> dependency conflict: |
18 |
>>> |
19 |
>>> app-text/xmlto:0 |
20 |
>>> |
21 |
>>> (app-text/xmlto-0.0.26-r1:0/0::gentoo, ebuild scheduled for |
22 |
>>> merge) conflicts with |
23 |
>>> >=app-text/xmlto-0.0.26-r1[text(+)] required by |
24 |
>>> >(x11-misc/xdg-utils-1.1.1-r1:0/0::gentoo, installed) |
25 |
>>> > |
26 |
>>> |
27 |
>>> Nothing to merge; quitting. |
28 |
>>> |
29 |
>>> |
30 |
>>> I don't understand this because these versions are already |
31 |
>>> installed on my system: |
32 |
>>> |
33 |
>>> [I] app-text/xmlto |
34 |
>>> Available versions: 0.0.26-r1{tbz2} ~0.0.28-r1 {latex text} |
35 |
>>> Installed versions: 0.0.26-r1{tbz2}(19:30:25 12/02/15)(text |
36 |
>>> -latex) |
37 |
>>> |
38 |
>>> [I] x11-misc/xdg-utils |
39 |
>>> Available versions: 1.1.1^t{tbz2} 1.1.1-r1^t{tbz2} {doc |
40 |
>>> +perl} Installed versions: 1.1.1-r1^t{tbz2}(20:14:37 01/15/17)(doc |
41 |
>>> perl) |
42 |
>>> |
43 |
>>> |
44 |
>>> |
45 |
>>> How can a package conflict with itself (same version)? |
46 |
>>> |
47 |
>>> -- |
48 |
>>> Regards |
49 |
>>> wabe |
50 |
>>> |
51 |
>> |
52 |
>> From what I can tell it's telling you that the xmlto package is too |
53 |
>> old. xdg-utils needs a newer version, and I suspect that it's marked |
54 |
>> unstable. If you unmask a newer version of xmlto the error will go |
55 |
>> away. |
56 |
> |
57 |
> That was also my first thought. But then I noticed the "greater or |
58 |
> equal" sign ">=". According to that, the installed version should |
59 |
> be sufficient. |
60 |
|
61 |
Whoops! I missed the '=' there. I wonder if there was a bug when it was |
62 |
evaluating dependencies. |
63 |
|
64 |
> |
65 |
> And I also expect that a stable package doesn't depend on an unstable |
66 |
> (~amd64) one. |
67 |
> |
68 |
> However you are right. Unmasking xmlto resolved the conflict. |
69 |
|
70 |
It doesn't happen often, but it does happen. I can only remember maybe a |
71 |
half dozen times over the last 10-12 years. The devs do what they can to |
72 |
minimize this, I would presume. |
73 |
|
74 |
Dan |