whitequark[cis] changed the topic of #glasgow to: https://glasgow-embedded.org · digital interface explorer · https://www.crowdsupply.com/1bitsquared/glasgow · meetings Saturday 2200 UTC · code https://github.com/GlasgowEmbedded/glasgow · logs https://libera.irclog.whitequark.org/glasgow · matrix #glasgow-interface-explorer:matrix.org · discord https://1bitsquared.com/pages/chat
notgull has joined #glasgow
redstarcomrade has joined #glasgow
ar-jan has quit [Ping timeout: 256 seconds]
redstarcomrade has quit [Read error: Connection reset by peer]
redstarcomrade has joined #glasgow
redstarcomrade has quit [Changing host]
redstarcomrade has joined #glasgow
nanographs[m] has joined #glasgow
<nanographs[m]> So
<nanographs[m]> ~something~ happened and now I can't run glasgow. We have tried many, many things relating to various python installations and environment paths and are still getting the same thing...
whitequark[cis] has joined #glasgow
<whitequark[cis]> yeah, I deprecated amaranth.vendor.lattice_ice40 upstream in amaranth but it never got fixed
<whitequark[cis]> lemme fix that
<whitequark[cis]> * yeah, I deprecated amaranth.vendor.lattice_ice40 upstream in amaranth but glasgow never got updated
<nanographs[m]> Thanks!
<_whitenotifier-3> [glasgow] whitequark opened pull request #504: Update to Amaranth 0.4 - https://github.com/GlasgowEmbedded/glasgow/pull/504
<whitequark[cis]> now that there's a recent release we should probably stick to the latest released amaranth
<whitequark[cis]> since other than for amaranth, we're following best practices for versioning which should prevent this exact thing from happening
<nanographs[m]> I should be good to pull now?
<whitequark[cis]> when the PR is merged
<_whitenotifier-3> [glasgow] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-504-5ed19170bcf833b5790a0646c90d1fe06e0bc8b2 - https://github.com/GlasgowEmbedded/glasgow
<nanographs[m]> not sure if it matters but it looks like a few checks are unsuccessful
<whitequark[cis]> the 3.13-dev ones?
<whitequark[cis]> it's because we depend on aiohttp (optionally) and the aiohttp people are suuuuper behind on supporting recent python environments
<whitequark[cis]> those packages are actually kind of broken for like 3 python releases already, it was just not the very obvious kind of breakage
<nanographs[m]> ah ic so much fun
<whitequark[cis]> no :(
<whitequark[cis]> it is not much fun :(
<_whitenotifier-3> [GlasgowEmbedded/glasgow] github-merge-queue[bot] pushed 1 commit to main [+0/-0/±3] https://github.com/GlasgowEmbedded/glasgow/compare/5ed19170bcf8...50202b2bf33b
<_whitenotifier-3> [GlasgowEmbedded/glasgow] whitequark 50202b2 - software: update to Amaranth 0.4.
<_whitenotifier-3> [glasgow] whitequark closed pull request #504: Update to Amaranth 0.4 - https://github.com/GlasgowEmbedded/glasgow/pull/504
<_whitenotifier-3> [glasgow] github-merge-queue[bot] deleted branch gh-readonly-queue/main/pr-504-5ed19170bcf833b5790a0646c90d1fe06e0bc8b2 - https://github.com/GlasgowEmbedded/glasgow
<whitequark[cis]> done
<nanographs[m]> again thanks
<whitequark[cis]> np
<nanographs[m]> I was convince I did something terrible to my environment haha
<whitequark[cis]> it's odd we didn't get deprecation warnings earlier
<whitequark[cis]> that's probably a misconfiguration on our (glasgow) side
redstarcomrade has quit [Read error: Connection reset by peer]
joerg has quit [Ping timeout: 256 seconds]
joerg has joined #glasgow
notgull has quit [Ping timeout: 260 seconds]
bvernoux has joined #glasgow
ar-jan has joined #glasgow
Eli2_ has quit [Quit: Ex-Chat]
notgull has joined #glasgow
notgull has quit [Ping timeout: 260 seconds]
cr1901 has quit [Quit: Leaving]
cr1901 has joined #glasgow
<disdi89[m]> thanks for sharing , both from sw and hw side
FFY00 has joined #glasgow
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #glasgow
Eli2 has joined #glasgow
Lord_Nightmare has quit [Quit: ZNC - http://znc.in]
Lord_Nightmare has joined #glasgow
notgull has joined #glasgow
notgull has quit [Ping timeout: 276 seconds]