On 08/07/2015 14:53, Peter Humphrey wrote:
It's my turn to seek help understanding portage.
Yesterday my daily update required a reinstallation of kdelibs with the
nepomuk flag switched on, and that pulled in nepomuk-core and nepomuk-widgets.
But according to equery, those three packages
It's my turn to seek help understanding portage.
Yesterday my daily update required a reinstallation of kdelibs with the
nepomuk flag switched on, and that pulled in nepomuk-core and nepomuk-widgets.
But according to equery, those three packages have only a conditional
dependence on nepomuk:
On Wednesday 08 July 2015 15:13:36 Alan McKinnon wrote:
On 08/07/2015 14:53, Peter Humphrey wrote:
It's my turn to seek help understanding portage.
Yesterday my daily update required a reinstallation of kdelibs with the
nepomuk flag switched on, and that pulled in nepomuk-core and
On Wednesday 08 July 2015 15:13:36 Alan McKinnon wrote:
On 08/07/2015 14:53, Peter Humphrey wrote:
It's my turn to seek help understanding portage.
Yesterday my daily update required a reinstallation of kdelibs with the
nepomuk flag switched on, and that pulled in nepomuk-core and
On 09/07/2015 01:05, Peter Humphrey wrote:
On Wednesday 08 July 2015 15:13:36 Alan McKinnon wrote:
On 08/07/2015 14:53, Peter Humphrey wrote:
It's my turn to seek help understanding portage.
Yesterday my daily update required a reinstallation of kdelibs with the
nepomuk flag switched on, and
On Thursday 09 July 2015 01:10:29 Alan McKinnon wrote:
Bitter hard experience with the same mistake has taught me to always do
this when faced with such issues:
egrep -r nepomuk|semantic|akonadi /etc/portage/
Indeed. It's just a matter of remembering to do that at the right time.
[sigh]
--
6 matches
Mail list logo
