On 2015-08-08 13:35:10 -0400, Frank McCormick wrote:
Guess I'll wait until the churn slows:) And continue with apt-get.
or you could reinstall the latest aptitude version that was working;
this should be the version in stable and testing, 0.6.11-1+b1).
--
Vincent Lefèvre vinc...@vinc17.net -
I am running Debian Sid and for the past 4 or 5 days I have had to
switch from using aptitude to upgrade to using apt-get.
This is what I get:
root@frank-debian:/home/frank# aptitude
aptitude: symbol lookup error: aptitude: undefined symbol:
_ZN7cwidget7widgets5pager8set_textERKSsPKc
Frank McCormick:
This is what I get:
root@frank-debian:/home/frank# aptitude
aptitude: symbol lookup error: aptitude: undefined symbol:
_ZN7cwidget7widgets5pager8set_textERKSsPKc
You should search for existing bug reports and consider creating one
yourself. Although it might help to just
On Sat, 08 Aug 2015 10:43:49 -0400
Frank McCormick debianl...@videotron.ca wrote:
I am running Debian Sid and for the past 4 or 5 days I have had to
switch from using aptitude to upgrade to using apt-get.
This is what I get:
root@frank-debian:/home/frank# aptitude
aptitude: symbol
On 08/08/15 11:09 AM, Jochen Spieker wrote:
Frank McCormick:
This is what I get:
root@frank-debian:/home/frank# aptitude
aptitude: symbol lookup error: aptitude: undefined symbol:
_ZN7cwidget7widgets5pager8set_textERKSsPKc
You should search for existing bug reports and consider creating one
On 08/08/15 11:16 AM, Joe wrote:
On Sat, 08 Aug 2015 10:43:49 -0400
Frank McCormick debianl...@videotron.ca wrote:
I am running Debian Sid and for the past 4 or 5 days I have had to
switch from using aptitude to upgrade to using apt-get.
This is what I get:
root@frank-debian:/home/frank#
On 2015-08-08 10:43:49, Frank McCormick wrote:
I am running Debian Sid and for the past 4 or 5 days I have had to switch
from using aptitude to upgrade to using apt-get.
This is what I get:
root@frank-debian:/home/frank# aptitude
aptitude: symbol lookup error: aptitude: undefined symbol:
On 08/08/15 11:49 AM, Sebastian Ramacher wrote:
On 2015-08-08 10:43:49, Frank McCormick wrote:
I am running Debian Sid and for the past 4 or 5 days I have had to switch
from using aptitude to upgrade to using apt-get.
This is what I get:
root@frank-debian:/home/frank# aptitude
aptitude:
On 08/08/15 01:32 PM, Frank McCormick wrote:
On 08/08/15 11:49 AM, Sebastian Ramacher wrote:
On 2015-08-08 10:43:49, Frank McCormick wrote:
I am running Debian Sid and for the past 4 or 5 days I have had to
switch
from using aptitude to upgrade to using apt-get.
This is what I get:
Hello,
I started using aptitude a few days ago. I remember that at that time it
was showing many packages were broken and wanted to remove a bunch of
them. I then did some operation that I now forget which made aptitude to
'forget' about those packages and to clear the cache or some such
On Mon, Feb 19, 2007 at 15:40:10 -0500, H.S. wrote:
Hello,
I started using aptitude a few days ago. I remember that at that time it
was showing many packages were broken and wanted to remove a bunch of
them. I then did some operation that I now forget which made aptitude to
'forget'
On (19/02/07 22:08), Florian Kulzer wrote:
Being broken (i.e. having an unfulfilled dependency, pre-dependency, or
conflict) is a property of the package itself and should not depend on
the package manager. The package manager, on the other hand, can help
you to resolve breakages that occur,
Florian Kulzer wrote:
Being broken (i.e. having an unfulfilled dependency, pre-dependency, or
conflict) is a property of the package itself and should not depend on
the package manager. The package manager, on the other hand, can help
you to resolve breakages that occur, for example, during an
Hi,
After an aptitude upgrade last week on an etch machine, which pulled in
all the KDE 3.4 packages, I am having problems installing a few
packages.
For example
# aptitude install kate-plugins
returns
E: Unable to correct problems, you have held broken packages.
E: Unable to correct
on Tue, Oct 28, 2003 at 01:20:58PM +0100, Richard Lyons ([EMAIL PROTECTED]) wrote:
Is there a quicker way of locating the broken packages announced at the head
of the screen than scrolling through everything?
For packages in other than normal state:
dpkg -l \* | grep -v '^.. '
Peace.
--
On Mon, Nov 03, 2003 at 12:29:29PM +, Karsten M. Self wrote:
on Tue, Oct 28, 2003 at 01:20:58PM +0100, Richard Lyons ([EMAIL PROTECTED]) wrote:
Is there a quicker way of locating the broken packages announced at the head
of the screen than scrolling through everything?
For packages
On Tue, Oct 28, 2003 at 03:38:41PM +0100, Richard Lyons said
On Tuesday 28 October 2003 14:18, JG wrote:
Is there a quicker way of locating the broken packages
[...]
/~b
will bring you to the next broken package.
l~b
will narrow the packages list to only those that are broken.
On Wednesday 29 October 2003 09:40, Rob Weir wrote:
[...lots of good advice snipped...]
Thanks!
--
richard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Is there a quicker way of locating the broken packages announced at the head
of the screen than scrolling through everything?
TIA
--
richard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Tuesday 28 October 2003 14:18, JG wrote:
Is there a quicker way of locating the broken packages
[...]
/~b
will bring you to the next broken package.
l~b
will narrow the packages list to only those that are broken.
[...]
Thanks. I really haven't got used to this apt system yet. The
Richard Lyons wrote:
Is there a quicker way of locating the broken packages announced at the head
of the screen than scrolling through everything?
TIA
hit / to get the search box[or l to limit the display to just those
packages], search for ~b.
pgp0.pgp
Description: PGP signature
21 matches
Mail list logo
