Jorge Morais wrote:
>>> Looking at /usr/portage/app-editors/emacs/emacs-22.3-r2.ebuild, I see
>>> that it depends unconditionally on app-emacs/emacs-common-gentoo.
>>> You cannot eliminate this dependency by changing USE flags.
>>> The most natural solution is to tell Portage to accept the package
> > Looking at /usr/portage/app-editors/emacs/emacs-22.3-r2.ebuild, I see
> > that it depends unconditionally on app-emacs/emacs-common-gentoo.
> > You cannot eliminate this dependency by changing USE flags.
> > The most natural solution is to tell Portage to accept the package
> > app-emacs/emacs-
Jorge Morais wrote:
> On Sat, 28 Mar 2009 14:47:56 -0400
> "John P. Burkett" wrote:
>
>> Starting March 14, whenever I have tried doing
>> emerge -D -uav system
>> the response has included
>> !!! All ebuilds that could satisfy
>> ">=app-emacs/emacs-common-gentoo-1[X]" have been masked.
>>
>> On
On Sat, 28 Mar 2009 14:47:56 -0400
"John P. Burkett" wrote:
> Starting March 14, whenever I have tried doing
> emerge -D -uav system
> the response has included
> !!! All ebuilds that could satisfy
> ">=app-emacs/emacs-common-gentoo-1[X]" have been masked.
>
> On my x86 box, the response adds
>
Starting March 14, whenever I have tried doing
emerge -D -uav system
the response has included
!!! All ebuilds that could satisfy
">=app-emacs/emacs-common-gentoo-1[X]" have been masked.
On my x86 box, the response adds
- app-emacs/emacs-common-gentoo-1.0 (masked by: ~x86 keyword)
On my amd64 mach
5 matches
Mail list logo