Bug#988716: platformio 4.3.4 cannot download required frameworks
Hi Sebastian (2021.05.18_10:34:31_-0400) > Upstream changed paths for the framework manifest files in recent > releases and did not maintain backward compatibility links resulting > in 4.3.4 no longer being able to install the frameworks. Had a quick look, and it's worse than that. Not just a change in paths, but an entire new package manager, with a new API (/v2/ in the URLs). Changelog: https://github.com/platformio/platformio-core/blob/master/HISTORY.rst#500-2020-09-03 Some relevant history here: https://github.com/platformio/platformio-core/commits/59b02120b648a41965974f27ac0b6c5d44dd11d3/platformio/package/manager/platform.py > This means the package is basically unusable for new installations > Since it did not exist in buster, it is always a new installation > in bullseye. Considering we are in late freeze phase I suggest to > drop the package from Debian testing (and upload a new upstream > release to sid). Sounds like the right call. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Bug#988716: platformio 4.3.4 cannot download required frameworks
Package: platformio Version: 4.3.4-1 Severity: grave Dear Maintainer, Upstream changed paths for the framework manifest files in recent releases and did not maintain backward compatibility links resulting in 4.3.4 no longer being able to install the frameworks. For example this happens when I try to build the arduino-blink hello world program: $ platformio run -e d1_mini Processing d1_mini (platform: espressif8266; framework: arduino; board: d1_mini) PlatformManager: Installing espressif8266 Error: Detected unknown package 'espressif8266' But not even native build is possible: $ platformio platform install native PlatformManager: Installing native Error: Detected unknown package 'native' There does not seem to be a way to get better error messages, but using strace I can say it receives a 404 response for the following query: "GET /platforms/manifest.json". The problem is fixed by updating to latest upstream release [I tested 5.1.1], which has already been requested in #976665. This means the package is basically unusable for new installations Since it did not exist in buster, it is always a new installation in bullseye. Considering we are in late freeze phase I suggest to drop the package from Debian testing (and upload a new upstream release to sid). -- Sebastian
