<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><p>January 25, 2023 at 9:05 PM, "Dan Smith via chirp_devel" <<a href="mailto:chirp_devel@intrepid.danplanet.com?to=%22Dan%20Smith%20via%20chirp_devel%22%20%3Cchirp_devel%40intrepid.danplanet.com%3E" target="_blank" tabindex="-1">chirp_devel@intrepid.danplanet.com</a>> wrote:</p><blockquote><blockquote><div>Since our (Mageia) most recent python3 updates sometime this month </div><div> chirp-next builds fail with:</div><div> </div><div> packaging.version.InvalidVersion: Invalid version: 'py3dev'</div><div> </div><div> The above exception was the direct cause of the following exception:</div><div> </div><div> Traceback (most recent call last):</div><div> File "/usr/lib/rpm/pythondistdeps.py", line 626, in <module></div><div> raise RuntimeError("Error: pythondistdeps.py generator encountered </div><div> an unhandled exception and was terminated.") from exc</div><div> RuntimeError: Error: pythondistdeps.py generator encountered an </div><div> unhandled exception and was terminated.</div><div> error: Dependency tokens must begin with alpha-numeric, '_' or '/': *** </div><div> PYTHONDISTDEPS_GENERATORS_FAILED ***</div><div> Provides: application() application(chirp.desktop) chirp = </div><div> 1:0.4.0-0.20230101.1.mga</div><div> Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 </div><div> rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 </div><div> rpmlib(PayloadFilesHavePrefix) <= 4.0-1</div><div> Requires: python(abi) = 3.10 python3.10dist(future) </div><div> python3.10dist(pyserial) python3.10dist(requests) python3.10dist(six) </div><div> python3.10dist(yattag)</div><div> </div><div> /--------------------------------------</div></blockquote><div><br></div><div>Since you're seeing py3dev I assume that means you're building directly from git? Why?</div></blockquote><div>I'd like to piggy back on this conversation. Dan, would it be possible to publish a file or set up a redirect for package maintainers to get to the latest release tar ball that is posted on the downloads page? Maybe I've just overlooked it, but I haven't come across anything like that. git seems to be the easiest place to get the latest sources. </div><div><br></div><div>If there was a URL like `<a href="https://trac.chirp.danplanet.com/chirp_next/latest">https://trac.chirp.danplanet.com/chirp_next/latest</a>` which either contained simple text or redirected to "<a href="https://trac.chirp.danplanet.com/chirp_next/next-YYYYMMDD/chirp-next-YYYYMMDD.tar.gz">https://trac.chirp.danplanet.com/chirp_next/next-YYYYMMDD/chirp-next-YYYYMMDD.tar.gz</a>" that would really help out, at least from what I've seen with snap, flatpak and appimage building thus far.</div><div><br></div><div>Tony</div></body></html>