| 1 |
Hi all, |
| 2 |
|
| 3 |
This morning I got |
| 4 |
|
| 5 |
centaur ~ # emerge -vDuNp world |
| 6 |
|
| 7 |
These are the packages that would be merged, in order: |
| 8 |
|
| 9 |
Calculating dependencies... done! |
| 10 |
<snip/> |
| 11 |
[ebuild UD] kde-base/pykde4-4.5.1 [4.5.1-r1] USE="semantic-desktop |
| 12 |
(-aqua) -debug -doc -examples (-kdeenablefinal) (-kdeprefix)" 0 kB |
| 13 |
[1=>0] |
| 14 |
<snip/> |
| 15 |
|
| 16 |
Total: 9 packages (7 upgrades, 1 downgrade, 1 reinstall), Size of |
| 17 |
downloads: 10,550 kB |
| 18 |
Portage tree and overlays: |
| 19 |
[0] /usr/portage |
| 20 |
[1] /var/lib/layman/kde |
| 21 |
|
| 22 |
I decided that I did not want to go back to 4.5.1 so I added |
| 23 |
|
| 24 |
=kde-base/pykde4-4.5.1 |
| 25 |
|
| 26 |
to /etc/portage/package.mask. |
| 27 |
|
| 28 |
To my utmost surprise, I got the exact same result as before when |
| 29 |
running the above emerge command again. I tried it with one of the |
| 30 |
other upgrades mentioned and package.mask had the expected result. |
| 31 |
|
| 32 |
So I'm confused. Why is package.mask not having any (apparent) effect |
| 33 |
for pykde4? How do I prevent the downgrade? |
| 34 |
|
| 35 |
Cheers, |
| 36 |
Hilco |
Archives