mbridon commented on issue #1855:
URL: https://github.com/apache/buildstream/issues/1855#issuecomment-1682138375

   > > Ubuntu, Debian, etc... neither have Python 3.12 yet and won't have it 
for a while. Do you want to cut off Buildstream from all of those?
   > 
   > Please no :)
   > 
   > We support python back to the last non EOL version (that is currently 
either 3.7 or 3.8 I believe...).
   > 
   > Do we intend to land this in BuildStream proper or land this in upstream 
versioneer first and then upgrade versioneer again ?
   
   Ah, I didn't know versioneer was imported into Buildstream as a subproject, 
I thought the code lived in Buildstream itself :shrug: 
   
   So I guess the bug report needs to be opeed there then, I'll try to see if 
versioneer itself has the same problem on its own first. :wink: 
    
   > PS: Long time no see Mathieu, hope you're doing well.
   
   Now I am, not sure whether the others told you what happened to me or not?
   
   Long story short, in march 2020 I caught the flu. I didn't know, but turns 
out a *possible* consequence of any flu is always that it attacks your spinal 
chord and nervous system, which is exactly whet happened to me. :disappointed: 
   
   Doctors told me while it's a known possible consequence, it's very serious 
and very rare, hurray for probabilities...
   
   So now I'm in a wheelchair, and I can't trust my body any more as it keeps 
sending me fake news. :facepalm: 
   
   Also I had to change my account as the Github support were unwilling to give 
me back access to `@bochecha` and I had to open a new `@mbridon`... One day 
they'll realise that account has been inactive for years and the only activity 
is them sending emails about long closed issues, costing them money in storage 
and bandwidth :shrug: 
   
   Sorry for plumbing the ambiance :smile: 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to