Mattias Dahlberg <[EMAIL PROTECTED]> writes:
> rpmdrake-2.0-13mdk
>
> When I put a checkmark after a package, rpmdrake-remove exits with the error:
>
> Can't use an undefined value as a HASH reference at /usr/sbin/rpmdrake-remove line
>416.
me sucks, didn't test rpmdrake-remove after adding t
rpmdrake-2.0-13mdk
When I put a checkmark after a package, rpmdrake-remove exits with the error:
Can't use an undefined value as a HASH reference at /usr/sbin/rpmdrake-remove line 416.
Regards,
Mattias
"Murray J. Root" <[EMAIL PROTECTED]> writes:
> > gc fixed that in the current version. It now restarts after an action
> > completes.
> >
>
> It's better, but it still looks rather silly to have it close
> and restart. It should just return to the file list.
It's true, I'll have a look but si
On Thu, 8 Aug 2002 15:17:31 -0700
Todd Lyons <[EMAIL PROTECTED]> wrote:
> Jaco Greeff wrote on Thu, Aug 08, 2002 at 09:18:12AM +0200 :
> >
> > I must admit, I don't like the fact that the rpmdrake* tools close down
> > after installing/uninstalling one package.
>
> gc fixed that in the current
Jaco Greeff wrote on Thu, Aug 08, 2002 at 09:18:12AM +0200 :
>
> I must admit, I don't like the fact that the rpmdrake* tools close down
> after installing/uninstalling one package.
gc fixed that in the current version. It now restarts after an action
completes.
Blue skies...
(I'd like to say "idiocy", but ...)
I went into rpmdrake and select old kernel-source and kernel and
kernel-secure. Next step presented me with amusing dialog:
In order to satisfy dependencies these packages will be removed:
wizards...
...
kdeadmin
drakconf
...
basesystem
...
May be it should
