} > 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).
} > ... 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. } This bugreport has now a link to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976665 New upstream version 5.0.x available
