• Re: Bug#263274: still seeing error with apt-listchanges

    From Matthias Klose@1:229/2 to Eric Boyer on Tue Aug 17 17:30:12 2004
    XPost: linux.debian.ports.mips
    From: [email protected]

    Mips people,

    that seems to be a problem on mips only. Is this an issue with db4.2
    or should python be changed to work with another dbm implementation on
    mips, when using the anydbm module?

    Thanks, Matthias

    Eric Boyer writes:
    Unfortunately, the issue with apt-listchanges in bug 263274 doesn't seem to fixed yet... Although the changelog for 2.3.4-6 says it was fixed there, I tried both 2.3.4-6 and 2.3.4-8, and I'm still seeing the exact same error
    on my SGI Indy. If you have any suggestions, I'd be happy to supply more info or try something that may help identify what's causing the
    problem. Just as an additional piece of information, everything is working perfectly on another i386 box with similar configuration (current testing), but with python2.3 2.3.4-5...

    Eric



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Thiemo Seufer@1:229/2 to Matthias Klose on Tue Aug 17 18:00:20 2004
    XPost: linux.debian.ports.mips
    From: [email protected]

    Matthias Klose wrote:
    Mips people,

    that seems to be a problem on mips only. Is this an issue with db4.2
    or should python be changed to work with another dbm implementation on
    mips, when using the anydbm module?

    Most likely the same db4.2 porblem which hit slapd. Still unresolved.


    Thiemo


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Eric Boyer@1:229/2 to All on Sat Aug 7 06:10:06 2004
    From: [email protected]

    Unfortunately, the issue with apt-listchanges in bug 263274 doesn't seem to fixed yet... Although the changelog for 2.3.4-6 says it was fixed there, I tried both 2.3.4-6 and 2.3.4-8, and I'm still seeing the exact same error
    on my SGI Indy. If you have any suggestions, I'd be happy to supply more
    info or try something that may help identify what's causing the
    problem. Just as an additional piece of information, everything is working perfectly on another i386 box with similar configuration (current testing),
    but with python2.3 2.3.4-5...

    Eric



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)