home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   MYSTIC      Mystic support echo      16,010 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 15,887 of 16,010   
   Dan Clough to cr1mson   
   Re: g00r00 - a49 32-bit alpha   
   14 Jan 25 16:19:04   
   
   TZUTC: -0600   
   MSGID: 4469.fido_mystic@1:135/115 2bec2a4d   
   REPLY: 1:220/20 0e171aa1   
   PID: Synchronet 3.20c-Linux master/444fecaf4 Jan 12 2025 GCC 14.2.0   
   TID: SBBSecho 3.23-Linux master/444fecaf4 Jan 12 2025 GCC 14.2.0   
   BBSID: PALANTIR   
   CHRS: CP437 2   
   -=> cr1mson wrote to All <=-   
      
    cr> g00r00-   
      
    cr> Hi, this is cr1mson from Raiders Inc BBS... I've been using Mystic for   
    cr> awhile now.  I've recently been using an RPi 3B+.  I ported Mystic a47   
    cr> over to it and upgraded to the prealpha a49 (32-bit).  I installed the   
    cr> libpython2.7.so.1 and Python 2.7 with a few pip modules.  Trying to run   
    cr> a mod that works fine with a47 and a48, I've run into this warning:   
      
    cr> sys:1: RuntimeWarning: Python C API version mismatch for module   
    cr> mystic_error: This Python has API version 1013, module mystic_error has   
    cr> version 2127954933   
      
    cr> I didn't get this warning in a47 or a48, however, with a48, I couldn't   
    cr> get my Mystic to do successful polls AND use the cl3441 SSH at the same   
    cr> time.  One would work and one would fail, but the mod worked fine, so I   
    cr> upgraded to a49.   
      
    cr> Has anyone else had this warning with threatsentry (python 2.7 mod) or   
    cr> anything like it?  g00r00 if you're listening, please please get an rpi   
    cr> 64-bit out of the prealpha as this might solve my issue.   
      
    cr> Any ideas I could do, g00r00 in the meantime?  I've rebuilt Python 2.7   
    cr> and the lib dev files, put the libpython2.7 in my mystic and specified   
    cr> it in the mystic cfg as well as even installed a brand new mystic a49   
    cr> with just the basics of the libpython, mystic a49 and the mod, but   
    cr> still getting the exact error.   
      
   He's not around, and hasn't been.   
      
   There was much talk a while back about needing to use Python 3.x for    
   more recent Mystic stuff, as I recall.  I also think I remember seeing    
   that doing so broke a lot of other stuff.  So I'm not sure there is a    
   good solution at the moment.   
      
      
      
   ... Behind every great man is an amazed mother-in-law!   
   === MultiMail/Linux v0.52   
   --- SBBSecho 3.23-Linux   
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)   
   SEEN-BY: 1/120 18/0 103/705 104/119 105/81 106/201 116/116 120/616   
   SEEN-BY: 123/0 25 180 525 755 3001 3002 124/5016 128/187 129/215 305   
   SEEN-BY: 135/0 115 205 210 211 212 220 240 363 366 382 385 388 390   
   SEEN-BY: 135/391 153/757 7715 154/10 30 50 110 700 203/0 218/700 220/6   
   SEEN-BY: 220/20 90 221/0 6 222/2 226/18 30 44 50 227/114 229/110 111   
   SEEN-BY: 229/114 206 300 307 310 317 400 426 428 470 550 664 700 705   
   SEEN-BY: 240/1120 5832 250/1 266/512 275/1000 280/464 5003 5006 291/111   
   SEEN-BY: 292/854 8125 301/1 320/219 322/757 341/66 234 342/200 396/45   
   SEEN-BY: 423/120 460/58 467/888 633/267 280 281 384 410 418 420 509   
   SEEN-BY: 633/2744 712/848 1321 770/1 902/26 2320/105 3634/0 12 27   
   SEEN-BY: 3634/56 57 58 60 119 5020/400 5075/35   
   PATH: 135/115 3634/12 154/10 280/464 633/280 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca