Aníbal Monsalve Salazar <[EMAIL PROTECTED]> writes:
>>The basic symptom was that it acted as if I was a different user: I
>>could not access my files unless they were world-readable.
>
> Please try the workaround found by Paul Collins (add sec=sys to the
> client's mount options) and tell us if it
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.
Than
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 underst
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
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.4
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
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 a
Package: libiiimp1
Version: 12.3.91-0.1
Severity: grave
Justification: renders package unusable
When installing:
(Reading database ... 155154 files and directories currently installed.)
Unpacking libiiimp1 (from .../libiiimp1_12.3.91-0.1_i386.deb) ...
dpkg: error processing
/var/cache/
Package: postfix
Version: 2.2.2-1
Followup-For: Bug #304559
I definitely think postfix shouldn't be spitting out warnings for such a
harmless situation -- not only is it confusing (and annoying) for users
to see them, but they confuse other software as well.
For instance, Emacs uses the /usr/li
9 matches
Mail list logo
