Colin Tuckley: > On 30/10/15 04:25, Bdale Garbee wrote: > >> The packages in Debian currently reflect the latest upstream release. I >> don't have the time or motivation to package unreleased versions of >> chirp for experimental. > > chirp has moved to rolling releases so the current Debian package is not > the latest release.
Debian has the latest "old stable release" (which is what upstream now calls them, indicating that those releases have ended), which used to be released here: http://chirp.danplanet.com/download/ 0.4.1 is now a year old. Okay... obviously this package needs to change. The new rolling releases are a problem because the only thing I see being released are daily builds which appear to be periodically deleted and which come with the following disclaimer: "The builds here are generated nightly at 4am pacific time from the tip of the CHIRP development tree. They should contain the most up-to-date bugfixes, but they may also contain the most up-to-date bugs. Use the builds here at your own peril! I recommend you join the chirp_users mailing list before/while using these builds so that you have an idea of what's going on with the current development. Thanks, Dan KK7DS" Because the "rolling release" tarballs are being deleted I think the only way forward that makes any sense is to switch the package to track the upstream repository (because otherwise there's no way to verify that the released tarball is intact/correct), which looks like it's in mercurial: http://chirp.danplanet.com/projects/chirp/repository I haven't yet been able to find a link to actually be able to clone this repository though. If someone finds it, please ping the bug and the [debian-hams] list. I've also had a look at the Ubuntu PPC, which names the package "chirp-daily" among a list of other issues -- these packages are definitely not releasable to Debian as-is, nor do they appear to help with the Debian packaging work. -- Chris -- Chris Knadle chris.kna...@coredump.us
