Steve Langasek [EMAIL PROTECTED] writes:
Subsequently, a version was uploaded to unstable which used the same version
as had previously been in experimental, but with a different ABI.
Ok, I understand now; so a new experimental aptitude (linked against the
new ABI) will fix everything.
Thanks
On Wed, Nov 30, 2005 at 02:27:27PM +0900, Miles Bader wrote:
When trying to run aptitude:
$ sudo aptitude
aptitude: symbol lookup error: aptitude: undefined symbol:
_Z14ReadConfigFileR13ConfigurationSsbj
I can confirm this bug.
Greetings
Marc
--
On Wed, Nov 30, 2005 at 09:53:29AM +0100, Marc Haber wrote:
On Wed, Nov 30, 2005 at 02:27:27PM +0900, Miles Bader wrote:
When trying to run aptitude:
$ sudo aptitude
aptitude: symbol lookup error: aptitude: undefined symbol:
_Z14ReadConfigFileR13ConfigurationSsbj
I can
On mer, nov 30, 2005, Marc Haber wrote:
downgrading apt to 0.6.42.3exp1 helped. Versioned depends or conflicts
needed.
For me, that was only enough to start aptitude, but it's still useless,
when installing I get:
ImportError: /usr/lib/python2.3/site-packages/apt_pkg.so: undefined
symbol:
On Wed, Nov 30, 2005, Loic Minier wrote:
For me, that was only enough to start aptitude, but it's still useless,
when installing I get:
ImportError: /usr/lib/python2.3/site-packages/apt_pkg.so: undefined
symbol: _Z15CheckDomainListRKSsS0_
Actually, installing works fine, but
On Wed, Nov 30, 2005 at 02:10:45PM +0100, Loic Minier wrote:
On mer, nov 30, 2005, Marc Haber wrote:
downgrading apt to 0.6.42.3exp1 helped. Versioned depends or conflicts
needed.
For me, that was only enough to start aptitude, but it's still useless,
when installing I get:
This is likely because the soname of apt in unstable is identical to the
soname of apt in experimental, but they present different ABIs. I don't
think I can do anything to fix this for you.
Daniel
signature.asc
Description: Digital signature
Daniel Burrows [EMAIL PROTECTED] writes:
This is likely because the soname of apt in unstable is identical to the
soname of apt in experimental, but they present different ABIs. I don't
think I can do anything to fix this for you.
That sounds like a (serious) bug with apt...
Maybe the
Daniel Burrows [EMAIL PROTECTED] writes:
This is likely because the soname of apt in unstable is identical to the
soname of apt in experimental, but they present different ABIs. I don't
think I can do anything to fix this for you.
FWIW, I installed apt from experimental (version 0.6.43exp1)
On Thu, Dec 01, 2005 at 10:39:35AM +0900, Miles Bader wrote:
Daniel Burrows [EMAIL PROTECTED] writes:
This is likely because the soname of apt in unstable is identical to the
soname of apt in experimental, but they present different ABIs. I don't
think I can do anything to fix this for
Steve Langasek [EMAIL PROTECTED] writes:
That sounds like a (serious) bug with apt...
Maybe the right thing is to re-assign the bug to apt.
Not really. If experimental breaks, you keep both pieces.
Um, sure, but it _is_ a bug, right? That is, if apt moves to unstable
in the current state
On Thu, Dec 01, 2005 at 12:57:06PM +0900, Miles Bader wrote:
Steve Langasek [EMAIL PROTECTED] writes:
That sounds like a (serious) bug with apt...
Maybe the right thing is to re-assign the bug to apt.
Not really. If experimental breaks, you keep both pieces.
Um, sure, but it _is_ a
Steve Langasek [EMAIL PROTECTED] writes:
Um, sure, but it _is_ a bug, right? That is, if apt moves to unstable
in the current state (ABI change, no version change), then it will be
officially broken.
It will be broken *only* with respect to packages in experimental.
I don't understand this
On Thu, Dec 01, 2005 at 04:09:21PM +0900, Miles Bader wrote:
Steve Langasek [EMAIL PROTECTED] writes:
Um, sure, but it _is_ a bug, right? That is, if apt moves to unstable
in the current state (ABI change, no version change), then it will be
officially broken.
It will be broken *only*
On Wed, Nov 30, 2005 at 11:26:30PM -0800, Steve Langasek wrote:
On Thu, Dec 01, 2005 at 04:09:21PM +0900, Miles Bader wrote:
Steve Langasek [EMAIL PROTECTED] writes:
Um, sure, but it _is_ a bug, right? That is, if apt moves to unstable
in the current state (ABI change, no version
Package: aptitude
Version: 0.4.0-3experimental2
Severity: grave
Justification: renders package unusable
When trying to run aptitude:
$ sudo aptitude
aptitude: symbol lookup error: aptitude: undefined symbol:
_Z14ReadConfigFileR13ConfigurationSsbj
There are reports (#321651, #321673) of
16 matches
Mail list logo
