Hi,
On Sat, Mar 19, 2011 at 10:04:47AM -0700, Joe Riel wrote:
> This morning I ran
>
> $ sudo aptitude update
> $ aptitude --simulate safe-upgrade
> Resolving dependencies...
> open: 16431; closed: 11272; defer: 105; conflict: 54
>
> At this point it kept churning; the numbe
Op 19-03-11 18:18, Joe Riel schreef:
> On Sat, 19 Mar 2011 10:04:47 -0700
> Joe Riel wrote:
>
>> This morning I ran
>>
>> $ sudo aptitude update
>> $ aptitude --simulate safe-upgrade
>> Resolving dependencies...
>> open: 16431; closed: 11272; defer: 105; conflict: 54
>>
>> At
On Sat, 19 Mar 2011 10:04:47 -0700
Joe Riel wrote:
> This morning I ran
>
> $ sudo aptitude update
> $ aptitude --simulate safe-upgrade
> Resolving dependencies...
> open: 16431; closed: 11272; defer: 105; conflict: 54
>
> At this point it kept churning; the number of open
This morning I ran
$ sudo aptitude update
$ aptitude --simulate safe-upgrade
Resolving dependencies...
open: 16431; closed: 11272; defer: 105; conflict: 54
At this point it kept churning; the number of open dependencies kept
increasing. Because of this I haven't run a real u
On Mon, May 03, 2010 at 01:24:23PM -0400, Rick Pasotto was
heard to say:
> I did send this to you but have not heard back. Just checking if I need
> to resend it.
No, I just haven't had time to analyze it.
Daniel
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a su
On Fri, Apr 30, 2010 at 07:07:21AM -0700, Daniel Burrows wrote:
> On Fri, Apr 30, 2010 at 09:31:28AM -0400, Rick Pasotto was
> heard to say:
> > Today's run of 'aptitude -s safe-upgrade' had been running for over an
> > hour and was using half my memory when I killed it. The status line was:
> >
On Fri, Apr 30, 2010 at 09:31:28AM -0400, Rick Pasotto was
heard to say:
> Today's run of 'aptitude -s safe-upgrade' had been running for over an
> hour and was using half my memory when I killed it. The status line was:
>
> open: 107756; closed: 119093; defer: 107181; conflict: 167
>
> There's
Today's run of 'aptitude -s safe-upgrade' had been running for over an
hour and was using half my memory when I killed it. The status line was:
open: 107756; closed: 119093; defer: 107181; conflict: 167
There's evidently some situation it can't resolve. How can I figure out
what package(s) cause
On Sat, Feb 09, 2008 at 14:41:14 -0600, cothrige wrote:
>
> I have managed to get myself in a bit of a bind regarding packages.
> Aptitude is reporting an error regarding an apparent half-finished
> upgrade to sun-java5-bin, and this has caused all things to stop.
> Unfortunately I have not found
"Adrian Levi" <[EMAIL PROTECTED]> writes:
>
> you could try running,
>
> #dpkg --configure -a
>
> But likely I suspect it will fail.
Yes, it appears to have changed little. Still failing.
> Another option is possibly to pre-empt it and go ahead and delete:
> /usr/share/icons/sun-java5.png
Actu
On 10/02/2008, cothrige <[EMAIL PROTECTED]> wrote:
>
> I have managed to get myself in a bit of a bind regarding packages.
> Aptitude is reporting an error regarding an apparent half-finished
> upgrade to sun-java5-bin, and this has caused all things to stop.
> Unfortunately I have not found a way
I have managed to get myself in a bit of a bind regarding packages.
Aptitude is reporting an error regarding an apparent half-finished
upgrade to sun-java5-bin, and this has caused all things to stop.
Unfortunately I have not found a way to resolve or work around this.
Here is what has been coming
12 matches
Mail list logo
