Summary: | Key directories and symlink not created on net-misc/ltsp-4.1-r1 emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | William Arlofski <waa-gentoo> |
Component: | Current packages | Assignee: | Heinrich Wendel (RETIRED) <lanius> |
Status: | RESOLVED CANTFIX | ||
Severity: | blocker | CC: | loial |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
William Arlofski
2005-08-15 05:39:54 UTC
unmerge and remerge it, it's a portage bug Hi Heinrich, thanks for your quick response. ...But it is hard to unmerge, re-emerge and then possibly have to completely reconfigure a piece of software that is being used by many clients in a production environment so that can't really be my only option can it? Will I be forced to mask ltsp from any future upgrades with /etc/portage/package.mask to prevent ltsp from getting whacked when a new package is available? Also, this problem exists on an initial "emerge ltsp" not only when the package is re-emerged. Can you point me to the portage bug so I might understand more clearly what is happening? Thanks again for the quick response. Bill Only revision bumps (-r updates) are affected, new versions, like 4.2 not. Furthermore your config *should* not be touched. I also experienced the problem after re-emerging net-misc/ltsp-4.1.1 and would like to know the portage bug report number, I cannot seem to find it anywhere... |