On Thu, Oct 14, 2010 at 2:38 AM, Dean Matzkov wrote:
> Well, if you were running portage-2-2_rc67, that's already pretty much
> bleeding edge =P
Except there have been about 30 update releases since that one. Only
the Changelog knows how many things have been fixed in that time. :)
On 14 October 2010 01:36, Neil Bothwick wrote:
> On Wed, 13 Oct 2010 18:52:14 -0700, Hilco Wijbenga wrote:
>> > Have you tried upgrading to the latest version of Portage 2.2? The
>> > newest version in the tree is currently portage-2.2_rc95, while you're
>> > still using portage-2.2_rc67. Perhaps
On 14 October 2010 00:38, Dean Matzkov wrote:
> Well, if you were running portage-2-2_rc67, that's already pretty much
> bleeding edge =P
Yeah, I was wondering if someone would notice that. :-)
> But just out of curiosity, though, is there any particular reason
> you're not running a more-stable
On Wed, 13 Oct 2010 18:52:14 -0700, Hilco Wijbenga wrote:
> > Have you tried upgrading to the latest version of Portage 2.2? The
> > newest version in the tree is currently portage-2.2_rc95, while you're
> > still using portage-2.2_rc67. Perhaps there's a bug causing this that
> > was fixed in sub
Well, if you were running portage-2-2_rc67, that's already pretty much
bleeding edge =P
But just out of curiosity, though, is there any particular reason
you're not running a more-stable version of Portage, such as v2.1.8.3
or v2.1.9.17? The 2.2 release-candidates are hard-masked for a reason
- wh
On 13 October 2010 15:29, Dean Matzkov wrote:
> Have you tried upgrading to the latest version of Portage 2.2? The
> newest version in the tree is currently portage-2.2_rc95, while you're
> still using portage-2.2_rc67. Perhaps there's a bug causing this that
> was fixed in subsequent release?
I
On Wed, Oct 13, 2010 at 12:05:40PM -0700, Hilco Wijbenga wrote:
> * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
> * with exit value -1.
> *
> * The problem occurred while executing the ebuild file named
> * 'arora-0.11.0.ebuild' located in the '/var/db/pkg/www-
> * c
Have you tried upgrading to the latest version of Portage 2.2? The
newest version in the tree is currently portage-2.2_rc95, while you're
still using portage-2.2_rc67. Perhaps there's a bug causing this that
was fixed in subsequent release?
On 13 October 2010 13:23, Paul Hartman wrote:
> On Wed, Oct 13, 2010 at 2:05 PM, Hilco Wijbenga
> wrote:
>> Hi all,
>>
>> I'm trying to unmerge some packages. They all fail like this:
>
>
>> * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
>> * with exit value -1.
>> *
>
On Wed, Oct 13, 2010 at 2:05 PM, Hilco Wijbenga
wrote:
> Hi all,
>
> I'm trying to unmerge some packages. They all fail like this:
> * The 'prerm' phase of the 'www-client/arora-0.11.0' package has failed
> * with exit value -1.
> *
> * The problem occurred while executing the ebuild file na
Hi all,
I'm trying to unmerge some packages. They all fail like this:
centaur ~ # emerge --unmerge arora
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean ` to check for reverse dependencies before
* removing packages.
www-client/arora
select
11 matches
Mail list logo